Announcements

Starting in December, we will archive content from the community that is 10 years and older. This FAQ provides more information.

Community
ReCap Forum
Welcome to Autodesk’s ReCap Forums. Share your knowledge, ask questions, and explore popular ReCap topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ReCap Maximum Point Cloud File Size

11 REPLIES 11
Reply
Message 1 of 12
Anonymous
4299 Views, 11 Replies

ReCap Maximum Point Cloud File Size

Hello,

 

I have a 90 Gb point cloud model consisting of 26 scans. I am wondering if there is a limit on the file size ReCap can handle? Or if there is a difference between basic ReCap and ReCap Pro with respect to file size? I would assume that file size shouldn't matter however I cannot get ReCap to properly display the point cloud. Yet when I import just one scan (much smaller file size) it has no issues. I can also mention, that I have no issues with the point cloud as it was generated using Leica Cyclone and exported in the .e57 format for import into Cylcone. 

 

I am a potential ReCap customer, but I need this answered as we often scan large projects.

 

Regards,

 

Chris

11 REPLIES 11
Message 2 of 12
Patrick_Aps_9121
in reply to: Anonymous

I have seen no limits in Recap or Recap Pro.

However, for this size of clouds you will need 32 or 64 GB or RAM and all data on an internal SSD hard drive to have some performance.

Message 3 of 12
denis_lachaud
in reply to: Anonymous

Hello,

 

Impossible for me to import a .e57 97go  file size in recap pro 4.2.

No message error after choosing the file but it returns to home page.

 

If someone have a solution,

 

Best regards,

 

Message 4 of 12
JvanReij
in reply to: denis_lachaud

Hello @denis_lachaud,

 

What are your computer specs? (see message @Patrick_Aps_9121)

Best regards,
Josha van Reij
Arcadis NV
BIM manager


Message 5 of 12
anil_mistry
in reply to: JvanReij

Hi @denis_lachaud,

 

I'm just checking in to see if you need more help with this. Did the suggestion that @JvanReij provided work for you?

If so, please click Accept as Solution on the posts that helped you so others in the community can find them easily.



Anil Mistry
Technical Support Specialist
Message 6 of 12
denis_lachaud
in reply to: anil_mistry

Thank you everybody for your quick answer.

 

I have tested on 2 computer Dell.

My first test use a Dell Workstation with Windows 7 64Bit ands 24 Go RAM

My last test use a local SSD disk 1To (but 350Go available)

 

 

It 's a Dell Precision with Windows 7 64Bit ands 32 Go RAM.

 

That I don't anderstand it's there is no error message but just a come back to the firs step.

 

If you have any other solution

 

Thanks again,

 

Best regards

Message 7 of 12
anil_mistry
in reply to: denis_lachaud

Hi @denis_lachaud,

 

I was wondering what version of ReCap Pro you are using. Also, what is your raw data file format? 

 

Thank you and have a great day!



Anil Mistry
Technical Support Specialist
Message 8 of 12
denis_lachaud
in reply to: anil_mistry

Hi,

 

Thanks for your interest.

 

My raw data are .e57 files export from Leica Cyclone (No error message during export) and my Recap Pro version is Recap Pro 2017 4.2.2.15

 

Thanks for your help.

 

Best regards

Message 9 of 12

If you want to do a fun experiment, export from Cyclone PTGs and index them.  Cyclone and Recap appear to handle them as a one and done thing.  Processing a huge E57, I believe, requires Recap to parse the information.  Its just another step.  

 

If you take and isolate scans in Cyclone and export individual scans as E57s, you may run into a naming problem with Recap.  All the RCS files want to be Scan-1, or something similar depending on your Cyclone setup or Leica machine.  This means if you add more E57's, they won't index.

 

In short, take a crack at a PTG, or even PTX. 

Message 10 of 12

Thank you for your solution.

 

I tested to export PTX from Cyclone (the size is bigger than .e57) - about 180Go). The import in Recap is correct but I lost géoreferencing for many scans. 

Maybe it's the same problem, if there are too many scans, the denomination in Recap failed.

So I have again a mistake because my aim is to import all my georefenced scans independently in Recap in order to have a a georeferenced cloud with independed scans in recap.

 

I'll try with PTG,

 

If someone has a new idea.

 

Thanks again

Message 11 of 12

Make sure in Cyclone you read the correct coordinates.  If you set coordinates by UCS, set that coordinate system as default for the scan world.  If the coordinates are correct in cyclone by registering to control files, you should already be good.  The PTG and PTX should carry the same coordinates.  This is not the case with a pts from Cyclone.

 

Recap and Cyclone should read the same coordinates.  I’m not sure how comfortable you are with Cyclone and the Recap interaction, but many problems occur in Cyclone and not Recap.  Please remember that PTG and PTX are all metric along with RCS.  Because we heavily use Cyclone, we keep Recap a little more on the simple side for our clients general usage.  

 

Youll need many checks to verify you’re not carrying over a Cyclone mistake through Recap.  Check and doublecheck! 

 

Hope this helps.  Recap has fantastic registration results too if you need another check.  

Message 12 of 12

....sorry one more thing.  Take 1 Scan from your Cyclone mode space , export that 1 scan to PTG, index with Recap.  This takes just minutes to verify your approach without wasting an entire day of exporting!  Cyclone will let you export just one or two scans, we like to isolate on layers.  This approach will also let you keep adding to the Recap Project.

 

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Rail Community


 

Autodesk Design & Make Report