Axis order of response coordinates does not follow the requested CRS axis order

[komima]

Axis order of response coordinates does not follow the requested CRS axis order

[jampukka]

Thanks for raising the issue. We should move towards a model where hakunapi internally always forces XY-order and let both input and output formats act accordingly.

Something to discuss: should we use external information on the axis order of a certain CRS (for example geotools epsg-hsql) or require configuration for each crs (with sensible/configurable default)? We already do require users to configure available CRSes.

[jratike80]

Maybe JSON-FG makes this issue outdated, and GeoJSON gets reserved for CRS:84 while for any other crs the output should use JSON-FG. Who knows. The specification is not accepted yet, but GDAL-dev has a new driver for JSON-FG that can be used as reference implementation https://gdal.org/drivers/vector/jsonfg.html.

[jratike80]

I do not know how this hakunapi service is configured, but it does return the coordinates in northing-easting order for the Finnish GK zones.
https://avoin-paikkatieto.maanmittauslaitos.fi/kiinteisto-avoin/simple-features/v3/collections/PalstanSijaintitiedot/items?crs=http://www.opengis.net/def/crs/EPSG/0/3878

The service requires an API key, but anybody can get such from https://omatili.maanmittauslaitos.fi/user/new/avoimet-rajapintapalvelut?lang=en.

[jampukka]

#55 should fix this issue and is included in version 1.1.0