You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SRS requested is urn:ogc:def:crs:EPSG::4326 which requires lat/lon ordering, as showed in the example, but the GPT ignores the SRS request and uses always long/lat. In the OGC documentation (OGC_API_-_Common.pdf pg. 40 and 06-121r9_OGC_Web_Services_Common_Standard.pdf pag. 58) is stated that coordinateordering depends on the SRS.
To solve this problem the java function to modify is com/esri/gpt/server/csw/provider/local/QueryFilterParser.java
Gianni
The text was updated successfully, but these errors were encountered:
HI,
I think that the axis order on a GetRecords request is wrong when the request is for a SRS that uses lat/lon instead of lon/lat.
For example:
The SRS requested is urn:ogc:def:crs:EPSG::4326 which requires lat/lon ordering, as showed in the example, but the GPT ignores the SRS request and uses always long/lat. In the OGC documentation (OGC_API_-_Common.pdf pg. 40 and 06-121r9_OGC_Web_Services_Common_Standard.pdf pag. 58) is stated that coordinateordering depends on the SRS.
To solve this problem the java function to modify is com/esri/gpt/server/csw/provider/local/QueryFilterParser.java
Gianni
The text was updated successfully, but these errors were encountered: