[pdal] not streaming from EPT to LAZ

Kirk Waters - NOAA Federal kirk.waters at noaa.gov
Mon Apr 3 03:50:54 PDT 2023


I must be doing something wrong in this pipeline that pulls data from an
EPT and outputs an LAZ. It ends up exceeding 70Gb of RAM and getting killed
by the system. I don't see anything that would cause it to use standard
mode instead of streaming mode. Would the switch to LAS 1.4 cause standard
mode? Here's the pipeline:
[{
"requests": "6",
"type": "readers.ept",
"bounds": "([-9080833.61616794, -9050564.55208689], [4013331.20703169,
4035337.95504148])",
"filename": "
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/SC_SavannahPeeDee_2_2019/ept.json
"
}, {
"limits": "Classification[2:2]",
"type": "filters.range"
}, {
"out_srs": "EPSG:6318",
"type": "filters.reprojection",
"in_srs": "EPSG:3857"
}, {
"compression": "lasperf",
"type": "writers.las",
"offset_x": "auto",
"scale_y": "0.0000001",
"minor_version": 4,
"scale_x": "0.0000001",
"offset_z": "auto",
"filename": "extractept2.laz",
"dataformat_id": 7,
"offset_y": "auto"
}]

This failed in PDAL 2.3.0. I'm trying PDAL 2.4.2 now and it looks like it
is doing the same thing. Is there anything in that pipeline that would
prevent streaming?

Thanks!

Kirk Waters, PhD
NOAA Office for Coastal Management
Applied Sciences Program
‪Phone: 843-284-6962‬ (email preferred)
coast.noaa.gov/digitalcoast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20230403/b4ed698a/attachment.htm>


More information about the pdal mailing list