Update - I've made a mistake usimg full file name N51E016.hgt.zip for input
instead of N51E016 only. Now I used it correctly but still the error about
projection is present:
$ r.in.srtm input=/home/john/gis/dane/srtm2/N51E016 output=N51E016
Extracting /home/john/gis/dane/srtm2/N51E016...
Archive: /home/john/gis/dane/srtm2/N51E016.hgt.zip
inflating: N51E016.hgt
Converting input file to BIL...
GRASS_INFO_ERROR(15045,1): Projection of dataset does not appear to match
current location.
GRASS_INFO_ERROR(15045,1):
LOCATION PROJ_INFO is:
GRASS_INFO_ERROR(15045,1): name: Latitude-Longitude
GRASS_INFO_ERROR(15045,1): datum: wgs84
GRASS_INFO_ERROR(15045,1): towgs84: 0.000,0.000,0.000
GRASS_INFO_ERROR(15045,1): proj: ll
GRASS_INFO_ERROR(15045,1): ellps: wgs84
GRASS_INFO_ERROR(15045,1):
cellhd.proj = 0 (unreferenced/unknown)
GRASS_INFO_ERROR(15045,1):
You can use the -o flag to r.in.gdal to override this check and use the
location definition for the dataset.
GRASS_INFO_ERROR(15045,1): Consider generating a new location from the input
dataset using the 'location' parameter.
ERROR: N51E016 - map not found
Done: generated map N51E016
(Note: Holes in the data can be closed with 'r.fillnulls' using splines)
Maciek
-------------------------------------------- Managed by Request Tracker
Maciek,
(cc Frank)
I had the same problem with v.in.ogr today (using GDAL/OGR from CVS).
Frank, did anything in GDAL/OGR recently change which makes fail the
recognition of the GRASS location projection in r.in.gdal/v.in.ogr?
This used to work.
Markus
On Tue, Feb 07, 2006 at 12:14:50PM +0100, guest user via RT wrote:
Update - I've made a mistake usimg full file name N51E016.hgt.zip for input
instead of N51E016 only. Now I used it correctly but still the error about
projection is present:
$ r.in.srtm input=/home/john/gis/dane/srtm2/N51E016 output=N51E016
Extracting /home/john/gis/dane/srtm2/N51E016...
Archive: /home/john/gis/dane/srtm2/N51E016.hgt.zip
inflating: N51E016.hgt
Converting input file to BIL...
GRASS_INFO_ERROR(15045,1): Projection of dataset does not appear to match
current location.
GRASS_INFO_ERROR(15045,1):
LOCATION PROJ_INFO is:
GRASS_INFO_ERROR(15045,1): name: Latitude-Longitude
GRASS_INFO_ERROR(15045,1): datum: wgs84
GRASS_INFO_ERROR(15045,1): towgs84: 0.000,0.000,0.000
GRASS_INFO_ERROR(15045,1): proj: ll
GRASS_INFO_ERROR(15045,1): ellps: wgs84
GRASS_INFO_ERROR(15045,1):
cellhd.proj = 0 (unreferenced/unknown)
GRASS_INFO_ERROR(15045,1):
You can use the -o flag to r.in.gdal to override this check and use the
location definition for the dataset.
GRASS_INFO_ERROR(15045,1): Consider generating a new location from the input
dataset using the 'location' parameter.
ERROR: N51E016 - map not found
Done: generated map N51E016
(Note: Holes in the data can be closed with 'r.fillnulls' using splines)
Maciek
-------------------------------------------- Managed by Request Tracker
--
Markus Neteler <neteler itc it> http://mpa.itc.it
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy
On 2/7/06, Markus Neteler <neteler@itc.it> wrote:
Maciek,
(cc Frank)
I had the same problem with v.in.ogr today (using GDAL/OGR from CVS).
Frank, did anything in GDAL/OGR recently change which makes fail the
recognition of the GRASS location projection in r.in.gdal/v.in.ogr?
This used to work.
Markus,
I can't think of anything.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent