[GRASS5] [bug #4064] (grass) r.in.srtm: doesn't work, though it's a latlong WGS84 projection
Maciek Sieczka via RT
grass-bugs at intevation.de
Thu Feb 9 06:08:47 EST 2006
I have built GDAL from CVS today to sort out the
As a side effect, I don't need the to override projection check for r.in.gdal
inside r.in.srtm to make it work anymore. See how the projections "appear to
match" back now:
$ r.in.srtm input=/home/john/gis/dane/srtm2/N51E016 output=N51E016_v2_newgdal
Converting input file to BIL...
Projection of input dataset and current location appear to match.
Proceeding with import...
CREATING SUPPORT FILES FOR N51E016_v2_newgdal
Color table for [N51E016_v2_newgdal] set to srtm
Done: generated map N51E016_v2_newgdal
(Note: Holes in the data can be closed with 'r.fillnulls' using splines)
I haven't changed anything in my Location setup since the bug report neither
altered Grass61 instalation. All I did was to replace my 2006-01-09 CVS GDAL
build with a fresh one.
How is your v.in.ogr problem now Markus?
-------------------------------------------- Managed by Request Tracker
More information about the grass-dev