Skip to main content

Connect intention to recorded evidence

A trip organizes intended travel and leg occurrences. A flight execution records what happened during a particular operation. A track preserves sampled position evidence. Link these objects by identity rather than rewriting the original plan to match the flown line.

Keep the recording intact​

Current PositionCore samples retain sensor/source information, accuracy and altitude data. Unprovided values and negative sensor accuracy sentinels have distinct meanings. Preserve ellipsoid altitude separately from the sensor's other altitude representation. Simulator, replay and accessory sources must stay identifiable.

Track geometry consists of runs separated by time, source or recording gaps. Never draw a long straight connection across missing evidence as if it were flown. Display thinning may reduce rendered points; it must not silently change the raw record or measured distance.

Existing interchange​

PositionCore's CSV schema 2 retains the legacy leading columns and adds extended fields. The importer preserves unknown columns and can report skipped rows, including a torn final row. Use the owner parser rather than splitting lines manually. Mixed-version and future-version behavior still needs explicit interoperability acceptance before another writer is advertised.

The shared JSON track/log contract remains to be formalized. The catalog intentionally marks the current owner as internal with an existing CSV interchange, rather than claiming an already-supported universal track SDK.

Persisting a plan​

Portable planning intent already provides stable document and occurrence identity. The host's Trip store adds application metadata and durable coordination. Save the intent through that owner, retain import assessments and handle divergent edits explicitly. See the planning lifecycle for SQLite reopening and conflict boundaries.

Future portable trip/flight/track adapters must pass a round trip that retains source flags, gaps, time precision, altitude basis and unknown fields according to the chosen version. Exporting a display polyline is a separate, deliberately lossy operation.