XGRIDS Pro Guide™ / Module 10: Resources

10.3 Accuracy Reference

What the published specifications actually mean, what conditions produce them, and how to choose the right accuracy method for each AEC project type.

What the Published Specifications Actually Mean

The accuracy figures published by XGRIDS are achievable results under defined conditions. They are not guaranteed outcomes from any scan regardless of technique, environment, or control strategy. Understanding what each number represents prevents misrepresentation to clients and unrealistic expectations in the field. RMSE figures also assume proper field procedure and unbiased error distribution. Real-world results can be affected by atmospheric conditions, antenna geometry, multipath from nearby structures, satellite count, baseline length to the correction source, and CRS or geoid configuration errors. Any of these can introduce systematic error that degrades outcomes below the published specification regardless of Fixed status or GCP count.

L2 Pro

1.0 cmRelative accuracy (RMSE)
3.0 cmAbsolute accuracy (RMSE) with RTK or GCPs
2.0 cmRepeat accuracy (RMSE)

K1

1.2 cmRelative accuracy (RMSE)
3.0 cmAbsolute accuracy (RMSE) with RTK or GCPs
2.0 cmRepeat accuracy (RMSE)

PortalCam accuracy note: The PortalCam produces 3D Gaussian Splat output only, not georeferenced point clouds. Published internal test data shows ranging error below 1% versus a laser ruler across multiple scenarios (2 outdoor, 1 indoor). Absolute coordinate output is not applicable. The PortalCam is designed for visualization and measurement within LCC Studio, not for geospatially anchored deliverables.

Relative Accuracy

Relative accuracy is the internal consistency of the point cloud: whether a wall is planar, whether measured dimensions repeat reliably, whether the geometry holds across the full scan without distortion. A scan with good relative accuracy looks correct and measures correctly within itself, even if it is not registered to any real-world coordinate system.

Relative accuracy is achieved through correct technique and loop closure. It does not require RTK, GCPs, or any external reference. It is the baseline result from any properly executed scan with genuine loop closures throughout the route. In environments with poor scene structure, long linear paths without loops, or technique errors, relative accuracy degrades regardless of which device is used.

Absolute Accuracy

Absolute accuracy is how closely the point cloud registers to a real-world coordinate system. It requires external control: RTK, PPK, or surveyed ground control points. Technique alone cannot produce absolute accuracy, no matter how well the scan is executed.

The 3.0 cm RMSE absolute accuracy figure applies when RTK or GCPs are used correctly. It is not the accuracy of a pure SLAM scan. A scan without any georeferencing has no defined absolute accuracy because it has no connection to a coordinate system.

The Two Sources of Elevation Error

Elevation error in SLAM scans comes from two independent sources that must be addressed separately:

IMU leveling error: The SLAM system uses the IMU to determine level. The average IMU leveling error is approximately 0.07 degrees. Over large areas, this small angular error compounds into meaningful elevation discrepancy. RTK eliminates this error by providing an absolute vertical reference. Surveyed GCPs with Z coordinates also eliminate it.

SLAM accumulated drift: SLAM systems accumulate positional error in X, Y, and Z over distance due to the absence of absolute constraints. Loop closure distributes and reduces this error. Ground control points constrain it. The denser the control point network, the smaller the residual drift error. RTK alone does not fully address SLAM drift across long trajectories.

This is why the hybrid approach (RTK plus GCPs) produces the best results for demanding projects: RTK eliminates IMU leveling error and GCPs constrain accumulated SLAM drift across the dataset. Each addresses a different error source.

What Loop Closure Does and Does Not Fix

Loop closure is the mechanism by which SLAM corrects accumulated drift. When the scanner returns to a previously visited area and the algorithm detects the match, it measures the accumulated error and distributes the correction back across the trajectory. Loop closure requires two conditions: you physically return to an area you have already scanned, and your viewing angle when you return is within approximately 40 degrees of your original angle at that location.

Loop closure improves relative accuracy. It does not provide absolute accuracy. A perfectly looped scan with no georeferencing still has no connection to a real-world coordinate system.

Realistic Accuracy Outcomes by Method

The following table shows the accuracy outcomes achievable with each control method, the conditions required to achieve them, and the factors that degrade each result. These ranges reflect field reality, not idealized test conditions.

Method
Typical Result
Required Conditions
What Degrades It
Notes
Pure SLAM, no georeferencing
Relative accuracy: 1.0–1.2 cm RMSE (L2 Pro / K1)

Absolute accuracy: undefined
Correct initialization, consistent walking speed, genuine loop closures throughout the route, feature-rich environment
Long linear routes without loops, featureless environments (blank corridors, open fields), excessive walking speed, poor initialization, scan duration beyond 60–90 minutes without control
Appropriate for renovation documentation, internal as-builts, visualization, and any deliverable that does not require georeferenced coordinates
XGRIDS relative control points (sticker targets)
Improved relative accuracy; reduced drift across long trajectories

Absolute accuracy: undefined
Points distributed throughout the scan route at regular intervals, not collinear, marked correctly in LixelGO
Points placed only at start and end, all points in a single line, points concentrated in one area of the scan
Constrains SLAM drift internally without providing any real-world coordinate reference. Use when geometry must be consistent over large areas but absolute registration is not required
RTK only
Absolute accuracy: approaching 3.0 cm RMSE under optimal outdoor conditions
Fixed satellite status confirmed before scan begins (not Float), more than 10 valid satellites, at least 10 meters of movement while Fixed, more than 100 valid RTK points logged, RTK antenna within 20 degrees of vertical throughout the scan
Indoor use (RTK signal frequently does not achieve Fixed), tree canopy and urban canyons blocking sky view, antenna tilt exceeding limits, moving before Fixed status is confirmed, scan beginning during the initial fix period
Eliminates IMU leveling error. Does not fully constrain SLAM drift across long trajectories. Most reliable for outdoor open-sky environments. Verify Fixed status in LixelGO before trusting it for any absolute coordinate deliverable. Real-world RTK accuracy is also affected by atmospheric conditions, multipath from nearby structures or machinery, baseline length to the correction source, antenna phase center offset, and satellite geometry. These factors can degrade results below the published specification even when Fixed status is maintained throughout the scan.
GCPs with surveyed coordinates
Absolute accuracy: 3.0 cm RMSE or better when spacing and distribution requirements are met
L2 Pro: GCP spacing at most 100 m, evenly distributed, not collinear. K1: spacing at most 50 m. Points placed at stable, identifiable locations. GCP names in CSV match LixelGO entries exactly, character for character
Sparse or clustered control (all points in one area), collinear point distribution, name mismatches between CSV and LixelGO entries, scanner dropped or jarred when placing on marker, insufficient dwell time at each point
Best method for indoor environments, underground, and any location where RTK signal cannot achieve Fixed. Eliminates both IMU leveling error and constrains SLAM drift. Requires pre-surveyed coordinates
Hybrid: RTK plus GCPs
Best achievable absolute accuracy. Typically at or better than 3.0 cm RMSE when both are applied correctly
RTK Fixed status confirmed, plus GCP network meeting spacing and distribution requirements
Any failure in either component. If RTK did not achieve Fixed, the RTK component does not contribute. GCP failures are the same as in the GCP-only method
RTK addresses IMU leveling error (Coordinate System 1). GCPs constrain accumulated SLAM drift (Coordinate System 2). Recommended for high-accuracy deliverables where both error sources must be mitigated. Required for legal survey-grade work
PPK (Post-Processed Kinematic)
Comparable to or slightly better than RTK in absolute horizontal accuracy; dependent on base station quality and baseline distance
GNSS base station data logged during the scan, post-processing in LixelStudio with PPK workflow, sufficient satellite observation quality
Same sky-view limitations as RTK. Long baseline distances from the base station. Base station data gaps. Not applicable indoors
Useful when NTRIP corrections are unavailable in the field. Requires access to a local base station or compatible CORS network data. Processing is performed in LixelStudio after the scan. Operational friction is higher than RTK: base station data must be logged continuously during the scan without gaps, baseline distance to the base station must stay under 5 km for reliable results, base station coordinates must be independently verified, and ionospheric activity during the scan window affects trajectory quality. A single gap in base data or an unverified base position can produce a mixed-quality or failed trajectory that is not recoverable.

Method Selection by AEC Project Type

The right accuracy method depends on the deliverable requirement, not the device capability. Choose based on what the client or downstream workflow actually needs, and confirm that requirement before leaving for the field. The control strategy cannot be changed after the scan.

As-Built Documentation for BIM

Recommended: GCPs or Hybrid

BIM deliverables are used for design coordination and construction. Dimensional accuracy drives fit and clash detection. Absolute coordinate registration enables multi-session dataset alignment and integration with survey control.

Minimum requirement: GCPs with surveyed coordinates at maximum spacing (L2 Pro: 100 m, K1: 50 m). Verify GCP residuals in LixelStudio before delivery.

When to use hybrid: Large facilities where the scan spans multiple floors or sections. RTK constrains the elevation across floors; GCPs constrain drift within each floor.

Pure SLAM is insufficient if the BIM model will be used for construction coordination or clash detection. Dimensional errors compound across large datasets.

Legal Survey or Cadastral Work

Recommended: Hybrid RTK + GCPs. Verify with licensed surveyor.

XGRIDS mobile SLAM is not a replacement for licensed survey instruments for legal boundary work. The system can provide supporting documentation and area measurements, but legal survey requirements vary by jurisdiction.

If XGRIDS data is used as supporting evidence: Use hybrid RTK plus GCPs, verify all residuals, and retain the processing report as documentation.

Accuracy context: The 3.0 cm RMSE absolute specification can support many legal documentation requirements, but confirm with the licensed surveyor of record before committing the data for legal purposes.

Do not misrepresent mobile SLAM data as survey-grade without independent verification.

Construction Progress Monitoring

Recommended: RTK or GCPs (consistent across sessions)

Progress monitoring requires repeatable registration between scan sessions more than it requires the highest possible absolute accuracy. What matters is that each session aligns to the same coordinate reference so that differences represent actual construction change, not scan-to-scan registration error.

Key principle: Use the same control strategy and the same physical GCP locations across every session. Changing the control network between sessions breaks the registration consistency.

Permanent GCP monuments are worth installing on long-term projects. They eliminate re-survey costs and guarantee consistent registration across dozens of scan sessions.

RTK alone is acceptable for open-air construction sites where Fixed status is reliable and consistent.

Visualization and Client Delivery (3DGS)

Recommended: Pure SLAM or relative control points

3D Gaussian Splat deliverables via LCC Studio are primarily visual. Clients viewing the model in a browser or the LixelWeb viewer are not measuring dimensions against a coordinate system. Absolute georeferencing adds cost and complexity that typically does not improve the deliverable for visualization purposes.

When absolute coordinates do matter for 3DGS: Map Fusion across multiple sessions requires a shared coordinate reference. If the project involves stitching multiple PortalCam or LCC-pipeline scans together, RTK or GCP data is required for the fusion to align correctly.

PortalCam-only projects: The PortalCam does not produce a point cloud or support GCP workflows. Relative accuracy within the LCC model is typically within 1% of true dimensions for small to medium spaces. This is adequate for most visualization, space planning, and client presentation use cases.

Industrial Facility or Large Indoor Site

Recommended: GCPs, denser network than minimum

Large indoor facilities are the most demanding accuracy scenario for mobile SLAM. RTK signal is unreliable indoors. Long trajectories accumulate drift. Multi-floor coverage introduces vertical error from IMU leveling that compounds across levels.

GCP spacing guidance for large indoor facilities: The published maximums (100 m for L2 Pro, 50 m for K1) are upper limits, not targets. For facilities where high dimensional accuracy matters, space control points at 50 m or less with the L2 Pro, and 25 to 30 m with the K1.

Multi-floor projects: Place GCPs on each floor and include points visible from stairwells or open voids that span floors. This constrains vertical drift across the building height.

Walk-and-stop technique at control points improves accuracy. Set the scanner down gently at the marker, allow it to rest for several seconds, then continue.

Outdoor Site with RTK Coverage

Recommended: RTK, verified Fixed status

Open outdoor sites with unobstructed sky view are where RTK performs most reliably. If the environment supports a sustained Fixed satellite lock throughout the scan, RTK alone can achieve the published 3.0 cm absolute accuracy specification.

Verify Fixed status before beginning: Confirm more than 10 satellites and a Fixed status (not Float) in LixelGO. Walk at least 10 meters while Fixed before starting the scan route. Do not trust RTK data captured during the initial fix period.

When to add GCPs to outdoor RTK scans: If the site includes areas under tree canopy, near tall structures, or in urban canyons where RTK signal may drop or degrade, add GCPs in those zones. Do not assume RTK is maintaining Fixed throughout the entire scan.

Antenna tilt: Keep the RTK antenna within 20 degrees of vertical throughout the scan. Exceeding this invalidates the fix record even when the LED remains green.

The accuracy method must be chosen before the scan begins. RTK must be configured and confirmed as Fixed before scanning starts. GCPs must be physically placed and marked in LixelGO during the scan. There is no way to apply georeferencing to a scan after the session without control that was captured during it. A scan collected without any georeferencing cannot be retrospectively tied to a real-world coordinate system.