full waveform, C2C, command line and global_shift

[paul.leroy]

Hi,

I have something strange when trying to launch a C2C in command line (the line is copied hereafter) between a full waveform laz and a laz that has been recorded by CloudCompare. In the messages, I do not see the line saying that my fwf_file1.laz has been shifted, but I see the line saying that file2.laz has been shifted. What is stranged is that I should have points after the filtering (I have checked this using the GUI version of CloudCompare). If I remove both -GLOBAL_SHIFT options, I get points in the ouput laz.

CloudCompare.exe -SILENT -NO_TIMESTAMP -C_EXPORT_FMT LAS -EXT laz -AUTO_SAVE OFF
-FWF_O -GLOBAL_SHIFT -1037000.0 -6741000.0 0.0 fwf_file1.laz
-O -GLOBAL_SHIFT FIRST file2.laz
-C2C_DIST -SPLIT_XYZ -MAX_DIST 20 -OCTREE_LEVEL 11
-POP_CLOUDS
-SET_ACTIVE_SF 9 -FILTER_SF -10 2 -SET_ACTIVE_SF 10 -FILTER_SF MIN 10
-SAVE_CLOUDS FILE out.laz

Any idea?

I have tested with several versions of CloudCompare. The files are here if you want to give it a try.

https://filesender.renater.fr/?s=downlo ... 2677f0abeb

Best regards,

Paul

[paul.leroy]

It seems to work with older versions of CloudCompare, I just tried with an old v2.11.

[daniel]

So versions 2.12+ were considering that the shift was insufficient (here, the Y coordinates remain greater than 30 000 even after the shift. So it was just discarding the input shift!

But I realize that it's not what we expect with the command line mode (since there's no other choice than using the input shift). I fixed that (on the master branch for now).

[paul.leroy]

Excellent, thank you Daniel!

[daniel]

For the records, the 2.13.alpha version has been updated.