On Tue, Aug 28, 2018 at 1:49 PM Veronica Andreo <veroand...@gmail.com> wrote: > > Sorry, I pressed send earlier than intended... > > El mar., 28 ago. 2018 a las 13:45, Veronica Andreo (<veroand...@gmail.com>) escribió: >> >> Thanks for the explanation, Glynn :) >> >> El mar., 28 ago. 2018 a las 11:01, Glynn Clements (< gl...@gclements.plus.com>) escribió: >>> >>> >>> Veronica Andreo wrote: >>> >>> > If I use a series of integer type maps as input to t.rast.series or >>> > r.series and select minimum as method, the output is a floating point map. >>> > I would have thought that if the input are integers then output should be >>> > integer as well. I realized when I made a plot of the map and got a smooth >>> > legend instead of integer numbers. >>> >>> > Is this an expected behaviour? >>> >>> The type of the output map is independent of the inputs, determined >>> solely by the method. The count, diversity, min_raster and max_raster >>> methods generate integer maps; all other methods generate >>> floating-point maps. >>> >>> It probably wouldn't be particularly involved to add another flag to >>> the method table to indicate that a particular method will always >>> produce an integer result for integer inputs. > > > Is this worth an enhancement ticket? I do not know how to implement any of this myself.
Please try trunk r73206. Markus M > > thanks again, > Vero > _______________________________________________ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
