Aprende a usar las herramientas para nubes de puntos desde la línea de comandos en LAStools, CloudCompare, FUSION y QGIS.

Aprende a usar las herramientas para nubes de puntos desde la línea de comandos en LAStools, CloudCompare, FUSION y QGIS.

Aprende a usar las herramientas para nubes de puntos desde la línea de comandos en LAStools, CloudCompare, FUSION y QGIS.

Descubre cómo generar Modelos Digitales del Terreno (MDT) y de Superficie (MDS) a partir de nubes de puntos LiDAR.

I ran into an issue of running the LAStools on QGIS. As it states in the subject, I have 3.28 Firenze version of QGIS, and it's operating on MacOS12.4 Every time I tried to run LASview, I get this message: LAStools command line /Applications/wine /Users/jeremywitek/Desktop/LAStools/bin/lasview -i "/Users/jeremywitek/Desktop/terra_las/cloud_merged.copc.laz" -points 5000000 LAStools console output /bin/sh: /Applications/wine: No such file or directory I did some research and I found out I need to install wine. I did, but now I am stuck trying to figure out how to set it up correctly so it works. Under Processig-> options -> Providers -> LAStools I have activated box checked, under Lastools folder I have correct folder selected. it states as follows: /Users/jeremywitek/Desktop/LAStools I am unsure what should I put under Wine folder. And also, not even sure if that's the cause of the problem... How can I fix this?

As I am trying to clip the LiDAR data (.las) file from shapefile (.shp) I have used the lastools(lasclip) to clip the .las file from area of interest that is shapefile from QGIS plugin but it didn't work it is creating the output file but it is not clipping that area of interest. After running the tool I am getting this output which is same as input LAS. Is there are any different method to cut LiDAR data with polygon?

Aprende a usar las herramientas para nubes de puntos desde la línea de comandos en LAStools, CloudCompare, FUSION y QGIS.

I'm indexing a set of airborne LiDAR flight lines (LAS 1.4, point format 6) with lasindex from LAStools to speed up clip_roi() queries in the R package lidR. For most files this works fine and produces reasonably sized .lax files. However, in one survey area almost all .lax files are only 1 KB, while a single file in the same folder got a ~180 KB index. The affected files are large (100+ million points), so a 1 KB index seems wrong — I'd expect a substantial quadtree index like the working files have. What confuses me: when I compare the lasinfo headers of a file with a "bad" (1 KB) index and a file with a valid index, they look essentially identical — same version, same point format, same number of point records: 0 in the legacy field with the count only in the extended field, and both report has spatial indexing LAX file. lidR::is.indexed() returns TRUE for all of them. File with the small (1 KB) index: version major.minor: 1.4 point data format: 6 number of point records: 0 extended number of point records: 110074792 min x y z: 402423.312 5259705.175 1419.484 max x y z: 413127.035 5261888.810 2033.601 has spatial indexing LAX file generating software: 'las2las (version 240810)' File with a valid index (same folder / survey): version major.minor: 1.4 point data format: 6 number of point records: 0 extended number of point records: 97252049 min x y z: 398127.961 5260324.658 555.614 max x y z: 407919.783 5266829.618 2167.613 has spatial indexing LAX file generating software: 'las2las (version 240810)' (Full lasinfo output available if needed.) My questions: * Given that the headers are practically identical, what could cause lasindex to write a trivial index for one file but a valid one for another? * Is there a reliable way to verify that a .lax file is actually functional (not just present), beyond is.indexed() returning TRUE? I've already tried deleting the small .lax and regenerating it, which produced the same result (a 1 KB file again). Environment: LAStools (lasindex), LAS files generated by las2las version 240810, R with lidR for downstream processing.

This article is obsolete. Please see New Plugin: LAStools...