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.
A quick list of the key additions in VeoViewer V3 are:
- ALL activity types – Hooray! No longer just your bike rides, now you’ll have the stats (and segment details/placings) for all of these different types e.g. run, swim, hike, ski etc.
- OAuth – to access the site you will need to give VeloViewer access to your Strava data though a simple button press when logged into Strava. The same as you get allowing websites access to your Facebook or Twitter data. This means that VeloViewer will finally know who you are and not let you see anyone else’s data unless they allow it. By default all your VeloViewer data will then only be visible to you but you will have the option to make it publically available if you so wish. Your private rides will always only be visible to yourself. If your friends are also and VeloViewer and they have made their data available then I should be able to provide comparisons between yourself and them.
- QOM – Following on from the OAuth I will also finally know if you are male or female and provide the QOM rather than the KOM.
- Update – I’ve completely reworked the update page and logic to provide a single click to upload all your data and another single click to check all your places. I’ve also reworked it to ensure it will be much more resilient than the current version. You can now stop the update process at any point and it’ll pick it up from where you left off next time you try, even if from a different device or browser.
- Hosting – moving to Amazon EC2. The current shared hosting setup has been increasingly plagued with downtime. It was fine when it was just myself and my club-mates using the site but its user base seems to be growing pretty quickly!
- Filtering – this was asked for many months ago and this code refresh is the perfect opportunity to introduce it. My personal interests are in data visualisations and combining this with the filtering was always a key thing for me to implement.
- More data – e.g. heart rate, power and hopefully cadence.
- Increased configurability and saving of settings – not quite sure of the extent of this as yet but hope to allow you to choose which columns you see and potentially allow you to save different column/filter/order configurations to switch between your favorite views of the data (e.g. bike view, run view).
- VeloFlow is saved! Yep, word on the street is that the Strava API necessary to keep VeloFlow alive will be created. Thank you Strava (and all you folks for supporting the request)!
Downsides/Restrictions in VeloViewer V3
- Unfortunately you will have to reload all your data into the new site. In order to get the new fields available in the new Strava API’s then everything will need to be reprocessed anyway so it is far easier to make a clean start. My initial testing has had an athlete with 600 activities and 2000 segments all being loaded up in 10 minutes with a single button press.
- The segments listed will just be “popular” segments. If a segment isn’t shown in VeloViewer then you’ll have to go and “unhide” it in Strava and then it will be pulled through on your next update.
- You will no longer be able to upload other peoples’ data, but that’s a good thing really.
- You will no longer be able to view other peoples’ data unless they have made it publicly available, once again, a good restriction.
When can we use it?
I’ve put together a V3 page that is available from the top menu where you can see the latest on the version 3 development.