[gdal-dev] Issue with GDAL WCS 1.1.x request

[Peter Baumann]

Hi Robert, Jukka,

FWIW, WCS 1.x is deprecated and superseded by WCS 2.0 (for which GeoServer 
recently has added support, too, following MapServer and others).

-Peter


On 02/13/2013 10:59 AM, Robert Kulawik wrote:
> Thank you Jukka,
>
> has someone from the GDAL guys a solution or idea to get a correct WCS
> 1.1.x response with GDAL? Nobody use this?
>
> Thanks in advance
> Robert
>
> Am 08.02.2013 18:25, schrieb Jukka Rahkonen:
>> Robert Kulawik <rob-news <at> gmx.de> writes:
>>
>>> Hi List,
>>>
>>> i try to request my Geoserver WCS (GS version 2.2.x, request 1.1.x) with
>>> GDAL 1.9.1.
>>>
>>> Here is the coverage description from Geoserver:
>>>
>> http://193.175.162.189/geoserver/wcs?request=DescribeCoverage&identifiers=raster_example_20130208_113005_078&VERSION=1.1.0
>> http://193.175.162.189/geoserver/wcs?request=DescribeCoverage&identifiers=raster_example_20130208_113005_078&VERSION=1.1.1
>>> When i specify the version in the GDAL request, e.g.
>>> <WCS_GDAL>
>>> <ServiceURL>http://193.175.162.189/geoserver/wcs?</ServiceURL>
>>> <CoverageName>raster_example_20130208_113005_078</CoverageName>
>>> <Version>1.1.0</Version>
>>> </WCS_GDAL>
>>>
>>> i get the response:
>>> C:\OSGeo4W\bin>gdalinfo wcs.xml
>>> ERROR 1: java.lang.IllegalArgumentException: The specified dimensional
>>> parameter is non-positive.
>>> The specified dimensional parameter is non-positive.
>>> gdalinfo failed - unable to open 'wcs.xml'.
>>>
>>> I asked this with a other background in the Geoserver-user list:
>>>
>> http://osgeo-org.1560.n6.nabble.com/Issue-with-noValue-in-WCS-coverageOfferings-tp5033051.html
>>> and it seems, GDAL does not consider the axis swiching in WCS 1.1.x
>>> It is possible to specify (or add) the axis order in the GDAL request?
>>>
>>> Has someone a solution or a idea for this?
>>> Thanks in advance
>>> Robert
>> I tried to investigate this case a bit on the Geoserver user list. The java
>> illegal argument error comes from Geoserver and because GDAL is sending BBOX
>> coordinates in lat-lon order.
>> This is captured from the GetCoverage request that was sent by gdalinfo
>> BOUNDINGBOX=-116.917,32.41666843,-116.75033333,32.5833351,
>> urn:ogc:def:crs:EPSG::4326
>>
>> However, I feel it may be because a bit earlier the same Geoserver has
>> responded to DescribeCoverage request that was sent by GDAL as
>> <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>-116.91699999999997 32.5833351</wcs:GridOrigin>
>> <wcs:GridOffsets>0.16666667 0.0 0.0 -0.16666667</wcs:GridOffsets>
>> <wcs:GridCS>urn:ogc:def:cs:OGC:0.0:Grid2dSquareCS
>> </wcs:GridCS></wcs:GridCRS>
>>
>> Does gdalinfo build the little GetCoverage request it is sending based on the
>> GridOrigin metadata it has queried from WCS server? And is this case the real
>> reason for the trouble caused by the wrong GridOrigin and GridOffsets metadata?
>>
>> -Jukka Rahkonen-
>>
>>
>>
>>
>>
>> _______________________________________________
>> gdal-dev mailing list
>> gdal-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev

-- 
Dr. Peter Baumann
  - Professor of Computer Science, Jacobs University Bremen
    www.faculty.jacobs-university.de/pbaumann
    mail: p.baumann at jacobs-university.de
    tel: +49-421-200-3178, fax: +49-421-200-493178
  - Executive Director, rasdaman GmbH Bremen (HRB 26793)
    www.rasdaman.com, mail: baumann at rasdaman.com
    tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
"Si forte in alienas manus oberraverit hec peregrina epistola incertis ventis dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata, nec preripiat quisquam non sibi parata." (mail disclaimer, AD 1083)