The SiteMap object in Cyclone REGISTER 360 PLUS is used to define areas of a registration by the setups in the SiteMap. SiteMaps can be added in the Import area or the Review and Optimize area. Each SiteMap can have its own UCS, control, and background image.
A Bundle can span multiple SiteMaps.
In many cases, the project may only have one SiteMap, but in larger registrations it is useful to break up the registration into SiteMaps that help define areas of the registration, such as multi-floor buildings or large complex areas where multiple bundles are connected by control.
In the Import area, multiple SiteMaps can be made and setups can be populated in them. An example is a multi-floor building where setups for each floor go into separate SiteMaps, so there could be one SiteMap per floor. In the Import area setups in separate SiteMaps will NOT be registered together. This allows for bundle formation to happen per SiteMap, then after import, setups can be joined to attach the SiteMaps together forming one bundle that spans all the floors or SiteMaps.
Only one bundle can be published at a time. However, using control will enable the publishing of multiple bundles at once since the bundles are in the same coordinate system (all bundles must be registered to control).
You can only proceed to Finalize after all setups are in one bundle, so if you have more than one bundle you will need to register setups from one SiteMap to the other SiteMap to form one bundle that spans both SiteMaps.
The exception to the one Bundle rule is where multiple bundles are rotated into control. In this case, the bundles remain separate, but since they are on the same control the whole project can be published at the same time.
You can also have a bundle under one SiteMap and another bundle under another SiteMap. In this scenario you could publish either SiteMap, but not both at once because you are only allowed to publish one bundle at a time.
You can also start with one bundle and add more SiteMaps, then take setups and drag and drop them into the newly added SiteMap(s). This way you will still have one bundle but the bundle's setups are in separate SiteMaps. This is useful when viewing a multi-floor building as the SiteMap view is always top-down, so if you have all the floor's setups in one SiteMap, looking down, it will be hard to view each floor, but if you separate the setups into different SiteMaps, one per floor, you can view each floor's setups clearly in SiteMap view.