r.stats's nsteps is not region-sensitive

[martinl]

r.stat's nsteps option is not region-sensitive, in other words ranges are calculated from original raster, not from current region. It can be very confusing for a user, I am not sure if it's a bug or just undocumented behaviour.

OK, I get 5 classes:

g.region rast=elevation
r.stats elevation nsteps=5 --q
55.578793-75.729007
75.729007-95.879221
95.879221-116.029436
116.029436-136.17965
136.17965-156.329865

Smaller number of classes when using sub-region:

g.region n=219326.524155 s=218357.261131 w=635573.588429 e=637027.482965 -a
r.stats elevation nsteps=5 --q
75.729007-95.879221
95.879221-116.029436
116.029436-136.17965

[neteler]

Ticket retargeted after 7.0.1 milestone closed

[martinl]

Any opinion / feedback? Thanks.

[mlennert]

Replying to martinl:

Any opinion / feedback? Thanks.

Both region-specific bins and map-specific bins can be useful. The latter allow easier comparison between different subregions, whereas the former allow getting the number of bins asked for in each subregion.

So, the ideal solution IMHO would be to have both. In the meantime, the fact that bins are calculated on the entire map's value range should be at least documented explicitly.

[neteler]

Ticket retargeted after milestone closed

[neteler]

Ticket retargeted after milestone closed

[neteler]

Ticket retargeted after 7.0.3 milestone closed

[martinl]

Milestone renamed

[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

[neteler]

Ticket retargeted after milestone closed

[neteler]

Ticket retargeted after milestone closed

[neteler]

Ticket retargeted after milestone closed