XGRIDS Pro Guide™ / Module 2: XGRIDS Foundations

2.5 Critical Basics

You have scanned once. You know what initialization feels like, what the LED sequence means, and what happens if you move too early. Now here is why all of that matters, and the principles that separate good scan data from data that has to be redone.

Section 1

SLAM Drift

SLAM tracks position by matching what it currently sees to what it has previously seen. Every match introduces a small amount of error. Over distance, those small errors compound. The scanner does not know they are accumulating, it has no external reference to compare against. This compounding positional error is called SLAM drift, and it affects all mobile LiDAR systems regardless of manufacturer or price.

XGRIDS Multi-SLAM fuses three sensors simultaneously, LiDAR, visual cameras, and IMU, which reduces the rate at which drift accumulates compared to single-sensor systems. But it does not eliminate drift. The IMU alone introduces a leveling error of approximately 0.07 degrees. SLAM drift compounds across all three axes (x, y, and z). For most indoor projects, the effect is modest. For large-scale or long-duration scans without control, it becomes significant.

Drift is the reason initialization position matters. Drift is the reason loop closure matters. Drift is the reason control points exist. Every technique decision in this guide traces back to managing it.

Section 2

Loop Closure

Loop closure is the primary mechanism for correcting accumulated drift. When the scanner returns to an area it has previously scanned, the SLAM algorithm compares the current geometry to the stored geometry of that location, measures the discrepancy, and distributes a correction back across the stored trajectory. The entire path between the two visits is adjusted.

This is why a scan route that creates genuine loops produces more accurate data than a straight-line route of the same length. The loops give the system the reference comparisons it needs to correct itself in real time.

Loop closure has two requirements. Both must be met.

1. You physically return to an area you have already scanned.

2. Your viewing angle when you return is within 40 degrees of your original angle at that location. Returning from the opposite end of a corridor often fails this condition, the geometry looks different enough from the reversed direction that the match fails.

A route that ends at the starting point after traveling the entire perimeter from only one direction does not reliably trigger loop closure. Plan routes with multiple crossing loops, not a single perimeter circuit.

When to Create Loops

At any point where you can return through an area you previously walked, do it deliberately, not incidentally
At the end of every scan session, return near the initialization point from a similar angle to your starting position
During large-scale scans, plan at least one midway loop before you have traveled more than a few hundred meters from your start
In challenging environments (long corridors, large open areas), loop more frequently, not less

Section 3

Relative vs. Absolute Accuracy

These are two different properties of a point cloud. Conflating them leads to incorrect deliverables and client expectations that cannot be met.

Relative Accuracy

Internal consistency of the point cloud. Whether a wall is planar. Whether measured dimensions repeat between two measurement points. Whether the geometry holds across the scan without distortion. Achieved through good technique and loop closure. Does not require GPS, RTK, or GCPs. The published relative accuracy figures (1.0 cm RMSE for the L2 Pro, 1.2 cm for the K1) are achievable with technique alone.

Absolute Accuracy

How closely the point cloud registers to a real-world coordinate system. Whether a point in the scan corresponds to a verifiable coordinate on earth. Relative accuracy alone cannot produce this, it requires RTK, PPK, or surveyed ground control points applied either during or after the scan. The published absolute accuracy figure (3.0 cm RMSE for both the L2 Pro and K1) requires RTK or GCPs to be applied.

What the Specifications Mean, and What They Do Not

The accuracy figures in XGRIDS documentation are achievable results under proper conditions, not guaranteed outcomes from any scan. A scan with poor technique, no loop closure, and no control can produce data that is far outside these figures. The specifications describe what the system is capable of when operated correctly. They describe your ceiling, not your floor.

Device

Relative Accuracy

Absolute Accuracy

L2 Pro

≤1.0 cm RMSE

≤3.0 cm RMSE (with RTK or GCPs applied)

≤1.2 cm RMSE

≤3.0 cm RMSE (with RTK or GCPs applied)

PortalCam

2 cm RMSE

Not applicable. 3DGS output only.

Section 4

Decisions You Cannot Undo After the Scan

Most scanning mistakes are recoverable. Some are not. These are the decisions that must be made correctly in the field, they cannot be corrected in LixelStudio or LCC Studio after the fact.

Georeferencing strategy RTK must be configured and active before scanning begins. GCPs must be physically placed in the environment and marked in LixelGO during the scan. There is no way to add georeferencing to a completed scan after the session ends. If a client requires absolute accuracy and you scanned without RTK or GCPs, the data cannot be corrected, the project must be rescanned.
Initialization quality If the initialization position was poor or the device was moved during the 15-second countdown, the starting reference frame is corrupted. The error propagates through the entire session. This cannot be corrected in processing. The scan must be redone from the beginning.
Coverage gaps Areas that were not scanned do not exist in the data. Processing cannot fill in geometry that was never captured. If a room was missed or a floor was partially skipped, that area requires a return visit. The LixelGO preview in the field is the only practical opportunity to catch this before leaving site.
GCP naming The names you type in LixelGO when marking ground control points during the scan must exactly match the point names in your coordinate CSV file, character for character, including capitalization. A mismatch means LixelStudio cannot apply the coordinate to the point. If the naming is inconsistent, the control point is effectively unused.
Scan duration relative to RAM If a single scan exceeds what your processing machine's RAM can handle (approximately 30 minutes on 64 GB, 60 minutes on 128 GB), LixelStudio will fail mid-processing. The scan data is not lost, but you cannot process it as a single session. You must split it and use Map Fusion, which requires additional planning and processing time that was not in the original project schedule.

Section 5

Before You Leave Site

A five-minute review on site is worth hours of recovery work at the office. Before packing up after any scan session, confirm each of the following.

The scan stopped cleanly, the LED reached solid green before the device was powered off
The project appears in LixelGO with a reasonable duration and file size for the area covered
The point cloud preview shows no large coverage gaps in areas you walked through
If RTK was used, the session included more than 100 valid RTK-fixed points and more than 10 meters of movement while fixed, LixelStudio requires both to apply the coordinate transformation
If GCPs were used, the names logged during the scan match your coordinate file
Battery state is noted, if a battery warning fired during the session, check the scan duration to confirm the data captures the full intended area

Foundations complete. Module 3 covers field technique in depth: route planning, movement fundamentals, challenging environments, and coverage strategy for every project type.

Movement and Posture →