[GRASS-user] r.proj's "use different location" error while working in different dbases

Nikos Alexandris nikos.alexandris at felis.uni-freiburg.de
Sun Jul 5 07:24:13 EDT 2009

> > I have "wgs84" locations in different dbases, for example:
> > "/grassdb/ellas/wgs84" and "/grassdb/global/wgs84".

> > I want to "r.proj" something from "ellas" to "global" dbase
> > and I get the following error:
> > ERROR: You have to use a different location for input than
> > the current

> > This is a bug, ins't it? I suppose the "dbase=" parameter
> > is not checked at all in this case (?).

> yes, it appears so.

> r.proj(.seg) has the following check:
>     if (strcmp(inlocation->answer, G_location()) == 0)
>         G_fatal_error(_("You have to use a different location for input than the current"));

> maybe it should assemble indbase->answer/inlocation->answer
> and test that against G_location_path(). ?  then dirsep hell?

> please file a bug

Done: http://trac.osgeo.org/grass/ticket/675

Alternative solution with respect to the specific example here: allow
g.copy to copy data from another dbase/location to the current dbase in
a location with identical name and projection definition of course (?).


More information about the grass-user mailing list