Module 2 Quick Field Guide
The need-to-know numbers and decisions for the field. Device specs, the two output pipelines, software pairings, and the rules you cannot break. Full explanations live in the pages this card links to.
Device Quick Reference
L2 Pro
K2
PortalCam
L2 Pro Model Variants
Full specs and the device comparison table: 2.3 Hardware Overview.
The Two Output Pipelines
Every project produces one output type or both. The two cannot be converted into each other after processing. Full detail: 2.2 Two Workflows.
Point Cloud (LixelStudio)
Cost: Free with hardware (license code tied to the device serial)
Devices: L2 Pro and K2
Use for: BIM, measured deliverables, Revit/AutoCAD/Navisworks, survey, as-built
Export: LAS/LAZ, E57, RCP, PLY, OBJ (with texture)
Dimensions: Yes
3D Gaussian Splat / 3DGS (LCC Studio)
Cost: Free generates models; Premium ($2,500/year) adds Map Fusion, Aerial-Ground Fusion, Aerial Reconstruction, HD Enhancement, and Spatial Recognition
Devices: L2 Pro, K2, and PortalCam
Use for: Client walkthroughs, presentations, virtual tours, visual documentation
Export: .lcc and .lcc2 (Free); .ply, .usd, 3D Tiles (Premium)
Dimensions: Reference only, not for engineering use
PortalCam produces 3DGS only. It cannot produce point clouds under any workflow. If the project needs measured deliverables, use an L2 Pro or K2.
K2 has reduced LCC Studio capability. K2 supports Single Model reconstruction and Spatial Recognition, capped at 90 minutes per scene. Map Fusion, Aerial-Ground Fusion, Aerial Reconstruction, and HD Enhancement are not supported for K2. For multi-segment 3DGS, use the L2 Pro.
Software Pairings at a Glance
System requirements and processing times: 2.4 Software Map.
Key Concepts and Accuracy Numbers
Quick reminders only. Full explanations: 2.1 SLAM vs. Static and 2.5 Critical Basics.
- Drift. SLAM position error compounds over distance. You manage it with a clean initialization, loop closures, and control points.
- Loop closure. Return to a previously scanned area within 40 degrees of your original viewing angle to trigger a correction. The L2 Pro and K2 both apply it in real time, visible in the LixelGO preview.
- Relative accuracy. Internal geometric consistency. Achieved through technique alone, no RTK or GCPs required.
- Absolute accuracy. Real-world coordinate position. Requires RTK, PPK, or GCPs configured before the scan.
Decisions You Cannot Undo After the Scan
Most scanning mistakes are recoverable. These are not. Make them correctly in the field.
- Georeferencing strategy. RTK active before scanning, or GCPs placed and marked during the scan. There is no way to add georeferencing later. Miss it on a project that needs absolute coordinates and the site must be re-scanned.
- Output pipeline. L2 Pro and K2 raw data feeds LixelStudio, LCC Studio, or both from one session. No pre-scan setting is needed, but confirm deliverables first so your technique supports both (loop closures, camera data, overlap). PortalCam goes to LCC Studio only.
- Camera coloring. Whether the scanner records camera data is set in LixelGO before scanning and cannot be added later. The color display mode (RGB, elevation, intensity) can still be changed in LixelStudio anytime.
- Project naming convention. Inconsistent names across sessions cause fusion failures. Set the convention before the first session of a multi-segment project.
Before You Leave Site
A five-minute review on site prevents hours of recovery at the office.
- Scan stopped cleanly. The LED reached solid green before the device was powered off.
- The project appears in LixelGO or LCC Scan with a reasonable duration and file size for the area covered.
- The real-time preview shows no large gaps in areas you walked through.
- If RTK was used, the device moved at least 10 m (33 ft) while the status was Fixed, with more than 100 valid RTK-fixed points. Keep unfixed sections under 100 m (328 ft) for the L2 Pro. The K2 has no published gap maximum, so keep unfixed sections short.
- If GCPs were used, all control point names match the coordinate CSV exactly, including capitalization.
- If this is a multi-segment project, the overlap zone with the next segment is fully covered and includes at least two loop closures.
- A quick walkaround confirms no area was missed that cannot be captured in a follow-up session.
Critical Warnings
- No recovery Scanning without georeferencing when the client requires absolute coordinates means re-scanning the site. RTK and GCPs must be in place before the first recording starts.
- No recovery PortalCam data cannot produce point clouds. If the project needs BIM-ready measured output and you scanned only with a PortalCam, the site must be re-scanned with an L2 Pro or K2.
- Warning Loop closure requires returning within 40 degrees of your original viewing angle. Returning to a room facing the opposite wall is not a loop closure. Drift keeps accumulating.
- Warning AMD GPUs are not supported by LCC Studio or LixelStudio. Both need an NVIDIA GPU with CUDA. AMD CPUs (e.g., Ryzen 9) are fully supported and XGRIDS-recommended for LCC Studio. Verify GPU compatibility before installing on a new machine.
- Warning LCC Studio Premium ($2,500/year) is required for Map Fusion, Aerial-Ground Fusion, Aerial Reconstruction, HD Enhancement, Spatial Recognition, and .ply, .usd, and 3D Tiles export. The Free tier covers single-scene generation and .lcc and .lcc2 export. Confirm your license tier before accepting a project that needs a Premium feature.
- Warning The K2 maximum LiDAR range is 100 m (328 ft). For tall structures, large open outdoor sites, or tunnels and degraded environments, use the L2 Pro (up to 300 m (984 ft) on the 32-300 model).
- Warning 3DGS output is not reliable for dimensional measurement. Do not extract engineering or construction dimensions from a 3DGS model. Use the point cloud workflow for measured output.
- Warning The K2 supports WGS84 and CGCS2000 coordinate systems only. For native NAD83 or another regional datum at capture, use the L2 Pro.
©2026 Alpine Reality Capture LLC • XGRIDS Pro Guide™ • Site Disclaimer