Hello,
The scenario is: the user opens a large Lidar file, changes the
classification labels of a small number of points and save the changes
to the file. When the Lidar file is huge, it is time-consuming to
output all the points. So it would be better if only the modified
points are updated in
On Jan 6, 2012, at 12:16 PM, Hongwei Shen wrote:
Hello,
The scenario is: the user opens a large Lidar file, changes the
classification labels of a small number of points and save the changes
to the file. When the Lidar file is huge, it is time-consuming to
output all the points. So it
All,
I am pleased to announce the release of libLAS 1.7.0. libLAS 1.7.0 signifies
libLAS going into maintenance mode from this point forward unless someone
else steps forward to bring momentum to it. libLAS 1.7.0 has limited support
for LAS 1.3, and no support for LAS 1.4. If someone wishes
Thank you for the answer, Howard.
I'll check if I can add this support.
Thanks,
Hongwei
On Fri, Jan 6, 2012 at 1:47 PM, Howard Butler hobu@gmail.com wrote:
On Jan 6, 2012, at 12:16 PM, Hongwei Shen wrote:
Hello,
The scenario is: the user opens a large Lidar file, changes the
If you do work to add this, you'll probably just need to add a seek() method to
the liblas::Writer class (and underlying implementation classes) that positions
the stream. After that liblas::Writer::WritePoint() should overwrite the data,
though you may want to do some header checks to make
