Thanks for the reply Jonathan.
I’m not sure if I follow your point, or maybe I didn’t do a good job explaining what I’m seeing.
Why wouldn’t the GridOrigin and GridOffsets not be in axis ordering of the coordinate system which defines the grid? Else there would be no way in ever knowing the order of the coordinates. The specification seems really clear about that. On a general note, the schemas have element definitions for ordering depending on the element used, such as the wgs84BoundingBox you cited, but that doesn’t apply in this case.
This is what I’d expect to see:
i.e., Lat / Lon (taken from Img_Sample)
…
wcs:GridCRS
wcs:GridBaseCRSurn:ogc:def:crs:EPSG::4326</wcs:GridBaseCRS
wcs:GridTypeurn:ogc:def:method:WCS:1.1:2dGridIn2dCrs</wcs:GridType>
wcs:GridOrigin-130.81666154628687 54.08616613712375</wcs:GridOrigin>
wcs:GridOffsets0.07003690742624616 0.0 0.0 -0.05586772575250837</wcs:GridOffsets>
wcs:GridCSurn:ogc:def:cs:OGC:0.0:Grid2dSquareCS</wcs:GridCS>
</wcs:GridCRS>
…
i.e., X, Y (something I hacked together in this email as an example)
…
wcs:GridCRS
wcs:GridBaseCRSurn:ogc:def:crs:EPSG::2036</wcs:GridBaseCRS
wcs:GridTypeurn:ogc:def:method:WCS:1.1:2dGridIn2dCrs</wcs:GridType>
wcs:GridOrigin2297561 7678078</wcs:GridOrigin>
wcs:GridOffsets0.5 0.0 0.0 -0.5</wcs:GridOffsets>
wcs:GridCSurn:ogc:def:cs:OGC:0.0:Grid2dSquareCS</wcs:GridCS>
</wcs:GridCRS>
…
So from what I can tell, it appears that this is a bug.
I’ve created GEOS-6635 describing this.
Thanks again for your reply,
Tim
···
On 29/08/2014 4:55 AM, Jonathan Moules wrote:
Hi Tim,
I’m not that well versed in WCS, but taking a gander at the spec, to me at least it’s non-obvious which order is “right”.
On your noted page 89 it says lat/lon is correct for gml:GeographicCRS, but for wgs84BoundingBox it’s lon/lat (page 18).
The examples on later pages (90 and 91) also seem to indicate lat/lon for GridOffsets, although that’s using EPSG:63266405.
So it may be worth double-checking the EPSG and choosing a flavour that allows lat/lon or lon/lat as desired.
Cheers,
Jonathan
On 27 August 2014 19:42, Timothy Astle <timothy.astle@anonymised.com> wrote:
Hi all,
I’m wondering if anyone noticed what I believe I’m seeing. I am using the sample data provided with GeoServer 2.5.2.
/geoserver/ows?service=wcs&version=1.1.1&request=DescribeCoverage&identifiers=Img_Sample
...
urn:ogc:def:crs:EPSG::4326</wcs:GridBaseCRS
urn:ogc:def:method:WCS:1.1:2dGridIn2dCrs
-130.81666154628687 54.08616613712375
0.07003690742624616 0.0 0.0 -0.05586772575250837
urn:ogc:def:cs:OGC:0.0:Grid2dSquareCS
...
The GridOrigin and GridOffsets are in long/lat ordering, not lat/long.
I double-checked the WCS 1.1 spec, and on page 89, it states that the GridOrigin and GridOffsets are in the GridBaseCRS. Based on what I’m seeing, it looks like the GridOrigin and GridOffsets values are flipped.
The inverted values seem to be tripping up GDAL as a WCS client.
Any thoughts?
–
Tim Astle
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
This transmission is intended for the named addressee(s) only and may contain confidential, sensitive or personal information and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
–
Tim Astle
Development Manager
Web Technologies
CARIS
115 Waggoners Lane
Fredericton, New Brunswick
Canada E3B 2L4
Tel: +1.506.458.8533 Fax: +1.506.459.3849
www.caris.com
Connect with CARIS
Twitter | LinkedIn | Facebook | Google+ | YouTube
Download your free copy of CARIS Easy View today!
www.caris.com/easyview
This email and any files transmitted with it are confidential and intended only for the addressee(s). If you are not the intended recipient(s) please notify us by email reply. You should not use, disclose, distribute or copy this communication if received in error.
Any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of the company. No binding contract will result from this email until such time as a written document is signed on behalf of the company.