VS: [mapserver-users] Re: WCS Geotiff output issue

Tue Nov 8 05:58:26 PST 2011

Hi,

Wow! Adding a projection object on layer level fixed the problem. I was
sure the map level projection object was used when a layer was lacking it.
Now the result is the same than that of the WMS GeoTiff output (except for
the background color but that's not an issue).

Thanks a lot for your help!
Guillaume Loiselle

2011/11/7 Rahkonen Jukka <Jukka.Rahkonen at mmmtike.fi>

> **
> Hi,
>
> Mapfile looks good to me. I fear I have only two suggestions left:
> - try adding projection also to the layer even it should use the map level
> projection by default
> - forget HDF5 for a moment and use some geotiff instead to check if there
> are some oddities due to source data format
>
> -Jukka Rahkonen-
>
>  ------------------------------
> *Lähettäjä:* mapserver-users-bounces at lists.osgeo.org [mailto:
> mapserver-users-bounces at lists.osgeo.org] *Puolesta *Guillaume Loiselle
> *Lähetetty:* 7. marraskuuta 2011 23:07
> *Vastaanottaja:* mapserver-users at lists.osgeo.org
> *Aihe:* Re: [mapserver-users] Re: WCS Geotiff output issue
>
>  Hi,
>
> Both mapfile and datasource are available in the first email I sent.
>
> http://lists.osgeo.org/pipermail/mapserver-users/2011-November/070670.html
>
> Filenames appear to be a little bit messed up but the data itself is fine.
> I don't know why it went so wrong.
>
> Mapfile :
> http://lists.osgeo.org/pipermail/mapserver-users/attachments/20111104/78e5fa24/2011102811-0001.obj
>
> Data (HDF5 format) :
> http://lists.osgeo.org/pipermail/mapserver-users/attachments/20111104/78e5fa24/data-0001.obj
>
> I intend to stick with 1.0.0 indeed. At least until it works... I will
> look up 1.1.0's details in due time.
>
>
>
>
> 2011/11/7 Rahkonen Jukka <Jukka.Rahkonen at mmmtike.fi>
>
>> Pity that is was not just version mismatch.  Could it be possible to see
>> your mapfile and info about the datasource?
>> Stay with version 1.0.0 while testing. With version 1.1.0 you must give
>> EPSG:4326 coordinates in Northing-Easting order which can make things more
>> complicated.
>>
>> -Jukka Rahkonen-
>> ________________________________
>>  Guillaume Loiselle wrote:
>>
>> Hi,
>>
>> I'm afraid it isn't. I didn't notice the request version I sent was a
>> "mixed" one but I tried Coverage on 1.0.0 and Identifier on 1.1.0 as well
>> and the result was basically the same.
>> Here is the 1.1.0 version of the error :
>>
>>
>> <?xml version="1.0" encoding="ISO-8859-1"?>
>> <ows:ExceptionReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xmlns:ows="http://www.opengis.net/ows/1.1" version="1.1.0"
>> xml:lang="en-US" xsi:schemaLocation="http://www.opengis.net/ows/1.1
>> http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd">
>>  <ows:Exception exceptionCode="bbox" locator="NoApplicableCode">
>>    <ows:ExceptionText>
>> msWCSGetCoverage(): WCS server error. Requested BBOX
>> (-178.804111261525,2802.84894277903,179.578125552223,2907.18853507175) is
>> outside requested coverage BBOX (-70,45,-55,52)</ows:ExceptionText>
>>  </ows:Exception>
>> </ows:ExceptionReport>
>>
>>
>> I of course spent a lot of time on the WCS server documentation page. I
>> saw no reference to such a problem, though. My request,
>>
>> http://localhost/cgi-bin/mapserv.exe?
>> map=D:/Guillaume/ProjetCourantsGlaces/WCSproblem/2011102811.map&
>> SERVICE=WCS&
>> VERSION=1.0.0&
>> REQUEST=GetCoverage&
>> COVERAGE=thelayer&
>> CRS=EPSG:4326&
>> BBOX=-67.5,48.922499263758255,-64.6875,50.736455137010665&
>> WIDTH=256&
>> HEIGHT=256&
>> FORMAT=GTiff
>>
>> is formatted the same way the example is :
>>
>> http://my.host.com/cgi-bin/mapserv?
>> map=mywcs.map&
>> SERVICE=wcs&
>> VERSION=1.0.0&
>> REQUEST=GetCoverage&
>> coverage=bathymetry&
>> CRS=EPSG:42304&
>> BBOX=-2200000,-712631,3072800,3840000&
>> WIDTH=3199&
>> HEIGHT=2833&
>> FORMAT=GTiff
>>
>>
>> My mapfile contains every required attribute.
>>
>> Thank you.
>> Guillaume Loiselle
>>
>>
>>  2011/11/7 Rahkonen Jukka <Jukka.Rahkonen at mmmtike.fi<mailto:
>> Jukka.Rahkonen at mmmtike.fi>>
>> 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<mailto:
>> mapserver-users-bounces at lists.osgeo.org> [
>> mapserver-users-bounces at lists.osgeo.org<mailto:
>> mapserver-users-bounces at lists.osgeo.org>] käyttäjän Guillaume Loiselle [
>> loiselle.guillaume at gmail.com<mailto:loiselle.guillaume at gmail.com>]
>> puolesta
>> Lähetetty: 7. marraskuuta 2011 21:21
>>  Vastaanottaja: mapserver-users at lists.osgeo.org<mailto:
>> 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><mailto: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).
>>
>>
>>  _______________________________________________
>> mapserver-users mailing list
>> mapserver-users at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20111108/c1b6ac06/attachment.htm>