Comments (5)

it looks more like an issue on Strava side. As I'm looking into system used for export to Strava, Locus simple export track to GPX file version 1.1 and send this file to Strava server.

Has Strava support for cadence values at all?

Is there any possibility to import own training from GPX file? If so, you may try to export your recorded track to GPX file, check if this file contains cadence values, and if so import it manually to Strava server.

I'm not saying, it is a workaround. It should just test, if Strava is able to read cadence values from GPX file or not. If not, it should be reported on their support system as an issue, instead of on Locus side.

"The base version of GPX does not allow for the inclusion of heartrate, cadence, distance or temperature data. As a result, extensions to GPX were created and Strava supports the two most popular plus a general format. The extensions extend the <trkpt> tag to include extra attributes with each datapoint."

Are you sure, cadence is not in exported file? It should be there in <gpxtpx:TrackPointExtension> tags, named as <gpxtpx:cad> , which should be correctly (I hope) used extensions system from Garmin’s Track Point Extension v1 as is also suggested on Strava websites. Unfortunately it looks, they do not support cadence from GPX in this way and to be true, I'm not a big fan of adding another extension tabs to exported GPX, when it is not needed.

What about writing to Strava support with link to this topic? It should be really easy task to add support for cadence also from GPX file over Track Point extensions, which is very common method.