libLAS / libLAS

C++ library and programs for reading and writing ASPRS LAS format with LiDAR data
http://liblas.org
Other
309 stars 158 forks source link

Cannot open .laz even though it is compiled with laszip #115

Closed squeakus closed 7 years ago

squeakus commented 7 years ago

Hi, I am compiling liblas with laszip support but it cannot open laz files. In ccmake I am enabling WITH_LASZIP and it is correctly finding the include folder and liblaszip.so (but not the laszip_dir). When compiling it correctly finds and identifies the version:

-- Searching for LASzip 2.0.1+ library -- Found LASzip version: 2.2.0 -- Searching for GeoTIFF 1.3.0+ library -- Found GeoTIFF version: 1.4.1 -- Enable libLAS utilities to build - done -- Enable libLAS unit tests to build - done -- Configuring done

but when I run lasinfo on one of the sample files (IowaDNR-stippled-overlap.laz ) I get the following error:

error: Compression support not enabled in liblas configuration

Everything seems to be compiling correctly so I have no idea where to start debugging this, any advice would be greatly appreciated!

squeakus commented 7 years ago

My apologies, the system libraries were shadowing the libraries I built from the source. I removed them and now everything works.

animaux commented 6 years ago

That was helpful pointing me in the same direction! Cheers.

animaux commented 4 years ago

Hei,

I’m really sorry but I honestly can’t remember. Hope you’ll find a way.

All the best,

Alex

  1. apr. 2020 kl. 00:36 skrev Pedrous notifications@github.com:

Hey,

could you please point out what you removed exactly?

I installed LASzip version 2.2 and after copying the header files from /usr/local/include/ to /usr/local/include/liblas, I was able to build liblas and LASzip was found. However, I still got the same exact error than you do.

I'm using Ubuntu 16.04 and I had liblas-dev and liblas-c-dev installed so I did apt-get purge to them. However, the error still persist?

I would be grateful if you could help. Thank you.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.