Using Manual Registration - Target Data when Combining Large Projects

[Anonymous]

Hello,

I am currently registering a large project with over 500 scans. I have broken down the project into smaller sub-areas that consist of about 40-50 scans, which are saved as their own *.rcp project database.

Each of these sub-areas are registered using the manual registration by picking black and white targets as well as spheres, I am using this method to verify the fit via the Target Data registration report.

Then, I have one overall *.rcp project database where I import each of the sub-area databases to create the combined ReCap database. When I import the sub-area databases I can no longer see the black and white targets or spheres that we previously added within each sub-area database and nothing shows up in the Target Data registration report.

It looks like when I am combining these sub-areas into the overall database my only option to combine datasets is by cloud to cloud registration and not target to target, is this correct? Is the only solution to get the target information in this overall combined database by re-adding all of the targets?

[anil_mistry · Accepted solution]

Hi @Anonymous,

Thank you for participating in our Community!!! That’s correct, Target data is not imported when bringing one RCP into another. If you need to create a single project with combining scans using targets, then you may need to add targets again. Please, let me know if this helps.

Thank you and have a great day!

Please select the Accept as Solution button if my post solves your issue or answers your question.

[Anonymous]

Thank you for posting this confirmation that target information is lost when combining target enhanced RCP files into a bigger RCP file.  FYI-I am currently using ReCap version 5.0.4.17  I would like to know if this issue is fixed in ReCap 2020?

Also, in my 2019 version of ReCap, when I select my targets again, their RMS values do NOT reflect the same great values as shown in the original RCP.  This issue gets resolved when I SUSPEND my project and reopen it.  See the attached 3 short videos which highlight this issue.  Watch them in order of zero, 1, & 2.