|
|
Aaron Sedgmen created an issue |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.18.1, 2.19.0 |
|
Assignee: |
Unassigned |
|
Components: |
Application schema |
|
Created: |
04/May/21 1:34 AM |
|
Environment: |
Tested with GeoServer 2.18.1, GeoServer 2.19.0, postgres/postgis and Oracle operating on Ubuntu 18.04.1 and Windows 10. |
|
Priority: |
|
|
Reporter: |
Low|
I have an app-schema WFS with a feature type containing a 3D LineString geometry. The axis order of the x,y coordinates is inconsistent in the json output, i.e. some features are returned with latitude first and longitude second and others the reverse. The gml32 output is ok, i.e. axis order is the same for all features. Following are two example features from a GeoSciML Boreholes app-schema WFS running on a test server that illustrate the issue. The “shape” property contains the LineString geometry: lat/lon (y,x) axis order - https://boreholes.gs.cloud.ga.gov.au/wfs?service=WFS&version=1.1.0&request=GetFeature&typeName=gsmlbh:Borehole&outputFormat=json&featureid=ga.borehole.466607 lon/lat (x,y) axis order - https://boreholes.gs.cloud.ga.gov.au/wfs?service=WFS&version=1.1.0&request=GetFeature&typeName=gsmlbh:Borehole&outputFormat=json&featureid=ga.borehole.10093 The examples are from a GeoServer 2.18.1 and postgres/postgis installation. GeoServer 2.19.0 accessing an Oracle database gives the same results. There are no differences in geometry type, srid and ordering of the coordinates in the database geometries (both postgis and Oracle) where axis order differs in the WFS json output. |
|
|
|
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#100157-sha1:e888363) |
|
|
|
