v.rast.stats tries to disable MASK before doing statistics, what is a
reason for that? BTW, in r66421 I fixed issue when MASK is not located
in the current mapset (and cannot be disabled).
v.rast.stats tries to disable MASK before doing statistics, what is a
reason for that? BTW, in r66421 I fixed issue when MASK is not located
in the current mapset (and cannot be disabled).
Just intrigued by this: I though the mask is mapset based, so how you can you have an active mask in a mapset that is not defined within that mapset ?
v.rast.stats tries to disable MASK before doing statistics, what is a
reason for that?
I would guess that in most cases, users want the info of v.rast.stats for all of their vector map and taking into account the mask might lead to counter-intuitive results (and you wouldn't easily know for which vector features the mask had an influence or not.
I agree that this possibly needs a flag to enable the mask for power users, but I would keep no-mask as the default.
This definitely needs a flag + explanation in documentation.
Taking into account philosophy behind GRASS raster processing, I would
say - default should be to apply MASK, as MASK affects all raster
reading operations (unless stated otherwise or requested by user).
Maris.
2015-10-06 19:15 GMT+03:00 Martin Landa <landa.martin@gmail.com>:
2015-10-06 18:13 GMT+02:00 Moritz Lennert <mlennert@club.worldonline.be>:
But this was a bug that you fixed in r66421, or ?
yes, it was. I was just wondering why the module should ignore the
mask. It was answered. Martin
2015-10-07 7:05 GMT+02:00 Maris Nartiss <maris.gis@gmail.com>:
This definitely needs a flag + explanation in documentation.
Taking into account philosophy behind GRASS raster processing, I would
say - default should be to apply MASK, as MASK affects all raster
reading operations (unless stated otherwise or requested by user).
This definitely needs a flag + explanation in documentation.
Taking into account philosophy behind GRASS raster processing, I would
say - default should be to apply MASK, as MASK affects all raster
reading operations (unless stated otherwise or requested by user).
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. As a federal employee, my email may be subject to FOIA request.
sorry I jumped so late into this discussion, but I think we can just remove any mask related code in v.rast.stats - it’s apparently leftover from https://trac.osgeo.org/grass/changeset/44444/
It used mask in the past, but now it uses r.univar zones instead.
This definitely needs a flag + explanation in documentation.
Taking into account philosophy behind GRASS raster processing, I would
say - default should be to apply MASK, as MASK affects all raster
reading operations (unless stated otherwise or requested by user).
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. As a federal employee, my email may be subject to FOIA request.
On Wed, Oct 7, 2015 at 3:27 PM, Anna Petrášová <kratochanna@gmail.com> wrote:
Hi,
sorry I jumped so late into this discussion, but I think we can just remove
any mask related code in v.rast.stats - it's apparently leftover from https://trac.osgeo.org/grass/changeset/44444/
It used mask in the past, but now it uses r.univar zones instead.
sorry I jumped so late into this discussion, but I think we can just remove
any mask related code in v.rast.stats - it’s apparently leftover from https://trac.osgeo.org/grass/changeset/44444/
It used mask in the past, but now it uses r.univar zones instead.