Source map
VIDEOAction camera or phone
GPS + SPEEDExternal GNSS logger
IMUUsually logger; device dependent
VEHICLE CHANNELSNone unless a third logger is added
Files produced
| Component | Typical original | Usable export | Clock |
|---|---|---|---|
| Camera | MP4 chapters | MP4 | Camera clock and stream timestamps |
| RaceBox Mini S example | Vendor session | CSV, VBO or GPX | GNSS-derived timestamps |
Formats vary by logger. GPX often carries time and position but may omit richer IMU and lap channels; CSV schemas are vendor-specific; VBO is associated with VBOX-style telemetry workflows.
How to align the recordings
- Preserve original files and note local timezone settings.
- Use absolute timestamps when both sources expose them reliably.
- Find a sharp shared event: launch, heavy brake application, visible clap or start-line crossing.
- Check alignment again near the end of the session to detect drift.
- Apply one offset only if drift is negligible; otherwise use software capable of time rescaling.
Expected precision is not universal.
It is bounded by video frame interval, telemetry interval, timestamp quality and the sharpness of the chosen event. At 30 fps each video frame spans about 33 ms; at 25 Hz each GNSS interval spans 40 ms.
Limitations
- Two batteries, mounts and start/stop states must be managed.
- Separate clocks introduce offset and possible drift.
- A GPS logger does not provide RPM, throttle or brake channels by itself.
- Stabilised video changes apparent camera motion and should not be treated as raw body movement.