The Multiple Ride Mapper
This great app / (website) pulls in all of the rides and runs you’ve ever logged on Strava and displays them on one map. Simply copy and paste your athlete number into the box and be amazed as it pulls in every ride and maps it. If you are struggling to find your athlete number then hit profile in strava and it will show a number in the address bar – this is you.
The website uses opaque lines so if you’ve ridden or run certain roads many times, you will end up with a darker line, whereas roads you’ve only ridden once will be more pale. The map is clickable, and the list on the left hand side takes you back to the ride screen on strava.com if you wony to see an indication of frequency then set opaqueness down to see all your routes clearly.
Here is a map of some of my rides over the last few months – some road, a few mtb and one or two commutes or runs.
KOM Notifier Service
Created by the same author as the multiple ride mapper above, Jonathan O Keefe, the KOM notifier service will give you detailed notifications about any changes to your KOMs, or indeed any changes in the top 10 positions.
Yet another brilliant bit of coding from Jonathan again, Segment Details can be accessed separately as a standalone thing, but it is also linked from the Strava KOM Notifier Service, above.
This one is really useful for tracking the history of a segment – who’s been KOM in the past, when did so and so take it, how many people have ridden it, what’s the average time taken etc.
RaceShape is essentially about analysing the differences between people riding a segment. Say you lost your KOM or if running your CR to someone – you can use this tool to analyse where they were quicker, and so help you to develop your strategy. It works by analysing how the gap changes between two riders, and works with segment data from Strava or Ride with GPS.
Here is a screengrab of a flat canal path section that I took my road bike on – it analyses your time over distance and although I am 3rd on this section I can see that in the first wee bit of the trail where I was chatting to someone with a flat tyre – suddenly that is the 40 sec gone. Although slower than no 1 and possibly no 2 it was close.
Using no 2 as a baseline you can see where I level out and we are quite matched. By comparison my friend Keith did the route and you can see the slope of his pace and where I eventually catch up and pass. So now that I know this is a section I might just burn it along here (although not on a weekend when there are so many dog walkers perhaps.
It gives you more stats to play with and get twitchy about than you might ever want. Dig around and you’ll discover a great new way to explore the segments you’ve done, and get ideas about which ones you want to revisit.
Tip: Click the table column headings to sort on that column. You can sort this on average speeds or overall length or steepness and so on.
You’ll discover segments you’ve already done, but never realised were there, prompting you to think about targeting them for a serious effort.
Here is a mtb climb once again using Michael D as the base line and my pal Stuart who is notionally behind me. Interesting to see I started fast but burnt out a bit on the muddy section with the big puddle. I could pretend it may have been dry on the days the others did it or it could just be that I was tired. Stuart and I swap the lead a lot towards the end. Does really let you see where others or quick and where you are slow.