I'm with Bigfella, I don't always want to race/compare splits in training.
That's why I just use a Garmin but not strava.
Each to their own, what ever works for you.
I lost a KoM on a strava segment by 1 minute and 10 seconds. What's peculiar is that we were running that section together at the same speed. They were using a Suunto device and I a Garmin. I think they'd changed the recording settings on their unit to save battery life so not sure if that accounts for the inaccuracies.
I had the reverse when I first started using it. There is a very rocky climb near my house and I was something like 9th/80 on the segment. I was really proud of myself, until a couple of days later I realized strava defaults to cycling. Upon changing it I plummeted to something like 14/18, that is a bit more like my standard
Ryan Smith's blog write-up of his 14hrs 17m BGR - http://www.dirtproof.co.uk/2017/06/b...ham-round.html - I like the cut of his gib.
I also like STRAVA for training incentives and comparing my own runs.
Sometimes the data is recorded inaccurately, it is more likely to be inaccurate on 10 or 20 second timings. If a segment looks dodgy flag it. I have flagged loads, and all of them so far have been taken off leaderboards.
I think a usefull additional feature would be to have a qualifying route for certain segments. So that they could only be beaten if the athlete had completed the race, or round attached to the segments. It would certainly make Ryans BG CRs tough to beat!
Last edited by Alan Lucker; 15-06-2017 at 06:34 PM.
Good, factual and interesting read.
How many people will now start drinking apple juice for long events
Fantastic effort Ryan. congratulations to all of you. Maybe next time you'll get the hill support that you deserve.