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 <[email protected]> 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 <[email protected]> wrote: > The LiDAR tools I was thinking of is PDAL. > > 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
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
