Jet Field Notes

Practical LiDAR workflows in the field

Independent publication · No official affiliation

Field Notes / Application guide

Mobile LiDAR vs. Terrestrial Scanning: A Field-Decision Matrix

A practical comparison of moving and stationary LiDAR workflows based on site geometry, feature needs, access, field time, QA, and hybrid capture.


Before-you-go brief

Use when

The environment, access plan, and requested output match the workflow described in this note.

Verify first

Confirm project coordinates, acceptance checks, site restrictions, and the required evidence of coverage.

Bring or prepare

Carry the approved control plan, route map, safety plan, field log, and redundant storage appropriate to the site.

Stop or escalate

Pause when access, control, coverage, safety, or deliverable assumptions no longer match the approved plan.

Workflow route

On this route: 01 Scope · 02 Capture · 03 Process · 04 Handoff

Mobile LiDAR and tripod-based terrestrial laser scanning observe many of the same sites through different field geometries. Mobile capture trades discrete stations for a moving trajectory and SLAM-based mapping. Terrestrial scanning builds the dataset from stationary setups registered together. A practical choice starts with the feature, tolerance, access, site motion, and schedule.

Artec positions Jet as a mobile SLAM LiDAR system and Ray II as a stationary long-range scanner. The manufacturer currently lists Jet mapping accuracy of plus or minus 15 millimeters in general environments and plus or minus 10 millimeters indoors or underground, while Ray II is listed with 1.9 millimeter 3D point accuracy at 10 meters. These are differently defined product specifications. A direct ranking from those numbers would be misleading, and neither one replaces a project acceptance test.

Field-decision matrix

Project condition Mobile LiDAR tends to fit Terrestrial scanning tends to fit
Large connected route Continuous walking or mounted capture Many stations and moves
Fine local geometry Useful if validated at required stand-off Controlled station geometry and denser local setup
Short access window Rapid route coverage can be decisive Fewer high-value stations may still work
Feature-poor open area Needs strong route, control, and crossover planning Station-to-station registration and control can be planned explicitly
Congested interior Continuous paths reach through doors and aisles Multiple viewpoints reduce local shadows
Repeated monitoring Repeat route families are efficient Repeat stations provide controlled comparisons
Hazardous access Robot, vehicle, pole, or drone options may reduce exposure Remote station placement may help where safe setup exists

Where mobile capture shines

A moving sensor can cover floors, corridors, yards, roads, tunnels, and connected plant spaces with few stops. The operator sees the route as one continuous job and can branch toward missed areas. Jet’s listed handheld, backpack, vehicle, robot, and drone modes extend that idea across varied access.

Mobile capture is especially attractive when the deliverable values broad context, fast field time, repeat coverage, and continuity between spaces. Progress documentation, general as-builts, facility context, corridor inventory, underground mapping, stockpile surfaces, and incident scenes can benefit. The live preview can support an immediate coverage review before the crew leaves.

The moving trajectory also creates dependencies. SLAM needs useful environmental geometry and benefits from loops and cross-connections. Long similar corridors, open slabs, changing scenes, vibration, abrupt motion, or sparse features may challenge the solution. Control and independent checkpoints remain central.

Where stationary capture earns its setup time

A terrestrial scanner observes from a known stationary position during each scan. The team chooses stations for angle, stand-off, overlap, target visibility, and critical detail. This can deliver highly controlled observations around façades, structural connections, machinery, tanks, and tolerance-sensitive zones.

Stationary work pays a time cost for setup, acquisition, movement, and registration. Occlusion still exists; a perfect scan from one tripod cannot see behind a column. Busy sites can also change during the sequence, producing moving people, vehicles, doors, and equipment across setups.

Compare systems using the finished feature

A useful pilot avoids comparing only point count or nominal accuracy. Select representative features: a floor plane, curb, beam, wall corner, pipe, opening, stockpile, or tunnel profile. Establish control, reserve checkpoints, and capture with production-ready methods. Process through the intended software and export at the actual delivery settings.

  • Measure total mobilization, setup, field, processing, QA, and revision time.
  • Evaluate absolute checkpoint residuals and their spatial pattern.
  • Review overlap or cross-sections for internal consistency.
  • Score required-feature completeness and extraction effort.
  • Record crew exposure, traffic control, closures, and access burdens.
  • Test the recipient’s CAD, BIM, survey, or viewer workflow.

The result may favor one method for the overall site and another for a critical detail. That is a productive outcome.

Hybrid work is often the strongest answer

A mobile pass can provide broad context and connect rooms, floors, or corridor segments. Terrestrial stations can reinforce a tolerance-sensitive machine base, façade, bridge component, or other localized feature. Conventional survey observations establish control and independent checks. Close-range scanning or photogrammetry may fill texture or small-detail needs.

Hybrid capture needs an integration plan. Specify the common reference frame, overlap areas, control, file naming, processing order, resolution policy, and which source governs each modeled feature. Avoid blending data until its provenance disappears. A modeler should be able to identify whether an element came from mobile, terrestrial, conventional, or interpreted data.

Decision patterns by application

Construction progress

Mobile LiDAR often suits broad weekly coverage. Add stationary scans when a specific installation has a tighter verification requirement or difficult occlusion. Keep comparison zones, processing, control, and checkpoints stable through time.

Industrial facilities

Mobile capture connects aisles, levels, and rooms quickly. Stationary setups can improve observation around dense pipe racks and equipment where multiple controlled viewpoints matter. Access permits and operational constraints may decide more than sensor speed.

Roads and corridors

Vehicle or backpack mobile capture can be efficient. Tripod work can target bridges, structures, or localized deformation. Traffic plans, safe pull-offs, route crossovers, and coordinate control belong in the comparison.

Underground

Mobile SLAM offers continuous mapping without satellite positioning and can support walking, vehicle, robot, or drone deployment. Stationary scanning may fit detailed chambers or control areas. Mine rules, approved equipment, communications, ventilation, examination, and recovery plans control the operation.

Procurement questions that expose the real fit

  1. Which deliverable features and tolerances were demonstrated in a site like this one?
  2. What control and checkpoint workflow is included?
  3. What happens in repetitive, open, dusty, wet, reflective, or moving environments?
  4. Which accessories, software, subscriptions, training, and export modules are required?
  5. How are raw observations preserved and reprocessed?
  6. How many crew members and site controls does each mode require?
  7. Can the vendor run a representative paid pilot with acceptance criteria?

Choose the observation method that produces an accepted feature with the least total field risk and rework.

There is plenty to love in both approaches. Mobile capture makes connected spaces feel wonderfully tractable; stationary scanning provides deliberate local observation. The field-decision matrix keeps that enthusiasm attached to the job rather than to a category label.

QA and handoff gate

  • ✓ Compare the registered dataset with the approved control and record exceptions.
  • ✓ Review occlusions and coverage gaps against the requested use.
  • ✓ Inspect registration joins, loop closures, and any segmented runs.
  • ✓ Confirm coordinate reference, project datum, units, orientation, and file naming.
  • ✓ Package source records, processed files, field logs, and known limitations.
  • ✓ Obtain stakeholder acceptance against written criteria—not an assumed visual check.

Adjacent field routes

Set the field control plan

Use this first when coordinates and independent checks still need agreement.

Carry capture into deliverables

Continue here when processing and acceptance packaging are the next decisions.

Choose another deployment mode

Compare access and risk conditions before changing the capture platform.

Methodology · Request a correction