-
KML and GPX won't work for me, as I don't have any GPS data points whilst training at the gym. Also, the GPS of the bangle.js is toont unreliably for datapoints within a 400m biking track if I go outside.
Then it seems like would need to hardcode the .CSV headers and do some error checking if they actually correspond to anything in the data store.
I'm not a developer and I'm certainly willing to give it a go, but I don't feel like this is a clean, "upstreamable" solution. I might be mistaking, though.
I guess it would be more feasible to feed (0,0) coordinates to the GPX file, so at least all HRM data points get exported?
What's your take on this? Wat would you consider the best idea
Edit: E.g. TrainingPeaks doesn't support Bangle.JS's GPX-output, giving feedback that it's not formatted as expected by the standard.
You are reading a single comment by @7rozen_7ear_ and its replies.
Click here to read the full conversation.
7rozen_7ear_
So you are using the
Recorderapp already to get the CSV data?Because when you click the 'interface' button in the App Loader for
Recorderyou should have the option to download the tracks in the raw CSV form, but also GPX or KML format (which include entries for BPM/other stuff which are compatible with Strava).You could easily add a new export type there (code is at https://github.com/espruino/BangleApps/blob/master/apps/recorder/interface.html#L15-L135) but it may well be that the GPX/KML export does what you need anyway?
edit: It'd be easy to modify that code to re-order the CSV output style (maybe leave an option to have it as-is), but I wouldn't change the format that the data is stored in on the watch because it could potentially break other apps.