wish: "higher that/lower than" flag and intervals definition in r.report and r.stats

[veroandreo]

Hello,

If the user wants to know the percentage of the map or surface occupied by values higher or lower than a certain threshold or even in specific intervals, the option nsteps in both r.stats and r.report is not very useful. You need to change nsteps setting several times until you find a set of intervals more or less according to your needs (but always suboptimal).

Wish: A flag or parameter for "higher than/lower than" values in r.report and r.stats, and also the possibility to set specific intervals for the report of areas.

Hint: I know it can also be achieved creating designated masks with r.mapcalc (r.mask would only work with integer maps), and then using r.report or r.stats with nsteps=1 for thresholds or intervals of interest, but this is not really straightforward and easy for anybody.

Thanks much!

Vero

[neteler]

Ticket retargeted after 7.0.1 milestone closed

[neteler]

Ticket retargeted after milestone closed

[neteler]

Ticket retargeted after milestone closed

[neteler]

Ticket retargeted after 7.0.3 milestone closed

[martinl]

Milestone renamed

[veroandreo]

Replying to veroandreo:

Hello,

If the user wants to know the percentage of the map or surface occupied by values higher or lower than a certain threshold or even in specific intervals, the option nsteps in both r.stats and r.report is not very useful. You need to change nsteps setting several times until you find a set of intervals more or less according to your needs (but always suboptimal).

Wish: A flag or parameter for "higher than/lower than" values in r.report and r.stats, and also the possibility to set specific intervals for the report of areas.

Hint: I know it can also be achieved creating designated masks with r.mapcalc (r.mask would only work with integer maps), and then using r.report or r.stats with nsteps=1 for thresholds or intervals of interest, but this is not really straightforward and easy for anybody.

Here an example with r.mask and r.univar for integer maps (since nsteps in r.report or r.stats works only for floating point maps):

for MAP in `g.list type=raster pattern=*sur_refl*filt` ; do
 eval `r.info -r $MAP`
 if [ "$max" -ge 10000 ] ; then
  r.mask $MAP maskcats="10000 thru 16000"
  echo $MAP
  r.univar -g $MAP | grep ^n= >> stats
  r.mask -r 
 fi
done

This would be so much easier and fast if G7:r.report and G7:r.stats had a range option (and/or low and high flags) in order to customize the range of values one is interested in getting the report.

[neteler]

Ticket retargeted after milestone closed

[martinl]

All enhancement tickets should be assigned to 7.6 milestone.

[martinl]

Ticket retargeted after milestone closed

[martinl]

Ticket retargeted after milestone closed