[GRASS-dev] liblas, laslib, lastools, anaconda, and GRASS

So here is an email chain with the conda-forge maintainers of the LAStools package about liblas in Anaconda which is not liblas, but actually laslib misnamed. This is why there is no liblas-config. Since liblas.dylib is installed with the lastools package in Anaconda, I asked if they might also create a liblas-config file (not currently installed) so that GRASS can compile against it for LiDAR support

The upshot is that LAStools (and laslib, misnamed as liblas) can be installed through Anaconda, but not the packages we know as libLAS. Also, it seems like libLAS is no longer maintained and superseded by LASlib and related tools. I have an email from William Kyngesburye (copied) from several years ago suggesting that GRASS lidar support could potentially use LASlib instead of liblas. But I don’t know what that would involve.

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

From: Sam Gillingham <notifications@github.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 5:19:45 PM MST

To: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com>

Cc: Michael Barton <c.michael.barton@gmail.com>, Author <author@noreply.github.com>

Reply-To: conda-forge/lastools-feedstock <reply+0088d5afff3e421a9fe599968afaa891e0ddd2cfca2dc97292cf0000000116a5cea192a169ce11d01e0b@reply.github.com>

Yes. Feel free to talk to the lastools maintainer about this confusing situation…

From: Michael Barton <c.michael.barton@gmail.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 5:08:45 PM MST

To: conda-forge/lastools-feedstock <reply+0088d5afb432f05c9506e1ef9f0d5fb3c795a0bc4ba02c0192cf0000000116a5bd8792a169ce11d01e0b@reply.github.com>

Cc: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com>, Author <author@noreply.github.com>

OK. This is good to know. So the file that is named liblas.dylib in the conda package of lastools is in fact laslib?

Michael

From: Sam Gillingham <notifications@github.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 4:06:47 PM MST

To: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com>

Cc: Michael Barton <c.michael.barton@gmail.com>, Author <author@noreply.github.com>

Reply-To: conda-forge/lastools-feedstock <reply+0088d5afb432f05c9506e1ef9f0d5fb3c795a0bc4ba02c0192cf0000000116a5bd8792a169ce11d01e0b@reply.github.com>

Yes the library file is called the same, but the contents are different. In an early version of this recipe i renamed the files to be clear, but that broke other software…

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 2:43:46 PM MST

To: conda-forge/lastools-feedstock <reply+0088d5af64024b45f60988c0b8f9368cac4eee6363df9a7492cf0000000116a57eb892a169ce11d01e0b@reply.github.com>

Cc: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com>, Author <author@noreply.github.com>

Indeed. But the anaconda package installs liblas, not laslib.

Michael

From: Daniel Clewley <notifications@github.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 11:38:55 AM MST

To: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com>

Cc: Michael Barton <c.michael.barton@gmail.com>, Author <author@noreply.github.com>

Reply-To: conda-forge/lastools-feedstock <reply+0088d5af64024b45f60988c0b8f9368cac4eee6363df9a7492cf0000000116a57eb892a169ce11d01e0b@reply.github.com>

LASlib isn’t a drop in replacement for libLAS (different function names for one thing) you’d have to modify the GRASS code if you wanted to use LASlib.

From: Michael Barton <c.michael.barton@gmail.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 8:59:25 AM MST

To: conda-forge/lastools-feedstock <reply+0088d5afde4903f9a76a7de6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0b@reply.github.com>

Cc: Vaclav Petras <wenzeslaus@gmail.com>, Eric Hutton <hutton.eric@gmail.com>

Thanks for the quick response Dan,

I have indeed seen both the open source libLAS code and the LAStools site. The thing is that the Anaconda package installs liblas.dylib into …/lib as well as command line tools in …/bin with the same names as the tools built with the libLAS code. A couple years ago, a colleague on the GRASS project looked into the (then new) LAStools distribution and thought that it could be a drop in replacement for libLAS code. So I was hoping to try this with the Anaconda build. But we need a liblas-config to do it. I’m copying a couple colleagues on GRASS who also might be able to help with this.

Cheers
Michael

From: Daniel Clewley <notifications@github.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 12:27:16 AM MST

To: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com>

Cc: Michael Barton <c.michael.barton@gmail.com>, Author <author@noreply.github.com>

Reply-To: conda-forge/lastools-feedstock <reply+0088d5afde4903f9a76a7de6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0b@reply.github.com>

This is the feedstock for LAStools and LASlib not libLAS which I believe is the library GRASS can be compiled against. The libLAS website has a page explaining the relationship between the two: https://www.liblas.org/lastools.html. The two libraries provide similar functionality but aren’t compatible.

From the libLAS website “As of 2014, libLAS has been almost entirely superceded by Martin Isenburg‘s LASlib library.”

More specifically this feedstock builds a fork of LAStools (https://github.com/gillins/LAStools/) which adds CMake build scrips. The standard LAStools doesn’t provide a liblas-config file, we could add one to the fork this is being build against but I think this would only make things between the two libraries more confusing.

I’m going to mark this as closed but if I am incorrect and it is LASlib you need please reopen for further discussion.

On Wed, Feb 21, 2018 at 7:43 PM, Michael Barton <Michael.Barton@asu.edu>
wrote:

So here is an email chain with the conda-forge maintainers of the LAStools
package about liblas in Anaconda which is not liblas, but actually laslib
misnamed. This is why there is no liblas-config. Since liblas.dylib is
installed with the lastools package in Anaconda, I asked if they might also
create a liblas-config file (not currently installed) so that GRASS can
compile against it for LiDAR support

Since that's the case, it doesn't seem that just liblas-config would solve
it. Daniel Clewley says "LASlib isn't a drop in replacement for libLAS
(different function names for one thing) you'd have to modify the GRASS
code if you wanted to use LASlib." Perhaps simpler than changing it to
PDAL, but I'm not sure if worth it. But I haven't seen the LASlib API.

The upshot is that LAStools (and laslib, misnamed as liblas) can be
installed through Anaconda, but not the packages we know as libLAS. Also,
it seems like libLAS is no longer maintained and superseded by LASlib and
related tools.

So far various people kept libLAS alive:

https://github.com/libLAS/libLAS/commits/master

But the situation is not ideal.

I have an email from William Kyngesburye (copied) from several years ago
suggesting that GRASS lidar support could potentially use LASlib instead of
liblas. But I don't know what that would involve.

As I said above, I dpn't know the LASlib API, but my guess is that it would
be possible, but I think the question is if somebody can work on it.

From what I understood replacement for libLAS is PDAL, but definitively not

a drop-in one. I was not able to dedicate any time to it lately except for
accepting patch from felixg few days ago which makes v.in.pdal work with
current PDAL. Also I have been told that PDAL package for Anaconda is
coming soon (in days).

Best,
Vaclav

MIchael

...

*From: *Daniel Clewley <notifications@github.com>
*Subject: **Re: [conda-forge/lastools-feedstock] can liblas-config be
included in package (#3)*
*Date: *February 21, 2018 at 11:38:55 AM MST
*To: *conda-forge/lastools-feedstock <lastools-feedstock@noreply.gi
thub.com>
*Cc: *Michael Barton <c.michael.barton@gmail.com>, Author <
author@noreply.github.com>
*Reply-To: *conda-forge/lastools-feedstock <reply+0088d5af64024b45f60988c
0b8f9368cac4eee6363df9a7492cf0000000116a57eb892a169ce11d01e0
b@reply.github.com>

LASlib isn't a drop in replacement for libLAS (different function names
for one thing) you'd have to modify the GRASS code if you wanted to use
LASlib.

*From: *Michael Barton <c.michael.barton@gmail.com>
*Subject: **Re: [conda-forge/lastools-feedstock] can liblas-config be
included in package (#3)*
*Date: *February 21, 2018 at 8:59:25 AM MST
*To: *conda-forge/lastools-feedstock <reply+0088d5afde4903f9a76a7de
6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0
b@reply.github.com>
*Cc: *Vaclav Petras <wenzeslaus@gmail.com>, Eric Hutton <
hutton.eric@gmail.com>

Thanks for the quick response Dan,

I have indeed seen both the open source libLAS code and the LAStools site.
The thing is that the Anaconda package installs liblas.dylib into ../lib as
well as command line tools in ../bin with the same names as the tools built
with the libLAS code. A couple years ago, a colleague on the GRASS project
looked into the (then new) LAStools distribution and thought that it could
be a drop in replacement for libLAS code. So I was hoping to try this with
the Anaconda build. But we need a liblas-config to do it. I'm copying a
couple colleagues on GRASS who also might be able to help with this.

Cheers
Michael

*From: *Daniel Clewley <notifications@github.com>
*Subject: **Re: [conda-forge/lastools-feedstock] can liblas-config be
included in package (#3)*
*Date: *February 21, 2018 at 12:27:16 AM MST
*To: *conda-forge/lastools-feedstock <lastools-feedstock@noreply.gi
thub.com>
*Cc: *Michael Barton <c.michael.barton@gmail.com>, Author <
author@noreply.github.com>
*Reply-To: *conda-forge/lastools-feedstock <reply+0088d5afde4903f9a76a7de
6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0
b@reply.github.com>

This is the feedstock for LAStools <https://github.com/LAStools/LAStools&gt; and
LASlib not libLAS <https://github.com/libLAS/libLAS&gt; which I believe is
the library GRASS can be compiled against. The libLAS website has a page
explaining the relationship between the two: https://www.liblas.org/la
stools.html. The two libraries provide similar functionality but aren't
compatible.

From the libLAS website "As of 2014, libLAS has been almost entirely
superceded by Martin Isenburg‘s LASlib library."

More specifically this feedstock builds a fork of LAStools (
https://github.com/gillins/LAStools/) which adds CMake build scrips. The
standard LAStools doesn't provide a liblas-config file, we could add one
to the fork this is being build against but I think this would only make
things between the two libraries more confusing.

I'm going to mark this as closed but if I am incorrect and it is LASlib
you need please reopen for further discussion.

Yes pdal is a good possibility. But we neither yet have pdal replacements for the lidar tools nor pdal in anaconda. I don’t know which is the better near term solution for lidar and which would be easier to to implement.

Michael

···

On Wed, Feb 21, 2018 at 7:43 PM, Michael Barton <Michael.Barton@asu.edu> wrote:

So here is an email chain with the conda-forge maintainers of the LAStools package about liblas in Anaconda which is not liblas, but actually laslib misnamed. This is why there is no liblas-config. Since liblas.dylib is installed with the lastools package in Anaconda, I asked if they might also create a liblas-config file (not currently installed) so that GRASS can compile against it for LiDAR support

Since that’s the case, it doesn’t seem that just liblas-config would solve it. Daniel Clewley says “LASlib isn’t a drop in replacement for libLAS (different function names for one thing) you’d have to modify the GRASS code if you wanted to use LASlib.” Perhaps simpler than changing it to PDAL, but I’m not sure if worth it. But I haven’t seen the LASlib API.

The upshot is that LAStools (and laslib, misnamed as liblas) can be installed through Anaconda, but not the packages we know as libLAS. Also, it seems like libLAS is no longer maintained and superseded by LASlib and related tools.

So far various people kept libLAS alive:

https://github.com/libLAS/libLAS/commits/master

But the situation is not ideal.

I have an email from William Kyngesburye (copied) from several years ago suggesting that GRASS lidar support could potentially use LASlib instead of liblas. But I don’t know what that would involve.

As I said above, I dpn’t know the LASlib API, but my guess is that it would be possible, but I think the question is if somebody can work on it.

From what I understood replacement for libLAS is PDAL, but definitively not a drop-in one. I was not able to dedicate any time to it lately except for accepting patch from felixg few days ago which makes v.in.pdal work with current PDAL. Also I have been told that PDAL package for Anaconda is coming soon (in days).

Best,

Vaclav

MIchael

From: Daniel Clewley <notifications@github.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 11:38:55 AM MST

To: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com>

Cc: Michael Barton <c.michael.barton@gmail.com>, Author <author@noreply.github.com>

Reply-To: conda-forge/lastools-feedstock <reply+0088d5af64024b45f60988c0b8f9368cac4eee6363df9a7492cf0000000116a57eb892a169ce11d01e0b@reply.github.com>

LASlib isn’t a drop in replacement for libLAS (different function names for one thing) you’d have to modify the GRASS code if you wanted to use LASlib.

From: Michael Barton <c.michael.barton@gmail.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 8:59:25 AM MST

To: conda-forge/lastools-feedstock <reply+0088d5afde4903f9a76a7de6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0b@reply.github.com>

Cc: Vaclav Petras <wenzeslaus@gmail.com>, Eric Hutton <hutton.eric@gmail.com>

Thanks for the quick response Dan,

I have indeed seen both the open source libLAS code and the LAStools site. The thing is that the Anaconda package installs liblas.dylib into …/lib as well as command line tools in …/bin with the same names as the tools built with the libLAS code. A couple years ago, a colleague on the GRASS project looked into the (then new) LAStools distribution and thought that it could be a drop in replacement for libLAS code. So I was hoping to try this with the Anaconda build. But we need a liblas-config to do it. I’m copying a couple colleagues on GRASS who also might be able to help with this.

Cheers
Michael

From: Daniel Clewley <notifications@github.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 12:27:16 AM MST

To: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com>

Cc: Michael Barton <c.michael.barton@gmail.com>, Author <author@noreply.github.com>

Reply-To: conda-forge/lastools-feedstock <reply+0088d5afde4903f9a76a7de6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0b@reply.github.com>

This is the feedstock for LAStools and LASlib not libLAS which I believe is the library GRASS can be compiled against. The libLAS website has a page explaining the relationship between the two: https://www.liblas.org/lastools.html. The two libraries provide similar functionality but aren’t compatible.

From the libLAS website “As of 2014, libLAS has been almost entirely superceded by Martin Isenburg‘s LASlib library.”

More specifically this feedstock builds a fork of LAStools (https://github.com/gillins/LAStools/) which adds CMake build scrips. The standard LAStools doesn’t provide a liblas-config file, we could add one to the fork this is being build against but I think this would only make things between the two libraries more confusing.

I’m going to mark this as closed but if I am incorrect and it is LASlib you need please reopen for further discussion.

A couple of notes:

  • Brad Chambers from the PDAL project has put forward an initial Anaconda build recipe that is waiting to be merged.
  • I have updated the libLAS website to tell people to use PDAL if they’re starting fresh
  • Sorry about the naming thing.

I hope enough developer attention can get GRASS caught up to PDAL for on-the-way-in data ingest and processing. PDAL brings a lot of filtering and processing possibilities that just aren’t available in libLAS. Most notably, it supports the latest ASPRS LAS 1.4 (and LAZ) specification, which libLAS does not, in addition to about 15 other formats. PDAL is also actively developed, patched, and improved. libLAS has not been in 5+ years except for critical outside patches.

Use PDAL :slight_smile:

Howard

···

On Wed, Feb 21, 2018 at 7:43 PM, Michael Barton <Michael.Barton@asu.edu> wrote:

So here is an email chain with the conda-forge maintainers of the LAStools package about liblas in Anaconda which is not liblas, but actually laslib misnamed. This is why there is no liblas-config. Since liblas.dylib is installed with the lastools package in Anaconda, I asked if they might also create a liblas-config file (not currently installed) so that GRASS can compile against it for LiDAR support

Since that’s the case, it doesn’t seem that just liblas-config would solve it. Daniel Clewley says “LASlib isn’t a drop in replacement for libLAS (different function names for one thing) you’d have to modify the GRASS code if you wanted to use LASlib.” Perhaps simpler than changing it to PDAL, but I’m not sure if worth it. But I haven’t seen the LASlib API.

The upshot is that LAStools (and laslib, misnamed as liblas) can be installed through Anaconda, but not the packages we know as libLAS. Also, it seems like libLAS is no longer maintained and superseded by LASlib and related tools.

So far various people kept libLAS alive:

https://github.com/libLAS/libLAS/commits/master

But the situation is not ideal.

I have an email from William Kyngesburye (copied) from several years ago suggesting that GRASS lidar support could potentially use LASlib instead of liblas. But I don’t know what that would involve.

As I said above, I dpn’t know the LASlib API, but my guess is that it would be possible, but I think the question is if somebody can work on it.

From what I understood replacement for libLAS is PDAL, but definitively not a drop-in one. I was not able to dedicate any time to it lately except for accepting patch from felixg few days ago which makes v.in.pdal work with current PDAL. Also I have been told that PDAL package for Anaconda is coming soon (in days).

Best,

Vaclav

MIchael

From: Daniel Clewley <notifications@github.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 11:38:55 AM MST

To: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com>

Cc: Michael Barton <c.michael.barton@gmail.com>, Author <author@noreply.github.com>

Reply-To: conda-forge/lastools-feedstock <reply+0088d5af64024b45f60988c0b8f9368cac4eee6363df9a7492cf0000000116a57eb892a169ce11d01e0b@reply.github.com>

LASlib isn’t a drop in replacement for libLAS (different function names for one thing) you’d have to modify the GRASS code if you wanted to use LASlib.

From: Michael Barton <c.michael.barton@gmail.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 8:59:25 AM MST

To: conda-forge/lastools-feedstock <reply+0088d5afde4903f9a76a7de6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0b@reply.github.com>

Cc: Vaclav Petras <wenzeslaus@gmail.com>, Eric Hutton <hutton.eric@gmail.com>

Thanks for the quick response Dan,

I have indeed seen both the open source libLAS code and the LAStools site. The thing is that the Anaconda package installs liblas.dylib into …/lib as well as command line tools in …/bin with the same names as the tools built with the libLAS code. A couple years ago, a colleague on the GRASS project looked into the (then new) LAStools distribution and thought that it could be a drop in replacement for libLAS code. So I was hoping to try this with the Anaconda build. But we need a liblas-config to do it. I’m copying a couple colleagues on GRASS who also might be able to help with this.

Cheers
Michael

From: Daniel Clewley <notifications@github.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 12:27:16 AM MST

To: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com>

Cc: Michael Barton <c.michael.barton@gmail.com>, Author <author@noreply.github.com>

Reply-To: conda-forge/lastools-feedstock <reply+0088d5afde4903f9a76a7de6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0b@reply.github.com>

This is the feedstock for LAStools and LASlib not libLAS which I believe is the library GRASS can be compiled against. The libLAS website has a page explaining the relationship between the two: https://www.liblas.org/lastools.html. The two libraries provide similar functionality but aren’t compatible.

From the libLAS website “As of 2014, libLAS has been almost entirely superceded by Martin Isenburg‘s LASlib library.”

More specifically this feedstock builds a fork of LAStools (https://github.com/gillins/LAStools/) which adds CMake build scrips. The standard LAStools doesn’t provide a liblas-config file, we could add one to the fork this is being build against but I think this would only make things between the two libraries more confusing.

I’m going to mark this as closed but if I am incorrect and it is LASlib you need please reopen for further discussion.

This is good news. I hope that GRASS can take advantage of this work.

Michael

···

On Wed, Feb 21, 2018 at 7:43 PM, Michael Barton <Michael.Barton@asu.edu> wrote:

So here is an email chain with the conda-forge maintainers of the LAStools package about liblas in Anaconda which is not liblas, but actually laslib misnamed. This is why there is no liblas-config. Since liblas.dylib is installed with the lastools package in Anaconda, I asked if they might also create a liblas-config file (not currently installed) so that GRASS can compile against it for LiDAR support

Since that’s the case, it doesn’t seem that just liblas-config would solve it. Daniel Clewley says “LASlib isn’t a drop in replacement for libLAS (different function names for one thing) you’d have to modify the GRASS code if you wanted to use LASlib.” Perhaps simpler than changing it to PDAL, but I’m not sure if worth it. But I haven’t seen the LASlib API.

The upshot is that LAStools (and laslib, misnamed as liblas) can be installed through Anaconda, but not the packages we know as libLAS. Also, it seems like libLAS is no longer maintained and superseded by LASlib and related tools.

So far various people kept libLAS alive:

https://github.com/libLAS/libLAS/commits/master

But the situation is not ideal.

I have an email from William Kyngesburye (copied) from several years ago suggesting that GRASS lidar support could potentially use LASlib instead of liblas. But I don’t know what that would involve.

As I said above, I dpn’t know the LASlib API, but my guess is that it would be possible, but I think the question is if somebody can work on it.

From what I understood replacement for libLAS is PDAL, but definitively not a drop-in one. I was not able to dedicate any time to it lately except for accepting patch from felixg few days ago which makes v.in.pdal work with current PDAL. Also I have been told that PDAL package for Anaconda is coming soon (in days).

Best,

Vaclav

MIchael

From: Daniel Clewley <notifications@github.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 11:38:55 AM MST

To: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com>

Cc: Michael Barton <c.michael.barton@gmail.com>, Author <author@noreply.github.com>

Reply-To: conda-forge/lastools-feedstock <reply+0088d5af64024b45f60988c0b8f9368cac4eee6363df9a7492cf0000000116a57eb892a169ce11d01e0b@reply.github.com>

LASlib isn’t a drop in replacement for libLAS (different function names for one thing) you’d have to modify the GRASS code if you wanted to use LASlib.

From: Michael Barton <c.michael.barton@gmail.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 8:59:25 AM MST

To: conda-forge/lastools-feedstock <reply+0088d5afde4903f9a76a7de6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0b@reply.github.com>

Cc: Vaclav Petras <wenzeslaus@gmail.com>, Eric Hutton <hutton.eric@gmail.com>

Thanks for the quick response Dan,

I have indeed seen both the open source libLAS code and the LAStools site. The thing is that the Anaconda package installs liblas.dylib into …/lib as well as command line tools in …/bin with the same names as the tools built with the libLAS code. A couple years ago, a colleague on the GRASS project looked into the (then new) LAStools distribution and thought that it could be a drop in replacement for libLAS code. So I was hoping to try this with the Anaconda build. But we need a liblas-config to do it. I’m copying a couple colleagues on GRASS who also might be able to help with this.

Cheers
Michael

From: Daniel Clewley <notifications@github.com>

Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)

Date: February 21, 2018 at 12:27:16 AM MST

To: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com>

Cc: Michael Barton <c.michael.barton@gmail.com>, Author <author@noreply.github.com>

Reply-To: conda-forge/lastools-feedstock <reply+0088d5afde4903f9a76a7de6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0b@reply.github.com>

This is the feedstock for LAStools and LASlib not libLAS which I believe is the library GRASS can be compiled against. The libLAS website has a page explaining the relationship between the two: https://www.liblas.org/lastools.html. The two libraries provide similar functionality but aren’t compatible.

From the libLAS website “As of 2014, libLAS has been almost entirely superceded by Martin Isenburg‘s LASlib library.”

More specifically this feedstock builds a fork of LAStools (https://github.com/gillins/LAStools/) which adds CMake build scrips. The standard LAStools doesn’t provide a liblas-config file, we could add one to the fork this is being build against but I think this would only make things between the two libraries more confusing.

I’m going to mark this as closed but if I am incorrect and it is LASlib you need please reopen for further discussion.

If anyone attending the Bonn Code Sprint [1] is interested, the entire
PDAL team will be available to help someone doing such integration work.

Howard

[1] https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018

On 2/22/18 10:39 AM, Michael Barton wrote:

This is good news. I hope that GRASS can take advantage of this work.

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
Tempe, AZ 85287-2402
USA

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

On Feb 22, 2018, at 8:07 AM, Howard Butler <howard@hobu.co<mailto:howard@hobu.co>> wrote:

A couple of notes:

* Brad Chambers from the PDAL project has put forward an initial Anaconda build recipe that is waiting to be merged.
* I have updated the libLAS website to tell people to use PDAL if they're starting fresh
* Sorry about the naming thing.

I hope enough developer attention can get GRASS caught up to PDAL for on-the-way-in data ingest and processing. PDAL brings a lot of filtering and processing possibilities that just aren't available in libLAS. Most notably, it supports the latest ASPRS LAS 1.4 (and LAZ) specification, which libLAS does not, in addition to about 15 other formats. PDAL is also actively developed, patched, and improved. libLAS has not been in 5+ years except for critical outside patches.

Use PDAL :slight_smile:

Howard

On Feb 21, 2018, at 9:29 PM, Michael Barton <Michael.Barton@asu.edu<mailto:Michael.Barton@asu.edu>> wrote:

Yes pdal is a good possibility. But we neither yet have pdal replacements for the lidar tools nor pdal in anaconda. I don't know which is the better near term solution for lidar and which would be easier to to implement.

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/&gt;

On Feb 21, 2018, at 7:43 PM, Vaclav Petras <wenzeslaus@gmail.com<mailto:wenzeslaus@gmail.com>> wrote:

On Wed, Feb 21, 2018 at 7:43 PM, Michael Barton <Michael.Barton@asu.edu<mailto:Michael.Barton@asu.edu>> wrote:
So here is an email chain with the conda-forge maintainers of the LAStools package about liblas in Anaconda which is not liblas, but actually laslib misnamed. This is why there is no liblas-config. Since liblas.dylib is installed with the lastools package in Anaconda, I asked if they might also create a liblas-config file (not currently installed) so that GRASS can compile against it for LiDAR support

Since that's the case, it doesn't seem that just liblas-config would solve it. Daniel Clewley says "LASlib isn't a drop in replacement for libLAS (different function names for one thing) you'd have to modify the GRASS code if you wanted to use LASlib." Perhaps simpler than changing it to PDAL, but I'm not sure if worth it. But I haven't seen the LASlib API.

The upshot is that LAStools (and laslib, misnamed as liblas) can be installed through Anaconda, but not the packages we know as libLAS. Also, it seems like libLAS is no longer maintained and superseded by LASlib and related tools.

So far various people kept libLAS alive:

https://github.com/libLAS/libLAS/commits/master&lt;https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_libLAS_libLAS_commits_master&d=DwMFaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=_O4k1Vw2r12rLzx299WafFcaDaH01hzHGCoCuf94J0I&s=Kt7DFBhZJWvgpo4vM-1sXm32KiKyQ5eGF-t9k3yBUzo&e=&gt;

But the situation is not ideal.

I have an email from William Kyngesburye (copied) from several years ago suggesting that GRASS lidar support could potentially use LASlib instead of liblas. But I don't know what that would involve.

As I said above, I dpn't know the LASlib API, but my guess is that it would be possible, but I think the question is if somebody can work on it.

From what I understood replacement for libLAS is PDAL, but definitively not a drop-in one. I was not able to dedicate any time to it lately except for accepting patch from felixg few days ago which makes v.in.pdal work with current PDAL. Also I have been told that PDAL package for Anaconda is coming soon (in days).

Best,
Vaclav

MIchael

...
From: Daniel Clewley <notifications@github.com<mailto:notifications@github.com>>
Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)
Date: February 21, 2018 at 11:38:55 AM MST
To: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com<mailto:lastools-feedstock@noreply.github.com>>
Cc: Michael Barton <c.michael.barton@gmail.com<mailto:c.michael.barton@gmail.com>>, Author <author@noreply.github.com<mailto:author@noreply.github.com>>
Reply-To: conda-forge/lastools-feedstock <reply+0088d5af64024b45f60988c0b8f9368cac4eee6363df9a7492cf0000000116a57eb892a169ce11d01e0b@reply.github.com<mailto:reply+0088d5af64024b45f60988c0b8f9368cac4eee6363df9a7492cf0000000116a57eb892a169ce11d01e0b@reply.github.com>>

LASlib isn't a drop in replacement for libLAS (different function names for one thing) you'd have to modify the GRASS code if you wanted to use LASlib.

From: Michael Barton <c.michael.barton@gmail.com<mailto:c.michael.barton@gmail.com>>
Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)
Date: February 21, 2018 at 8:59:25 AM MST
To: conda-forge/lastools-feedstock <reply+0088d5afde4903f9a76a7de6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0b@reply.github.com<mailto:reply+0088d5afde4903f9a76a7de6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0b@reply.github.com>>
Cc: Vaclav Petras <wenzeslaus@gmail.com<mailto:wenzeslaus@gmail.com>>, Eric Hutton <hutton.eric@gmail.com<mailto:hutton.eric@gmail.com>>

Thanks for the quick response Dan,

I have indeed seen both the open source libLAS code and the LAStools site. The thing is that the Anaconda package installs liblas.dylib into ../lib as well as command line tools in ../bin with the same names as the tools built with the libLAS code. A couple years ago, a colleague on the GRASS project looked into the (then new) LAStools distribution and thought that it could be a drop in replacement for libLAS code. So I was hoping to try this with the Anaconda build. But we need a liblas-config to do it. I'm copying a couple colleagues on GRASS who also might be able to help with this.

Cheers
Michael

From: Daniel Clewley <notifications@github.com<mailto:notifications@github.com>>
Subject: Re: [conda-forge/lastools-feedstock] can liblas-config be included in package (#3)
Date: February 21, 2018 at 12:27:16 AM MST
To: conda-forge/lastools-feedstock <lastools-feedstock@noreply.github.com<mailto:lastools-feedstock@noreply.github.com>>
Cc: Michael Barton <c.michael.barton@gmail.com<mailto:c.michael.barton@gmail.com>>, Author <author@noreply.github.com<mailto:author@noreply.github.com>>
Reply-To: conda-forge/lastools-feedstock <reply+0088d5afde4903f9a76a7de6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0b@reply.github.com<mailto:reply+0088d5afde4903f9a76a7de6418c35ec29798e65e254574992cf0000000116a4e15492a169ce11d01e0b@reply.github.com>>

This is the feedstock for LAStools<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_LAStools_LAStools&d=DwMFaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=_O4k1Vw2r12rLzx299WafFcaDaH01hzHGCoCuf94J0I&s=ldj8Sw8X5ftlAivmAsG7tmePCgMcO2HxM6XH99LrTfU&e=&gt; and LASlib not libLAS<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_libLAS_libLAS&d=DwMFaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=_O4k1Vw2r12rLzx299WafFcaDaH01hzHGCoCuf94J0I&s=GuVlnoktk-csitrgckBePx4WJ1v_ZYXiIl8B51Ydttk&e=&gt; which I believe is the library GRASS can be compiled against. The libLAS website has a page explaining the relationship between the two: https://www.liblas.org/lastools.html&lt;https://urldefense.proofpoint.com/v2/url?u=https-3A__www.liblas.org_lastools.html&d=DwMFaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=_O4k1Vw2r12rLzx299WafFcaDaH01hzHGCoCuf94J0I&s=TJQ1eSBXpa8L3IrseTebZgyoHHFaNnOxyqkHZbdxQ88&e=&gt;\. The two libraries provide similar functionality but aren't compatible.

From the libLAS website "As of 2014, libLAS has been almost entirely superceded by Martin Isenburg‘s LASlib library."

More specifically this feedstock builds a fork of LAStools (https://github.com/gillins/LAStools/&lt;https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_gillins_LAStools_&d=DwMFaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=_O4k1Vw2r12rLzx299WafFcaDaH01hzHGCoCuf94J0I&s=wQwQ2hTaHMK_RPNZcXN3rVYXsqw6UAnnYFN0kv4AuD4&e=&gt;\) which adds CMake build scrips. The standard LAStools doesn't provide a liblas-config file, we could add one to the fork this is being build against but I think this would only make things between the two libraries more confusing.

I'm going to mark this as closed but if I am incorrect and it is LASlib you need please reopen for further discussion.

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/grass-dev

On Thu, Feb 22, 2018 at 6:33 PM, Howard Butler <howard@hobu.co> wrote:

If anyone attending the Bonn Code Sprint [1] is interested, the entire
PDAL team will be available to help someone doing such integration work.

Howard

[1] https://wiki.osgeo.org/wiki/OSGeo_Code_Sprint_2018

Yes, there will be at least eight GRASS devs:

https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018#Planned_participation

Glad to speak in person to the PDAL team!

Markus