On Feb 8, 2012, at 12:41 PM, Hongwei Shen wrote:
To solve this problem, I think we can add a member variable,
m_AbsoluteIndex, to liblas::Point. Then we can also store the absolute index
of the point in liblas::detail::ReadNextPoint() .
I think I'm ok with this as long as the tests
Hi,
Make sure you disable the feature when the file is laszipped. There is
*no* way to add this. However, we could - in theory - support the
appending of points to an exsiting LAZ file.
cheers,
martin
On Fri, Feb 10, 2012 at 8:49 AM, Howard Butler hobu@gmail.com wrote:
On Feb 8, 2012, at
On Feb 10, 2012, at 11:10 AM, Martin Isenburg wrote:
Hi,
Make sure you disable the feature when the file is laszipped. There is
*no* way to add this. However, we could - in theory - support the
appending of points to an exsiting LAZ file.
Yes, definitely. The Update class will not be
Hello,
My work on liblas::Writer::WritePoint() was delayed by other tasks and I
just resume it recently.
Now I implemented what we talked about (but with some small changes). I
tested it and it worked in unit test. However, in real cases to use it,
we still have two problems to solve.
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
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
