Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

las2las in OSGeo4W Shell: las2las (libLAS 1.8.1 with GeoTIFF 1.4.2) --> LASzip is missing #51193

Closed
1 of 2 tasks
weisev-repo opened this issue Dec 13, 2022 · 1 comment
Closed
1 of 2 tasks
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@weisev-repo
Copy link

What is the bug or the crash?

If I'm running the following cmd-line in OSGeo4W Shell:

las2las 3dm_32_510_5704_1_nw.laz --output out.laz --extent "510100 5703500 510900 5704500"

The following error occurs:

error: Compression support not enabled in liblas configuration

I noticed that if I'm running las2las in the cmd-line I get in the header:


las2las (libLAS 1.8.1 with GeoTIFF 1.4.2)

But I think LASzip is missing and therefore the error of compression support occurs.

What is a little confusing if I navigate to C:\Program Files\QGIS 3.22.13\bin, there is laszip3.dll

Do you have any advice?

I'm using QGIS 3.22.13 LTR.

Steps to reproduce the issue

  1. Go to https://wheregroup.com/blog/details/visualisierung-und-manipulation-von-lidar-daten-mit-qgis-und-pdal/ and download the LIDAR Testdaten aus OpeGeoData.NRW
  2. Open OSGeo4W Shell and type "las2las" --> Check the header
  3. Paste the following into the command line: las2las 3dm_32_510_5704_1_nw.laz --output out.laz --extent "510100 5703500 510900 5704500"

Versions

QGIS 3.22.13 LTR

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

  • I tried with a new QGIS profile

Additional context

No response

@weisev-repo weisev-repo added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Dec 13, 2022
@nicogodet
Copy link
Member

nicogodet commented Dec 13, 2022

This should be reported on OSGeo4W Tracker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

No branches or pull requests

2 participants