On my last two rides Strava did not use the mileage from my Garmin or the ascent data. What is up with that. Garmin had this ride at 31.58 miles and 1522 at 19.0. I thought Strava just went with what the Garmin says.
Chris T.
And clearly I did not do the Caln/Oakley road segment, that is where I missed the turn. Weird.
Brian J.
aha! now you see my comment from earlier in week. I had a similar weird experience- Garmin correctly dropped all periods of stopwatch being off and calculated a true average speed. Strava imported all location points but then used the total time w/o dropping the already noted off periods.
Brian J.
nice ride. Do you need to start leaving a breadcrumb trail?
David S.
Your getting dangerous on Broad Run.
Gibbs T.
Looks like strava is including all stopped time in averages. My average is (just recently) being shaved by .2 or .3 mph from what my Garmin reports.
Chris T.
In this case though I had no stopped time (mine is set to only stop when I am still), its the distance that is wrong on mine. Don't know if the Garmin freaked out in the rain. But I agree, recently it has been weird.
On my last two rides Strava did not use the mileage from my Garmin or the ascent data. What is up with that. Garmin had this ride at 31.58 miles and 1522 at 19.0. I thought Strava just went with what the Garmin says.
And clearly I did not do the Caln/Oakley road segment, that is where I missed the turn. Weird.
aha! now you see my comment from earlier in week. I had a similar weird experience- Garmin correctly dropped all periods of stopwatch being off and calculated a true average speed. Strava imported all location points but then used the total time w/o dropping the already noted off periods.
nice ride. Do you need to start leaving a breadcrumb trail?
Your getting dangerous on Broad Run.
Looks like strava is including all stopped time in averages. My average is (just recently) being shaved by .2 or .3 mph from what my Garmin reports.
In this case though I had no stopped time (mine is set to only stop when I am still), its the distance that is wrong on mine. Don't know if the Garmin freaked out in the rain. But I agree, recently it has been weird.