Importing registered .pts files with Cyclone
Posted: Thu Oct 06, 2016 10:05 am
Hi everyone,
I have registered various PC with Cyclone. As the original files were ASCII files (not .ptx files), after the registration process I only could export as .pts or others, not as .ptx. As a result of this, when importing the exported file (pts) with CC, it is loaded as a single cloud instead of each registered cloud. Contrarily, using 3DReshaper I found that it loads the .pts file and allows to separate and inspect each single cloud.
The .pts file contains the following structure:
- number of points of the cloud 1: n1
- n1 rows, containing the n1 points
- number of points of the cloud 2: n2
- n2 rows, containing the n2 points
number of rows of the .pts file: 1 + n1 + 1 + n2
Do you think that it may be possible that CC loads the pts files separating each subcloud? This might lead to further analysis, such as the inspection of distances of the common region and the validation of the registration.
Thanks a lot.
Adri.
I have registered various PC with Cyclone. As the original files were ASCII files (not .ptx files), after the registration process I only could export as .pts or others, not as .ptx. As a result of this, when importing the exported file (pts) with CC, it is loaded as a single cloud instead of each registered cloud. Contrarily, using 3DReshaper I found that it loads the .pts file and allows to separate and inspect each single cloud.
The .pts file contains the following structure:
- number of points of the cloud 1: n1
- n1 rows, containing the n1 points
- number of points of the cloud 2: n2
- n2 rows, containing the n2 points
number of rows of the .pts file: 1 + n1 + 1 + n2
Do you think that it may be possible that CC loads the pts files separating each subcloud? This might lead to further analysis, such as the inspection of distances of the common region and the validation of the registration.
Thanks a lot.
Adri.