F
@Dimitrios-Kanellopoulos said in Strava sync issue - moving time not calculated:
I hear you. There will be a change locally next week to how it was before.
This change makes things even worse since the distance still does not match Suunto. The result on Strava is now slower pace. For example, my run today was
Suunto: 4.08 miles, 36:51 Duration, Pace 9:01/mi
Strava (uncorrected): 4.06 miles, 36:51 MT, Pace 9:04/mi, Elapsed Time: 36:51
Strava (corrected): 4.08 miles, 34:01 MT, Pace 8:20/mi, Elapsed Time: 36:51
Strava (reverted): 4.06, 36:52 mt, Pace 9:04/mi, Elapsed Time: 36:51
The previous implementation for Strava (uncorrected) brought the distance down a little but also brought the moving time down a little (discussed before), but then pace typically matched which is preferred. Selecting Correct Distance in Strava kills moving time and was to be avoided,
Hopefully we all at least go back to what it was, but soon it all get’s straighten out. The expected behavior is for Suunto and Strava to Match initially (both distance and time (Suunto Duration and Strava Moving time). Seams like this was an attempt to do half that. If I correct distance, Moving time should not change.