[GRASS-dev] grass6.2?

[Michael Barton]

Is there a reason to change i.rectify at some point so that it also will
read from a different directory and write to the current one? This is how
the georectifier works, but I have to switch back and forth between
locations/mapsets to make i.rectify work.

I have no idea about the locking. But probably not or I would have probably
run into it like I did with g.mapset.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
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



> From: Glynn Clements <glynn at gclements.plus.com>
> Date: Mon, 12 Jun 2006 06:24:52 +0100
> To: Michael Barton <michael.barton at asu.edu>
> Cc: Helena Mitasova <hmitaso at unity.ncsu.edu>, Wolf Bergenheim
> <wolf+grass at bergenheim.net>, <grass-dev at grass.itc.it>, <cavallini at faunalia.it>
> Subject: Re: [GRASS-dev] grass6.2?
> 
> 
> Michael Barton wrote:
> 
>> I noted the difference because i.rectify reads from the current location and
>> writes to the location specified by i.target.
> 
> Ah. That is something which its replacement shouldn't imitate.
> 
> Reading from a different location or mapset is reasonable enough, but
> nothing should write outside of the current mapset. The case of
> r.in.gdal creating a new location is probably OK, but writing to an
> existing mapset (other than the current one) isn't.
> 
> BTW, does i.rectify bother to lock the destination mapset?
> 
> -- 
> Glynn Clements <glynn at gclements.plus.com>