Supported ride data formats

JSON — the preferred Ride2Map standard

JSON is the richest format for board telemetry, and the Ride2Map Normalized Ride format is our recommended standard. It is one stable shape that every source maps into: GPS-only rides work out of the box and get richer automatically as VESC and board telemetry — battery, duty cycle, temperatures, pitch and roll — is added. Optional fields never break an import, and unknown fields are preserved.

Full reference: Ride2Map import schema.

GPX import

GPX is the simplest GPS-only fallback. Import tracks from Strava, Komoot, Bergfex or any GPS app for route geometry; speed and elevation appear when included in the export. See also GPX 3D map replay.

CSV import

CSV ride logs are a tabular fallback. They work when GPS latitude/longitude columns and timestamps are present; Float Control and VESC-compatible CSV exports are supported today.

Floaty exports

Paste a Floaty session UUID or upload JSON. Ride2Map maps Floaty fields to replay telemetry when available.

Stoked Sync exports

Ride2Map publishes a recommended JSON export shape for Stoked Sync. Adapter import is rolling out.

Future FIT-compatible data

FIT-based enrichment is planned for sources that can provide it. Core imports remain GPX, CSV and JSON with versioned schema metadata.

Required fields

• latitude
• longitude
• timestamp

Optional telemetry fields

When your source app provides them, Ride2Map can preserve and display:

• elevation
• speed
• distance
• battery_voltage
• battery_current
• battery_percentage
• board_temperature
• motor_temperature
• controller_temperature
• pitch
• roll
• yaw
• motor_current
• duty_cycle
• ride_mode
• source_app

Full schema: Import schema documentation.