+- RouteConverter Forum (https://forum.routeconverter.com)
+-- Forum: Users (https://forum.routeconverter.com/forum-17.html)
+--- Forum: English: Discussions (https://forum.routeconverter.com/forum-12.html)
+--- Thread: Cadence data not read from FIT or written to GPX (/thread-4074.html)
Pages:
1
2
Cadence data not read from FIT or written to GPX - PHarRut - 27.10.2025
Hello
After using RouteConverter for a few years, I have recently
been needing to translate Wahoo FIT files to GPX.
The FIT files contain connected device heart rate, ambient
temperature and cadence data (confirmed present using
other FIT viewing software).
However, within RC, when the FIT file is saved/exported
as a GPX file the cadence information is missing (again
confirmed using other software).
I assume that RC is either not reading the cadence data or
is not writing it. However upon checking the RC data columns,
Cadence is not listed therefore it has probably not been read
from the FIT file.
Thank you
RE: Cadence data not read from FIT or written to GPX - routeconverter - 27.10.2025
RouteConverter tries to convert such data - I have running tests for that - but the „standards“ are sometimes complex and ambiguous. Please send me example data if you observe problems and I’ll check what’s going wrong.
RE: Cadence data not read from FIT or written to GPX - PHarRut - 28.10.2025
(27.10.2025, 12:44)routeconverter Wrote: RouteConverter tries to convert such data - I have running tests for that - but the „standards“ are sometimes complex and ambiguous. Please send me example data if you observe problems and I’ll check what’s going wrong.
Thank you for responding
I have attached a FIT data sample which includes HR, temperature and cadence.
Regards
RE: Cadence data not read from FIT or written to GPX - routeconverter - 04.11.2025
Hi PHarRut,
I've double checked your file and the source code and in fact, RouteConverter does not process cadence anywhere – which I forgot over the years. Pressure, Temperature, Heartbeat is processed and cadence not. And the reason is pretty simple: there is no data field in GPX for cadence.
So whatever software you've used that could read cadence from GPX – I wonder what it was, must use extensions of GPX to read cadence data
RE: Cadence data not read from FIT or written to GPX - PHarRut - 07.11.2025
Thank you for investigating the issue.
I use the Android app OSMAnd+ for recording GPX files that incorporate bike cadence, and data from other sensors. I use the multi-platform GPXSee and the Android app GPX Viewer Pro for viewing such data.
Would you be interested in my sending an example GPX file produced by OSMAnd that contains cadence, HR and temperate?
RE: Cadence data not read from FIT or written to GPX - routeconverter - 07.11.2025
(07.11.2025, 04:12)PHarRut Wrote: Would you be interested in my sending an example GPX file produced by OSMAnd that contains cadence, HR and temperate?
Yes, please send it around
RE: Cadence data not read from FIT or written to GPX - PHarRut - 14.11.2025
(07.11.2025, 10:46)routeconverter Wrote:(07.11.2025, 04:12)PHarRut Wrote: Would you be interested in my sending an example GPX file produced by OSMAnd that contains cadence, HR and temperate?
Yes, please send it around
Sorry for the delay in replying.
File attached.
RE: Cadence data not read from FIT or written to GPX - routeconverter - 15.11.2025
Thank you, that file showed that osmand is using custom extensions:
Quote:<extensions>
<osmand:provider>gps</osmand:provider>
<gpxtpx:TrackPointExtension>
<gpxtpx:atemp>19.32</gpxtpx:atemp>
<gpxtpx:cad>15</gpxtpx:cad>
<gpxtpx:hr>99</gpxtpx:hr>
</gpxtpx:TrackPointExtension>
<osmand:heading>68.0</osmand:heading>
<osmand:speed>5.4</osmand:speed>
</extensions>
RouteConverter currently is only able to read speed from the GPX file (I don't know why ;-)) because it doesn't know the other extensions yet.
RE: Cadence data not read from FIT or written to GPX - routeconverter - 15.11.2025
I found an issue with the files that osmand seems to write: it mistakes the XML schema location for the XML namespace.
If you change
xmlns:gpxtpx="https://www8.garmin.com/xmlschemas/TrackPointExtensionv1.xsd"
to
xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1"
then RouteConverter reads speed, temperature, heartbeat rate and heading (not displayed though) from your example file.
RE: Cadence data not read from FIT or written to GPX - routeconverter - 15.11.2025
Or try the latest prerelease which I've just uploaded: it tries to workaround this bug in osmand.