Garmin

2 lurkers | 209 watchers
Bazoaxe
Bazoaxe
Oct 2021
9:18am, 18 Oct 2021
21,084 posts
  •  
  • 0
Bazoaxe
strava does seem to knock 0.1m off the distance shown on my garmin sometimes
larkim
larkim
Oct 2021
9:24am, 18 Oct 2021
15,776 posts
  •  
  • 0
larkim
I've never seen inconsistent laps before though, I don't think.
SPR
SPR
Oct 2021
9:28am, 18 Oct 2021
35,482 posts
  •  
  • 0
SPR
If you correct distance does it go back to what the Garmin says? strava obviously does its own measuring but not sure how.
larkim
larkim
Oct 2021
9:32am, 18 Oct 2021
15,777 posts
  •  
  • 0
larkim
No, no change when I correct distance (though I did lose a little on the overall, went from 6.07 to 6.04 I think).

I presume the logic is that when the watch thought 1m had been run (and therefore created a "lap" entry in the fit file), strava has measured the distance of the trace from the start of the lap to the lap point and decided that it is only 0.99m of trace. Which is odd.
K5 Gus
K5 Gus
Oct 2021
9:38am, 18 Oct 2021
4,721 posts
  •  
  • 0
K5 Gus
Like Baz, I often see strava knock 0.1 off the total distance, but have never seen it adjust the individual laps
SPR
SPR
Oct 2021
9:41am, 18 Oct 2021
35,486 posts
  •  
  • 0
SPR
Does Garmin round up at 0.995 and is it using that for laps? strava rounds down doesn't it?

Only other thing I can think of is smart recording Vs every second recording. Smart recording could in theory get distance a bit out.
larkim
larkim
Oct 2021
9:43am, 18 Oct 2021
15,778 posts
  •  
  • 0
larkim
Not using smart recording, so it can't be that.

I'll keep an eye on it, see if other activities display the same.
Bazoaxe
Bazoaxe
Oct 2021
9:58am, 18 Oct 2021
21,085 posts
  •  
  • 0
Bazoaxe
To be honest I rarely look at laps in strava and use Fetch for that so not sure. What I have noticed is that a 7.0 * mile run on garmin/fetch is often 6.99 in strava and presumably would be 6 x 1.0m laps and one x 0.99m. If the laps were 0,99m on strava there would be lost distance somewhere ? Might need to check future runs

* The times I noticed this are when I stop bang on a mile and press stop on the garmin as soon as I see 7.0 miles but before the mile alert has sounded and so had assumed it was my fault of a watch press just a nanosecond too early.
larkim
larkim
Oct 2021
10:03am, 18 Oct 2021
15,779 posts
  •  
  • 0
larkim
Yes, I've had that before so I've had a habit for the last 4 or 5 years of running to x.03 or x.04 miles before hitting stop if I want a nice neat log. But laps with a different distance isn't something I've seen before (or at least, not for a very long time since I was recording runs with a phone I think in the "early days" of strava). Maybe it's a one off.

I'm only really bothered as I finished my race on Sunday thinking I'd managed to sneak under 7min/mile but perhaps not...
MarkyMarkMark (3M)
MarkyMarkMark (3M)
Oct 2021
11:27am, 18 Oct 2021
16,376 posts
  •  
  • 0
MarkyMarkMark (3M)
From memory, Garmin (like most GPS watches) records position data to 4 decimal places, but strava only works to 2, so all of your data points will have been rounded.

I've had a few ".99" km over the years - I've learned that you've gotta pay the strava tax and do an extra 0.1km at least!

Of course, if you set your watch to show distance and laps in miles, but let strava work in Km, it all gets much harder to see and you can stop worrying about it!

About This Thread

Maintained by fetcheveryone
For all questions and comments about Garmin devices, including importing to Fetch.

Related Threads

  • garmin
  • gps
  • tech









Back To Top
X

Free training & racing tools for runners, cyclists, swimmers & walkers.

Fetcheveryone lets you analyse your training, find races, plot routes, chat in our forum, get advice, play games - and more! Nothing is behind a paywall, and it'll stay that way thanks to our awesome community!
Get Started
Click here to join 112,278 Fetchies!
Already a Fetchie? Sign in here