Strava is calculating ave mph using elapsed time in Garmin, instead of the time Garmin has designated as Moving time. This causes my MPH averages in Strava to be much lower than they actually are.

Strava is calculating ave mph using elapsed time in Garmin, instead of the time Garmin has designated as Moving time. This causes my MPH averages in Strava to be much lower than they actually are. 

Examples of this is my activity on November 25, 2018, titled, 'Testing new Garmin Sensors with Garmin VivoActive 3'.

Strava is using (19:27) elapsed time, instead of the actual moving time reported by Garmin (15:09). This causes my mph in Strava to be recorded as 11.5 mph instead of the actual recorded speed of 14.8 mph.

Another example is activity title, 'GCN - 20 min Fat burning intervals workout - YouTube'. Garmin records my moving time as 19:24 for a 17 mph average. From that data, Strava chooses to grab the elapsed time of 20:48 to calculate mph average which lowers the mph ave from 17 to 15.9.

 

My guess is you've seen this before, so I'm seeking to understand what type of setting needs to be altered. I really hope this isn't a bug or isn't as designed as this would be a big problem for many of us that work hard in our workouts and use Strava to share and compete with peers. Strava is Data and if the date isn't accurate, then I'm sure you could see how we would  really have no need for Strava. 

 

Thanks so much. Hope to hear back soon.

Markmark.curbeam@gmail.com

0

评论

0 条评论

请先登录再写评论。

没有找到您要找的?

新建帖子