5.1 Map Fusion Fundamentals
What Map Fusion is, when to use it, the hard limits that govern it, and how the three connection methods work.
What Is Map Fusion
Map Fusion is a post-processing mode in LixelStudio that combines multiple independent L2 Pro or K2 scan segments into a single unified point cloud. Each segment is processed through SLAM optimization individually, then the fusion algorithm aligns and merges them using shared spatial reference: RTK coordinates, matching control point names, or both.
It exists because a single SLAM session has limits: battery life, RAM, and site scale. Map Fusion lets you break a large project into manageable segments during collection and reassemble them into one coherent dataset in post-processing. It is an alignment tool for sequential segments that together cover a complete site, not a stitching tool for redundant data. Segments must share spatial reference at their connection zones; that reference is what locks them together accurately.
When to Use It
Five situations make Map Fusion the correct approach rather than attempting a single long scan.
Projects Exceeding Battery Life
The L2 Pro and K2 each provide up to 90 minutes of scanning time per battery charge. Large facilities, warehouses, campuses, and multi-floor commercial buildings require more time than a single battery supports. Plan segment breaks at logical transition points and join the segments in post-processing.
Projects Exceeding RAM Capacity
LixelStudio holds the entire scan trajectory in memory during SLAM optimization. On a 64 GB machine, scans longer than approximately 30 minutes risk failure. On 128 GB, the ceiling is approximately 60 minutes. If project scope exceeds your hardware, process shorter segments that fit in RAM, then fuse the results.
Multi-Floor Buildings
Moving between floors on stairways creates SLAM stress: narrow geometry, repetitive structure, brief feature interruption. Breaking at floor transitions and fusing produces more reliable results than carrying a single session through multiple stairways.
Long Linear Environments
Tunnels, mine galleries, and corridors exceeding 1,600 ft (500 m) are not suitable for a single Narrow Space session. Break these into segments of 1,600 ft or less and fuse them with relative control points. Field execution for this scenario is covered in 5.3 Field Collection.
Recurring Scan Projects
Facilities that require periodic rescanning (construction progress monitoring, facility management, asset tracking) use Map Fusion to merge new scan segments with existing baseline data. Only the changed zones need recapture; the new segments fuse with the unchanged baseline through shared control points.
This requires control point infrastructure planned into the baseline scan from day one. Control points cannot be added to a completed scan after the fact. If the baseline has no shared control points with the future rescan zones, fusion is not possible. See 5.2 Pre-Project Planning for permanent control point requirements.
Loop closure still matters within each segment. Map Fusion aligns segments to each other, but it cannot fix drift that already exists inside a segment. Each individual scan must be executed with proper loop technique before fusion adds any value.
Hard Limits
These are system constraints, not recommendations. Exceeding them causes fusion to fail or produce unusable output.
- Maximum 10 segments per fusion job
- Maximum 200 minutes total scan duration across all segments in a job
- Keep each segment within 20 minutes (target 12 to 15 for buffer). Longer segments demand significantly stronger processing hardware
- Minimum 50 ft (15 m) overlap between consecutive segments; plan 65 to 100 ft (20 to 30 m) for field adjustment room
- Shared control points per junction: 2 advised, 3 recommended. One is the bare minimum and leaves no redundancy. Narrow Space requires 2
- Same device model per fusion job. L2 Pro and K2 segments cannot be mixed, and 16-line and 32-line L2 Pro units cannot be fused together
Overlap placement determines fusion reliability. Overlap zones with rich, stable surface features (furnished rooms, structured intersections, equipment areas) give the algorithm strong matching geometry. Hallways, stairwells, and reflective surfaces give it weak or ambiguous geometry. Poor overlap placement is the most common cause of fusion failure on otherwise good data.
Complete overlap also causes failure. If one segment's scan path is entirely contained within another's, the algorithm cannot determine the spatial relationship between them. Each segment must cover some unique area, with the overlap zone serving as the connection bridge, not the entire content of the segment.
Connection Methods
Map Fusion uses one of three methods to establish alignment between segments. The method determines whether the fused output has global coordinates, relative coordinates, or no georeferencing. This decision must be made before collection begins; it cannot be applied retroactively.
RTK-Based Fusion
Each segment carries valid RTK data acquired during scanning. The fusion algorithm uses the shared coordinate system embedded in each segment's RTK record to align them.
- Requires Fixed RTK status during scanning, not Float or Single Point
- Each segment must independently meet RTK validity thresholds
- Any segment with valid RTK pulls global coordinates into the fused output
- Best choice when outdoor RTK coverage is reliable across all collection windows
Control Point Fusion
Shared physical locations are marked with identical names across consecutive segments. The algorithm matches same-named points between segments to establish alignment.
- Plan 2 identically named points per junction; 3 is the recommendation. One can work but leaves no redundancy
- Point names must match exactly: every character, every capital letter. Never reuse a name for a different physical location
- Mark with the device set on its standard metal control point base on the ground
- Strongest method: end one segment and start the next without moving the device, marking the same point in both. See 5.3 Field Collection
- Rescan 50 ft (15 m) of overlap after marking each control point
- Output has relative coordinates unless RTK is also present
Hybrid Fusion
Some segments carry RTK; others connect through shared control points. The algorithm uses whatever reference is available per segment pair. This is the most common approach for large mixed-environment projects: outdoor areas on RTK, interior areas on control points.
- Any segment with valid RTK pulls global coordinates into the result
- Control point connections fill the gaps where RTK was unavailable
The Four Valid Connection Patterns
Official documentation defines which configurations the fusion algorithm can resolve. Every segment must be linkable to at least one adjacent segment through one of these patterns.
- All segments have RTK
- No RTK: consecutive pairs share identically named control points
- Segment 1 has RTK; segments 1 and 2 share control points; segments 2 and 3 share control points
- Segments 1 and 2 have RTK; segments 2 and 3 share control points
A segment with no connection to its neighbors cannot be fused. This is a hard requirement, not a guideline.
What Comes Out
The output of a successful Map Fusion job is a single unified point cloud spanning all input segments. If any segment carried valid RTK, the output has global coordinates. If only control points were used, the output has relative coordinates: internally consistent geometry with no absolute position.
The fused result exports from LixelStudio as LAS, LAZ, PLY, or E57. For Autodesk workflows, the built-in LAS-to-RCP converter produces RCP without requiring a ReCap Pro license. The same export selection and quality considerations that apply to single-scan outputs apply here. Regardless of how many segments contributed, the final output is one dataset.
Processing time for Map Fusion is substantially longer than single-scan processing, and hardware requirements are higher. The next sections cover pre-project planning, field collection execution, and the full processing workflow.
Map Fusion exists in two processing pipelines. This module covers Map Fusion in LixelStudio (point cloud output for CAD, BIM, and survey deliverables). Map Fusion also exists in LCC Studio for 3D Gaussian Splat output, supporting the L2 Pro, K2, and PortalCam. The field collection requirements are the same; the processing workflow differs. See Module 9 LCC Studio for the 3DGS processing procedure.
Next: 5.2 Pre-Project Planning for Fusion, planning segment structure before arriving on site.
©2026 Alpine Reality Capture LLC • XGRIDS Pro Guide™ • Site Disclaimer