Scan Splitting and Multi-Session Workflows for K1 and L2 Pro | XGRIDS Pro Guide

XGRIDS Pro Guide™ / Module 6: Advanced K1/L2 Pro

6.2 Scan Splitting and Multi-Session Workflows

Knowing when to end a segment and how to set up the next one correctly is what makes large projects processable. Poor split planning produces unusable data, not just larger files.

Section 1

When to Split a Scan

A scan that runs beyond the device battery limits or exceeds the processing capacity of your workstation can produce data that cannot be processed or that requires more time than the project schedule allows. Planned splits are better in every respect: they produce smaller files, give processing more manageable segments, and create natural checkpoints for quality review.

The L2 Pro and K1 each provide up to 90 minutes of scanning time per battery charge. Cold weather (below approximately 10°C) reduces this to around 72 minutes. Any project that requires more total scanning time than one battery charge will need at least one planned split regardless of processing considerations.

Reasons to Split a Scan

Battery change: The most common reason. Plan the split before battery level drops below 20%. Do not scan until shutdown occurs.
RAM and processing capacity: LixelStudio requires approximately 2 GB of RAM per minute of scan data. A 30-minute scan requires around 60 GB of RAM to process. Systems with less RAM than the scan requires will fail during processing.
Logical site divisions: Floor boundaries, fire doors, building wings, and parking structures are natural split points that also produce cleaner scan organization.
Drift risk in complex geometry: Long scans in challenging environments accumulate more trajectory drift than short ones. Splitting at transition zones reduces the total drift exposure per segment.

Map Fusion hard limits: LixelStudio Map Fusion accepts a maximum of 10 segments. Each segment must be under 20 minutes. Total combined duration of all segments must not exceed 200 minutes. Plan your splits to stay within these limits if the project requires merging segments.

Section 2

Where to Split: Choosing Good Transition Points

The Map Fusion algorithm joins segments by finding matching geometry in their overlap zones. A split at a point where the subsequent segment begins with nothing recognizable from the previous scan will fail or produce misalignment.

Characteristics of a Good Split Point

Feature-rich geometry visible from multiple angles, such as a corridor intersection, equipment cluster, or lobby with columns
A location you can return to and scan from the same approach direction for the next segment
Not in the middle of a long featureless corridor or against a blank wall
Not in an outdoor area with limited vertical structure visible to the LiDAR
At least 15 meters of planned overlap with the previous segment on each side of the split

Minimum Overlap Requirement

Segments must share at least 15 meters of overlap for Map Fusion to align them. This means the second segment must cover at least 15 meters of space that the first segment also covered, with the scanner traveling through it in a way that captures the geometry from similar angles.

Overlap less than 15 meters causes fusion failure. When planning the end of a segment, scan past the intended split point by at least 15 meters. Then begin the next segment 15 meters before that point and continue past it. The overlapping zone in the middle is where fusion does its work.

Section 3

Executing a Clean Split

The procedure at each split point is the same whether you are changing a battery, taking a break, or ending a floor. The sequence matters.

Scan past the split point

Continue scanning at least 15 meters past the location where you intend to end the segment. The scan data in this overlap zone is what the fusion algorithm uses to connect the segments.

End the segment intentionally, not at battery death

Tap Stop in LixelGO. Wait for the green light to become solid before handling the device. A solid green light means the project file has saved. Do not power off or remove the battery before the light is solid green; the project file is not recoverable if interrupted during save.

Document the split location

Note the room, landmark, or approximate position where the segment ended. This makes it faster to navigate to the correct overlap position when beginning the next segment.

Begin the next segment at least 15 meters before the split point

Walk back to a position at least 15 meters before the location where the previous segment ended. Initialize the scanner there and begin scanning. Move through the entire overlap zone before continuing into new territory.

Vary the angle of travel slightly through the overlap zone

Scanning the overlap zone from exactly the same path as the previous segment gives the fusion algorithm less to work with. Walking slightly different lines or pausing at a perpendicular angle provides geometry from different viewpoints and improves alignment confidence.

Section 4

Naming Conventions for Multi-Session Projects

Consistent naming is not a formality. When you have 8 scan segments across a 3-floor building and bring them into LixelStudio for Map Fusion, disorganized naming makes it impossible to verify which segments belong to which fusion project and in what order.

Recommended Naming Structure

Use the pattern: ClientName_SiteName_Date_FloorOrZone_SegmentNumber

For example: Breckenridge_Main_Library_20260205_FL1_S01, Breckenridge_Main_Library_20260205_FL1_S02, Breckenridge_Main_Library_20260205_FL2_S01.

Element

Guidance

Client name

Abbreviate to avoid long paths. No spaces; use underscores.

Site name

Building or specific location. Keep under 20 characters total including underscores.

Date

YYYYMMDD format. Makes chronological sorting automatic.

Floor or zone

FL1, FL2, B1, ROOF, EXT. Use consistent abbreviations across the project.

Segment number

S01, S02, S03. Zero-pad to ensure correct alphabetical sort order.

LAS export filenames must be 20 characters or fewer or they will fail to convert to RCP or E57 in some workflows. Keep your naming convention tight enough that the exported file name stays within this limit.

Section 5

Multi-Day Projects

Projects that span more than one day require the same discipline as multi-segment projects, with additional attention to site conditions that may have changed between sessions.

Continuity Between Days

If using RTK, re-establish fix status before scanning on day two. RTK data from a previous session is not carried forward.
If using ground control points, do not remove or disturb any GCP markers placed on day one until all scanning that references them is complete.
Control point names are case-sensitive. A marker named GCP_A on day one and GCP_a on day two will not be recognized as the same point by LixelStudio.
Verify that the Insta360 camera settings match the session from the previous day. Cameras reset to default settings after the battery is fully discharged overnight.

Previous 6.1 Camera Coloring Options Next 6.3 L2 Pro Drone Mode