[mapserver-users] Re: WCS Geotiff output issue

[Rahkonen Jukka]

Hi,

See examples in http://www.mapserver.org/ogc/wcs_server.html and try to avoid mixing versions 1.0.0 and 1.1.0. Let's hope using "coverage" instead of "identifier" will be enough.

-Jukka Rahkonen-
________________________________
Lähettäjä: mapserver-users-bounces at lists.osgeo.org [mapserver-users-bounces at lists.osgeo.org] käyttäjän Guillaume Loiselle [loiselle.guillaume at gmail.com] puolesta
Lähetetty: 7. marraskuuta 2011 21:21
Vastaanottaja: mapserver-users at lists.osgeo.org
Aihe: [mapserver-users] Re: WCS Geotiff output issue

Hi,

For some reason, the text part of the email didn't make it. It can be read below.
Attachments can still be found in the first message :
http://lists.osgeo.org/pipermail/mapserver-users/2011-November/070670.html

Thanks.
Guillaume Loiselle


2011/11/4 Guillaume Loiselle <loiselle.guillaume at gmail.com<mailto:loiselle.guillaume at gmail.com>>
Hi,

I installed MapServer 6.0.1 on Windows XP from MS4W. I cannot give you access to my MapServer instance but I can show you what "-v" gives me :

MapServer version 6.0.1 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PR
OJ SUPPORTS=AGG SUPPORTS=CAIRO SUPPORTS=FREETYPE SUPPORTS=ICONV SUPPORTS=FRIBIDI
 SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT
 SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI SUPPORTS=THREADS SUPPO
RTS=GEOS INPUT=JPEG INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE

I am able to generate a GeoTiff file through the use of a WMS service (see attachment : wmsoutput.tif). The request is :

http://localhost/cgi-bin/mapserv.exe?SERVICE=WMS&map=D:/Guillaume/ProjetCourantsGlaces/WCSproblem/2011102811.map&LAYERS=thelayer&VERSION=1.1.1&REQUEST=GetMap&bbox=-67.5,48.922499263758255,-64.6875,50.736455137010665&SRS=EPSG:4326&WIDTH=256&HEIGHT=256&FORMAT=GTiff

However, I cannot do so with a WCS service. I first tried with :

http://localhost/cgi-bin/mapserv.exe?SERVICE=WCS&map=D:/Guillaume/ProjetCourantsGlaces/WCSproblem/2011102811.map&IDENTIFIER=thelayer&VERSION=1.0.0&REQUEST=GetCoverage&BBOX=-67.5,48.922499263758255,-64.6875,50.736455137010665&CRS=EPSG:4326&WIDTH=256&HEIGHT=256&FORMAT=GTiff

, to which I can add :

&RESPONSE_CRS=EPSG:4326

for the same result (since 4326 is my native projection). Said result is not a tiff file, but an error :

<?xml version='1.0' encoding="ISO-8859-1" ?>
<ServiceExceptionReport version="1.2.0"
xmlns="http://www.opengis.net/ogc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/ogc http://schemas.opengis.net/wcs/1.0.0/OGC-exception.xsd">
  <ServiceException code="NoApplicableCode" locator="bbox">msWCSGetCoverage(): WCS server error. Requested BBOX (-178.835708198757,2803.05273104522,179.552848002437,2906.98474680556) is outside requested coverage BBOX (-70,45,-55,52)
  </ServiceException>
</ServiceExceptionReport>

This error doesn't make sense to me. Which projection is it using to get these silly values? Anyway, the BBOX in the request is definitely included in the extent... Now what if I change the Response_CRS? I would expect it to give me the same error, since it doesn't affect the requested BBOX. Yet, this time no error is produced and I obtain a tiff file (see attachment : wcsoutput.tif). The data is all wrong (0 everywhere), though. And if I open both WMS and WCS obtained tiffs in QuantumGIS, they appear nowhere near each other (for the same bbox... yes).

I attached the results of GetCapabilities and DescribeCoverage requests as well as the MapServer logs (modified to map logs with requests). The data source is an HDF5 file (see attachment : data.h5). I suspect an issue on MapServer's side but I would be happy if you could tell me it's all my fault (and how to fix it).

Oh, a last thing : it may or may not be related. I had issues with the KML/KMZ WMS outputformats. Results for epsg:4326 and epsg:900913 were completely different (and wrong, of course). I might open a new discussion on this subject at some point.

Thank you all for your help.
Guillaume Loiselle

P.S. : If you want to test, know that epsg:900913 is the same as epsg:3857 (which is more likely to be in your epsg reference file).