I read throught htat one but people are talking about 100-200m over 15km.  I can't see anyone who's getting such bad results over a short distance which is why I thought it might be a setting on the watch and not the gps 2.60 per say.

Multi-band has definitely improved distance accuracy for me.

Here is just one example from a trail run on Rattlesnake Mountain (Seattle, USA) that I did recently with 6X and later with 7X (with multi-band enabled).

The official distance shown on trail…

Ok. Sounds like the distance from tee to net was too short. 

Which could be my issue as well. 

Maybe the unit requires skightly more distance on lower flight shots as the angle is less?

I think the spec says min 2,4 meters.

It did. On the third attempt. Time is (almost) correct now. But distance is now 300km short...
I got to log off for a few days now and then will have some detailed work on it with the tool.
Thanks!

Yes, indeed. I double checked the course and found that the course backtracks on itself for a short distance before continuing in the right direction.

That is surprising because I created that course myself in Strava the night before. But perhaps I made…

My experience has been that if I start a course somewhere after the beginning, it will "want" to guide me back to the start of the course at first, but after a short distance it eventually figures out that I'm midway through the course already and corrects…

In hiking mode is it not better to use smart recording rather than 1 sec recording to smooth out tracks? Otherwise you will have a lot of data points over a relatively short distance.

The solution is to tune distance calculation specifically for each sport. I am too happy with distance calculation for road running. I think it is quite accurate. But I am unhappy with distance calculation for trail running and would be happier if Garmin…