[Geoserver-devel] [JIRA] (GEOS-9302) WFS axis order inconsistency between Geoserver's documentation and implementation

[Robin Houtmeyers (JIRA)]

Title: Message Title

Robin Houtmeyers created an issue   GeoServer / GEOS-9302 WFS axis order inconsistency between Geoserver's documentation and implementation Issue Type: Bug Affects Versions: 2.15.2 Assignee: Unassigned Components: Documentation, WFS Created: 06/Aug/19 6:21 PM Priority: Medium Reporter: Robin Houtmeyers According to the axis ordering section in the documentation page https://docs.geoserver.org/latest/en/user/services/wfs/basics.html#wfs-basics-axis, the following assumptions are used: EPSG:xxxx => longitude/latitude (x/y) http://www.opengis.net/gml/srs/epsg.xml#xxxx => longitude/latitude (x/y) urn:x-ogc:def:crs:EPSG:xxxx => latitude/longitude (y/x) In practice, this doesn't hold for EPSG:xxxx. Try for instance the following request for the default sample data tiger:poi: http://demo.luciad.com/geoserver/ows?SERVICE=WFS&TYPENAMES=tiger:poi&VERSION=1.1.0&REQUEST=GetFeature The result is latitude/longitude. Although this is correct according to the EPSG database, it does conflict with the documentation; I assume the latter should be updated? Note: to test this, you have to adjust the WFS service to let it use the EPSG notation; by default, the URN notation is used. Add Comment   Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107-sha1:a6aabc9)

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel