Opened 13 years ago

#2940 new defect

WCS 1.1.0 and axis ordering

Reported by: rouault Owned by: sdlime
Priority: normal Milestone:
Component: WCS Server Version: 5.2
Severity: normal Keywords:
Cc: tomkralidis, warmerdam

Description

I think there might be a issue with the axis ordering of the <GridOrigin?> and <GridOffsets?> elements inside the <GridCRS> element returned by a DescribeCoverage? request.

See the following output :

    <Domain>
      <SpatialDomain>
        <ows:BoundingBox crs="urn:ogc:def:crs:OGC::imageCRS" dimensions="2">
          <ows:LowerCorner>0 0</ows:LowerCorner>
          <ows:UpperCorner>21599 21599</ows:UpperCorner>
        </ows:BoundingBox>
        <ows:BoundingBox crs="urn:ogc:def:crs:EPSG::4326" dimensions="2">
          <ows:LowerCorner>3.47733758454538e-10 -180.000000000333</ows:LowerCorner>
          <ows:UpperCorner>90.0000000003333 -90.0000000003477</ows:UpperCorner>
        </ows:BoundingBox>
        <ows:WGS84BoundingBox dimensions="2">
          <ows:LowerCorner>-180.000000000333 3.47733758454538e-10</ows:LowerCorner>
          <ows:UpperCorner>-90.0000000003477 90.0000000003333</ows:UpperCorner>
        </ows:WGS84BoundingBox>
        <GridCRS>
          <GridBaseCRS>urn:ogc:def:crs:EPSG::4326</GridBaseCRS>
          <GridType>urn:ogc:def:method:WCS:1.1:2dSimpleGrid</GridType>
          <GridOrigin>-179.997916667 89.997916667</GridOrigin>
          <GridOffsets>0.004166666666666 -0.004166666666666</GridOffsets>
          <GridCS>urn:ogc:def:cs:OGC:0.0:Grid2dSquareCS</GridCS>
        </GridCRS>
      </SpatialDomain>
    </Domain>

The ordering in ows:BoundingBox looks right (lat, long), but not in GridCRS (long, lat). (The WGS84BoundingBox is in (long, lat) order, but it is OK I imagine as it's not using urn:ogc:def:crs:EPSG::4326 ?)

Change History (0)

Note: See TracTickets for help on using tickets.