Requesting to solve the issue of the characteristics of scans when uploading to the CloudCompare

[Mehrab1995]

Hello,
I hope you are well. I used Leica P50 scanner to scan a retaining wall underneath the bridge and after registering the scans in Cyclone Core, the registered scans were assembled in a single model.
When I exported the model as 'las" file format and trying to upload the model in CloudCompare, the registered model scattered into several scans. It was not a single model at all.
This is my thesis work and that's why, I am not able to compare the model to the same type of other models. Could you please assist me to solve this issue?

Thanks
Mehrab

[daniel]

Hi,

I guess Cyclone keeps the knowledge of the relative positioning of the scans in a separate file?

Also, since LAS can only contain one cloud/scan at a time, I'm a bit surprised by the 'scattering' of the clouds. Does Cyclone exports multiple files? (if yes, is there a way to export the whole merged cloud as a single file?). If not, then the issue would necessarily come from within Cyclone...

[Mehrab1995]

Thank you for your reply.
I am sure that the file we exported was a merged single file. Moreover, we scanned two sites by using Leica P50 and registered all scans of one site with the georeferenced and merged scans/clouds were not " scattered", but scans of another site were scattered after registering with georeferenced in same coordinate system and transferring in "LAS" file. In both cases, we used same Cyclone Core with same version and followed same instructions. Then, how the issue can be come from Cyclone?

The background of our works is in the following:

We have used a Leica P50 scanner to scan the retaining wall underneath the bridge in the year of 2024. We did 9 scans, among them scan number 2,6 and 8 were incomplete scans as during the scanning the machine detected the prism and we were unable to proceed the scans in the next phase. As a result, we needed to scan again. After completing the scans, we deleted the incomplete scans and registered the remaining 6 scans with georeferenced. The registered scans worked well in Cyclone Core and there was no issue.

We have another registered point cloud model of 2023 year in the same site and we tried to compare the model of 2023 and 2024 in CloudCompare software. For this reason, we exported the both models in "las" file format and uploaded these files in CloudCompare. However, the model of 2023 was working well in the CloudCompare but the model of 2024 was not working as the registered assembled model of 2024 showed the scattered in individual scans although it was a registered georeferenced model (Single file in Cyclone Core).

[daniel]

Well, once again, CloudCompare loads the point cloud 'as is' (no transformation or anything to the raw coordinates apart from the Global Shift that just translates all the points). And a LAS file can only contain a single cloud.

I guess you could try to load the file in another tool to check?