Race pacer on Coros watches
Dear Coros team,
First off, I loved using the Pacer function on my Coros watch for my first marathon! It was incredibly helpful in maintaining a steady 4:58/km pace throughout the race.
Unfortunately, there were two tunnels on the route that caused my GPS to drift. As a result, the watch overestimated my total distance by about 0.4km. Because the watch thought I was further along than I actually was, the Pacer showed a slightly optimistic time. I ended up missing my 3:30 marathon target by just 1 minute (even though my watch recorded 3:29 at the 42.2km mark).
Feature Request: It would be amazing if you could update the Pacer function to calculate the "real" pace based on a loaded GPX track provided by race organizers, rather than relying strictly on live GPS distance. This would completely eliminate pace inaccuracies caused by tunnels or tall buildings.
Since the watch already calculates the distance to the finish line, the distanceFromStart is also known, the logic could simply be:
raceTime - (distanceFromStart * targetPace)
Displaying this adjusted metric on the Pacer page would be a game-changer for city marathons.
Thanks a lot for the great Coros Pace watches.
