[GRASS-user] Re: /usr/lib/grass/scripts/r.in.wms: line 439: /usr/lib/grass/etc/r.in.wms/r.in.gdalwarp: Argument list too long

[Seb]

Hi,

I should have mentioned that before trying with 'gdalwarp', I tried what
'r.in.wms' does with 'r.in.gdalwarp', but it also failed with:

---<--------------------cut here---------------start------------------->---
$ /usr/lib/grass64/etc/r.in.wms/r.in.gdalwarp in='wms_global_mosaic_nc__0.geotiff,wms_global_mosaic_nc__1.geotiff' out=test s_srs='EPSG:4326'
Creating output file that is 1054P x 1056L.
Processing input file wms_global_mosaic_nc__0.geotiff.
0...10...20...30...40...50...60...70...80...90...100 - done.
ERROR: Projection of dataset does not appear to match current location.

       Location PROJ_INFO is:
       name: Albers Equal Area
       datum: wgs84
       towgs84: 0.000,0.000,0.000
       proj: aea
       ellps: wgs84
       a: 6378137.0000000000
       es: 0.0066943800
       f: 298.2572235630
       lat_0: 58.2500000000
       lat_1: 57.0000000000
       lat_2: 59.5000000000
       lon_0: -63.0000000000
       x_0: 0.0000000000
       y_0: 0.0000000000

       Dataset PROJ_INFO is:
       name: Albers Equal Area
       proj: aea
       datum: wgs84
       ellps: wgs84
       lat_1: 57
       lat_2: 59.5
       lat_0: 58.25
       lon_0: -63
       x_0: 0
       y_0: 0
       no_defs: defined

       ERROR: units

       You can use the -o flag to r.in.gdal to override this check and use
       the location definition for the dataset.
       Consider generating a new location from the input dataset using the
       'location' parameter.
ERROR: r.in.gdalwarp: r.in.gdal failure.
---<--------------------cut here---------------end--------------------->---


Cheers,

-- 
Seb