Skip to main content

Evolve the aviation model without losing its source

ARINC supplies useful aviation vocabulary, relationships and coded procedure semantics. Aeronautic extends those concepts for interactive maps, runtime calculations and dynamic procedures. The source record remains identifiable after normalization and derivation.

Map the layers​

ConceptPreserve from the sourceExtend for clients
Fix / navaidQualified identity, type, position, source cycleStable references across datasets; explicit ambiguity resolution
SID / STAR / approachTransition, ordered coded legs, constraints, discontinuitiesSelected transition state, parameterized execution and generated geometry
Dynamic procedureDefinition and parameter meaningVersioned parameters, input provenance, evaluated geometry and ownership
AirwayQualified endpoints, direction, segment restrictionsTraversable graph and selection-specific route projection
AirspaceBoundary and vertical restriction semanticsTemporal activation, explicit 3D applicability and display projection

The current ARINC owner already has typed records and geometry adapters. Extend those owners after inspecting their capabilities. A common library should not introduce a second competing procedure or navigation engine just to make a cleaner example.

Identity needs qualification​

A fix ident alone can collide across regions and kinds. The existing navigation map schema allows namespace and qualified_ident to be absent. Consequently, schema acceptance does not prove globally unique identity. The public catalog marks this representation as audited, with portable identity work remaining. Preserve qualification when available and require an explicit resolution step when it is not.

Route occurrences add another identity: two visits to one fix are separate editable elements. Generated arc samples and runway expansion vertices are derived geometry, not new pilot-entered fixes.

Airspace is more than a polygon​

Keep lateral boundary, vertical limits and activation state separate. Polygon arrays use longitude/latitude order. A local database integer key must not become a global volume ID. Retain original restriction values alongside normalized quantities and explicit datums. An AGL base needs terrain context to compare against an MSL position; a display height fallback is not evidence that this comparison was performed.

Activation may depend on schedules, exceptions and current operational information. A missing activation record does not prove the volume is inactive. Future shared volume contracts must make unknown, conditional and active states explicit.

Procedure adoption boundary​

Document the selected airport, procedure and transition; retain coded-leg constraints and source cycle. Keep dynamic definition/parameters separate from an evaluated path. A rendered polyline cannot supply turn semantics, discontinuities or restriction ownership by itself. The catalog identifies current owners; a unified public writable procedure contract still needs the scoped definition and consumer conformance work.