<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 27, 2008, at 7:37 PM, Gennady Khokhorin wrote:</div><br><blockquote type="cite"><div>Hello, Mateusz.<br>Have couple questions kind of about library design.<br><br>Did receive you liblas Beta 1 announce from one of my college:<br><a href="http://lidarbb.cr.usgs.gov/index.php?showtopic=3700&pid=4622&st=0&#entry4622">http://lidarbb.cr.usgs.gov/index.php?showtopic=3700&pid=4622&st=0&#entry4622</a></div></blockquote><div><br></div><div>Hi Gennady,</div><div><br></div><div>I'm glad to hear.</div><div><br></div><br><blockquote type="cite"><div>It is a great news that las is finally linked to GDAL. I'm using a lot<br>of GDAL vector, raster functionality building stand-along apps.</div></blockquote><div><br></div><div><br></div><div>Yes, libLAS can link to GDAL but it's optional functionality.</div><div>So, those who are not interested in using GDAL and OGR features are not required to link</div><div>against GDAL binaries.</div><br><blockquote type="cite"><div> So, as far as liblas is part of GDAL what the purpose of lasmerge<br>routine?</div></blockquote><div><br></div><div>Looks like a small misunderstanding.</div><div>libLAS is not a part of GDAL, but a standalone library + set of utilities.</div><div>libLAS can use GDAL as a client, means you can link libLAS against GDAL</div><div>binaries to be able to use some of GDAL features, but this is optional.</div><br><blockquote type="cite"><div>Should it be part of GDAL syntax like "ogr2ogr -append.." ?</div></blockquote><div><br></div><div>According to the above, I'd answer: no, it shouldn't.</div><div>lasmerge is a tool specialized in processing ASPRS LAS data.</div><div>For merging LAS files, it is not necessary to involve translation between LAS data</div><div>model and GDAL data model. IMHO, it would be unnecessary overhead.</div><div><br></div><blockquote type="cite"><div><span class="Apple-style-span" style="-webkit-text-stroke-width: -1; ">In the past I did create driver for las (ASPRS), bin (TerraScan), cmp</span></div></blockquote><blockquote type="cite"><div>(Optech), xyz (text) lidar data formats with multiple operations:</div></blockquote><blockquote type="cite"><div>logical (merge, split), spatial<br>(shift, reproject, VLR georeference), extract data (by time, by prizm).</div></blockquote><div><br></div>Sounds very interesting.</div><div><br><blockquote type="cite"><div>I'm wonder what are team's plans to extend liblas to create such<br>features? Or it will be up to GDAL?</div></blockquote><blockquote type="cite"><div></div></blockquote></div><div><br></div><div>As I can tell, we are going to complement current functionality of the libLAS library and utilities</div><div>with new features like the operations you're listing above, if not implemented yet.</div><div>The libLAS is a standalone project, not a part of GDAL, so its roadmap is up to us.</div><div><br></div><div>If you would be willing to contribute some features or share implementation of the features listed above,</div><div>as an improvement to the current state of libLAS, you're strongly welcome.</div><div><br></div><div>Greetings</div><div> <div><div><div><div>-- </div><div>Mateusz Loskot, <a href="http://mateusz.loskot.net">http://mateusz.loskot.net</a></div><div>Charter Member of OSGeo, <a href="http://osgeo.org">http://osgeo.org</a></div><div><br></div></div></div><br></div><br> </div><br></body></html>