Garmin timing different in strava?

jpower

I am using a Garmin Edge 705 with GSC 10 sensor, when i get home I upload it to Connect which auto uploads to strava and I upoad to mapmyfitness, connect and mapmyfitness show the figures the same as the 705 showed, but strava is adding time on. Why?

meanredspider

Yes - I've noticed this. Strava must process the raw data slightly differently. I don't get big differences but there will be a decimal point difference in average speed quite often (rounding?)

jpower

I got a difference of 25.5 to 24.7

frisbee

Strava isn't always consistent with itself for average speeds.

dabber

I think the way Strava calculates the stopped time is relevant here...
To quote Strava....
"Strava considers a point "not moving" if your speed is less than 0.3 meters/sec (0.67 mph), but we don't start accumulating resting time unless you're "not moving" for at least 15 seconds."

jpower

Dabber wrote:

I think the way Strava calculates the stopped time is relevant here...
To quote Strava....
"Strava considers a point "not moving" if your speed is less than 0.3 meters/sec (0.67 mph), but we don't start accumulating resting time unless you're "not moving" for at least 15 seconds."

That probably explains it the garmin doing auto so guess the shorter ones in traffic are not counted hence the increase. Thanks.

BrandonA

Even Garmin is inconsistent with itself. If you load a ride into Connect directly from your Edge the FIT file is loaded. This will give you a certain average speed and moving time. If you then export this ride to TCX or GPX, delete the ride from Connect and then re-import it you will get a different amount of moving time and hence a different average.

None of the systems are perfect and all will handle stopped time or very slow rolling differently. If you speed is important then I think the key is to measure against the same source every time.

jpower

Thanks. Not really just disappointing when you expected to see one figure and you see something lower.