We’ve just had some instances where people made new location from georeferenced file or from running r.in.gdal and the PROJ_INFO and PROJ_UNIT files weren’t made–although the location was created with no problems. I just tried this with an SRTM geotif and PROJ_INFO and PROJ_UNIT files WERE made.
I’m not sure what is going on, but wonder if anyone else has run into this?
Michael
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>
On Mon, 11 Feb 2008, Michael Barton wrote:
We've just had some instances where people made new location from georeferenced file or from running r.in.gdal and the PROJ_INFO and PROJ_UNIT files weren't made--although the location was created with no problems. I just tried this with an SRTM geotif and PROJ_INFO and PROJ_UNIT files *WERE* made.
Find out what was wrong with the file by runing g.proj -p georef=filename on it. Probably it is not actually georeferenced or there is some problem with GDAL/OGR reading the georeferencing information.
Paul
On 12/02/08 06:52, Michael Barton wrote:
We've just had some instances where people made new location from georeferenced file or from running r.in.gdal and the PROJ_INFO and PROJ_UNIT files weren't made--although the location was created with no problems. I just tried this with an SRTM geotif and PROJ_INFO and PROJ_UNIT files *WERE* made.
I'm not sure what is going on, but wonder if anyone else has run into this?
Are we talking wingrass here ?
Moritz