🚴

Garmin FIT Course (Flexible and Interoperable Data Transfer)

Preço antes do pagamento

.fit · application/vnd.ant.fit

FIT is Garmin's binary fitness protocol that powers Forerunner watches, Edge bike computers, Fenix multisport devices, plus Wahoo, Polar and Bryton gear. On osm2cdr we write FIT in the Course profile: the roads and paths of your selected area are chained by nearest endpoints into connected runs — segments follow the ways that touch instead of the order they were read in, and the chaining works at any density, with no cut-off. To be honest about the content: this is the road network of your bbox, not one planned route — where two ways do not meet, the track moves to the next run in a straight line. Those transfers are not counted as distance: lap.total_distance is the length of the ways themselves, not the sum of the jumps between them. Every point carries coordinates (in semicircles, Garmin's integer units), cumulative distance and a timestamp derived from a nominal speed; the file holds a header, file_id, course and lap messages, start/stop events and CRC-16 checksums — fields laid out strictly per the FIT profile and verified with an independent parser. Honest about the data too: this is an export of geometry, not a recorded workout — there is no heart rate, cadence, power or elevation in the file, because those come from sensors during the ride, not from the map. Very long exports are downsampled to 10,000 points — thinning happens inside the runs, and both ends of every run are kept.

Dados do OpenStreetMap de 5 de outubro de 2026 · há 24 dias