Telemetry overview
How Outlap uses GPS and logger data: which sources feed which features, and what accuracy to expect.
Outlap turns three kinds of data into laps and insight:
| Source | What you get | Typical use |
|---|---|---|
| Transponder timing | Authoritative lap times, sectors, running order, flags | The event’s official results and live board. |
| GPS from a logger or phone | Lap times timed by Outlap, a GPS trace, speed, sector splits | A driver’s own history, analysis, comparison and the AI coach. |
| Your own code | Whatever you send | Custom timing systems, scripts, spreadsheets. |
Feature map
Data loggers Import VBOX, AiM, RaceChrono, TrackAddict and Garmin Catalyst sessions. GPS lap timing How laps are timed from a GPS trace, and why 10 Hz is accurate to a few thousandths. RaceBox 25 Hz GNSS over Bluetooth into the phone lap timer. Phone lap timer Live delta, predicted lap and real sectors from a mounted phone.
Accuracy
Where a file has GPS, Outlap finds each crossing of the start/finish line and interpolates between samples. Accuracy therefore scales with the sample rate:
| Source | Sample rate | Expectation |
|---|---|---|
| Phone GPS | about 1 Hz | Good for trends and comparison; coarser per lap. |
| 10 Hz loggers (VBOX, AiM, RaceChrono with external GPS…) | 10 Hz | Laps to a few thousandths of a second. |
| RaceBox Mini / Mini S / Micro | up to 25 Hz | The best case for a phone setup. |
Transponder timing remains the reference for results. GPS timing is for the driver’s own analysis, and for the board when the organiser allows it.
Data you own
A driver’s imported sessions belong to their account. They choose which event, if any, the laps are added to, and which of their cars and setups are public.
Was this page helpful?
Reviewed · Contact support