Widgets & Data Sources
Overview of the different data sources and widgets supported by Vectora.
Vectora widgets can ingest telemetry from multiple sources, including head units, wearables, indoor trainers, and third-party platforms. Each widget is designed to read a specific data channel and render it consistently across different recording ecosystems.
Supported device categories include Garmin, Wahoo, Hammerhead, Apple Watch, and platforms such as Strava or TrainingPeaks. When available, Vectora prioritizes native sensor values (e.g., FIT fields) over derived metrics to maintain fidelity.
Common data channels include speed, cadence, power, heart rate, GPS position, elevation, grade, temperature, and lap/segment metadata. Additional channels—such as left/right balance or cycling dynamics—are supported when the source device provides them.
When documenting widgets in `src/content/pages/vectora/widgets-and-data-sources.json`, consider grouping them by purpose: performance (power, HR, cadence), environmental (temp, altitude), positional (map, elevation profile), and session-level metrics (duration, distance, laps).
Example: A power widget can read power data from Garmin FIT, Wahoo FIT, or Strava GPX uploads that include derived power. If a data source lacks a channel, the widget gracefully degrades to an unavailable state.
Troubleshooting: If a widget displays incomplete data, confirm that the original file contains the required fields. Some GPX exports omit heart rate or power, and certain indoor trainer apps may embed nonstandard extensions requiring normalization before import.
Where possible, document device-specific caveats—for example, Garmin’s cycling dynamics fields require FIT; Strava GPX exports strip advanced metrics; Wahoo units may smooth GPS under low-signal conditions, affecting map widgets.