PDAL exception: writers.las
Posted: Tue Feb 02, 2021 4:17 pm
Hi Daniel!
First, thanks for this excellent piece of software, I've been using and abusing it a lot and it beats most bespoke SW in sheer functionality!
I've been trying to get my head around an error that I get while running ICP through command line using command (on v2.11.3 64-bit):
"c:\Program Files\CloudCompare\CloudCompare.exe" -AUTO_SAVE OFF -O -GLOBAL_SHIFT AUTO input_1.las -O -GLOBAL_SHIFT AUTO input_2.las -ICP -REFERENCE_IS_FIRST -OVERLAP 70 -C_EXPORT_FMT LAS -SAVE_CLOUDS FILE "out_1.las out_2.las"
The error I've been getting when trying to save the result is:
PDAL exception: writers.las: Unable to convert scaled value(-399999999998) to int32 for dimension 'Y' when writing LAS/LAZ file out_1.las
The funny thing is, input datasets on which this crashes are part of a series of several pairs of input datasets, all of which are geographically within few hundred meters, clipped from same inputs using same software (Safe software FME Workbench). Most work fine, but I have two pairs that throw this error.
I checked the LAS file metadata using PDAL info, but I cannot find anything terribly wrong with its offsets. All files, working and not working look very similar.
Do you maybe have any fresh insights?
Many thanks!
First, thanks for this excellent piece of software, I've been using and abusing it a lot and it beats most bespoke SW in sheer functionality!
I've been trying to get my head around an error that I get while running ICP through command line using command (on v2.11.3 64-bit):
"c:\Program Files\CloudCompare\CloudCompare.exe" -AUTO_SAVE OFF -O -GLOBAL_SHIFT AUTO input_1.las -O -GLOBAL_SHIFT AUTO input_2.las -ICP -REFERENCE_IS_FIRST -OVERLAP 70 -C_EXPORT_FMT LAS -SAVE_CLOUDS FILE "out_1.las out_2.las"
The error I've been getting when trying to save the result is:
PDAL exception: writers.las: Unable to convert scaled value(-399999999998) to int32 for dimension 'Y' when writing LAS/LAZ file out_1.las
The funny thing is, input datasets on which this crashes are part of a series of several pairs of input datasets, all of which are geographically within few hundred meters, clipped from same inputs using same software (Safe software FME Workbench). Most work fine, but I have two pairs that throw this error.
I checked the LAS file metadata using PDAL info, but I cannot find anything terribly wrong with its offsets. All files, working and not working look very similar.
Do you maybe have any fresh insights?
Many thanks!