Unexpected Point Cloud Visualization Issue After Exporting from CloudCompare CommandLine
Posted: Sun Jan 12, 2025 7:54 pm
I am facing a strange issue with a point cloud and CloudCompare. Let me explain with a simple example:
I have a point cloud, which I’ll call "input_cloud".
I perform a simple process in CloudCompare via command line: I load the file and then export it. The exported file becomes "output_cloud".
The problem:
When I display "output_cloud" in any software, it visually appears as if the cloud has been decimated or downsampled. It is no longer a dense point cloud but looks like a grid of points aligned vertically, with bands spaced 50 cm apart.
However, the total number of points in "input_cloud" and "output_cloud" is exactly the same, and the file sizes are almost identical.
I have tried several approaches:
I loaded "output_cloud" into RealWork, and the same issue is visible.
I tried with different clouds,
I modified my script to test other parameters (such as -MESH_CLOUDS and -CROP2D) or tried different import/export formats (e57, LAS, BIN), but the result is always the same.
I tested this with CloudCompare versions v2.14.alpha and v2.11.13, but nothing changed.
Has anyone encountered this problem before or has any idea how to resolve it? I’m open to any suggestions!
my script :
@echo off
setlocal
"C:\Program Files\CloudCompare\cloudcompare.exe" -O "statique.e57" -C_EXPORT_FMT E57 -SAVE_CLOUDS FILE "3sortie"
endlocal
I have a point cloud, which I’ll call "input_cloud".
I perform a simple process in CloudCompare via command line: I load the file and then export it. The exported file becomes "output_cloud".
The problem:
When I display "output_cloud" in any software, it visually appears as if the cloud has been decimated or downsampled. It is no longer a dense point cloud but looks like a grid of points aligned vertically, with bands spaced 50 cm apart.
However, the total number of points in "input_cloud" and "output_cloud" is exactly the same, and the file sizes are almost identical.
I have tried several approaches:
I loaded "output_cloud" into RealWork, and the same issue is visible.
I tried with different clouds,
I modified my script to test other parameters (such as -MESH_CLOUDS and -CROP2D) or tried different import/export formats (e57, LAS, BIN), but the result is always the same.
I tested this with CloudCompare versions v2.14.alpha and v2.11.13, but nothing changed.
Has anyone encountered this problem before or has any idea how to resolve it? I’m open to any suggestions!
my script :
@echo off
setlocal
"C:\Program Files\CloudCompare\cloudcompare.exe" -O "statique.e57" -C_EXPORT_FMT E57 -SAVE_CLOUDS FILE "3sortie"
endlocal