As I posted elsewhere on this forum, several of these exported scans crash CR outright, e.g.:
www.insightdigital.org/temp/import.7z
I exported a group of ~70 point clouds from Leica Cyclone. The scans were made with two Lecia Cryax HDS-3000 and one Mensi GS-200 scanners.
Here is an example of the ~65 scans that import into CR fine, but may not align:
www.insightdigital.org/temp/hypo.7z
Aignment on a reasonably fast i7 with 32GB of RAM is now 12+ hours for ~65 scans. CPU is consistent (~13%), RAM (9%). Is this time and resource use normal or a sign that the alignment isn’t working?
Thanks!
Hi Kevin Cain
Aignment on a reasonably fast i7 with 32GB of RAM is now 12+ hours for ~65 scans. CPU is consistent (~13%), RAM (9%). Is this time and resource use normal or a sign that the alignment isn’t working?
No, its not working it should be aligned in 1-2 minutes max Co can cancel the alignment
The Lecia Cryax HDS-3000 (10 years ?!? ) and Mensi GS-200 (12 years ?!? ) scanners are some older generation technology ??
Can send us whole dataset from it for inspection of the data ? Send it to milos.lukac@capturingreality.com as the previous PTX have internal issues. not on our side…
What software (version ) use for processing of the scanns to PTX ?
The PTX files were delivered by two companies, we have only the PTX, not the original project files – however, these are older projects so those files would not be readable.
What is the specific problem with these files in CR?
If CR doesn’t like multiple viewpoints, should I merge the data in GSI / MeshLab / et cetera before CR?
Hi Kevin Cain
The issue is the lasers have probably “low resolution” results and as have already asked im a bit curious what sw was used to export the PTX. its because have seen some “beta” versions of Cyclone with not proper PTX exports…
This are your only laser scanners ? or have something from say 2010+ years ?
we have almost no issues with nowadays devices from Faro or Leica ( other too ) data…
Im much more sure the merging of data will not help here…
If CR will only work with data from scanners in the last few years, it won’t work for those in archaeology like me, who often need to use data gathered years ago. Of course, I know of no reason why the age of the scanner makes any difference: PTX as a format has been around for many years. Points are points, after all.
I can’t answer your question about the specific version of Cyclone these were exported from, as they were handed to us by the scanner service provider.
If I take two point clouds (with strong overlap) containing only XYZ data, it would remove any question of PTX format parsing. Would you recommend that?
Hi Kevin Cain
I can’t answer your question about the specific version of Cyclone these were exported from, as they were handed to us by the scanner service provider.
= OK
If I take two point clouds (with strong overlap) containing only XYZ data, it would remove any question of PTX format parsing. Would you recommend that?
= Yes if can make “fresh” scans with the scanners and send it as PTX ( try even E57 Export if possible )
I don’t know what you mean by ‘fresh’ scans. Do you mean re-scanning? That wouldn’t be possible.
If you can publish your PTX parser code or give a simple test case, that would be useful to know what CR expects.
Is there a way for you to convert simple XYZ point clouds to your preferred PTX input?
Thanks,
-Kevin
Hi Kevin Cain
I don’t know what you mean by ‘fresh’ scans. Do you mean re-scanning? That wouldn’t be possible.
so cannot make clean scann with that scaner ?
Is there a way for you to convert simple XYZ point clouds to your preferred PTX input?
Will not work that easy… save your time
best if digg intro official Leica description of the PTX format
http://w3.leica-geosystems.com/kb/?guid … 79E5937CB2
No, it’s not possible to go back to the site and re-scan from scratch, if that’s what you are suggesting.
It seems that the PTX files I uploaded respect the structure you indicate on the Leica page.
If you could diagnose a specific problem with the PTX files I provided, that would help.
If not, let’s stop here.
-Kevin
Hi Kevin Cain
No, it’s not possible to go back to the site and re-scan from scratch, if that’s what you are suggesting.
= no just suggesting to get fresh scann with that devices and export the PTX to see what you get now for a PTX file
It seems that the PTX files I uploaded respect the structure you indicate on the Leica page.
as have seen have tried to import it in Faro scene but cannot get a look on the data as the Faro scene crash
when trying to get a 3D view.
If you could diagnose a specific problem with the PTX files I provided, that would help.
= can take a look but it will take some time… But as im say even Faro Scene have issues to get the PTX in.
its not common that get every scan with different resolutions ( from same device ) like its in this PTX
OK, I see what you’re asking for – testing a current scan from the same equipment.
Unfortunately, that would still leave me with no way to work with these scans, which of course is my whole point.
I’ll try to import these PTX files in the current Cylone, then export out as PTX to CR.
Hi Kevin Cain
Im asking to try it out as have seen more times that some “unoficial versions” Cyclcone software PTX export have not worked.
as there was something with proper PTX exports…
So the new scans and new processed data give us a CLEAR view on the proper structure of the scanner data…