-
My guess Re: issue 1) - I think this is caused by the “hide start/finish” function on strava so rather than pinpointing your exact start/end point (e.g your house) it will choose a different start point close by for safety purposes
-
Re the first thing, could be that the watch isn’t getting a full gps lock on enough satellites until you’ve set off and is struggling to place the first coordinates.
The second thing sounds like Strava cutting out all the stops at traffic lights etc. It almost always shows a slightly faster average pace for me compared to the true number that I get from the Polar watch.
Is the elapsed time different on Strava than it is on your watch? If so, it’s just how they calculate moving time. -
One of the tricks is apparently to start recording 30 seconds before you start running, then hit pause immediately. Because the activity has started it’ll try and get a proper GPS position, so when you unpause and start running a bit after then it’ll be accurate, rather than it spending the first bit of your actual run acquiring a lock
You are reading a single comment by @salad and its replies.
Click here to read the full conversation.
Leeroy1313
Well_is_it
duncs
@salad
(this probably belongs in the Strava thread, thought I'd post it here though as it's running-related I guess)
I'm using an Apple Watch 4 with a free Strava account to track my runs and get some stats.
This works really well, though there are two bugs / glitches / whatever that happen repeatedly, and I'm wondering if there is a fix for it -
Strava / the Apple Watch is GPS-tracking my routes fine for the most part (sometimes a little bit off, but it's all within, say, a 20 meter tolerance) - what I don't understand is though: it usually does not record the first ~50m of my runs (it pretends I started two blocks further down the road - this also happened somewhere else completely, in the mountains - overall tracking was fine / close to where I actually ran, but the start was about 40-50 meters "late", the start of the run (the green dot) is just further down the road than where I actually started the run, or the green dot is correct, but the first about 50m of the run is just a straight line (like a beeline, through buildings etc.) until it properly picks up the tracking).
Can't seem to figure out why it does that. It happens not every single time, but most of the time.
The overall pace seems off (with every run I record) - meaning that Strava list the pace of the run as, say 6:00/km - but the individual paces of the kilometers are all higher, like 6:10, 6:05, 6:20 etc. - why is that?
Thanks in advance for any help!