I'm using the Bosch Flow app and my Garmin Fenix 6x to display my bike rides. Unfortunately I'm not able to display the cadence on a combined file. I can display the cadence in the original Garmin and Flowapp file but the cadence is disapearing in the combind file. The power is shown so the basic import works.
maybe I make a mistake - you have any tips or tricks?
Rainer-
When you export the combined file from gotoes, are you exporting as the GPX format? If so, please switch to TCX or better yet, FIT. GPX does not support cadence. Strava does accept a special format (which gotoes uses) to override the fact that GPX does not support cadence… but no other platforms can read this special encoding within a GPX file. FIT is the best format for interoperability.
just did some test's if I export the file in garmin (.FIT) and import again the cadence is shown. If I merge with gotoes garmin and Flow and export as .FIT and import in Garmin again the cadence is not shown anymore.
Ahh, I see. You are correct: with Garmin, the cadence disappears, but with Strava, the cadence is interpreted. I looked at the file exported by gotoes (raw source) and the cadence is in the file. The problem is with the session data; there is some minor corruption in your source file in the session field, and that is being transferred to the end output from gotoes. I believe it is causing a very minor frame shift error, and the (odd) symptom is that Garmin isn’t showing the cadence. This isn’t a bug with gotoes per-se, but actually corruption in the source files. In fact, when I upload to gotoes, it indicates that there was minor corruption in one of the files. Having said all of that, gotoes should be able to properly repair this minor corruption. When I get home (I’m on the road right now) I will dig deeper into the cause of the corruption, and I will train the gotoes algorithm to be able to detect and repair this type of problem. It might take a few days because I’ve been gone from home for a while. Thanks!
