CloudCompare Workflow Documentation Please

Follow

Robert Paulsen

• June 26, 2020 14:20

Hi, 

I am working a lot with pointclouds from laserscans. I do not know which format works best in RC. Sometimes e57 works - sometimes it does not. I really do not know what makes RC say it cannot load small file while it can load other big ones. 

Same applies do PLY. Should we use BINARY or ASCII and when we import what settings can crash the import? Is there any documenation out there that we can use to know how to deal with this?

Also how do people without Cyclone and Faro Scene create PTX files with free software? Any tips would be highly appreciated.

thanks in advance

0

• 

  romain.janvier

  • June 27, 2020 09:27

  Beware that e57 is a complex format and some software could leave you with e57 files without any sensor informations in it (only point clouds) that may leads to be a no go with RC. Typically in CloudCompare we do not rexport full sensor/grid informations in e57 files.

  cheers,

  0

  Comment actions Permalink
• 

  Erik Kubiňan CR

  • June 29, 2020 13:01

  What our software needs is ordered/structured data. If you have multiple scanning positions, I recommend you to export each as a separate file. Other than that, PTX file works the best currently in terms of errors and such. If you meet the requirements for the file but yet it fails to import it mostly is corrupted and reexporting from the registration software might help.

  0

  Comment actions Permalink

Please sign in to leave a comment.