Please check down this list of Frequently Asked Questions before getting in touch:
No, not at all. VeloViewer will show you all the details of all of your Strava data even if you are a free Strava user.
If you do have the Strava Summit Analysis Pack then you will also be able to view your heart rate and power zone information for all of your activities in VeloViewer.
Whenever an activity is checked for new segments on the update page it also updates any other changes (e.g. name or gear), but of course the frequency of these bulk checks are restricted for performance and API rate limit reasons. You can however force an update on a specific activity at any time in order to check for new segments as well as pick up any other changes by following these steps:
Remember, “hidden” segments on Strava will not be pulled through to VeloViewer (see below).
- Open the activity’s details page.
- Go to the activity’s Summary tab.
- Press the “Update Activity” button.
- The placings will not have been checked for any new segments at this stage so you’ll then need to press the “Check Placings” button on your Update page to get everything fully up-to-date.
VeloViewer only includes segments that are classed as “popular” by Strava. When you look at the bottom of the segment list for one of your activities on Strava then you will most likely see a button saying something like “Show 24 hidden efforts” (an “effort” is an attempt at a segment). This list can vary over time as Strava’s algorithm to determine which segments should be hidden includes a number of variables that change over time, e.g. how many times it has been starred, how many times people look at the segment details page and possibly how “overlappy” (my term) it is.
When VeloViewer’s update process gets a new activity details or checks it for new segments (runs the same code) then that is when the list of “popular” segments on that activity at the exact time is being recorded. If you did it the next day then it might be different. Because not all activities are checked at exactly the same time you might end up with some segments appearing on one activity and not another and so your Tries count might be out.
If one of your favourite segments has disappeared then just find, on Strava, any activity that you have done that includes that segment, find it in the hidden efforts list and click the “Unhide” button that appears when you hover the mouse over that segment. The next time any activity that includes that segment is checked in VeloViewer then it should reappear in your lists. And once all of the activities have been checked for new segments, your Tries counts should be accurate too.
There are many millions of segments on Strava (over 8 million at time of writing), some areas have far more than others. Many of these are flagged, many more are duplicates or just poorly created. In order to keep the segment numbers down on activities Strava apply a number of rules to determine which segments should be hidden for any particular activity. You can view the hidden segments by scrolling down to the bottom of your activity’s segment list on the Strava website and expanding the hidden segments section.In terms of how Strava determines which segments should be hidden then read the following excerpt from their API documentation:
By default, only “important” efforts are included. “Importance” is based on a number of factors and its value may change over time. Factors considered include: segment age, views and stars, if the user has hidden/shown the segment and if the effort was a PR. Note, if two activities cover the same segment, it is possible that for one activity the associated effort is “important” but not for the other.
So expect them to change between activities.
As it stands I take the details for the Strava Challenges using a script (manually at present) from Strava’s Challenges page
. For some reason not all Challenges appear on that page, possibly because some are segment specific challenges or because they don’t fit the typical challenge structure. In the future I could potentially manually crank the data together for challenges that aren’t on that page but right now I don’t have the time.
When you visit your Update page it will automatically look for deleted activities and remove them from VeloViewer. It should do this silently in the background. There is a chance that you might have to press one of the refresh buttons next to the main page headings on the Summary or list pages in order to remove the activity from your local storage. If this still doesn’t remove it then let me know via email me
with the VeloViewer link to the deleted activity’s details.
This is just due to your locally cached (in your browser’s localStorage) data still retaining your old gear names. Press one of the refresh buttons (e.g. the one next to the “Your Summary” page heading) and it’ll clear your localStorage and grab all the data, without the old gear names, from the server.
Possibly but probably not 🙂 The Eddington Number is based on the total distance covered PER DAY rather than PER ACTIVITY. So if you’ve ridden more than once in a day then it is the sum of the distances that is used. This does make it a little trickier to see which activities are making up your number. If you hover your mouse over your Eddington Numbers you will see how many times you’ll need to ride over the next distance in a day in order to raise your number by 1 or 2 points.
Head to your Update page and expand the “Options” section. At the top you will see the list of activity types that you are currently have set to sync with VeloViewer. Make sure the “Virtual Ride” box is checked and then you’re Zwift rides will be pulled in.
This will be because not all of your activities have been updated recently to get these new fields. Head to your Update page and press the “Check for new segments” button until all of your activities have been checked. This process also updates all the details of each activity being checked so will pull in this newly stored data. There is a limit as to how often an activity can be updated/checked so you might need to wait up to a week for this button to check all of your activities (unless you are PRO+ in which case you can update all of your activities at any time).
Since the GDPR related rewrite of the leaderboards this shouldn’t really be an issue any more as the collecting of times works in a very different way that avoids the previous occasional issue with Strava’s club leaderboards. See this blog post
for full info on how to get your times into the leaderboards.
I’ve had a number of users with this one get in touch over the years. Make sure that your data is up-to-date (and any deleted activities removed) and all your activity types are being synced, then also make sure you don’t have any filters on your Summary page. If the numbers still don’t match then the issue will be at Strava’s end. You will find a “Refresh Stats” button below your totals on your Strava profile page, try pressing that. Apparently it can take an hour or so for it to process at Strava’s end so give it a bit of time before heading back to your Strava profile and reloading the stats.
If you are seeing Explorer Tiles that aren’t being ticked when viewing the map in your Activities List then open up the Activity’s Details page and in the background it will populate a definitive list of Explorer Tiles using all of the Activity’s data points (by default the ticked tiles are only calculated using each Activity’s simplified map line which only includes a small number of data points). For more information see the “Definitive tiles for an activity” section of this blog post
Once you retire gear (bikes and shoes) in Strava then their details are no longer provided via the Strava API. The activities that reference these retired items still contain the code of the gear (e.g. b123456 for a bike or g123456 for shoes) but there isn’t a way to get their text description from Strava. This is why you might see these codes in the gear column. If you un-retire your bike/shoes in Strava then you will see their full description in VeloViewer. (Note, you’ll need to logout and back in to VeloViewer to pick up the change in gear).
The “to city” shown in the Infographic is taken from a list of around 400 world cities. Mostly capital cities with a selection of state capitals in places like the USA and Australia. There will inevitably be occasions when the total distance covered doesn’t neatly map onto a city from the list from your chosen start location. In this case the next closest city will be shown (which may in fact be a fair bit further away than the Total Distance). You could always try changing the start location to provide something more realistic. The Infographic is designed as an end-of-year graphic so hopefully once you’ve racked up some more distance this won’t be a problem any more.
Unfortunately the Rivals page had to be turned off due to the restrictions imposed by the GDPR which came into affect in May 2018. Some more details available in this blog post
The Strava API does allow me to get any of your segment leaderboard positions using age and/or weight categories it just gets far too complicated and expensive (in terms of number of API calls) finding out all of someone’s age/weight specific positions.
I provide a the option for women to have their positions using QOM but then people very rarely swap from one gender into another so all of their efforts will have been in the QOM bracket. When you come to age brackets, people move from one to the next as they age (and it gets even more complicated with weight brackets!) so you will end up having a PR and a position in one age brackets and then another PR (possibly faster, possibly slower) in another age bracket. Both of which would technically have their own Score. So if you’ve passed from one age bracket to the next then I would have to at least double up the API calls to find positions in each age bracket. Given that some people have way over 10000 segments, that is something that would not scale.The other tricky thing is that Strava’s API doesn’t provide your date of birth.
So although it is technically possible, it isn’t something I’m able to offer in a way that would scale for the number of users I have.
The individual tries on an segment are known as “efforts”. When you sync your activities to VeloViewer the site grabs the non-hidden segment efforts provided by Strava’s API at that time and the results are cached. If a segment didn’t exist or was auto-hidden (see #4 above) then that effort will not be stored/shown in VeloViewer. At a single point of time if a segment is shown on an activity (i.e. not auto-hidden) then it should be shown on all activities that covered that segment. If the activities are synced/checked at different points of time then there is a chance that not all efforts for a segment make it into VeloViewer which will result in the difference in the number.
If you press the “Check activities for new segments” button on your Update page then it’ll work through your activities to bring them all into line and afterwards the number of efforts for each segment should match what you see in Strava. PRO+ users only need to press the button once to recheck all of their activities (although it can take a while!), for PRO users it is batched and there is a limit to how often you can recheck each activity.
I’ll add more FAQs to this list as they crop up.