[GRASS-dev] v.in.lidar: store return or class as category

[Vaclav Petras]

Dear all,

in r66343 I've added the option to store return or class as category. This
is much faster than storing them as attributes. Also, the further
processing will be faster supposing that the subsequent workflow can use
categories in the same way as attributes.

Return and class can be stored at the same time, each in its own layer,
otherwise they would get mixed. There is no protection against specifying
same layer for all, perhaps there should be.

Please note that this change lacks test and documentation. The same still
applies to two recent changes in r.in.lidar and v.in.lidar.

Vaclav


v.in.lidar: store return and class as cats or store no cats
https://trac.osgeo.org/grass/changeset/66343

v.in.lidar: use unsigned long long for counting point counts
https://trac.osgeo.org/grass/changeset/66255

v.in.lidar: decimation (skip, preserve, offset, limit)
https://lists.osgeo.org/pipermail/grass-dev/2015-September/076275.html

r.in.lidar: height above ground
https://lists.osgeo.org/pipermail/grass-dev/2015-September/076147.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20150926/761bf3c8/attachment.html>