[Geoserver-devel] [jira] (GEOS-6635) WCS GridOffsets GridOrigin axis ordering does not match GridBaseCRS

_Failed_to_Retrieve · August 28, 2014, 2:13pm

Tim Astle created an issue

WCS GridOffsets GridOrigin axis ordering does not match GridBaseCRS

Issue Type:	Bug
Affects Versions:	2.5.2
Assignee:	Andrea Aime
Components:	WCS
Created:	28/Aug/14 9:12 AM
Priority:	Major
Reporter:	Tim Astle

This request:

/geoserver/ows?service=wcs&amp;version=1.1.1&amp;request=DescribeCoverage&amp;identifiers=Img_Sample

Returns a CoverageDescription with the following Grid definition:

&lt;CoverageDescriptionSnip&gt;
...
&lt;wcs:GridCRS&gt;
  &lt;wcs:GridBaseCRS&gt;urn:ogc:def:crs:EPSG::4326&lt;/wcs:GridBaseCRS
  &lt;wcs:GridType&gt;urn:ogc:def:method:WCS:1.1:2dGridIn2dCrs&lt;/wcs:GridType&gt;
  &lt;wcs:GridOrigin&gt;-130.81666154628687 54.08616613712375&lt;/wcs:GridOrigin&gt;
  &lt;wcs:GridOffsets&gt;0.07003690742624616 0.0 0.0 -0.05586772575250837&lt;/wcs:GridOffsets&gt;
  &lt;wcs:GridCS&gt;urn:ogc:def:cs:OGC:0.0:Grid2dSquareCS&lt;/wcs:GridCS&gt;
&lt;/wcs:GridCRS&gt;
...
&lt;/CoverageDescriptionSnip&gt;

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.

Add Comment

This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)