CloudCompare forum

Bon jour tout les mondes

I have an ASCII file 'XYZ_RGB_01.csv' like
//X,Y,Z,Red,Green,Blue
10.001,20.001,1.001,255,255,100
10.002,30.002,2.002,100,255,100
20.003,20.003,3.003,255,100,100

... and a batch file like
"C:\Program Files\CloudCompare\CloudCompare.exe" -SILENT -C_EXPORT_FMT LAS ^
-o -GLOBAL_SHIFT 0 0 0 XYZ_RGB_01.csv ^
-AUTO_SAVE OFF -SAVE_CLOUDS FILE XYZ_RGB_01.laz

A former version of CC 2.13 alpha (2023/09/??12, W64bit) saved a correct laz file.
The actual CC 2.13 beta (2023/09/17, W64bit) saves a laz file falsified with ??missing XYZ.
As a test: I am loading this falsified file to the CC 2.13 alpha (2023/09/??12) it says 'PDAL execption: Unable to fetch data and convert as requested; Z:double(nan) - >int'

-> Question: How can I import ASCII files correctly in CC 2.13 beta in CMD-mode?

Merci beaucoup

Dan

%%--
Background: I have many *.laz generated by CC 2.13 alpha (2023/09/??12) who have RGB saved as 16 bit. RGB is not loaded as colors but as scalar fields [Red,Green,Blue] in CC 2.13 beta (2023/09/17). I recompute (e.g. x 1/256) & save these scalar fields to uint8. Then I reload the *.laz to CC 2.13 beta (2023/09/17), but scalar fields [Red,Green,Blue] are still imported as scalar fields but not as RGB-colors.

Can you share a file with us so that we can reproduce or investigate this on our side?

You can send it to admin@cloudcompare.org

Or is the ASCII file with the 3 lines above sufficient?

The ASCII file with the 3 lines above is sufficient. (However, I have sent it to admin* as well.)

Notes:
The 3 points are wrongly saved with NaN-Coordinates, but with correct RGB.
Vice versa, a *.laz with three uint8 scalar fields ['Red', 'Green', 'Blue'] is not automatically RGB-colored when imported to CC 2.13 beta (2023/09/17). But in CC 2.13 alpha (2022/09/xx) this was still the case.

As discussed by email, this was due to an issue with the save dialog. Mind that right now the LAS scale will be forced to 1e-3 with the command line mode (but that should be ok for most of the vast majority of cases).

The latest 2.13.beta version is fixed and online.

Issue is solved. Works fine. Merci beaucoup for the immediate reply and bug fixing!