As the title says. I have had a Epix 2 and a Forerunner 255 used on the same track here in Paris. Officially the track is 350m, yet on both the Garmin watches consistenly record 400m. On other tracks that are 400m the watches also record 400m correctly, everything is great there.
However, this error is highly annoying when you want to do proper intervall sessions on this specific track and also just looks awful on Strava later on. Any idea how I could fix this issue, preferably permanently on the watch or with a workaround to have the correct 350m per lap counted?
You are using the “Track Run” setting. It is for 400m tracks only. You can calibrate the watch to the track by going to the calibration mode and running 4+ laps then hitting the lap button as you finish. It will not calibrate to 350m though. It will only calibrate to 400m. You can select the lane you are running in for it to adjust distances but if you are not on a 400m lap you need to turn off the Track Run setting. For more information you can send an inquiry to the Garmin Support team. They are really good with their product support. Once you turn off the setting things might not look any prettier. When I run on the track I have problems with occasional laps having a diagonal line across the middle of the track rather than being an oval around the track. I don’t know how accurate the distance is with my location skipping corners because my settings are in miles and the track is in meters. I expect to run one lap and cross at start line at .25 miles or to run four laps and cross the finish line at 1.00 mile. The conversion shows a mile to be 1609m but every track I have ever run on I get my mile alert when I still have about 40m to go to complete the 4th lap. So, it isn’t very pretty on Strava. On the track I know the distance though so all I am using the watch for is to see my interval time, rest time, and HR. I don’t need the distance metric at all. I still get kudos on Strava even if it isn’t pretty.
The issue for the first poster in the thread has zero to do with what satellite navigation system is used but 100% with what activity type when doing the session.
Thanks slow_bob, by using normal run on the track and just doing open repeats it worked well enough (700m vs 710m recorded on Garmin). I’ll take that. Cheers!