r.proj's "use different location" error while working in different dbases
|Reported by:||nikos||Owned by:|
|Keywords:||r.proj, dbase, location, indbase->answer, inlocation->answer||Cc:||nikos.alexandris@…|
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:
--- # working in "global" g.gisenv
GISDBASE=/geo/grassdb/global LOCATION_NAME=wgs84 MAPSET=PERMANENT
# trying to "pull" data r.proj aster_gdem out=aster_gdem_ellas location=wgs84 mapset=PERMANENT dbase=/geo/grassdb/ellas
ERROR: You have to use a different location for input than the current ---
Even though r.proj is meant to re-project data from one location to another (= usually different projection definitions) within a dbase, it could be used to "pull" data from a different grass-dbase as in my example-attempt above.
This is a bug, ins't it? I suppose the "dbase=" parameter is not checked at all in this case (?).
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 (?).