Hi there,<br><br><div>> lidarformat (they even use libLAS :) ) is pretty much exactly the direction I'd like to go except 1) LGPL instead of BSD and 2) source code layout.<div class="gmail_quote"><div>What do you mean by "code layout" ?</div>
<div><br></div><div>> Ok, I'm not so concerned about license at all as long as there is a collaborative project behind it with some weight. I don't know if lidarformat (bad name IMO) has that yet.<font color="#888888"><br>
</font></div><div>Actually there is not a strong collaborative project behind lidarformat, and lidarformat *is* a poor name that I would like to change.</div><div><br></div><div>Lidarformat is designed to handle point clouds as vector<Point> where Point is a data structure known only at runtime. This structure is described in an xml file (<a href="http://code.google.com/p/fullanalyze/wiki/UserGuidePointClouds#Point_clouds_file_formats" target="_blank">here</a> is an example). A few templates are used to have almost the same performances as if the point cloud was implemented as a real vector, but some parts still need to be refractored (especially the iterators should be based on boost iterator facade instead of being hand-coded).</div>
<div>Of course LAS is one of the format that should be supported by the library, but it is currently broken.</div><div><br></div><div>Is that what you have in mind for liblas ?</div><div><br></div><div>Actually lidarformat is the base of another project dedicated to full-waveform lidar data management and visualization (<a href="http://code.google.com/p/fullanalyze/" target="_blank">Fullanalyze</a>), but the fullwave format is still a draft mainly adapted to Riegl data. So it's still a part of the FullAnalyze project and is not available as a standalone library. I don't know if it would fit with Leica data and LAS 1.3. </div>
<div><br></div><div>Best regards,</div><div>Adrien</div><div><font color="#888888"><br></font></div></div></div>