Skip to main content
Solved

Bugs transfert de données / Data transfer bugs

  • August 3, 2024
  • 1 reply
  • 13 views

Forum|alt.badge.img

Bonjour à tous

Deux petits constats sur l'utilisation de Strava que je ne comprends pas.

Mon temps d'activité indiqué sur Strava est plus court que mon temps d'activité mesuré avec ma montre (le transfert des données se fait automatiquement) ? Dernier trail, il y a 15 minutes d'écart...

Sur un 20 km, sur Strava, le temps indiqué est de 1 h 57 et sur meilleurs efforts, il est indiqué 2h07...

Bref je ne comprends pas. Des bugs ?

Merci pour votre retour et bonne journée !

TRANSLATION:  Hello everyone

Two small observations on the use of Strava that I do not understand.

My activity time indicated on Strava is shorter than my activity time measured with my watch (data transfer is done automatically)? Last trail, there is a 15 minute difference...

On a 20 km, on Strava, the time indicated is 1 h 57 and on best efforts, it is indicated 2h07...

In short, I do not understand. Bugs?

Thanks for your feedback and have a nice day!

Best answer by Bryant

Hey @Alexandra1,

Sorry for the differences you're seeing in your activities. These data discrepancies could either be a result of the way your file is formatted or the way your device/app is choosing to analyze the data.

To provide context, Garmin set the industry standard with FIT and TCX file formatting (read more here and here). We use Garmin's file formats in order to upload and analyze the data in your file. If your device/app isn't following these standards or if the company has made file formatting modifications to accommodate device or app specific features, then we may not be able to correctly parse the files. This could lead to differences in your activity stats when compared between platforms.

Another consideration is whether your device/platform is using a different method than Strava when calculating your stats. For example, consider the process of determining how much resting vs moving time is in an activity. What constitutes a rest? Is it when you're at rest for 1, 3, 10, or 20 seconds? And what does your speed have to fall below in order for you to be considered at rest? 1 second might capture too many false positives and 20 seconds may be too strict. One calculation isn't necessarily correct or incorrect, but we do feel we're using standards that most athletes would agree upon.

We understand our athletes use hundreds of different devices and apps and are doing our best to accurately analyze each file regardless of the differences in file formatting. We're always working to improve our athletes' experience and we will pass this feedback along to our engineering teams.

I hope this helps. If you have any other questions, please let me know.

View original
Did this topic help you find an answer to your question?

1 reply

Bryant
Community Manager
Forum|alt.badge.img+26
  • Community Manager
  • 752 replies
  • Answer
  • August 8, 2024

Hey @Alexandra1,

Sorry for the differences you're seeing in your activities. These data discrepancies could either be a result of the way your file is formatted or the way your device/app is choosing to analyze the data.

To provide context, Garmin set the industry standard with FIT and TCX file formatting (read more here and here). We use Garmin's file formats in order to upload and analyze the data in your file. If your device/app isn't following these standards or if the company has made file formatting modifications to accommodate device or app specific features, then we may not be able to correctly parse the files. This could lead to differences in your activity stats when compared between platforms.

Another consideration is whether your device/platform is using a different method than Strava when calculating your stats. For example, consider the process of determining how much resting vs moving time is in an activity. What constitutes a rest? Is it when you're at rest for 1, 3, 10, or 20 seconds? And what does your speed have to fall below in order for you to be considered at rest? 1 second might capture too many false positives and 20 seconds may be too strict. One calculation isn't necessarily correct or incorrect, but we do feel we're using standards that most athletes would agree upon.

We understand our athletes use hundreds of different devices and apps and are doing our best to accurately analyze each file regardless of the differences in file formatting. We're always working to improve our athletes' experience and we will pass this feedback along to our engineering teams.

I hope this helps. If you have any other questions, please let me know.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept, you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings