[GRASS-dev] FW: [GRASS-user] Projection of dataset does not appear to match thecurrent location!!!

This problem pops up about once a month or maybe more frequently. It seems
like at a minimum it would be good to edit the error message to say
something like Glynn responded. Or maybe point the user to a FAQ somewhere.

Jerry

-----Original Message-----
From: grass-user-bounces@lists.osgeo.org
[mailto:grass-user-bounces@lists.osgeo.org] On Behalf Of Glynn Clements
Sent: Thursday, February 14, 2008 3:19 PM
To: Kunal Malik
Cc: grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] Projection of dataset does not appear to match
thecurrent location!!!

Kunal Malik wrote:

i am Trying to display one raster image kept on my harddisk,
I have kept spearfish60 on /usr/local/grassdata so I set Location :
spearfish60
I have made one user user1 then i set Mapset: user1..
then i start grass ,
the n throu command
r.in.gdal -e in=nf42.tif out=tm
then i am getting the error,.,

Projection of dataset does not appear to match the current location!!!
I have tried the same thru GIS manager,
file->import->Raster->multiple formats using gdal..
I want to know where i am doing wrong..

You need to create a location whose projection matches the data you
wish to import.

Try using g.proj with the -c flag and the location= and georef=
options to create a new location based upon the projection information
in the file.

You should then be able to import the file into that location with
r.in.gdal. If desired, you can then re-project it to another location
with r.proj.

--
Glynn Clements <glynn@gclements.plus.com>
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

I have added the comment from Glynn to the manual page of r.in.gdal
and in modified form to v.in.ogr.

Markus

On Feb 14, 2008 9:24 PM, Gerald Nelson <gnelson@uiuc.edu> wrote:

This problem pops up about once a month or maybe more frequently. It seems
like at a minimum it would be good to edit the error message to say
something like Glynn responded. Or maybe point the user to a FAQ somewhere.

Jerry

-----Original Message-----
From: grass-user-bounces@lists.osgeo.org
[mailto:grass-user-bounces@lists.osgeo.org] On Behalf Of Glynn Clements
Sent: Thursday, February 14, 2008 3:19 PM
To: Kunal Malik
Cc: grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] Projection of dataset does not appear to match
thecurrent location!!!

Kunal Malik wrote:

> i am Trying to display one raster image kept on my harddisk,
> I have kept spearfish60 on /usr/local/grassdata so I set Location :
> spearfish60
> I have made one user user1 then i set Mapset: user1..
> then i start grass ,
> the n throu command
> r.in.gdal -e in=nf42.tif out=tm
> then i am getting the error,.,
>
> Projection of dataset does not appear to match the current location!!!
> I have tried the same thru GIS manager,
> file->import->Raster->multiple formats using gdal..
> I want to know where i am doing wrong..

You need to create a location whose projection matches the data you
wish to import.

Try using g.proj with the -c flag and the location= and georef=
options to create a new location based upon the projection information
in the file.

You should then be able to import the file into that location with
r.in.gdal. If desired, you can then re-project it to another location
with r.proj.

--
Glynn Clements <glynn@gclements.plus.com>
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

--
Open Source Geospatial Foundation
http://www.osgeo.org/
http://www.grassbook.org/

Markus Neteler wrote:

I have added the comment from Glynn to the manual page of r.in.gdal
and in modified form to v.in.ogr.

BTW, I overlooked the r.in.gdal location= option when I wrote that
reply. In this particular case, that appears to be more
straightforward than using a separate g.proj -c step.

--
Glynn Clements <glynn@gclements.plus.com>