[gdal-dev] WCS driver

[Ari Jolma]

Ari Jolma kirjoitti 27.10.2017 klo 19:38:
>
>
> * I'm testing against existing ArcGIS, GeoServer and MapServer servers 
> on the net

Version 1.0.0 seems to be usually understandable/ok but strangeness 
begins with 1.1

For example this request to a MapServer WCS (I'm not responsible for 
that server so don't know much about it), which is generated in the 
driver during a DescribeCoverage for the coverage,

http://194.66.252.155/cgi-bin/BGS_EMODnet_bathymetry/ows?SERVICE=WCS&VERSION=1.1.1&REQUEST=GetCoverage&IDENTIFIER=BGS_EMODNET_CentralMed-MCol&FORMAT=image%2Ftiff&BOUNDINGBOX=9.833333335,46.183333325,9.837500005,46.187499995,urn:ogc:def:crs:EPSG::4326&RangeSubset=band

gets the response

WCS server error. Requested BBOX 
(46.183333325,9.833333335,46.187499995,9.837500005) is outside requested 
coverage BBOX (9.83125,30.01040372,22.23542659,46.18958333)

If I change the order of X and Y in the bounding box in the request, the 
reply is ok. I'm thinking MapServer is in error here, for example 
similar request to ArcGIS WCS server

http://paikkatieto.ymparisto.fi/arcgis/services/Testit/Velmu_wcs_testi/MapServer/WCSServer?SERVICE=WCS&VERSION=1.1.2&REQUEST=GetCoverage&IDENTIFIER=1&FORMAT=image%2FGeoTIFF&BOUNDINGBOX=61686.0383772501,7302181.14320843,61706.0383772501,7302201.14320843,urn:ogc:def:crs:EPSG::3067&RangeSubset=Field_1

gets an ok response.

The case of GeoServer is also strange

https://msp.smartsea.fmi.fi/geoserver/wcs?SERVICE=WCS&VERSION=1.1.1&REQUEST=GetCoverage&IDENTIFIER=smartsea%3Aeusm2016&FORMAT=image%2Ftiff&BOUNDINGBOX=61610,7303970,61630,7303990,urn:ogc:def:crs:EPSG::3067&RangeSubset=contents

-- GeoServer does not seem to understand that GDAL wants only a 2 x 2 
sample - the response is huge (the whole geotiff?).

Ari