5.7 Map Fusion Connection Visual
How scan segments link together through RTK, control points, or both, and the 2 configurations that always fail.
How Segments Connect
Every segment in a fusion project must link to at least 1 neighbor through valid RTK or matching control points. If any segment has no connection, it is excluded from the fused result. Use this diagram to verify your connection plan before going to site. Full detail is in 5.1 Fundamentals and 5.3 Collection.
Fusion Connection Patterns
Legend and Specifications
Segment Types
Connection Types
Outputs
Choosing a Connection Method
Applies to both processing pipelines. These patterns apply equally to LixelStudio (point clouds for CAD, BIM, survey) and LCC Studio (3DGS for visualization, virtual tours, LCC for BIM Revit plugin). Field collection is the same. See 9.3 LCC Studio Map Fusion for 3DGS processing steps.
RTK Connection
How: Each segment independently achieves Fixed RTK with at least 100 feet of effective coverage. A zigzag scanning path produces better results than a straight line. The shared coordinate system aligns them.
Why: Simplest method. No naming conventions, no coordination between segments. Eliminates the most common failure cause: CP naming errors.
Output: Global coordinates.
Best for: Outdoor projects with reliable satellite coverage.
Control Point Connection
How: Adjacent segments share identically named points in the overlap zone. Names are the only matching mechanism. Device must be on the ground when marking. For K1/L2 Pro, the procedure uses 1 shared point per junction; a second adds redundancy. For PortalCam, a minimum of 3 CPs in an L-shaped layout is required.
Why: Works everywhere, including GPS-denied environments. Combined with surveyed GCPs, delivers absolute accuracy indoors.
Output: Relative coordinates, unless at least 1 segment also has RTK.
Best for: Indoor, underground, tunnels.
Hybrid Connection
How: RTK where available, CPs where not. Methods can be mixed in the same project. Any segment with RTK gives the entire result global coordinates.
Why: Most real projects have both indoor and outdoor. If RTK drops to Float, a shared CP saves the connection.
Output: Global coordinates (if any segment has valid RTK).
Best for: Mixed environments. Most common approach for large facilities.
Invalid: No Connection
Isolated segment: No RTK, no shared CPs. Excluded from the fused output.
Complete overlap: 1 segment entirely inside another. Algorithm cannot compute the transformation.
Prevention: Plan fallback CPs at every segment break, even on RTK projects. Details in 5.6 Troubleshooting.
The Overlap Zone
The 1 Rule That Governs All Fusion
Every segment must connect to at least 1 neighbor through valid RTK or matching control points. A segment with no connection is excluded. This must be decided before collection begins because RTK data and CP names cannot be added after the scan.
Plan 65 to 100 ft of overlap, not exactly 50. The 50 ft minimum is a hard limit, but barely meeting it is risky because small field adjustments can push the actual overlap below the threshold. An overlap zone that falls short at 40 ft causes fusion failure. Building in a buffer protects against this. The overlap zone must also contain rich, stable surface features: lobbies, furnished rooms, equipment clusters, corridor intersections. Avoid stairways, narrow corridors, glass or mirror surfaces, monochrome or dark areas, and high traffic zones where objects move between segment collections. Feature-poor overlap zones fail even when distance requirements are met. Full planning guidance is in 5.2 Pre-Project Planning.
Need to Combine More Than 10 Scans?
Break the project into multiple fusion jobs
Map Fusion is limited to 10 segments and 200 minutes per job. For larger sites, process groups of up to 10 as separate fusion jobs, then combine the outputs downstream.
Point cloud (LixelStudio): Export each fused result as E57 or LAS. Merge in CloudCompare, Autodesk ReCap Pro, or Leica Cyclone. RTK-based jobs share a coordinate system and align on import.
3DGS (LCC Studio): Each fused model can be viewed in LCC Studio, published to the web, or imported into Revit via the LCC for BIM plugin. RTK-based jobs align automatically.
Field planning: Plan overlap zones between the last segment of 1 job and the first segment of the next. Mark CPs at cross-job boundaries if RTK is unavailable.
©2026 Alpine Reality Capture LLC • XGRIDS Pro Guide™ • Site Disclaimer