open topic, for anything cycling related.
Its been a weird week on Strava. I have received 3 of the dreaded "oh no, xxxxx just stole your KOM ..." emails. 1 was obviously driven in a car so I regained my KOM by flagging the ride. The other 2 are very weird in that they sent me the email but the times recorded by the newcomer are less than my KOM time and when I actually go to the segment, it still lists me as the KOM, so I have no idea whats going on there.
The upside is that somebody else created a segment which I am now the KOM holder on, but I had no idea as I wasn't even aware it was a segment and I've never ridden it aggressively, only my normal commuting speed. Its impressive on paper too given its a 1st of 2040 !!! But before you say "liar", its a long slight downhill and I ride a velomobile so even rolling down there is fast. So in reality, its a little lame but a bonus none the less
Link of evidence: http://app.strava.com/segments/1570359
And while I'm on the subject of strava weirdness, can anyone explain why my all time biggest climb is reported as only 32m despite me having registered climbs on Mt Coot-tha etc. No matter where I ride I cannot get that figure to go up.
Some people wrap them with [ url ] and [ /url ] tags so it is both an image and a clickable URL. Its described on the veloviewer signature page, take a closer look at it
I did read it but it was mainly jargon to me. The url bit, as you pointed it out in laymans terms, helped the penny drop . Thanks
For those who don't follow STRAVA on Facebook, this is an article they linked me/us to:
http://www.outsideonline.com/fitness/bi ... tml?page=1
I thought it captured what was happening with cycling stravaphiles quite well.
Ok, dumb question time.
How do I delete some rides that I don't want in my history because they weren't rides. I just wanted to record for distance and average speed over a long distance.
I don't suffer fools easily and so long as you have done your best,you should have no regrets.
My garmin (edge 800) was mucking up on todays ride, seemed to autopause whenever I went over 35kph for some reason. When I got home it was under reading distance by about 7km and the garmin connect upload agreed with the device. However when I've uploaded the ride to Strava the distance is correct (more or less) for the ride at just over 100km.
I guessing that's because strava ignores the pauses? Any ideas?
I wasn't very clear, but Ozkaban got it. I meant that strava takes the pauses into account on the ride - (ie it ignores them as pauses and sees them as ride time). So we're all right
Now I've just got to work out why it's autopausing unexpectedly.
I think that's what Ozkaban meant by ignoring the pauses ie your time doesn't pause while you do.
In terms of how Strava handles the data from the Edge it's definitely different to Garmin Connect. I find that Garmin Connect always matches what the Edge records for things like distance, average and max speed, metres climbed etc whereas Strava is slightly different. I assume strava takes the gpx data for each (or every so many) point/s recorded and works out it's own data from that. So while the Garmin was paused the Edge and Connect make no changes to overall ride data whereas Strava assumes a straight line at constant speed from the last point recorded before the pause to the first one after the resume. It does exclude certain points from the data where it appears something is amiss which Connect doesn't appear to. The best example is where atmospheric pressure changes while you're at a stop in the ride. Connect will attribute you for the climb or descent associated with the pressure change as soon as you start riding again whereas Strava ignores it.
Here is two graphs of the same ride last weekend, one from Bryton, the other from Strava, along the freeway bike path. It includes several tunnels underneath roads, which I assume would interrupt the GPS signal. I have placed my cursor at the Thomas Rd underpass in both graphs.
This is what the Bryton graph shows:
And this is what the Strava graph shows:
Notice that each time I go under a road, the speed drops very low, at Thomas Rd it says I'm only doing 6.3km/h, when I was actually doing around 25km/h.
I think Strava interprets the data at face value, it doesn't try to smooth out any anomalies. So each time a signal is lost, it thinks I'm going nowhere. I don't know how it works out an arbitrary speed of e.g. 6.3km/h, it must think I've gone through a wormhole or something. But with the Bryton (and I think Garmin Connect is similar) it interpolates the readings from one point where the signal was good, to the next point where the signal was good, and averages it out over that missing distance.
I do remember when riding through the underpasses that the speed on the GPS determined speed looked correct, the signal said it was strong. So I don't know exactly what is going on.
Here is a run I did which included going through the Graham Farmer Freeway tunnel, which you can clearly see on both graphs, starting at the 5km mark.
Strava does interpolate between readings at either end of the tunnel. But the speeds are somewhat different. At one slow point Bryton said I was doing 5:52min/km, while Strava said I was doing 8:49min/km at the same point (8.9km mark).
For the sake of comparisons here's my profile from both strava and garmin connect.
stravaprofile by _granty, on Flickr
garminprofile by _granty, on Flickr
They are quite different and Strava will translate the pauses as pauses and include them in the profile as periods of no speed. The prominent flatlines are stop to help mate fix puncture, rests at top of hills. Strava then translates these as rests, which is something Garmin doesn't do it seems.
And at one point garmin has me descending at 180kph.
edit: higher res
All your rides past, present and future.
Who is online
Users browsing this forum: No registered users