It has taken some time for me to get round to reimplementing the Strava Challenge Trophy Cabinet that was a popular feature of the last version of VeloViewer but the wait is now over! On your VeloViewer Summary page you are now provided with a list of all the Strava Challenges that you have completed, fully or in part along with any current Challenges that are in progress.
Following on from my last post about my bookmarklet to view any Strava route, activity or segment in 3D, here is the follow-up post about a far more simple bookmarklet that will swap out the default Google Maps found in the Strava website for a choice of Open Cycle, Landscape and Street Maps or the Ordnance Survey maps in the UK. At least here in the UK the Google Maps can be rather limiting from a cycling or running perspective due to a distinct lack of detail, particularly around off-road routes. Fortunately the Open Maps (and even more so the Ordnance Survey maps) have detail in spades and with a bit of JavaScript magic we can swap out the Google Maps for the alternative map of our choosing.
Back in July I had my first experience with bookmarklets when playing with Marc Durdin’s excellent bit of code that provides his funky elevation profiles for Activities and Segments right there, in amongst Strava’s own page contents. I might have been a bit naive but I just didn’t realise that this thing was so easy to do, so time for a quick play and see what I could come up with. First off I wanted to get an interactive 3D view of the new Strava Routes, the other thing that sprung to mind was to see if I could swap out the Google Maps view for the more detailed (at least here in the UK) Open Street/Cycle Maps which I’ll go into in my next blog post.
This is something I’d been wanting to do for ages and I’ve even surprised myself with how well they’ve turned out! The majority of elevation profiles you see around the cycling world look like they were drawn in the late 1990’s so it was time to bring them up to date and make the most of the latest technologies to allow you to interact with them.
The VeloViewer Score is a composite measure providing a single value that represents your best Strava achievements. This value can then be used to benchmark yourself against any other VeloViewer user around the world. In this post I’ll explain how it is calculated and where your Score fits in against other VeloViewer users.
Over the last year I’ve had a number of people getting in touch (along with a couple of my own club mates) saying things along the lines of not needing to set up a Privacy Zone to hide where they live because they are using the Enhanced Privacy Mode in their Strava settings. This is not the case. The only ways to hide you home’s location on an activity will be by using a Privacy Zone, marking your activity as private or not uploading them to Strava at all!
The blog has taken a bit of a back seat of late as I’ve attempted to get as many of the pages migrated across to the new Strava APIs as possible. The previous version of VeloViewer was around a year old and had grown slowly over that period and the replacement version will follow a similar path. Currently only the VeloFlow screen isn’t able to be migrated due to a few missing options in the new API but the majority of the rest of the site (and more) will be coming back on-line over the next few months. Where possible I will be improving those pages as I migrate them and also adding some interesting new features. As it stands I’m rather thankful that I have managed to get access to the new API as it seems a large number of people in a similar position to myself haven’t and it looks like that is how it will be for the foreseeable future.
The Strava web services which are the backbone of VeloViewer are set to be replaced in the very near future with a much improved set. These new API’s will open up a huge amount of additional data to what I’ve had to play with previously and I’ll finally know who is actually visiting the site and display or hide data appropriately, First up though is a video I’ve put together of the new Activities page I’ve been working on that shows the new, very interactive cross-filtering functionality integrated with a new activity summary map. Sorry for the very poor narration skills:
Hopefully you’ll understand how these filters will work and how powerful they’ll be for you.
As most of you will know Strava is moving to a new and improved version of their API (the way I get all my data from Strava to populate VeloViewer) and I’m currently working on VeloViewer to use this new version of Strava’s API. In general we are all going to be very excited by what the new API will offer us and I’ll go into that very soon in another post, but there is one sad bit of news – the main API that drives VeloFlow will no longer be available 🙁 This will mean that I will not be able to get the list of rides to display and I can’t think of another way to do it. So, the only hope I can see to keep VeloFlow going is to get all you good people to vote up and comment on my request to save the API on the Strava support site to show Strava how much you all want to keep VeloFlow running.
A massive thank you to everyone who took the time to fill in the usability survey and for those that added some comments at the end. VeloViewer’s final SUS score is 76.3 (out of 100) and here is how the responses averaged out:
