[GRASS-user] r.in.wms / Wheregroup OSM WMS

[Nick Cahill]

I found r.in.wms difficult because the server would time out and return an error file, which would be saved as a file named e.g. Wald__0.geotiff, but would actually be an html error message. This of course causes gdalwarp to fail. I got around it by just deleting those 4 kb error files and running it again, getting a few more tiles, deleting the error files, run again...... It took me a couple days (!) to download all the tiles I needed for a large high resolution map from Blue Marble, but it worked in the end. I also ended up patching and such manually, not using gdalwarp at all.

It was a bear, but not GRASS's fault, perhaps, but a server failure.

Hope this helps. 

Nick Cahill




On Apr 25, 2010, at 4:14 AM, Hamish wrote:

> Hi Peter,
> 
>> I`m trying to access a WMS service for european OSM data
>> (german link: http://www.wheregroup.com/de/freier_wms_mit_openstreetmap_daten)
>> in GRASS 6.4 with r.in.wms in an EXPSG4326 location
>> 
>> r.in.wms --o v=5 layers=Wald mapserver=http://osm.wheregroup.com/cgi-bin/osm_basic.xml
>> output=Wald
>> 
>> This produces this error message by r.in.wms:
>> 
>> ERROR 4: `/shazzam/locations/wms_download/Wald__0.geotiff'
>> not recognised as a supported file format.
>> ERROR: r.in.gdalwarp: gdalwarp failure.
>> 
>> The error message is justified, as  the content of
>> "Wald__0.geotiff" is actually XML, not a geotiff:
>> 
>> <?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.1" 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="service"
>> locator="MissingParameterValue">
>>     <ows:ExceptionText>msWFSDispatch(): WFS
>> server error. Incomplete WFS request: SERVICE parameter
>> missing</ows:ExceptionText>
>>   </ows:Exception>
>> </ows:ExceptionReport>
>> 
>> 
>> What is the proper r.in.wms configuration to overcome this
>> ?
> 
> first try setting debug level to 1:
> g.gisenv set="DEBUG=1"
> 
> this will show you the formed HTTP request string.
> 
> as a first stab I'd try the -g flag though.
> 
> 
> Hamish
> 
> 
> 
> 
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user