Incorrect GPS starting point causing shifted route

Interesting. Could be an unavoidable result of challenging conditions (tall buildings?) but that wouldn't explain why you only see the problem intermittently.

I have had situations where I waited for a shorter time than usual and I thought my GPS signal was stable, but I still had issues at the start of the run (too much distance, unrealistically fast pace). I can only assume that in those cases, I needed to wait longer.

As FR265 does not have true mapping (just breadcrumb trails), it's harder to use the watch to verify your actual position. (I can do so just by comparing my position on the map page with my irl position.)

What you can do is save a location to your watch at the start/end location of your run when you are sure you have a good GPS fix. Maybe one good opportunity to do this would be at the very end of a run. The next time you go for a run, look at the "map" page and make sure that the watch shows that you are standing at the correct location, before you press the start button.

You could also use google maps to get the coordinates of your start location and save the location on your watch by entering the coordinates.

To add to this discussion, I went for a run and something similar to what the OP described happened to me (not for the first time).

- I waited for the green GPS ring

- I waited for my pace to settle to 0:00

But despite waiting about 2 minutes (much longer than normal), my start position on the map was incorrect. Since I didn't want to wait any longer, I just started the timer and started running. Ofc my stats and GPS track near the beginning of the run were bad.

This does happen to me every now and then - no matter how long I wait (while standing still) at the beginning of a run, sometimes my start position is wrong, and GPS never "catches up" until I start running.

Another point of nuance in this entire discussion is the idea that unavoidable GPS drift occurs when you're standing still, which is why some people recommend pausing your watch whenever you stop running.

So I guess the ultimate solution would be to:

- wait for the green GPS ring

- wait for pace to settle to 0:00

- wait for start location to be correct

But if pace / start location is still wrong after a few minutes, I guess you could start running (without starting the timer), and only start the timer when you feel like you have a true GPS fix. (It would be harder to tell in your case, without a true map.)

Even I'm not willing to start running without starting the timer though, for various reasons. 

Another solution could be to just wait for as long as practical, and start running. If you still have bad data at the beginning of your run, you can always crop it. (I do this sometimes.)

Sébastien said:

When you mention the "map page", what exactly do you mean ? Where can I find it on my Garmin Forerunner 265 ?

It's an optional data page that you can add to your running activity which shows a breadcrumb trail:

https://www8.garmin.com/manuals/webhelp/GUID-F41EAFB3-6CC9-42DE-9C6C-9E358DBB0671/EN-US/GUID-A877CC78-A0E1-4836-84E2-6A7366C8F705.html 

It's also displayed by default when you use the navigation feature.

Like I said, it's not as useful on FR265 for this situation because FR265 doesn't have true maps (with place names, streets, etc), but only a breadcrumb trail. It does show your current position and any nearby saved locations.

So if you save a known location (like your home / usual start/end point for a run), you can see whether the watch correctly places you close to that location (indicating a good fix), or incorrectly places you a little too far away.

Like I said, yesterday I saw that the map showed me as too far away from my actual position, but I started running anyway.

An example of the map page:

https://www8.garmin.com/manuals/webhelp/GUID-F41EAFB3-6CC9-42DE-9C6C-9E358DBB0671/EN-US/GUID-CF774818-0C30-4992-962C-DDA9EA00E8C6.html 

Sébastien said:

I live in the city, surrounded by houses and a few low-rise buildings, so it’s definitely not a skyscraper-type environment.

Yeah, yesterday when I had a similar problem to you, I purposely crossed the street so I could stand next to a parking lot (as opposed to tall buildings). It actually helped me get a faster fix, but I still had GPS issues (bad starting position).

So I think tall buildings can make the problem worse, but just because you don't have tall buildings, doesn't mean you won't have the problem.

I'm not really sure how to avoid it completely. I mean it's possible that if I had waited 5 or 10 minutes the watch would've eventually showed the right starting position, but ofc I don't want to do that.

Maybe the real solution would've been to start running without starting the timer (after waiting for as long as reasonably possible), then only start the timer when my position was better. (Ofc this would be harder for you, without having a real maps.)

I'm just thinking that if GPS drift is an issue while standing still, maybe the same can be said of having a slightly incorrect position? Maybe once you have a good fix, motion actually fixes these little problems?

After all, we both see that only the start of the run is affected in these situations.

Ofc, maybe the best of both worlds is to just start the timer at the start of the run anyway, but crop the start of the activity if you have bad data. If you can't completely control / prevent the bad data, you can get rid of it after the fact.

On the flip side, if it's something important like a race or even an interval workout where you don't want to crop data, then the best solution is probably just to get a fix well in advance. When I run races, I make sure to get a fix at least 15 minutes before the race starts. (I enable the extended power save timeout activity setting so the activity doesn't automatically time out if I forget to press buttons to keep it alive.)

Hi everyone,

Once again, it took a long time for the watch to get a GPS signal before starting my run, probably around five minutes.

Even though I waited for the GPS indicator to turn green and stay stable, the beginning of the run was still inaccurate. The track placed me on the other side of the street, not where I actually was (I was actually on the same sidewalk) :

It's only after about one kilometer that the GPS finally corrected itself and put me back in the right position on the map.

Later during the run, the GPS track can also be very approximate. Sometimes it does not follow the roads at all and even goes straight over buildings, which obviously does not reflect the real route.

At this point, I’m wondering whether this behavior is "normal" for this device, or if it could indicate a hardware issue with my watch.

Try running GPSTest app on your phone, the Sky view will tell you the satellites it can see, their constellation and strength. Check your PDOP (Position Dilution of Precision) in the status page, a value less than 2 will indicated excellent positioning.
Obviously your watch won't be as good as your phone in getting GNSS signals.

Doing this will tell you whether it is your location or watch that's having issues.

I usually recommend setting recording to per second, but I'm not sure how much that would help in this case.

I forgot to mention that for my running activities, I use the satellite setting which provides the greatest accuracy (All + Multi-Band), at the expense of a bit of battery life. I don't know if using this setting will solve your problem, but I guess it couldn't hurt to try.

https://www8.garmin.com/manuals/webhelp/GUID-F41EAFB3-6CC9-42DE-9C6C-9E358DBB0671/EN-US/GUID-E01D9421-9E1B-4D85-81A0-46C6DCFAA9E4.html