Issue with transfering Google Fit TCX files to Strava

I have a few jogging activities on Google Fit that I was able to download into TCX format to transfer to Strava. After I transferred, about half of the jogging TCX files were uploaded incorrect. For example, while everything is obviously correct for my activity in Google Fit, when viewing it in Strava, some of the TCX activities are split into two workouts or the duration of the activity is completely off. I am breaking world records here and running 2.5 minute miles apparently.

It's also odd that for some of the Google Fit activities, they are 100% correct and transferred correctly. All the Google Fit activities are the same "Jogging" activity and I don't understand why there is a discrepancy upon transferring the data within Strava. There must be something I am missing and I don't mind manually uploading my activities from Google Fit but would be great if I can get to the bottom of this. Any suggestions?



Комментариев: 4
  • I'm having a similar issue with old ride activities. It shows me riding ~5 miles in about 2 minutes. On Google Fit, the activity looks as it should. In strava, the geographic and most other data data is fine, but the ride time is ridiculous.


    By changing ".tcx" to ".txt" in the file name, you can open the file in a text editor and view the raw data. I checked the .tcx file I got from google and it seems to be an issue with the exported data. It looks like Google is not counting increments correctly - like maybe by a factor of 10. The time stamps show the ride beginning at the correct time, there seem to be the correct number of timestamps for the distance ridden, but the final time stamp is actually only a couple of minutes later than the initial one. 

    Действия с комментариями Постоянная ссылка
  • Faced a similar issue while importing googl fit data

    Действия с комментариями Постоянная ссылка
  • I have figured out the issue and have a fix.


    Google Fit only updates the "DistanceMeters" value in the tcx file in large chunks - like, there are 10 values with the same, and then a sudden jump, even though the latitude and longitude coordinates are continuing to update.

    Strava then uses this value and only counts the time between the jumps as total moving time.

    If you delete every <DistanceMeters>XXXX</DistanceMeters> value from the file (open it with a text editor), then Strava will instead calculate the distance from the position data instead of using this chunky data and get the correct moving time. You'll need some quick coding or a text editor that supports matching a pattern to do this in an efficient manner, but you can of course do it manually too.

    Действия с комментариями Постоянная ссылка
  • Just ran into this same problem - Nicholas, if you edit and reupload will the activities update automatically, or do you have to delete them and then re-upload?

    Действия с комментариями Постоянная ссылка

Войдите в службу, чтобы оставить комментарий.

Не нашли то, что искали?

Новая публикация