search

landam / grass-gis-git-migration-test

0 stars 0 forks source link

r.stats's nsteps is not region-sensitive #162

Open landam opened 5 years ago

landam commented 5 years ago

Reported by @landam on 16 Mar 2015 16:25 UTC 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

GRASS GIS version and provenance

svn-trunk

Migrated-From: https://trac.osgeo.org/grass/ticket/2625

landam commented 5 years ago

Comment by neteler on 30 Jul 2015 21:19 UTC Ticket retargeted after 7.0.1 milestone closed

landam commented 5 years ago

Comment by @landam on 12 Sep 2015 22:43 UTC Any opinion / feedback? Thanks.

landam commented 5 years ago

Comment by mlennert on 14 Sep 2015 09:39 UTC Replying to [comment:2 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.

landam commented 5 years ago

Comment by neteler on 20 Nov 2015 17:08 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Comment by neteler on 28 Jan 2016 08:02 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Comment by neteler on 28 Jan 2016 08:06 UTC Ticket retargeted after 7.0.3 milestone closed

landam commented 5 years ago

Modified by @landam on 12 May 2016 06:36 UTC

landam commented 5 years ago

Modified by @landam on 23 Aug 2016 07:52 UTC

landam commented 5 years ago

Comment by @landam on 27 Aug 2016 13:42 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by neteler on 12 Jun 2018 20:48 UTC

landam commented 5 years ago

Comment by @landam on 25 Sep 2018 16:52 UTC All enhancement tickets should be assigned to 7.6 milestone.

landam commented 5 years ago

Comment by @landam on 25 Jan 2019 21:07 UTC Ticket retargeted after milestone closed