The exported files include randomly introduced "dummy" lap data strings (or at least I think they are redundant - I'm not a programmer) that look like this:ĭeleting these blocks in a text editor repairs the file, it's imported by Garmin Connect in full, shows all info you would expect except the number of strokes, and even provides complete details on the intervals in the split section. (2) I seem to have located the issue with TCX files output by the Logbook.
#GARMIN CONNECT EXPORT DATA TCX ANDROID#
Both FIT files created by ErgData IOS and Android are imported this way now, historical workouts as well. There's no split section / intervals data in the imports. These could be removed using online fitfiletools field stripper. The imported workouts contain all data and some additional unnecessary fields such as temperature (set at 0 Celsius), elevation (constant at minus 500 m), and GPS (ground zero location). (1) C2 Logbook has started producing FIT files that could be imported in Garmin Connect (or, alternatively, GC has corrected something in their import algorithm). Most likely there was some change implemented on GC since I tried simultaneous Strava to TP export via Tapiriik, and it worked.īy way of an update, in case someone needs this functionality: Historically I was able to export TCX to Strava and then transfer my workouts to GC via Tapiriik. has stopped exporting from Strava to Garmin Connect altogether since late December in my case, it shows all workouts as exported but nothing appears in GC. Strava and Training Peaks import the files (also, there is a direct online export from Logbook to both of them), but there is no connection from these platforms to GC, only from GC to them.
I'm still to find a service that imports TCX or FIT and exports to Garmin as a workaround. It's quite possible that the repair of the FIT done by FFRP ended up in the removal of the interval data from the file.
#GARMIN CONNECT EXPORT DATA TCX FULL#
The resulting import into GC was a success, with full data present including strokes (no strokes are present in any TCX import), but excluding intervals (laps).
These errors could be corrected as I was demonstrated on Garmin forums - my FIT file was repaired by the Fit File Repair Tool. FIT files have some errors that lead to GC rejecting them with an error message. Probably, there is an issue with the import of laps breakdown from the file. TCX export is not reliable, some interval data is lost and not shown in GC unpredictably, some data is excluded from the summary and from splits breakdown of the workout page in a totally random fashion. My take on the current status of C2 logbook => Garmin Connect export is as follows yet: Never had any issues with logging interval data in the logbook itself previously though.
I think the release note you quoted is related to the logbook rather than the capability to export data.
0 kommentar(er)
