On Tue, Dec 6, 2016 at 9:15 PM, Markus Neteler <nete...@osgeo.org> wrote: > On Tue, Dec 6, 2016 at 7:34 PM, Vaclav Petras <wenzesl...@gmail.com> wrote: >> On Tue, Dec 6, 2016 at 12:34 PM, Moritz Lennert > ... >>> Why not make the flag mean the contrary, i.e. include null values ? Then >>> it wouldn't break anything...
ok >>> 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). > > Ah I see, they kind of belong together. > >> 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. ok. I have submitted a new -i flag to include no data values (r70017). This can be used for t.rast.out.xyz and backported for 7.2.1. Markus _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
