Since the Garmin Instincts release, there have been complaints about its under-recording of distance.
My own experiences with the Instinct have been that it performs well in good GPS conditions such as open countryside, but struggles as soon as tree cover, hillsides, valleys, walls, hedges etc are introduced. The more time spent in these conditions the further the Instinct under records distance.
I have compared my Instinct with my Ambit 3 Peak over 60 walks, hikes and trail run where it tends to under record compared to the Ambit by 2-3% sometimes more, sometimes less, depending on terrain. Yes, I am aware of the limitations of GPS technology, but the Instinct underperforms, when tested against other GPS watches in recording distance.
"Garmin Instinct Review THE GPS Summary: After finally completing my formal test I found that the Instinct’s GPS performance in that test was mediocre. In easy GPS reception conditions it was good but when buildings or trees were involved the GPS performance slipped notably and the overall score was 65% and a good Garmin on a good day would normally give up to 79%, with other, non-Garmins scoring even higher. So here we are typically talking about positional accuracy often being more than 5m away from where it should be and some times a lot further away."
Until recently I just assumed it was the antenna or chipset, but after running data through a comparison site https://quantified-self.io/ and Comparing it to a plotted route and the Ambit, I am convinced its an algorithm the Instinct uses that is responsible for under-recording data.
Here is an example from today. Plotted route and the Ambit were extremely close, with the Instinct falling quite a distance behind. This was a route that had tree cover and went to the bottom of the valley by a river.
However, if you look at the GNSS recorded distance, the Instinct was very close to the actual distance. Frustrating as when running 10 miles, 3% under-recording means having to run an extra 480 meters which has a large impact on lap times and lap pace.
Is this issue something Garmin can fix as I have read lots of comments from people who returned the Instinct because of under-recording over known distances?
Antanna design/placement issue, GPS Chipset issue, Algorithm problems?