Just van den Broecke

In a recent project starting to use MP with Mapnik and ran into performance issues when serving tiles. Direct Mapnik `render_tile.py` without MP btw was also fast, multiple tiles, keeping...

Yes, I see/understand @ArneBab. Been using the `mapnik.py` version from this PR for months now. The locking problems I found seemed had to do with the complexity (many layers) of...

Suggestion: maybe it is possible to support both `srs`-assignment syntaxes? Maybe on Mapnik version-check or sometimes from an Exception, like we do for `lxml`?

The above temp-fix by @xmnlab works for me (`django-user-accounts 2.0.3`).

Hi all, I'd like to contribute code to pygeoapi. I confirm that my contributions to pygeoapi will be compatible with the pygeoapi license guidelines at the time of contribution. Just...

My $2ct: The "id thing" requires some thinking-through: it needs to be unique within a `Collection` on one hand, so IMHO cannot be enforced on the client (think of multiple...

btw The [STAC Pilot Transaction spec](https://github.com/radiantearth/stac-spec/tree/master/api-spec/extensions/transaction) (to which [OAPIF refers](https://github.com/opengeospatial/WFS_FES/issues/140), see above) is IMHO not really clear on this: one `POST`s an Item to a `Collection` and probably if the...

`POST /collections/{collectionID}/items` with a body of `Item` or even `FeatureCollection` (have seen latter somewhere, MapFish API?). `Item` already has an `id`-field (cannot find back if `id` is indeed mandatory, seems...

@francbartoli thanks, yes `PATCH` for partial updates (except for `id` itself IMHO) should be considered.

I can only comment on this: Note: adding '&f=json' causes it to work correctly. As far as I'm aware this should not be required, as it should default to json....