Register RTC scans with pre-registered cloud

[MattS]

Hi All

Using Register360+ 2023.0.0

I have an e57 (from TBC) that contains multiple pre-registered clouds and would like to add a few extra RTC scans.

When I try to do a visual alignment the e57 file seems to be range limited which means the individual scans often have no visible overlap. However the e57 looks good when viewed as a setup cloud.

Is there a setting to change somewhere or any other tips for achieving this?

Thanks
Matt

[Mackkowalski]

If there is commonality between the RTC scans and the pre-registered you could create virtual of USC targets and along using those. You might be able import the pre registered selecting the pre-registered option then export a unified cloud. Which you should then be able to register the RTC360 scans with

[MattS]

Thanks for the reply, but you have lost me with "create virtual of USC targets and along using those."

I don't think I need to unify and reimport because I can already use the split view to register if need be, but it would make life a lot easier if the alignment method would show the whole of the dataset.

[badam]

Thanks for the reply, but you have lost me with "create virtual of USC targets and along using those."

I don't think I need to unify and reimport because I can already use the split view to register if need be, but it would make life a lot easier if the alignment method would show the whole of the dataset.

is this data structured? so it does have multiple setups in register 360? if yes maybe your problems comes from the import settings how register 360 filters cloud2 cloud points.

or if it is an unstructured cloud with only 1 "setup" visible in register 360 at the center of the bounding box?
if latter then you can create new waypoints (in setup or bundle cloud pick point then rightclick context menu if i recall correctly) so you could have different positions to register to.
PS:
https://www.youtube.com/watch?v=1NDHGZ6P8pQ

[gsisman]

Thanks for the reply, but you have lost me with "create virtual of USC targets and along using those."

I don't think I need to unify and reimport because I can already use the split view to register if need be, but it would make life a lot easier if the alignment method would show the whole of the dataset.

is this data structured? so it does have multiple setups in register 360? if yes maybe your problems comes from the import settings how register 360 filters cloud2 cloud points.

or if it is an unstructured cloud with only 1 "setup" visible in register 360 at the center of the bounding box?
if latter then you can create new waypoints (in setup or bundle cloud pick point then rightclick context menu if i recall correctly) so you could have different positions to register to.
PS:
https://www.youtube.com/watch?v=1NDHGZ6P8pQ

If you only see one Red "SETUP" DOT as BADAM said, then you have to CREATE a Pseudo Setup or "Waypoint near the area of the RTC 360 scan you want to add, then do your Visual alignment with the overlaps between the RTC360 scan and the Waypoint C2C creation.
What I don't like about the C2C waypoint is it is Range limited to about 50 or 75 feet and many times you need more than that in an outdoor setting. I've requested Leica to add a Range filter at the point of creation (similar to choosing the target height box), so you can tell it how large a radius of C2C data to include when creating the waypoint.

[MattS]

Waypoints worked great. Thanks guys.