Skip to content

Airside Map Hygiene Ground Truth Protocol

Last updated: 2026-05-09

Why It Matters

Map hygiene ground truth defines what belongs in the permanent map, what belongs only in the live operational layer, and what should trigger review or inspection. Without this protocol, dynamic removal and map-change benchmarks can score well while erasing FOD, preserving parked GSE as infrastructure, or deleting safety-critical markings under occlusion.

The protocol below is designed for airport AGVS and fleet map maintenance. It turns raw captures into auditable labels, map-patch decisions, and safety-case evidence.

Ground Truth Layers

LayerLabelIncludeExclude
Permanent staticstatic_keepFixed infrastructure, fixed signs, terminal edges, approved markingsAircraft, GSE, temporary objects
Static change candidatestatic_changeNew/removed/shifted fixed features pending approvalOne-pass occlusion or perception artifacts
Movable-staticmovable_staticParked aircraft, staged GSE, carts, stairs, cones, barriersPermanent localization anchors
Current dynamicdynamicMoving vehicles, people, aircraft under tow, wildlifeBase map elements
FOD/hazardhazardDebris, tools, loose material, spills, unsafe objectsStatic-map features
ArtifactartifactRain spray, reflections, bad registration, sensor noiseOperational obstacles unless persistent/confirmed
Unknown/reviewunknown_reviewAmbiguous clusters or conflicting evidenceAutomatic promotion/deletion

Capture Plan

Capture sliceMinimum requirementPurpose
Quiet baselineLow-traffic pass with clear sight linesPermanent static reference
Busy operationNormal aircraft/GSE activityMovable-static and dynamic separation
Aircraft present/absentSame stand in both states where possiblePrevent aircraft from entering static map
GSE staged/removedSame route with equipment changesMovable-static policy labels
Day/nightRepresentative lightingDetection robustness
Wet/dry/weatherSurface condition variationMarking visibility and artifact control
Construction/closureWork-zone capture with ops recordTemporary restriction and static-change labels
FOD drill or inspection recordControlled objects or verified inspection outcomesHazard handling validation

Annotation Units

UnitRequired fields
Point/voxellayer label, source capture, timestamp, pose quality, reviewer ID
Object instanceclass, bounding geometry, movable flag, current state, persistence
Map elementelement ID, prior version, new geometry, change type, approval state
Tilemap version, capture set, QA status, localization regression result
Hazard ticketobject class, location, image/point evidence, response status, clearance time

Labeling Workflow

  1. Register all captures into the airport ENU map frame and record pose-quality flags.
  2. Build a quiet baseline candidate from high-quality passes only.
  3. Annotate obvious permanent infrastructure and approved markings as static_keep.
  4. Annotate aircraft, GSE, workers, carts, cones, and other movable classes as movable_static or dynamic based on motion/state.
  5. Route debris, loose tools, foreign material, and spills to hazard even if the static map cleaner would remove them.
  6. Compare current captures against the approved prior map and label candidate additions/removals/edits as static_change.
  7. Require reviewer decision for every safety-critical deletion and every route/topology change.
  8. Run localization and route regression on the cleaned candidate map before promoting a tile.

Reviewer Decision Table

Evidence patternLabelDecision
Fixed feature visible across independent passesstatic_keepKeep/promote
Prior feature absent in one view but occluded by aircraft/GSEunknown_reviewNo deletion
Prior marking absent in clear dry multi-view evidencestatic_changeReview deletion/repaint
New barrier appears with active work-zone recordstatic_change or temporary restrictionAdd restriction; promote only if permanent
New cone line appears without ops recordmovable_staticLive restriction, expire/review
Small debris visible in routehazardAlert/inspection, not map feature
Moving object trail in accumulated mapdynamicRemove from static map
Sensor ghost or registration streakartifactReject from map and benchmark positives

QA Gates

GatePass condition
Sensor calibrationCamera/LiDAR/radar extrinsics current and versioned
Pose qualityGNSS/INS/SLAM residuals within map-build threshold
Inter-session alignmentControl points and static landmarks agree within tolerance
Static preservationFixed landmarks retained after cleaning
Movable rejectionAircraft/GSE not present in permanent layer
Hazard handlingFOD/hazard labels preserved as alerts
Localization regressionNo unacceptable scan-to-map residual or relocalization degradation
Route regressionNo route graph change without approval
Audit completenessEvery promoted/deleted element has evidence and reviewer state

Dataset Splits

SplitContentRule
TrainCommon stands/routes and routine GSE variationMay include synthetic edits after real-label seed
ValidationHeld-out stands/routes at same airportTune thresholds and reviewer burden
TestHeld-out terminal/airport or real operational changesFinal airside transfer evidence
Safety casesFOD, work zones, hold points, aircraft-present edgesReport separately from aggregate metrics

Metrics

MetricReport by
Static preservation ratefeature class, tile, stand
Movable-static rejection rateaircraft, GSE, cones/barriers
Hazard retention/alert recallFOD type, size, surface, lighting/weather
False-free-space rateroute segment, stand, safety-critical zone
Change precision/recallinsertion, deletion, geometry edit, topology edit
Reviewer burdenalerts per stand/km/shift and approval rate
Time to decisioncapture to quarantine, review, publish, rollback
Localization impactATE/RPE, scan residual, inlier ratio, relocalization success

Sources

Public research notes collected from public sources.