Hot answers tagged

4

validate does not need to be called on the pipeline to run it and if you comment out pipeline.validate() then the pipeline executes within Python. This is a bug https://github.com/PDAL/PDAL/issues/2891 where calling validate as it clears the metadata for the stage. This causes an issue with the TileDB driver in that metadata is read/written and required. ...


4

You should use min and max property of header. from laspy.file import File f = File("path/to/file.laz", mode='r') h = f.header # h.min: [min_x, min_y, min_z] - h.max: [max_x, max_y, max_z] extent = [*h.min, *h.max] # extent: [min_x, min_y, min_z, max_x, max_y, max_z]


4

The las format defines that points have X/Y/Z coordinates and it defines how to include information about georeferencing https://www.asprs.org/wp-content/uploads/2010/12/LAS_1_4_r13.pdf. However, it is not clearly defined what X and Y mean. Traditionally many GIS software consider that X is always longitude or easting and Y is latitude or northing. But ...


3

Perhaps there is something to tune in the PDAL parameters. If tindex does not give good enough result when used like in this tutorial https://pdal.io/workshop/exercises/analysis/boundary/boundary.html then perhaps you could do better by running density https://pdal.io/apps/density.html directly with different --sample_size and --threshold parameters. For ...


3

pdal info will report summary statistics (source): pdal info --boundary /Users/me/test/data/las/autzen_trim.las { "boundary": { "area": 746772.7543, "avg_pt_per_sq_unit": 22.43269935, "avg_pt_spacing": 2.605540869, "boundary": "MULTIPOLYGON (((636274.38924399 848834.99817891, 637242....


2

PDAL supports streaming, but not all filters support it. If you don't want to load all of the data into memory at once, you need to use streaming. filters.decimation can support streaming because it doesn't need to consider all of the points to complete its work. For example, the following would keep every tenth point in the file: pdal translate input.las ...


1

According to the doc of pdal info: If no options are provided, --stats is assumed. This means that you need to read the entire point cloud to derive information that you don't actually need. What you are looking for is in the metadata of the file (the header). You don't need to read the payload (the points) at all. Try pdal info file.las --metadata This ...


1

This was a bug that is currently fixed in PDAL master and will be part of the next PDAL release. See https://github.com/PDAL/PDAL/pull/3099 for more detail.


Only top voted, non community-wiki answers of a minimum length are eligible