CloudCompare forum

Hi Daniel, I think the point is that the transformation matrix is not being applied to the sensor when importing a PTX file, but looking at various recent Register360 exports, it appears that they all have 1s & 0s in rows 3-7. This seems to be different export behaviour compared to other software.

I literally have hundreds of scans. Please note that this is a functionality request. I'm not after alternative solutions, but I guess someone on here might find it useful.

Also, can I please ask that you trim or remove the screenshot image you posted as it contains identifiable information in it ...

Thanks c3kkos,

The reason for the zeros is that this is gridded data, measured from a single terrestrial scanner setup. Zeros represent no return measurement (eg. sky). Yes the ASCII import option works, but the sensor data is critical to my workflow.

Hi Daniel,

No luck with the latest beta. Still getting a malformed error.

Here is a PTX file with normals. It has been exported from Leica Register 360. This is one setup in a project of registered point clouds.

https://www.dropbox.com/scl/fi/lb1qyxt91hccn8zlja46u/SS13095_S73.ptx?rlkey ...

Thanks for the suggestion. Yes the ASCII method works, but the station info doesn't come through which is critical to my workflow.

Hi Daniel. Have tried on 2.13.2 and 2.14.beta. Behaviour is the same on both.

Hi Daniel,

Pretty sure this is a bug. When importing a PTX file that has been registered (eg. exported from Leica Register360), the Sensor coordinates come through at 0,0,0. This is incorrect. The sensor coordinates should be translated by the values in row 10. See here: https://wiki.photoneo.com ...

Hi Daniel,

It's now common for PTX files to include normals. Leica Register360 now has this option for exported PTX files. They have 10 columns in total: X Y Z int R G B Nx Ny Nz. Any chance you can add support for this extended PTX format?

Hi Daniel. Just giving this one a polite bump. Retaining the sensor info when subsampling would be a very useful enhancement :)

Yes the loss of Sensors in command line mode is annoying. Also not working for e57 files that contain multiple clouds (e.g. TLS data) in command line mode is:
- Generating scalar field with original cloud index when merging, and
- Global shift using Auto or First mode doesn't apply the same shift to ...