How to Evaluate Air-Ground Mapping for Industrial Sites and Complex Facilities
Begin with the assets and decisions that need geometry
A facility mapping project may support asset inventory, maintenance planning, engineering reference or another use. Each purpose requires different surfaces and detail. Identify the structures, pipe racks, facades, access roads, equipment zones or surrounding terrain that matter, and note areas that cannot be safely or legally accessed. The pilot should be designed around those required observations instead of maximizing raw point count. A clear asset list also makes later completeness checks possible.
Use complementary viewpoints to address occlusion
Aerial collection can observe roofs and open areas efficiently, while ground platforms may capture facades, under-canopy areas and details hidden from above. The value of an air-ground workflow comes from how those viewpoints complement each other, not from assuming that more sensors automatically produce a better map. Define where each platform is expected to contribute and where neither can observe the target. Mark inaccessible or intentionally excluded zones so they are not confused with accidental gaps.
Test cross-platform consistency where datasets overlap
Select common surfaces or features seen by both platforms and examine alignment after processing. Review trajectory continuity, registration residuals, visible seams and any systematic difference between aerial and ground observations. These checks are distinct from absolute checkpoint accuracy. A dataset can align well internally yet be offset from the required reference system, or meet checkpoints while containing local registration problems. Keeping the tests separate makes the root cause easier to diagnose.
Evaluate field QA under realistic operating constraints
Industrial sites can impose access windows, moving equipment, radio restrictions or other operational constraints. A pilot should document how data moves between platforms, how operators see collection status and how they decide whether another pass is needed. Aervimo’s AG-RMS materials describe an encrypted in-vehicle LAN and real-time field coordination, but a buyer should still test the workflow under the intended site conditions rather than treating the architecture description as proof of uninterrupted operation.
Deliver enough metadata for another team to understand the dataset
The handover should identify sensors, coordinate reference, calibration status, processing configuration, control/checkpoint roles, exceptions and any areas with known limitations. USGS Lidar Base Specification deliverables provide a useful example of separating ground-survey documentation, mapping reports and metadata. A commercial facility project can use a lighter package, but the principle is the same: the dataset should carry enough context for another technical team to understand how it was produced and what was actually validated.
Checklist
["Asset/surface inventory", "Expected aerial vs ground contribution", "Overlap consistency checks", "Field QA and access constraints", "Metadata and exception handover"]
Sources
[["USGS — Lidar Base Specification Deliverables", "https://www.usgs.gov/ngp-standards-and-specifications/lidar-base-specification-deliverables"], ["USGS — Lidar Collection Requirements", "https://www.usgs.gov/ngp-standards-and-specifications/lidar-base-specification-collection-requirements"]]