On Mon, May 9, 2016 at 2:10 AM, Vaclav Petras <wenzesl...@gmail.com> wrote:
> On Sat, May 7, 2016 at 5:14 PM, Nikos Alexandris <n...@nikosalexandris.net>
>>> - The k-flag (keep current computational region) is invers to
>>> GRASS standards. Maybe better to switch the behavior?
>>
>> Not sure. It's kind of related to the #1 mistake everyone does, forget
>> setting the right region extent. So, I'd thought of letting the module
>> operate on the whole scene.
>
> Then really all GRASS modules should be changed.
Yeah, probably not :-)
>> Do we have a reference for this ("GRASS standards") or you
>> mean the "common" behaviour of most modules?
>
> No. Perhaps we need another Submitting page on Trac or perhaps just adding a
> best practice to the main Submitting page.
Here you go:
https://trac.osgeo.org/grass/wiki/Submitting/General#Modulebehaviour:computationalregionsettings
> This particular thing should be also somewhere in the user documentation
> (which obviously should be followed when developing a new module). It seems
> that g.region man page uses outdated terminology and doesn't do a good job
> on describing this behavior. Anyone, please contribute a better text.
It could be taken from here:
https://grasswiki.osgeo.org/wiki/Computational_region
Markus
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
