CloudCompare forum

Not that I am aware of.

See https://www.cloudcompare.org/doc/wiki/i ... _line_mode

Works fine on my side... maybe a temporary issue?

Hum, I fear another issue is that currently CCCoreLib doesn't know/care about the point normals. This information is not passed to CCCoreLib.

Anyway, anyone could perform this change, as long as it's done properly ;)

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?