CloudCompare forum

Yes but you DO have sensor data to work with.

It can be used as a matrix to do things.

Yes, it is manual work, but unless you have hundreds scans, it is a way you can ride on

framed,

the .ptx files you shared is a bit weird.

let me paste the first data in it:

10168
4166
0.000000 0.000000 0.000000
1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
0.637030 0.770839 -0.000195 0.000000
-0.770839 0.637030 0.000483 0.000000
0.000497 -0.000157 ...

CC is decimating your cloud to have better framerate during the pan/rotate mouse operation.

If you want that look, subsample the cloud to any % you like

The sensor is not imported correctly because the I/O filter for ASCII files is parsing data -> to points only.

Hence, CC will need a better, ad hoc filter for that format, in order to get the job done.

For now, you can painfully use the data to craft by hand the sensor item..... or can you?

is ...

"Render to file" under Display menu does not get the job?

Is it plain ASCII file?

if so, rename extension to whatever ASCII format CC support and the wizard form will let you choose what gives what based on any number of columns

Daniel i find myself using "AAA" expensive software and they do have indeed a very good way to automate all the workflow and to give you back the full aligned cloud.

However this is what you get when your site workflow is "flawless".

There were some cases where big "jumps" or small overlaps (or ...

Manual rough alignment is often required even with expensive closed source software (Leica, Faro).

Quick & dirty

Using 2.14 downloaded last week

OK it is confirmed it is a dumb question:

i didn't noticed that "Coord.Z" is the name of the scalar field that indeed i created and THEN applied some transforms.
Maybe its good to have a suffix to that label. "SF Coord.Z =" to have a nice "first glance ...

That is a wise request

+1