Hi John , have noticed a bit of a glitch . I reached E101 on August 12th with a combo of 2 rides due to be hitting save part way through a ride and yesterday I rec'd notification that I am back on E100 and have 3 more activities to reach E101 , today I had a count up of all my rides over 101 miles on the ride summary page and there is 101
This is unfortunately caused by a bug fix! I hadn't been using an accurate conversion factor from metres to miles, so was giving you more miles than I should. It's accurate now, and your adjustment down must mean that you had a few days that were actually just shy of 101 miles. Sorry for the confusion!
Hi John , I do all my rides in miles so there should be no conversion required . Also setting the peremiters between 101 and 215 I counted up 101 actual rides on the ride summary page and you'll notice I mostly ride an extra .1 or .2 mile to factor in discrepincies so am still a wee bit confused
Strava supplies all data in metric form - but my recent update still didn't convert accurately! I've fixed it now, so you should once again see an E-number of 101.
Glad to hear that you like it, Jeroen. The reason for the km/miles discrepancy though, is because the count also factors into the formula - so a score of 112 needs 112 days at that distance, whether it's in km or in miles.
Hi Jarek, I calculate this myself by storing activity co-ordinates and figuring out for a new activity which co-ordinates are new. It's a bit crude, but gives a reasonable estimate of the new distance covered.
Thanks for the explanation! I assumed you don't have to figure it out yourself, as they apparently do this stuff in their segment affinity algorithm. So you basically consider each point outside a buffer computed around all the previous polylines?
I actually store all previous lat/lon co-ords (to 100m accuracy) and consider a point to be "new" if there aren't any pairs of adjacent co-ords crossing it. So there's no actual polyline comparison - which makes it less accurate, but probably more efficient in cpu and storage.
I was hoping to be one step closer to 46 (km) but somewhow, of the rides for 01 Nov 2021 only read one of the two rides I did (one started home, finished mid-trip (28ish km), and the second started a few minutes later from where the first ended, and went all the way home again (21ish km)... only the first appears, so instead of a 49 kms day, i've got a 28 kms day)
Just checking to see if this is something particular of this day, a bug, or how it would be expected to work.
Hi Gonzalo! I've been doing some server maintenance work recently, so it may be that your other ride was missed out. Best thing to do is for you to check my little "Help Guide" (link at the top left of the page).
Hi John. I've been making use of the Activity Analyser, a very useful tool! One observation; it asks for the ride parameters in miles but gives the results in metric which, unless I've missed a control somewhere, seems illogical? Would it also be possible to add an ascent filter? Cheers Malcolm
I wasn't being consistent with your measurement preferences, so sorry for that confusion. You can manually set them now (in the sidebar below your profile photo) and this should allow you to see everything in miles.
As for the ascent filter, I'll definitely add that when I get time!
KM: 105
Miles: 70
But using the 1.609 conversion I would get to 112, which does not match my number of rides over 112km. Am I missing something?
I was hoping to be one step closer to 46 (km) but somewhow, of the rides for 01 Nov 2021 only read one of the two rides I did (one started home, finished mid-trip (28ish km), and the second started a few minutes later from where the first ended, and went all the way home again (21ish km)... only the first appears, so instead of a 49 kms day, i've got a 28 kms day)
Just checking to see if this is something particular of this day, a bug, or how it would be expected to work.
Thanks again, Gonzalo!