Robert Coup

I presume there's a reason, but why comma-separate attributes when repeating querystring/post parameters is perfectly find under HTTP? Another concept I've seen a few places (Django uses): * `&sortby=attr` =>...

See also discussion on #67. ElasticSearch also has a query syntax worth reviewing

(Because I had to go look it up, the `info:` block comes [from OpenAPI (spec)](https://swagger.io/specification/#infoObject)) > Many clients will not be capable to follow links from capabilities to metadata and...

> @cholmes said: > I wonder if there's a way to do this that's more compatible with web architectures? > I'm not sure of the exact mechanism, but something with...

@cholmes is this the same issue discussed at https://github.com/opengeospatial/WFS_FES/issues/16 but just asking for `fields=id`? (ie. excluding all the other fields)

> To fix that we could reverse that decision and start adding envelopes to our stored geometries. cc @rcoup isn't that in the v2 spec? Haven't decided on a format.

Looks like Click already [has a solution for this](https://click.palletsprojects.com/en/7.x/utils/#pager-support) (and further down the same page, ["Launching Editors"](https://click.palletsprojects.com/en/7.x/utils/#launching-editors)) 👏 We should start by trying that out

Relevant... * https://github.com/OSGeo/gdal/issues/3174: ogr2ogr: definition is not compatible with the official definition (export from PostGIS) * https://github.com/OSGeo/gdal/issues/3177: PostGIS: on reading, instanciate SRS from EPSG when possible instead of srtext to...

Yeah, I think an optional argument that we make required for TAB/CSV/whatever would be fine.

Yes. The Makefile stuff is a messy pile of hacks already, I'm tempted to punt this until after we switch fully to CMake, in which case it'll be much saner...