Telemetry & GPX Import

1. Prerequisites for a Usable Race Session

To generate a meaningful replay and tactical analysis report, a session must satisfy five foundational data checks:

1. 01
   Identified competitors & sail numbers: every telemetry track must be bound to a distinct boat with sail number and division.
2. 02
   Confirmed start gun timestamp: the exact millisecond of the starting signal must be recorded to anchor TTL and DMG30 metrics.
3. 03
   Course topology & mark locations: the course layout and mark coordinates must match actual field placements.
4. 04
   Valid wind reference: an observed, manual, or inferred wind direction is required for wind-axis VMG, MMG and maneuver Loss.
5. 05
   Timezone consistency: verify that imported GPX/CSV timestamps match the regatta venue's local time zone.

2. Review Imported Material & Track Coverage

Open the Data management tab to inspect incoming telemetry and imported files before passing them to Results:

1. 01
   Coverage inspector: check whether 1 Hz points cover the entire race duration or have interrupted gaps from cellular loss.
2. 02
   Replay alignment check: visually review the start, mark roundings, and finish on the 2D chart to verify plausible trajectories.
3. 03
   Rebuild stale analysis: if the course layout, mark coordinates, or competitor list are edited after the race, click "Rebuild Analysis" to regenerate all dependent metrics before importing finish times.

3. Four-Stage Decoupling Principle

SurgeRace strictly separates four engineering and operational stages: Ingestion → Replay → Analysis → Results. A successful upload proves that telemetry was stored safely; it does not constitute an official race finish. An interrupted track is an operations incident to examine, never an automatic DNS, DNF or DSQ ruling.