CloudCompare forum

You should maybe take a look at the new 3DFin plugin: https://github.com/3DFin/3DFin (it's included in the Installer version of CloudCompare 2.13 for Windows).

So normally you simply need to deselect the entity. That's the only way to prevent the bounding-box from appearing.

Ah none of these are options of the command line. And I'm afraid it would be a little too specific. But that would be a good job for the Python wrapper (https://github.com/CloudCompare/CloudComPy).

So currently it's hardcoded and this behavior can't be changed by the user... What would be easy to do is to make the timestamp more detailed (with seconds or even microseconds).

And/or add an option to set the base output filename.

I'll add this to the TODO list.

No, there's no such feature at the moment.

And it's probably already in the TODO list... but this list is way too long!

Hum, not sure how to manage this with the command line. Maybe Python would be a better option (with CloudCompy). And sadly, the only scalar field that can be saved with the E57 format is 'intensity'. So the only option would be to rename the distances SF 'Intensity', and I'm not sure what would happ...

Yes, so you can see that the bounding box along X and Y is super small (<0.02) and super large along Z (> 420). This is once again typical from a geographical coordinate system. You can try to rescale X and Y with the 'Edit > Multiply / scale' tool (by using a factor of 100 for instance for X and Y ...

I don't believe there's any such feature in CloudCompare...

To export to ascii, you have to use -C_EXPORT_FMT ASC (or TXT should work). This must be placed before -SAVE_CLOUDS.

And before calling -EXTRACT_VERTICES, I would remove the cloud with -POP_CLOUDS (so that only the plane remains, because it's a mesh).

See https://github.com/CloudCompare/CloudCo ... rtObject.h (it's part of the 'DB' library)