Hi there, > 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. What do you mean by "code layout" ?
> 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. Actually there is not a strong collaborative project behind lidarformat, and lidarformat *is* a poor name that I would like to change. 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 (here<http://code.google.com/p/fullanalyze/wiki/UserGuidePointClouds#Point_clouds_file_formats>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). Of course LAS is one of the format that should be supported by the library, but it is currently broken. Is that what you have in mind for liblas ? Actually lidarformat is the base of another project dedicated to full-waveform lidar data management and visualization (Fullanalyze<http://code.google.com/p/fullanalyze/>), 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. Best regards, Adrien
_______________________________________________ Liblas-devel mailing list Liblas-devel@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/liblas-devel
