Timeline for How do I specify the lon,lat ordering in CSW bounding box request?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 1, 2014 at 21:49 | comment | added | user30184 | Coincidentally this fresh and long thread on SpatiaLite forum is about axis order groups.google.com/forum/#!topic/spatialite-users/rhHRB8MhhUE | |
| Dec 1, 2014 at 21:22 | comment | added | Rich Signell | The GML 3.1.1 document doesn't appear to add insight here. It just says "Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions." I think the key thing is that the order of the coordinates in the bounding box specification is supposed to follow the CRS. But in practice, it seems that many of the CSW services I am trying to query are just assuming (lon,lat) ordering and ignoring the CRS specification. So is there a specification of EPSG that specifies (lon,lat) ordering? If there was I could cover these sins... | |
| Dec 1, 2014 at 21:14 | comment | added | user30184 | So you take this seriously. That's good but for example GML 3.2.1 standard is 437 pages. If you build your filter in GML 3.1.1 and give srsName as "urn:x-ogc:def:crs:EPSG:6.11:4326" then lat,lon is for sure right. Only hope that the CSW server understands the urn-style srsName. Probably it does. | |
| Dec 1, 2014 at 20:57 | comment | added | Rich Signell | So this document? portal.opengeospatial.org/files/?artifact_id=4700 | |
| Dec 1, 2014 at 20:55 | comment | added | tomkralidis | @RichSignell CSW uses GML 3.1.1. | |
| Dec 1, 2014 at 20:54 | comment | added | Rich Signell | @user30184, do you know which of the many OGC GML standard docs would be the "right version", in this case? | |
| Dec 1, 2014 at 20:47 | comment | added | Ian Turton | Surely the spec is authorative | |
| Dec 1, 2014 at 20:39 | comment | added | user30184 | I think that this is authoritative portal.opengeospatial.org/files/?artifact_id=20555. OGC standards are not very easy to interpret. Your both examples are using "QueryConstraintType" of "ogc:Filter" and especially "version" 1.1.0 which means that for finding the correct syntax next step is to go to feature encoding standard v. 1.1.0 portal.opengeospatial.org/files/?artifact_id=51130. That tells that BBOX is "a very common bounding box constraint based on the gml:Envelope geometry". So finally take a right version of GML standard from opengeospatial.org/standards/gml. | |
| Dec 1, 2014 at 20:26 | comment | added | Rich Signell |
So if I want to ensure (lat,lon) order, I could specify: <gml:Envelope srsName="urn:x-ogc:def:crs:EPSG:6.11:4326"> Is that right?
|
|
| Dec 1, 2014 at 20:09 | history | answered | tomkralidis | CC BY-SA 3.0 |