Dieter Stüken ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=6048e1a1ceccdd006a25ea04
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiMmU0M2FkYWFlNDEyNDBkM2JjMTBlZTkyZmVhMzRlMDYiLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-11039?atlOrigin=eyJpIjoiMmU0M2FkYWFlNDEyNDBkM2JjMTBlZTkyZmVhMzRlMDYiLCJwIjoiaiJ9
 ) GEOS-11039 ( 
https://osgeo-org.atlassian.net/browse/GEOS-11039?atlOrigin=eyJpIjoiMmU0M2FkYWFlNDEyNDBkM2JjMTBlZTkyZmVhMzRlMDYiLCJwIjoiaiJ9
 ) WFS Axis Order with JSON output ( 
https://osgeo-org.atlassian.net/browse/GEOS-11039?atlOrigin=eyJpIjoiMmU0M2FkYWFlNDEyNDBkM2JjMTBlZTkyZmVhMzRlMDYiLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.22.3 Assignee: Unassigned Components: WFS 
Created: 21/Jun/23 4:58 PM Priority: Medium Reporter: Dieter Stüken ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=6048e1a1ceccdd006a25ea04
 )

I observed an unexpected axis order for a WFS getFeature request when using 
outputFormat=application/json. The CRS is shown as urn:ogc:def:crs:EPSG::4326.

After reading about Axis ordering ( 
https://docs.geoserver.org/latest/en/user/services/wfs/axis_order.html ) , I 
noticed the axis order shall be different for version=1.0.0 and version=2.0.0. 
I traced it down to: jsonWriter.setAxisOrder() ( 
https://github.com/geoserver/geoserver/blob/7636c1dccc9331b8c6e8a7e660602b066b519001/src/wfs/src/main/java/org/geoserver/wfs/json/GeoJSONGetFeatureResponse.java#L407
 ) which is called with different (and correct) AxisOrder. This is even 
respected on GeoJSONBuilder.writeCoordinate(x,y) ( 
https://github.com/geoserver/geoserver/blob/7636c1dccc9331b8c6e8a7e660602b066b519001/src/wfs/src/main/java/org/geoserver/wfs/json/GeoJSONBuilder.java#L176
 ).

Unfortunately the coordinates are already swapped at this point and the given 
AxisOrder gets canceled again.

So I guess this is a bug.

With XML the output is fine.

( 
https://osgeo-org.atlassian.net/browse/GEOS-11039#add-comment?atlOrigin=eyJpIjoiMmU0M2FkYWFlNDEyNDBkM2JjMTBlZTkyZmVhMzRlMDYiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-11039#add-comment?atlOrigin=eyJpIjoiMmU0M2FkYWFlNDEyNDBkM2JjMTBlZTkyZmVhMzRlMDYiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100227- 
sha1:28a616e )
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to