In the last days I did some runs on a tartan track and a parking place for my warm up.
Both times the GPS track was really accurate mostly, but there were some problematic sections where the GPS signal/track was rather bad.
1. Example, the tartan track: most of the signal on the tartan track is fine, but at one point the signal jumps to a near street and some time later it jumps back in a straight line to the actual position. There are no high trees, houses, power lines etc nearby, which could interfere with the signal - my girlfriend did the same run with her Fenix 6 Saphire, but even when her signal was worse in the beginning, die tartan track part was nearly perfect.
2. example, the parking place: some of the inaccuracies are fine and because of trees, but then it suddenly jumps in a straight line from the actual track to another location and back again.
I was in contact with the Garmin support chat and tried their recommendations (soft reset, switch to multiband, wait a couple of minutes for the signal, since the watch with Connect so that CPE is up to date etc).
On this scale and in the open air, it was the first time with such a large deviation. When running past tall buildings or in the forest under tall trees, inaccuracies do sometimes occur, but despite changing it to Multiband, these were never such large jumps as these times.
It seems to me that in some situations the watch assumes that I am moving from an unmarked path (e.g. tartan track) towards a marked road and therefore incorrectly jumps to this path/road and takes it as the correct track - if you then move away from the "wrong" location assumed by the watch, it jumps back to the actual location.
Some more information:
My watch is a Fenix 7 Saphire and it is on the software version 10.43. You can find some pictures in the attachment.
Does anyone else have such accuracy problems while tracking repetitive runs like these, and do you have an idea what might be the problem?
Here are also some pictures:
