[GRASS-dev] t.rast.out.xyz not exporting all cells in the computational region
Vaclav Petras
wenzeslaus at gmail.com
Tue Dec 6 10:34:14 PST 2016
On Tue, Dec 6, 2016 at 12:34 PM, Moritz Lennert <
mlennert at club.worldonline.be> wrote:
> Le 6 décembre 2016 17:53:48 GMT+01:00, Martin Landa <
> landa.martin at gmail.com> a écrit :
> >Hi,
> >
> >2016-12-06 17:45 GMT+01:00 Markus Neteler <neteler at osgeo.org>:
> >> Big question: add to 7.2.0 or not? I am in favor.
> >
> >+1 Ma
>
> I understand the motivation, but IIUC it's definitely an API change that
> could break existing scripts, which is against our normal policy.
>
> Why not make the flag mean the contrary, i.e. include null values ? Then
> it wouldn't break anything...
>
> I'm pretty sure that most people exporting data via r.out.xyz would
> expect null values to be excluded...
>
r.out.xyz export XY and their values. When there is no value, nothing is
exported. This is the correct counterpart for r.in.xyz where you get NULLs
for cells without any input XY(Z).
I agree with Moritz. Adding a flag to export NULLs looks like the best way.
It doesn't break API nor expectations. NULLs simply not being there seems
like a better default here.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20161206/37d5cdfb/attachment-0001.html>
More information about the grass-dev
mailing list