CloudCompare forum

Maybe it would be 'easier' with CloudCompy (CloudCompare Python wrapper).

Currently the command line code doesn't allow for this. One would have to upgrade it...

So is it really 'noise', or simply a bad registration between scans? In the first case, you could simply play with the tools under the 'Tools > Clean' menu (see https://www.cloudcompare.org/doc/wiki/index.php/Methods#Clean ). But if it's a registration issue, you could also split the cloud into thes...

Hi,

Ideally, you would add Open3D as a submodule. But it's also acceptable to let developers simply install/compile it on their side and add the necessary CMake options to point to it.

Then you could compute the distance between the cloud and the polyline (With 'Tools > Distances > Cloud/Primitive dist.').

Then you can extract the points which are really close to the polyline based on this distance (with 'Edit > Scalar fields > Filter by value').

What do you mean by "ants to finalize the Selection with another point to create a 2D polygon" exactly?

Is it because the trace polyline is not closed maybe?

If there's one (or several), you would see them in the cloud properties. And if there is, then you can probably remove all the other options.

Yes, that's because with the command line you need to explicitly specify how to manage large coordinates.

You should add just after

Not sure to understand... Does your scan have an associated scan grid (because in this case you don't need to use any of the other options. If not, then you need a radius as large as possible so that enough points are captured in all areas of the cloud (normally the 'Auto' button works quite well to...

And what the bounding-box looks like once you've loaded the cloud?

There's good chances that Quick Terrain Modeler does manage properly geographic coordinate systems...