[pdal] PDAL compilation (MSVC9)

[Michael P. Gerlek]

OK, so if you just want to load (all) the points into memory, you can do two things:

- create a PointBuffer equal in size to the number of points in the file, and then just do one read() into it

- create your own storage system; then, read in the points one chunk at a time, and copy the points from the chunk-sized PointBuffer into your own storage area

Is that what you're looking for?

Some lidar files are VERY large, and it might not be practical to keep all the points in RAM.  In this case, you'd want to use some sort of thinning or decimating filter in the chain, so as to intelligently lessen the number of points you're managing and displaying.

_mpg


-----Original Message-----
From: Jerome Chatillon [mailto:j.chatillon at terraimaging.nl] 
Sent: Monday, November 28, 2011 8:44 AM
To: mpg at flaxen.com
Cc: 'Howard Butler'; pdal at lists.osgeo.org
Subject: Re: [pdal] PDAL compilation (MSVC9)

Hi,

My tool is to determinate the calibration parameters with a clear and pedagogic user interface.
- load the points and the trajectography in the memory
- display points as a picture
- make some cross sections
- Display the cross sections
- display a parameters button and 'doublespinbox'(using QT)
- change settings and see the result directly in the views
- save the settings, and apply them on all data (of the same flight of course :P )

A lidar point editor may also be interested to store the points info the memory. No ?

thanks.

Jerome Chatillon

TerraImaging
Groenewoudsedijk 40
3528 BK  Utrecht
The Netherlands
tel: +31 (0)30-686 616 7
fax: +31 (0)30-686 616 6
email: j.chatillon at terraimaging.nl


On 28/11/2011 17:26, Michael P. Gerlek wrote:
> Jerome-
>
>> What the best PDAL pratice to store all the data into memory ?
> What do you mean "store into memory"?  PDAL is designed to process data in chunks, so as not to require loading the whole file in memory...
>
> Can you explain more, or give us an idea what your intended workflow is?
>
> _mpg
>
>