[GRASS-user] Region definition in Grass 6.1 (and 6.1 cvs)

[Michael Barton]

This use of computational region works better

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton


> From: Glynn Clements <glynn at gclements.plus.com>
> Date: Wed, 23 Aug 2006 09:50:13 +0100
> To: Hamish <hamish_nospam at yahoo.com>
> Cc: <grassuser at grass.itc.it>, <michael.barton at asu.edu>
> Subject: Re: [GRASS-user] Region definition in Grass 6.1 (and 6.1 cvs)
> 
> 
> Hamish wrote:
> 
>>> OTOH, if you don't use the region from an active display, but have a
>>> distinct "current region", there should be an option to indicate this
>>> on the display(s), so that the user isn't surprised when a
>>> newly-created map has different bounds and/or resoltion to the map
>>> they were just looking at.
>> 
>> Hi, if I can jump in for a second with a suggestion:
>> 
>> I find some of these discussions can get confusing WRT to talking about
>> the multiple "regions" in use.
>> 
>> Proposal: we use "computational region" to talk about WIND region and
>> "display region" to talk about GUI zoom.
> 
> Proposal: use "display region" to talk about GUI zoom/pan and
> "computational region" to talk about non-display commands (regardless
> of whether they use WIND, $WIND_OVERRIDE, or $GRASS_REGION).
> 
> -- 
> Glynn Clements <glynn at gclements.plus.com>