[GRASS-dev] interferring ovewrite flags [was: [bug #5167]
(grass) v.patch: -a(ppend) issues]
michael.barton at asu.edu
Mon Sep 25 11:13:38 EDT 2006
Is having both -o and --o a problem?
The reason I ask is that --o, by design, doesn't show up in the
module/script GUI. For r.mask, much of the time, the user will simply want
to overwrite the existing MASK file, to avoid the annoyance of having to run
g.remove each time (note the MASK file created by r.mask is a reclass of a
real raster file, so there is little loss if it is deleted).
So in this case, I'd prefer to have an overwrite option easily accessible to
a user. How best to do this?
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
> From: Maciej Sieczka <tutey at o2.pl>
> Date: Mon, 25 Sep 2006 11:53:57 +0200
> To: Michael Barton <michael.barton at asu.edu>
> Cc: <grass-dev at grass.itc.it>
> Subject: Re: [GRASS-dev] interferring ovewrite flags [was: [bug #5167] (grass)
> v.patch: -a(ppend) issues]
> Michael Barton wrote:
>> R.mask is a shell script, so the -o flag is there to run the underlying
>> GRASS module with --o.
>> Is there a better way to do this script programmers?
> r.reclass (used in r.mask) supports --o as all other Grass raster
> modules do (besides r.mapcalc).
> I checked r.mask and it doesn't matter whether you use it with -o or
> --o. In both cases the output is ovewritten, so you just remove your -o.
> Looks like parser takes care of it.
More information about the grass-dev