If you don't have many segments, you can always create some new ones. In our neck of the woods there are so many variations on a theme you can hold the KOM on about 4 different sections and never run anywhere different
If you don't have many segments, you can always create some new ones. In our neck of the woods there are so many variations on a theme you can hold the KOM on about 4 different sections and never run anywhere different
When I move recently, there was 1 segment within a mile of where we live. There's now about 10. I have all but 2. No idea who created them.
Some of them with daft name would be created automatically. One of the classic climbs in the Dark Peak (Sandy Heys) has a segment on it called "A 57 Climb" the A57 is about 4 miles away!
Is it me or are the automatically created segments always rubbish anyway. Whenever I add a new run to strava it always comes up with a random (and not too steep) segment. Usually a fraction of the hill climb I'm actually running
Ya I notice that they can be very short. Strava must have some rule about "steepness" so that only a small part of a longer climb satisfies that rule so the automatic segment only covers that bit.Originally Posted by Stolly
I get that a lot near me. The alternative is about seven different sections with the same name, yet are often on the other side of the hill from one another.
I find that the auto generated ones take their name from a local road or feature, I auto created a few in the lakes over the last few years, all of them were called 'seldom seen climb'!
yep got hacked off with that so set the parameters for the actual Sandy Heys climb last winter.
Autosegment is a very irritating segment that should be done away with -any that show up on my routes I delete ASAP.
Just discovered a solution for that problem stolly.A bit of an update on Strava.....
Its a bit crap
Well to be fair its not completely crap and trying to improve your times up particular hill climbs is good fun but here's a couple of things it does really badly:
1. Moving time! The only time that it gives for a run is an arbitrarily calculated moving time and not the actual total time it takes. For short runs there's not so much in it either way I guess but for longer runs the difference can be massive, especially so if a route has ultra steep climbs. The weekend before last I supported Dave Spencer on leg 3 of his BG attempt and it took me approximately 6 hrs and 32 minutes to get from Dunmail to Wasdale. Guess how long Strava gave the moving time as?
4 hrs and 24 minutes!!!! Hahahahaha!
It must have counted every steep climb and especially Lords Rake and the West Wall traverse as me being stationary! The thing is though a couple of people who followed my run on Strava were stunned by my time and really impressed (falsely) but thats not surprising if Strava is knocking 2 hours off
2. A more minor point admittedly but Strava is also rubbish as a running log in that, if you forget to turn your watch on for a run or accidentally turn it off mid-run, although you can enter the missing distance in as a manually input adjustment, you can't include the lost elevation. So if you're particularly keen on recording elevation, thats too bad
Its for pedal pushers really, lets face it
If you select "race" on strava for a run, it makes the elapsed equal to moving.
You can do that after the event, or even flip it now.
Alternatively for a training run where you are stopping here and there, just prevent the auto stop on your watch so all time is logged, then stop or start your watch when you have a picnic..
My watch doesn't auto stop - strava seems to discount movement below a certain pace
Posting Permissions
Reply With Quote