Exporting different formats results in different coordinates

[c3kkos]

Yes! it worked putting CC into:

C:\Users\USER\AppData\Local\Temp\CloudCompare_v2.14.beta_bin_x64

[c3kkos]

Uhm, scale and orientation issue still there.

Wrong scale is not a big deal anyway. easy fix

Orientation is critical


I clicked NO on both imports when asked to apply global transformations
Also tryied clicking YES at everything, resulting in .e57 point cloud traslated and nothing else.

[daniel]

Can you give me your exact workflow?

On my side:
- I load the pts file
- I accept the default Global Shift
- save the cloud as E57
- load the E57 file
- I accept the default Global Shift
- I get the exact same points / positions

[c3kkos]

Workflow:

bigger point clound inside a standard, cc's .bin file.

Used X tool to slice it up, to export only the tiny slice into other software for development.

At this point i had to chose point cloud format for the other sw. it can be either .e57, las/laz OR plain ascii .pts

Decided to go with .e57

Saved slice (from cc) in .e57. Opened in other SW, noticed the misalignment.
Saved slice (from cc) in .pts. Opened in other SW, noticed everything is OK.


Opened again both files in cc shows same behaviour.

Where is the issue?

Here: I saved a point clound from cc in .e57 format and i lost original position and alignment.
saving it in .pts format is OK

[c3kkos]

The job is done using "CloudCompare_v2.13.2.preview_bin_x64" dated 30/06/25

[daniel]

And have you retried the same process with the 2.14.beta version?

Also, did you rotate the large cloud prior to make a section?

[c3kkos]

I've rotated and traslated the original cloud, yes.

I used the default tool for manual alignment with targets within the cloud and applied the resulting transformation.

Then, i sliced up the big cloud.


I do confirm that exporting a slice in .pts and .e57 formats do produce exact results using 2.14