<div dir="ltr">Sorry about that,<div>I appreciate all of the great work done on creating the liblas,laspy, and pdal software. As an occasional python scripter, I'm still trying to work my way through the documentation.</div>
<div><br></div><div>Doug</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 4, 2014 at 12:26 PM, Newcomb, Doug <span dir="ltr"><<a href="mailto:doug_newcomb@fws.gov" target="_blank">doug_newcomb@fws.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Howard,<div>So, which would you use for large lidar data files (3 billion + points) that you want to alter with information from an elevation raster?</div>
<div>Laspy, trying to work around it's desire to load all of the points in memory at the same time, or the plang option in pdal with pipelines. <br>
</div><div><br></div><div>Doug <br></div><div><br></div><div> </div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Wed, Jan 29, 2014 at 12:46 PM, Howard Butler <span dir="ltr"><<a href="mailto:howard@hobu.co" target="_blank">howard@hobu.co</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><br>
On Jan 29, 2014, at 11:26 AM, Larry Shaffer <<a href="mailto:larrys@dakotacarto.com" target="_blank">larrys@dakotacarto.com</a>> wrote:<br>
<br>
> Hello,<br>
><br>
> First off, thanks for all your work on PDAL. I especially look forward to trying out the new Postgres/PostGIS integration.<br>
<br>
Paul Ramsey did all the Postgres work. I have done some work recently to speed up the Postgresql stuff with some surprising results. I hope to cook up an email to the list or update the pg docs for posterity in the future on that item once I'm done.<br>
<br>
><br>
> After a recent (and ongoing) discussion about somehow integrating LiDAR data into QGIS on the QGIS-dev mailing list [0], I went about revamping the minimal Mac Homebrew PDAL formula [1] to include many more options [2] and added formulae for Hexer [3] and Nitro [4].<br>
<br>
I have joined the list and when more questions come up about PDAL, I'd be happy to join in. I must admit that PDAL is intended to be useful for GUI developers, but only in the sense of a data access/translation and light duty processing library. In practice, it is very possible there are sticky points for people looking to use PDAL inside of GUI apps due to the fact that most of my development is focused on processing/translation pipelines rather than feeding data to a window. That said, I hope it to be useful for those tasks, and as more people jump in and start using PDAL, I expect that aspect of it to get beefier.<br>
<br>
I read on the lists logs about some questions about libLAS, LASlib, and PDAL. I hope to clarify some of that murkiness. PDAL is the successor to libLAS, which itself was a reaction to LASlib not being available under an open source license at the time. libLAS is essentially a maintenance-only library at this time, and PDAL contains nearly all the functionality that libLAS had, except for the ability to manipulate LAS data with Python. That feature's now covered much better by <a href="http://www.laspy.org" target="_blank">http://www.laspy.org</a>. PDAL is very much intended to be like GDAL except in the point cloud format domain. LASlib is now straight LGPL and has a fantastic toolbox of functionality that is poorly integrated into existing systems. It also has no release mechanism, github repository, or other open source accouterments. PDAL aims to stay out of LASlib's niche to provide data access and format translation as its primary capability.<br>
<br>
><br>
> Currently, Hexer and Nitro do not have any tagged releases. This presents a roadblock for submitting their formulae upstream to the main Homebrew repository (aka a 'tap'), since one of the 'acceptable formula' criteria is that the formula not be HEAD-only. From the CMakeLists.txt for Hexer I see it is set to a 1.0.1 version, while Nitro appears to be at 2.7 (?).<br>
<br>
PDAL is *very* close to a 1.0.0 release. I have a few more items that I want to clean up before I release 1.0.0 and signal that I'm interested in folks coming along for real and kicking the tires. I appreciate the PDAL homebrew update. I had been meaning to do that but have't had time yet.<br>
<br>
I'll create a hexer 1.0.1 tag today and make sure that the CMake configuration is up to date with it.<br>
<br>
Nitro is not something that is generally needed. Nitro is for reading NITF files, and there is a DoD lidar format that stores LAS files inside of NITF containers (it is as awful as you think it would be). The PDAL Nitro configuration is for that specific format. I don't know how generally useful it would be. The Nitro fork that I maintain is due to the fact that the maintainer wasn't interested in either collaborating on github or in cmake configuration for the library. I do not wish to materially fork the library in any way except to make the integration easier with my own CMake-based metabuild system.<br>
<br>
<br>
> Could you possibly tag both of those repos so that those formula can be submitted upstream?<br>
><br>
><br>
> Btw, any input to the QGIS-dev mailing list on how PDAL might be used with QGIS would be appreciated. The three main options would be: via GDAL support, as a separate data provider, and/or utilizing its command line utilities via the Processing plugin provider.<br>
<br>
I'll be happy to answer a question on that via the qgis list.<br>
<br>
><br>
> The Processing plugin provider is straightforward to do, as it only requires modest Python scripting to implement [5]. LASTools and Fusion have been incorporated already [6], but they are basically Windows-only utilities, having very limited functionality on other platforms.<br>
><br>
><br>
> [0] <a href="http://osgeo-org.1560.x6.nabble.com/Lidar-data-into-QGIS-td5100547.html" target="_blank">http://osgeo-org.1560.x6.nabble.com/Lidar-data-into-QGIS-td5100547.html</a><br>
><br>
> [1] <a href="https://github.com/Homebrew/homebrew/blob/master/Library/Formula/pdal.rb" target="_blank">https://github.com/Homebrew/homebrew/blob/master/Library/Formula/pdal.rb</a><br>
> [2] <a href="https://github.com/dakcarto/homebrew-osgeo4mac/blob/master/Formula/pdal.rb" target="_blank">https://github.com/dakcarto/homebrew-osgeo4mac/blob/master/Formula/pdal.rb</a> (work in progress)<br>
> [3] <a href="https://github.com/dakcarto/homebrew-osgeo4mac/blob/master/Formula/hexer.rb" target="_blank">https://github.com/dakcarto/homebrew-osgeo4mac/blob/master/Formula/hexer.rb</a><br>
> [4] <a href="https://github.com/dakcarto/homebrew-osgeo4mac/blob/master/Formula/nitro.rb" target="_blank">https://github.com/dakcarto/homebrew-osgeo4mac/blob/master/Formula/nitro.rb</a><br>
><br>
> [5] <a href="https://github.com/qgis/QGIS/tree/master/python/plugins/processing/exampleprovider" target="_blank">https://github.com/qgis/QGIS/tree/master/python/plugins/processing/exampleprovider</a><br>
> [6] <a href="https://github.com/qgis/QGIS/tree/master/python/plugins/processing/lidar" target="_blank">https://github.com/qgis/QGIS/tree/master/python/plugins/processing/lidar</a><br>
><br>
> Best regards,<br>
><br>
> Larry Shaffer<br>
> Dakota Cartography<br>
> Black Hills, South Dakota<br>
<br>
<br></div></div>_______________________________________________<br>
pdal mailing list<br>
<a href="mailto:pdal@lists.osgeo.org" target="_blank">pdal@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pdal" target="_blank">http://lists.osgeo.org/mailman/listinfo/pdal</a><span class="HOEnZb"><font color="#888888"><br></font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br>
<br clear="all"><div><br></div>-- <br><div>Doug Newcomb</div><div>USFWS</div>
<div>Raleigh, NC</div><div>919-856-4520 ext. 14 <a href="mailto:doug_newcomb@fws.gov" target="_blank">doug_newcomb@fws.gov</a></div><div>---------------------------------------------------------------------------------------------------------</div>
<div>The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.</div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Doug Newcomb</div><div>USFWS</div><div>Raleigh, NC</div><div>919-856-4520 ext. 14 <a href="mailto:doug_newcomb@fws.gov" target="_blank">doug_newcomb@fws.gov</a></div>
<div>---------------------------------------------------------------------------------------------------------</div><div>The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.</div>
</div>