Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Reccomendations/guidelines for axis order? #321

Open
aaime opened this issue Jan 22, 2020 · 1 comment
Open

Reccomendations/guidelines for axis order? #321

aaime opened this issue Jan 22, 2020 · 1 comment

Comments

@aaime
Copy link
Contributor

aaime commented Jan 22, 2020

Should the specification give recommendations on axis order, while leaving implementers free to use the axis order they prefer?
Would the order have to be fixed, so that all outputs requested in, say, "http://www.opengis.net/def/crs/EPSG/0/4269" (NAD83), share the same order (ask the same, get the same)?
However, by experience, the "useful" axis order is linked to the chosen output format, shapefiles hardly work in practice when returned in north/east order for example.

@cportele
Copy link
Member

In general, the axis order is fixed by the CRS definition. Where necessary, a conformance class for an encoding can state different rules based on the practices of the encoding.

So, for the GeoJSON and GML conformance classes the CRS definition applies.

For a shapefile extension, one could specify a different rule for the axis order.

This would also apply in the other case. Say, we have a format the requires latitude/longitude. An extension for that encoding would have to specify that the response uses lat/long even for CRS84.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants