[GRASS-dev] grass 7.2 planning

[Michael Barton]

Vaclav,

I agree with all of your points. There was a little discussion about recoding GRASS LiDAR tools to use PDAL instead of libLAS. I am just wondering if that has gone anywhere or not.

libLAS is missing some of the most sophisticated filtering routines found in the non-open-source LAStools. PDAL seems to have them according to the web site but I admit that I have not yet tried them. I might have time to do so in the coming weeks.

Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu



On Apr 30, 2016, at 10:26 AM, Vaclav Petras <wenzeslaus at gmail.com<mailto:wenzeslaus at gmail.com>> wrote:

Hi Michael,

I'm currently looking at the lidar-related functionality, so here is some info.

On Sat, Apr 30, 2016 at 12:28 PM, Michael Barton <Michael.Barton at asu.edu<mailto:Michael.Barton at asu.edu>> wrote:
Related to this, is there a plan to replace liblas with the new Python alternative (the name escapes me at the moment)? This would further simplify making robust LiDAR tools available in GRASS

On Sat, Apr 30, 2016 at 12:36 PM, Michael Barton <Michael.Barton at asu.edu<mailto:Michael.Barton at asu.edu>> wrote:
The LiDAR tools I was thinking of is PDAL.

http://www.pdal.io<http://www.pdal.io/>

You can try compile GRASS with PDAL right now. Just note that PDAL is not a drop-in replacement for libLAS and so far the PDAL functionality is available only through special module v.in.pdal. See #2732 [1] for details.


I guess it's C++.

Yes, it's C++ not C or Python and it currently does not have C API, so it might be even harder to connect in general. The basic functionality newly (since release 1.2) does not depend on Boost but the new C++ (I think C++11) is needed. It is important to note that most of the fancy functionality (like ground detection) is provided through another dependency, PCL (http://pointclouds.org/), which is a large point cloud processing library which depends on Boost (if I recall correctly).

But it's open source without some of the legal and compiling issues of LAStools.

With the current GRASS source code we are able to use only libLAS (http://www.liblas.org/), not LAStools (https://rapidlasso.com/lastools/) [2].

Best,
Vaclav


[1] https://trac.osgeo.org/grass/ticket/2732
[2] https://lists.osgeo.org/pipermail/grass-dev/2015-September/076318.html


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20160430/3c8e6e68/attachment.html>