Update on Strava API use and the implications for VeloViewer

Thank you once again for all the support you have shown recently, we know we are incredibly lucky to have such loyal users.

We have been working closely with the team at Strava and are appreciative of their partnership. At this time, we fully understand the implications and will be making a subtle adjustment to make sure that we continue to uphold the highest standards of data security and to ensure that we fully align with Strava’s API agreement.

The single change is that users who choose to share their data publicly within VeloViewer will now be asked to confirm consent regularly. Visibility will default back to ‘private’ if consent is not reconfirmed.  Previously, it was a ‘one & done’ consent process, this change will help users to be fully aware of the data sharing that they have agreed to.

This change will be released in the next couple of weeks and all other functionality will remain unchanged. We hope that you will continue to enjoy exploring your data and planning your adventures with VeloViewer.

VeloViewer Update 3rd December 2024:

Your options for sharing data in VeloViewer have now been updated.  This gives you more control over the privacy of your data.

Previously, when you synced your Strava data to VeloViewer, your data was visible only to you, across the whole site.  You could then check a box to opt-in to make your Strava data public within VeloViewer (note this only relates to your public/non-private Strava data, VeloViewer has never allowed private Strava data to be shared). This option made your data visible until, either, your PRO subscription expired, or until you unchecked the box.  

This has now been improved; when you opt-in to make your Strava data public in VeloViewer, it will only remain public for 7 days, after which it defaults back to private.  On your Update page you can press a button each week, when you update your data, to keep it public, if that is your wish. We have tried to make this process as quick and easy as possible.

If you opt-in to show your information in the overall, and Zwift-Insider/100 Climbs leaderboards, as well as your public VeloViewer Explorer Tiles in the Explorer Global Heatmap, then those continue to be indefinite, no need to renew.

The place to initially share your data is in the Options section of your Update page:

If you check the box to make your data public, then the next time you visit your Update page you will see when your data is public until, along with buttons to reset the data visibility for 7-days from when you press the button, so in effect, you have the option to reset the clock.  You will also see an alternate option to make your data private:

Why the change and why now?

Giving users choice and control of their data privacy is very important to us.  We wanted to move to a system that makes data sharing as transparent as possible. The new system prompts users to consider whether their data sharing preferences have changed, rather than assuming that they haven’t.

This update was prompted by conversations with Strava and we believe it is a positive move for our users.

VeloViewer V3.1 – New update options and page load improvements

VeloViewer ScoreIt always surprises me how many rides and runs some people load up into Strava and the knock-on affect for VeloViewer is some slow page loads for those people concerned. Hopefully those days are now behind us!  As well as improved page loading I’ve finally got round to adding the most requested feature from the Usability Survey many of your filled in earlier in the year: “Could we have one update button, one click does everything”. Well now you’ve got one!

Continue reading

Update Ride Dates

Update Ride DatesAfter being pointed out that the Velo Flow link from segments for some rides in Australia weren’t always returning results as expected I discovered I’ve not consistently using the right date from the Strava API. The majority of dates I use have been Greenwich Mean Time which is causing an issue when your ride happened to not be the same day as it was at the time in London.

Easy fix though – once only you will need to press the “Update Ride Details” button on your Update page and then this button will disappear then all your data should be in the appropriate time zones.

Optimistic Placings Bug Fixed

Worse PlacingsGreat news! Strava have fixed the bug with their API that resulted in segments with people tied on time returning placings that were better than reality.

This was the main “Known Issue” with VeloViewer and I’ve been completely at the mercy of Strava’s tech team for getting a fix. But it has arrived and with it the most depressing placings update statistics you’re every likely to get! Out of my 804 segments a whopping 486 have resulted in my placing getting worse.

Go update all your placings to get all your correct placings.

Continue reading