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
<CoverageDescriptionSnip>
...
<wcs:GridCRS>
<wcs:GridBaseCRS>urn:ogc:def:crs:EPSG::4326</wcs:GridBaseCRS
<wcs:GridType>urn:ogc:def:method:WCS:1.1:2dGridIn2dCrs</wcs:GridType>
<wcs:GridOrigin>-130.81666154628687 54.08616613712375</wcs:GridOrigin>
<wcs:GridOffsets>0.07003690742624616 0.0 0.0
-0.05586772575250837</wcs:GridOffsets>
<wcs:GridCS>urn:ogc:def:cs:OGC:0.0:Grid2dSquareCS</wcs:GridCS>
</wcs:GridCRS>
...
</CoverageDescriptionSnip>
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
