Why Strava distance is always 0.01 mile shorter than Garmin distance?

[Silentvoyager]

I know it is a small thing but it is one of those things that is quite annoying about Strava. You know that situation when you finish a run and notice that it is very close to a round number of miles, than you run a bit further to make it e. g. 5 miles. Then it uploads to Strava and shows as 4.99 miles in some parts of the app and 4.9 miles in other parts of the app (e. g. the training calendar). Can Strava stop doing that? 

[varun · Accepted solution]

Hi @Silentvoyager, 

We know this has been a long-time quirk, and often a frustration for many athletes, including some of our own employees! The reason this happens is that Garmin (both the device and Garmin Connect) rounds up distances, whereas Strava rounds down. Distances are always stored in meters on devices and then shown on Strava in the athlete's preferred units (i.e. miles/yards for imperial and kilometers/meters for metric). So for example, a distance that comes over in a file as 4995 meters will get displayed on Strava as 4.99 km and on Garmin as 5.00 km. Similarly, if on your watch you run until you see 1.00 miles, that might actually be something like 1608.0 meters (0.9994 miles) and Strava will show 0.99 miles.

It is also worth clarifying that most Garmins, even relatively older ones, provide a distance directly in the file that Strava uses. There are cases we calculate distance ourselves from the raw GPS points; for example, if a certain device doesn't provide it. And athletes can also choose to use our calculated distance to override the device one - see How Distance is Calculated for more. 

One other nuance for the question from @MattS_bsb regarding race distances like a half marathon or marathon. There are features like Best Efforts and Challenges based on those Best Efforts that require athletes to complete a certain distance. One thing we have seen is athletes who run 26.2 miles and not receiving credit. This stems from the same issue above - that a marathon is 26.22 miles when converted from its official distance (26 miles and 385 yards), and athletes are often slightly short.

We understand that this is a bit of a philosophical stance we've taken - the digital version of "running all the way to the line". There is a tradeoff here between the consistency with Garmin and satisfaction of the round numbers (because yes, we've all been there), and the care we aspire to take with data correctness and integrity. This is one of an exceedingly long list of nuances around data as we pursue making Strava work for thousands of devices, each with its recording subtleties and differences.

Hopefully that helps clear things up and explains why you might see some crafty athletes running til they see 1.01 on the watch. We will strive to continue using this forum as a place to transparently explain more of these types of situations to athletes.

[hunterpc]

Can we not just have a manual override button, where we can change the distance?  So for a 10k race that comes up short at 9.9 we can have it recorded as 10k, and that then gets factored into your average pace, etc. Main thing folks want is to see the race distance recognised in the app and rewarded as such, showing under my best 10ks etc. You already have a distance correction option that uses a different calculation so have another one that lets us round up or even round down for that matter? Maybe a certain percent of tweak.

[Smarties · Accepted solution]

Your philosophical stance just cost me a pb on a half marathon that i have been training for for 5 months. Garmin says 21.1km and Strava says 21.09km. What gives you the right to do this? Rounding down is just stupid. I work with data for a living and no dataset is 100% correct anyway, but you are denying athletes pb’s for a couple of meters. I trained, i cried, I covered the distance but yet you deny me a pb. Do you really think that anyone cares about your philosophical stance? Its stupid. Who is the clown making these decisions in your company? Get your act together Strava!

[jacopoc]

I understand your frustration, but I actually think Garmin should be the one updating how they round numbers.

Cause you didn't run a half marathon, you were short by 5 meters haha.

I prefer the rounding down approach.

[Silentvoyager]

Yeah, the true half marathon distance is 21.0975 km. You were probably just a few meters short. I think Strava's stance about this issue doesn't show them in a good way. I remember seeing a comment from Strava that all GPS devices always measure distance long, which is clearly not the way with modern GPS devices if you read Garmin forums. The Sony chipset is especially bad in that regard. Distance measurement does no longer come directly from GPS. It comes from fusing data between the GPS and the accelerometer, and in my experience Garmin's distances often ends up being a bit on the short side when running on open terrain and even more short when running on trails. 

I think the right solution would be (a) to round exactly the same way as Garmin and (b) award a PB even when the distance is a bit short. How much, I don't know but something like 99.5% of the distance sounds like the right threshold. That would significantly reduce disappointment of users when they don't get a well deserved PB due to being a few meters short. 

[Smarties]

So if your sales director has a sales target of say $10k and that person only reaches $9,999.99, would you deny him his bonus ? I dont think so. Match Garmin or dont sync with Garmin

[Rogier]

Per the rules of World Athletics, a marathon is 42.195 km, not 42.19499999999999999999... . If the distance covered is even a fraction of a nanometer short, your sales manager won't get a bonus from World Athletics. That means no world record, no olympic ticket, no Boston Qualifier... .

Garmin should round distances down like Strava does.

[Silentvoyager]

> Per the rules of World Athletics, a marathon is 42.195 km, not 42.19499999999999999999...
The main issue is that Strava doesn't really know if that was 42.195 km or 42.19499999999999999999. The same actual distance could be measured by a GPS device as 41.77 km or as 42.62km - that all would still be within a very respectable 1% distance accuracy depending on whether there were some buildings, trees, or any other obstacles. Many GPS devices do much worse, especially when running on trails.
Arguing about which way to round when a typical GPS error is far greater is just stupid. Everyone refers to that as "Strava tax"! 

[Smarties]

The source of this data is Garmin, not Strava. You dont have the right to change the data. 

[triman66]

In slightly oversimplified terms Garmin sends a series of gps coordinates that maps your track. The issue is that the way Garmin adds up the distance between those points is different from how Strava calculates and adds up the distance between the points.

So it's not that Strava is "changing" the data rather they are comming up with a different answer for the same dataset due to a difference in how they are interpreting the raw data.

[Roebie]

Hi Varun,
Your text explains a lot, but it doesn't make it right. When I run an official half-marathon, then a professional company has measured the distance 3 times, just to make sure it's correct. No philosophical stance or roounding should deny me my Best Effords or Challanges reward in such cases. But Strava does. Running just a bit more might be an option (although quite ridiculous) during training, but in competion it just isn't. Get your act together!