Opened 11 years ago

Last modified 6 years ago

#2321 new enhancement

Assign suitable map output typ automatically in modules which use lib/stats

Reported by: sbl Owned by: grass-dev@…
Priority: normal Milestone: 7.6.2
Component: Raster Version: unspecified
Keywords: r.resamp.stats, r.series, r.series.interp, r3.neighbors, v.vect.stats, r.in.xyz, t.rast.aggregate Cc:
CPU: All Platform: All

Description

Recently Glynn implemented a logic for assigning the moste suitable output type (integer / float) to maps produced in r.neighbors.

Basically, all modules which use lib/stats would benefit from such a logic, like r.resamp.stats, r.series, r.series.interp, r3.neighbors, v.vect.stats and possibly r.in.xyz, as well all modules which are based on them (e.g. t.rast.aggregate).

Implementing Glynns logic on library level would help to both avoid that maps produced with these modules unnecessarily occupy hard disk space and speed up subsequent operations as well as it would spare users who care about the storage type from running r.mapcalc int() / float() and g.remove after one of the named commands.

Not sure how FCELL/DCELL differences for float output could/should be tackled...

For the original discussion see: http://osgeo-org.1560.x6.nabble.com/G7-r-neighbors-changes-data-type-from-CELL-to-DCELL-tt5134367.html

Change History (10)

comment:1 by neteler, 11 years ago

Keywords: r.resamp.stats r.series r.series.interp r3.neighbors v.vect.stats r.in.xyz t.rast.aggregate added

Original discussion link (since nabble servers tend to change their name over time):

http://lists.osgeo.org/pipermail/grass-dev/2014-April/068247.html

comment:2 by neteler, 9 years ago

Milestone: 7.1.07.2.0

Milestone renamed

comment:3 by neteler, 8 years ago

Milestone: 7.2.07.2.1

Ticket retargeted after milestone closed

comment:4 by martinl, 8 years ago

Milestone: 7.2.17.2.2

comment:5 by martinl, 7 years ago

Milestone: 7.2.27.4.0

All enhancement tickets should be assigned to 7.4 milestone.

comment:6 by neteler, 7 years ago

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:7 by neteler, 7 years ago

Milestone: 7.4.17.4.2

comment:8 by martinl, 6 years ago

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:9 by martinl, 6 years ago

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:10 by martinl, 6 years ago

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.