[GRASS-dev] r.bioclim output integer maps

Paulo van Breugel p.vanbreugel at gmail.com
Mon Feb 22 00:18:27 PST 2016


On Sun, Feb 21, 2016 at 12:20 PM, Markus Metz <markus.metz.giswork at gmail.com
> wrote:

> On Wed, Feb 10, 2016 at 2:39 PM, Paulo van Breugel
> <p.vanbreugel at gmail.com> wrote:
> >
> >
> > On Wed, Feb 10, 2016 at 1:16 PM, Markus Neteler <neteler at osgeo.org>
> wrote:
> >>
> >>
> >> On Feb 10, 2016 12:03 PM, "Paulo van Breugel" <p.vanbreugel at gmail.com>
> >> wrote:
> >> > On Wed, Feb 10, 2016 at 10:26 AM, Markus Neteler <neteler at osgeo.org>
> >> > wrote:
> >> >> I guess for the compatibility with WORLDCLIM (have added that, too).
> >> >> The other Markus will know better :-)
> >> >
> >> > I still think it is really preferable to not round these numbers, but
> >> > leave that to the user (perhaps include it as an option though). But
> in any
> >> > case, the text you added makes things more explicit / clear, which is
> most
> >> > important.
> >>
> >> Python patches are welcome!
> >
> >
> > I could give that a try (wasn't difficult if I remember well), but I
> rather
> > first hear from Markus (the other ;-) whether he thinks it is something
> that
> > could/should be changed
>
> It could be changed, but I am not sure if it is worth the trouble.
> When I wrote the module, I used bioclim from worldclim as test suite
> which also uses integer. That means when using worldclim as input, the
> default settings produce output identical to worldclim's bioclim maps.
>
> Instead of leaving the rounding to the user, you could also leave the
> conversion to fp to the user. I prefer to have rounding to integer
> because 1) users will not get the false impression of high accuracy
> with floating point values,2) it saves a lot of disk space.
>

OK, that is clear. I think the most important is that this is now clearly
explained in the manual pages.


>
> Markus M
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20160222/f3b225d4/attachment.html>


More information about the grass-dev mailing list