A topographic mobile LiDAR plan should begin with the surface and features the survey must deliver. Pavement edges, breaklines, drainage structures, walls, utilities, vegetation limits, and obscured ground do not respond equally to one fast pass. The field plan has to join control, trajectory geometry, coverage, feature extraction, and independent checks into one defensible survey.
Artec lists Jet as a SLAM-based LiDAR mapper with handheld, backpack, vehicle, robot, and drone deployment. The current manufacturer specifications include a 0.5 to 300 meter sensing range, multiple returns, LAS and LAZ output, and optional GNSS-assisted georeferencing. Those features can support many survey designs. They do not select the coordinate system, certify boundary evidence, or define the accuracy class of a finished topographic product.
Start from a feature matrix
The feature matrix names what must be found, the minimum useful representation, where occlusion is likely, and how the item will be checked. It prevents the crew from chasing general density while missing the assets that matter.
| Feature | Capture concern | Planned response | Check |
|---|---|---|---|
| Hard-surface breakline | Grazing angle or parked vehicles | Opposing passes at practical stand-off | Cross-section and surveyed spot |
| Inlet or manhole | Cover visible, invert hidden | Surface capture plus conventional measurement | Asset ID and field note |
| Vegetated ground | Returns may not represent bare earth | Multiple-return capture and planned ground checks | Ground checkpoints |
| Fence or cable | Thin geometry | Shorter stand-off and crossing view | Visual completeness review |
| Building edge | Roof overhang and façade occlusion | Two-direction perimeter path | Corner ties where required |
The matrix also identifies work that belongs to another method. A laser return cannot reveal a buried pipe or an inaccessible invert. Boundary decisions require the appropriate licensed survey practice, records, monument search, and professional judgment. The mobile point cloud can provide valuable context without being asked to answer questions it never observed.
Define control and checkpoints independently
The survey lead specifies the horizontal reference system, vertical datum, geoid model where applicable, units, epoch if relevant, and site calibration. Control should surround and pass through the project geometry rather than occupy one convenient cluster. The observation method and expected uncertainty for each point belong in the control report.
Reserve checkpoints from adjustment. Distribute them across the project, elevation range, surface types, and difficult geometry. The USGS Lidar Base Specification is written for 3DEP collections rather than every mobile survey, yet its emphasis on project-defined accuracy, surveyed checkpoints, metadata, and deliverable consistency offers a strong planning model. The current online edition is 2025 rev. A.
Design loops around terrain
A productive route contains closure opportunities and cross-connections. On a small site, the crew might begin near stable control, circle the perimeter, cross the interior on two paths, and finish near the start. On a corridor, periodic crossover loops or return passes can provide stronger geometry than a single out-and-back line along the same edge.
Feature-poor open ground deserves special care. SLAM needs environmental geometry, and a broad smooth surface supplies fewer constraints than a structured streetscape. Route design can use stable façades, curbs, poles, rock faces, barriers, and cross streets while maintaining safe movement. Control observations and independent checks become increasingly important where environmental geometry is weak.
- Sketch the start, finish, loops, crossover points, control visibility, and safe pull-offs.
- Mark traffic control, rail, water, steep-slope, and public-interface constraints.
- Plan complementary shots for culverts, walls, ditches, canopy, and recessed features.
- Set maximum logical segment lengths based on the team’s tested workflow.
- Predefine a recovery route if access or weather removes the preferred path.
Match deployment to the segment
A handheld route suits detailed sidewalks, courtyards, and short structures. A backpack can free the operator’s hands and support longer walking sections. A vehicle covers accessible corridors quickly but changes stand-off and view geometry. A drone can reach slopes or hazardous areas, subject to an approved flight plan, payload integration, airspace, and operating rules.
For US commercial drone operations under Part 107, the FAA requires a qualified remote pilot or direct supervision by one, aircraft registration, visual-line-of-sight operation unless authorized otherwise, and compliance with operating limits and airspace requirements. Site permission and aviation compliance remain part of deployment planning even when a sensor supports a drone mount.
Collect evidence in the field
The field log records equipment identifiers, software and configuration, mount, start and stop times, weather, surface conditions, control observed, interruptions, route deviations, and exclusions. It should also note standing water, dense vegetation, moving traffic, dust, reflective surfaces, and temporary obstructions. These conditions influence classification and interpretation later.
The live preview is a terrific coverage tool. The operator uses it to find holes around structures, under parked equipment, and along steep banks. Before leaving, the crew confirms that raw data are saved, the route closed as expected, planned control appears, all required segments exist, and conventional supplemental observations are complete.
The field gate closes only when the crew can explain both the observed surface and every planned surface that remains unobserved.
Process toward the survey deliverable
Processing preserves raw observations and records trajectory review, control use, coordinate transformation, filtering, classification, and export. Ground classification should be checked against slopes, curbs, low vegetation, retaining walls, and structures rather than accepted as an opaque automated step. Breaklines and spot elevations follow the feature matrix and the agreed drafting rules.
Checkpoint evaluation happens in the delivered coordinate frame. Report the checkpoint survey method, residuals, summary measure required by the project, and spatial distribution. Inspect cross-sections at overlaps and closures. A local pass at one control mark cannot validate the full corridor.
Package the handoff
The survey package may include LAS or LAZ, a surface, breaklines, feature linework, point list, control and checkpoint reports, coordinate metadata, route or coverage map, processing record, and limitations. File names should include project, area, date, coordinate frame, content, and revision without becoming cryptic.
Open the exports in a second environment before delivery. Verify units, coordinates, extents, elevations, classification codes, missing tiles, and surface behavior. Compare several known points and inspect the hardest features from the matrix. The final transmittal names excluded areas and distinguishes field-observed geometry from interpreted or supplemental information.
The satisfying close to a topographic run is a clean loop on the route map. The professional close is broader: independent checks pass, the required features are present, metadata makes the coordinates unambiguous, and the recipient can use every file without guessing how it was made.