If only the large battery icon is displayed, the unit is off, and charging - it will need to be turned on to connect. Note: the ELEMNT/BOLT/ROAM must be powered on to connect over USB. re-importing without having to delete the activities first) is currently disabled, but I understand it will be re-instated soon, see #3770.īUT first I need to spend a bit of time searching to see what the official device names should be, as I expect this may affect other Garmin devices when exported to Strava, as I see that some of the others (such as "Garmin FR630" & "Garmin FR230") appear in an abbreviated form as well.ELEMNT/BOLT/ROAM support file transfer via MTP (Media Transfer Protocol) - a USB standard used by many cameras, MP3 players, and Android phones.Ĭonnect the ELEMNT/BOLT/ROAM to your computer over USB to transfer workout files (in FIT format) and/or route files (in GPX or TPX format). Note: Overwriting of existing activities (i.e. Unfortunately files already ingested into GC will hold the old mapping, so once GC is fixed they would need to be re-imported and then the modified mapping process will be applied to give the correct Barometric device name on TCX export. When a FIT file is imported into GC it should be straightforward to modify the fix to change the mapping from "Garmin FR935" to ""Garmin Forerunner 935" or just "Forerunner 935" which GC holds internally, and is then used when a TCX file is exported, and as I understand this will fix the problem. Thank you for the extra information and additional testing. Currently, without any fix, it shows 465ft elevation gain on Strava, essentially Strava ignored the elevation information stored in this file due to the lack of recognizable known barometric device identifications. So ideally if we can somehow encode the correct Garmin Barometric Watch string (or code) in this exported "FIT" file, it should achieve the same elevation gain information shown on the device. However, if I change the device name to be either "Garmin Forerunner 935" or just "Forerunner 935", it now shows 661ft elevation gain, same as the Garmin exported TCX file. If I change the device name to "Garmin FR935", it still shows 465ft elevation gain, which means Strava doesn't recognize "Garmin FR935" as a valid barometric device name. When uploaded it shows 465ft elevation gain as Strava applies its own elevation correction due to the lack of barometric device name in this file. This is the GodenCheetah exported TCX file without your device name fix. I suspect GIT file does contain that information, hence Strava was able to extract that after uploading. When I upload this to Strava, the total elevation gain is now 661ft! My guess is that TCX file doesn't contain the total elevation gain information computed by the device (which uses 3s smoothing), so Strava simply just added up all the elevation differences. If I upload this one to Strava, I got an elevation gain of 515ft, which is exactly what I see when I recorded on my watch. Ok, this is the original fit file exported from Garmin Connect. The mapping between device string names and integer values supports the FR935 (as per below) so the FIT file will contain something representing 2691, whilst the TCX will now contain "Garmin FR935" for your device.Ĭase 2531: return "Garmin Edge 820 Explore" Looking in the FIT file export the device is coded as integer rather than a string description as its a compact binary file. Searching the code I cannot find any smoothing applied to the Altitude on import or export, although you can manually "Fix Elevation Errors" using the option in the Edit drop down menu which will modify the values held in GC, and then in any exports. The proposed fix only affects the exported TCX file, and it will now export what GC holds as the device type (see examples below), and looking in my TCX files they contained the altitude information exported from GC. Fixed by -> #3826 TCX export to Strava with the incorrect Creator tag
0 Comments
Leave a Reply. |