New answers tagged lidar
1
This isn't a python fix, but in ArcPro you can just use the Convert LAS tool. I find even though its an optional parameter, you just need to make sure the coordinate system is set and it works great!
1
Thank you all for your suggestions, however I have just found the solution!
The latest release of Blender reads float32 tif files!!! No uint16 needed. I feel stupid to ask the question in the first place... but I will leave it up in case anyone else has the same problem I was experiencing. Just update your Blender to 3.0 or higher and it will natively read ...
2
You can't change data type from float32 to integer without loosing precision. The values will be rounded to the closest meter (or whatever crs unit you are using).
I'm using Warp to change data type. The DEM is styled with a hillshade ffect:
What you can do is to create a hillshade first, then convert this to integer:
1
classify_noise was introduced with lidR 3.2.0 and includes two algorithms: Statistical Outliers Removal (SOR) and isolated voxels filter (IVF).
So you would need to first run the function to classify noise in the point cloud, and then use filter_poi
For example:
las <- classify_noise(las, sor(15,7))
las_denoise <- filter_poi(las, Classification != ...
6
I downloaded your contour geopackage. Open it with QGIS, right click the layer -> Layer CRS -> Set Layer CRS -> Search for "3912" -> OK
Your contour lines should be where you want them
Top 50 recent answers are included