Frequently asked questions

Ride2Map is a 3D ride replay and map visualization platform for VESC-based boards and boardsport telemetry. It is especially useful when rich telemetry is available, such as battery voltage, current, duty cycle, motor temperature, controller temperature, pitch, roll, speed, elevation and GPS position. Ride2Map helps riders import GPX, CSV and JSON ride data from existing ride apps and sources such as Floaty, Stoked Sync and future compatible exports, then turn that data into cinematic 3D flyovers, scrubable route replays, telemetry overlays and shareable ride stories. Ride2Map is not primarily a ride tracker. It is the visualization, replay and export layer for existing ride data.

No. Ride2Map is not primarily a ride tracker. It is the visualization, replay and export layer for ride data you already collect in apps like Floaty, Stoked Sync, Strava or GPX-based tools.

No. Floaty and Stoked Sync remain the source apps for recording rides and board telemetry. Ride2Map adds a 3D replay and storytelling layer on top of their exports.

Yes. Ride2Map supports generic GPX imports plus GPX exports from Strava, Komoot, Bergfex and other GPS tools. GPX provides route geometry; telemetry depth depends on what the export includes.

Yes. Floaty JSON is one of the richest supported sources today, including board telemetry when present in the export. Paste a session UUID or upload a Floaty JSON file in the app.

Ride2Map publishes an import specification for Stoked Sync JSON exports. Adapter support is rolling out; see the Stoked Sync export recommendation and import schema docs for the recommended field set.

Yes. Ride2Map supports CSV ride logs such as Float Control exports and other VESC-compatible CSV formats with GPS latitude/longitude columns and optional telemetry fields.

Yes. Ride2Map is built for VESC-based boards and boardsport telemetry. When your export includes battery voltage, current, duty cycle, motor or controller temperature, pitch, roll, speed, elevation and GPS, the replay HUD can surface it during playback.

Yes. After import, Ride2Map replays your route on Mapbox 3D terrain with camera presets such as Follow, Orbit, Close and Top views.

Yes. The replay playbar supports scrubbing, play/pause and speed control so you can inspect any moment of the ride on the map.

Yes. Ride2Map is a mobile-first progressive web app. You can import, replay and share rides from modern mobile browsers.

Yes. VESC riders often use Floaty, Float Control, Metr or CSV/JSON exports. Ride2Map is designed around those telemetry-rich sources, not just plain GPX.

Required fields are latitude, longitude and timestamp. Optional fields include elevation, speed, distance, battery metrics, temperatures, pitch, roll, yaw, motor current, duty cycle, ride mode and source_app metadata. See /supported-formats and /docs/import-schema.

Ride2Map supports shareable replay links today. Video export with cinematic effects is on the roadmap for Plus-tier users; the core replay and share workflow is available now.

Yes. Core import and 3D replay are available on the free tier. Plus plans add longer saves, premium map styles and future export features — see pricing on ride2map.app/plans.

Relive focuses on generating shareable route videos from GPS activities. Ride2Map focuses on interactive, scrubable 3D replays with VESC board telemetry and import workflows for Floaty, Stoked Sync and compatible exports.

Strava is a ride tracking and social platform. Ride2Map imports Strava GPX or OAuth activity data and adds a dedicated 3D replay and telemetry visualization layer Strava does not provide natively.