Page 2 of 2

Re: Saving bin-file to pts or comparable

Posted: Tue Jun 09, 2015 9:14 am
by Youngtimer
Thanks for your reply! I'm glad that this is a problem of meshlab, I was getting worried that this could be a problem of my files or something I've done with them :D
May I ask you another question? The .pts files that I already have are build in the following way:

21183956
-0.021856 1.958903 0.942040 -2030 1 1 1
-1.020605 1.000081 0.068065 -2014 9 1 1
-1.018487 1.000074 0.066315 -2030 1 1 1
-1.017673 0.999588 0.068003 -2014 9 1 1
-1.022445 1.000137 0.064658 -2030 1 1 1
-1.022109 0.999553 0.062153 -2030 1 1 1
-1.020539 0.999032 0.065357 -2014 9 1 1
-1.021308 0.999728 0.064365 -2030 1 1 1
-1.038918 0.997766 0.062939 -392 110 97 109

Is it possible to see which options were chosen? I can see a header with the amount of lines, but the following lines seem slightly different?

Re: Saving bin-file to pts or comparable

Posted: Tue Jun 09, 2015 9:18 am
by daniel
The PTS files are always: X Y Z Intensity R G B.

More generally in CloudCompare you can check the 'Columns title' in the 'Save' dialog to make CC write the column names on the first line of the file.

Re: Saving bin-file to pts or comparable

Posted: Tue Jun 09, 2015 9:30 am
by Youngtimer
Ah, I see. Many thanks for your help!