Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong axis order on GetRecords for 4326 #337

Open
gcampanile opened this issue Oct 26, 2021 · 0 comments
Open

Wrong axis order on GetRecords for 4326 #337

gcampanile opened this issue Oct 26, 2021 · 0 comments

Comments

@gcampanile
Copy link
Contributor

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:

<csw:GetRecords maxRecords="10" outputFormat="application/xml" 
outputSchema="http://www.opengis.net/cat/csw/2.0.2" resultType="results" 
service="CSW" version="2.0.2" 
xmlns:csw="http://www.opengis.net/cat/csw/2.0.2" 
xmlns:gml="http://www.opengis.net/gml" 
xmlns:ogc="http://www.opengis.net/ogc" 
xmlns:ows="http://www.opengis.net/ows" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.opengis.net/cat/csw/2.0.2 
http://schemas.opengis.net/csw/2.0.2/CSW-discovery.xsd">
     <csw:Query typeNames="csw:Record">
         <csw:ElementSetName>full</csw:ElementSetName>
         <csw:Constraint version="1.1.0">
             <ogc:Filter>
                 <ogc:BBOX>
                     <ogc:PropertyName>ows:BoundingBox</ogc:PropertyName>
                     <gml:Envelope srsName="urn:ogc:def:crs:EPSG::4326">
                         <gml:lowerCorner>39.725753 16.957494</gml:lowerCorner>
                         <gml:upperCorner>40.863650 18.816817</gml:upperCorner>
                     </gml:Envelope>
                 </ogc:BBOX>
             </ogc:Filter>
         </csw:Constraint>
     </csw:Query>
</csw:GetRecords>

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant