Strava query

[Uni]

Just went for a jog with my BIL

 

He's garmin recorded 7.2 km and strava 9.9

 

Then on rides it sometimes records ridiculous max speeds. Recorded a 65km/hr at big red barn.

 

?

 

Just curious.

[fanievb]

it's probably your Phone GPS that's wonky

[Bateleur1]

GPS accuracy is the impacting factor.  Especially if there are lots of trees.  I often had Strava recording issues when I was still only using my phone for Strava

[Uni]

Would average speed still be accurate then or not?

 

Maybe all this time i thought I was getting faster but I'm not

[Bateleur1]

Would average speed still be accurate then or not?

 

Maybe all this time i thought I was getting faster but I'm not

 

No. If your distance is calculated incorrectly then the speed that is calculated on the time used to cover the distance will be incorrect as well.

[Uni]

No. If your distance is calculated incorrectly then the speed that is calculated on the time used to cover the distance will be incorrect as well.

I hate strava. Do I have to give my QOM back?

[GaryvdM]

If you have a Garmin, why not just record with the Garmin, and then upload your ride from the Garmin to Strava?

[Uni]

If you have a Garmin, why not just record with the Garmin, and then upload your ride from the Garmin to Strava?

I don't have garmin

[Paddaman]

Strava is a user interface product that takes data recorded from various sensors, smooths out various anomalies (bmo algorithms) and displays it in various formats.

 

Your sensor, be it a polar watch, a smart phone, a garmin or tomtom records various waypoints (these being GPS determined locations, heart rate ext).  From these points speed, VO2 max, Altitude and so forth are calculated (sometimes on the devices and sometimes in the cloud).

 

When your sensor uploads to strava, it can be direct from the device or via the "cloud" in the case of garmin.  The strava platform will be fed only a few fields of your data, such as HR, GPS locations and altitude.  From this data the strava "backend" will work with the data, scrubbing it of "Stationary points", adding in possible attitude based on location and smoothing your route onto known routes, segments and foot paths/ roads.  (This may actually shorten your overall ride, as all the swerving you do is smoothed out).

 

Then the data is presented back to you via the front end.  For these reasons you might find average speed will be different vis-a vis your device (as strava may trim your pause functionality more aggressively than your device) your route may be shorter or longer ext.

[Mudsimus]

I always have a 30m difference from my watch to Strava. Doesn't matter if I run 1km or 40km.

[Paddaman]

I always have a 30m difference from my watch to Strava. Doesn't matter if I run 1km or 40km.

Do you have the auto-pause function on?  this may result in the watch only recording a few seconds after you have started running.

[Mudsimus]

Do you have the auto-pause function on? this may result in the watch only recording a few seconds after you have started running.

No, but its always exactly the same. I always finish my runs at 10.03km not to come up short on Strava ????

[Uni]

Strava is a user interface product that takes data recorded from various sensors, smooths out various anomalies (bmo algorithms) and displays it in various formats.

 

Your sensor, be it a polar watch, a smart phone, a garmin or tomtom records various waypoints (these being GPS determined locations, heart rate ext).  From these points speed, VO2 max, Altitude and so forth are calculated (sometimes on the devices and sometimes in the cloud).

 

When your sensor uploads to strava, it can be direct from the device or via the "cloud" in the case of garmin.  The strava platform will be fed only a few fields of your data, such as HR, GPS locations and altitude.  From this data the strava "backend" will work with the data, scrubbing it of "Stationary points", adding in possible attitude based on location and smoothing your route onto known routes, segments and foot paths/ roads.  (This may actually shorten your overall ride, as all the swerving you do is smoothed out).

 

Then the data is presented back to you via the front end.  For these reasons you might find average speed will be different vis-a vis your device (as strava may trim your pause functionality more aggressively than your device) your route may be shorter or longer ext.

Schooled

[thisismyotherbike]

Buy a Garmin, then go affirm your QOM achievements again.

[Dirkitech]

For what it is worth, when I drive somewhere navigating with google maps (GPS usage)- google always results in at least a few km's less than the actual distance I drove.
When I ride on the bike, strava (GPS usage) will consistently record slower average speeds and shorter distances compared to my bicycle computer.

I personally think it has more to do with the gps measuring estimated points, like of you take a 90 degree corner, the gps would at some point measure it as a chamfered corner and thereby reduce your distance but retain your time, making the average slower.

[SwissVan]

If you have a Garmin, why not just record with the Garmin, and then upload your ride from the Garmin to Strava?

Even then strava records differently....

Strue