search

opengeospatial / ets-ogcapi-features10

Public Repository for the OGC API - Features Compliance Test Suite
Other
16 stars 6 forks source link

Fix Axis Order Handling #167

Closed lgoltz closed 3 years ago

lgoltz commented 3 years ago

https://github.com/opengeospatial/ets-ogcapi-features10/issues/160#issuecomment-867024137

lgoltz commented 3 years ago

Proj4 does not specify the axis order, so all crs in https://github.com/locationtech/proj4j/blob/master/src/main/resources/proj4/nad/epsg are specified without explicit declaration of the axis order (except some CRSwith axis order +axis=wsu). This means "+axis=enu", lon/lat.

Axis order was corrected: https://github.com/opengeospatial/ets-ogcapi-features10/commit/07d63adc84ebe2f54d2f463028a70e1802f47d5f

lgoltz commented 3 years ago

The title of "Example 4. HTTP header declaring the CRS and axis order used in the body of the response" in https://docs.opengeospatial.org/is/18-058/18-058.html#_coordinate_reference_system_information_independent_of_the_feature_encoding is a bit confusing. As far as I see and axis order should be removed.