[GRASS-dev] another not quiet GRASS command
Michael Barton
michael.barton at asu.edu
Mon Sep 3 13:01:45 EDT 2007
On 9/3/07 7:22 AM, "Glynn Clements" <glynn at gclements.plus.com> wrote:
>
> Hamish wrote:
>
>> In the above case of georect.tcl, we may ask 1) if switching between
>> mapsets in the script is really the best solution; 2) if that warning
>> should be a warning.
>
> 3) If g.mapset is the right way to switch mapsets, or whether gis.m
> should generate a temporary GISRC and "set env(GISRC) $tmp_gisrc".
>
> If you're going to modify the existing $GISRC with g.mapset, the user
> had better not be running GRASS commands on the terminal in the
> meantime.
Because of the way GRASS works, it is necessary to switch between mapsets.
i.e., a display command will only work with the current environment and an
accessible mapset. Any operation that changes something (e.g., i.group) will
only work in the current mapset.
However, with more experimentation, it looks like g.mapset won't work as a
way to do this. I've had to revert to using g.gisenv
set=LOCATION_NAME=[xy_location].
Michael
__________________________________________
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-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
More information about the grass-dev
mailing list