This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Track Runs with data errors on 955

I've used Track Run mode successfully in the past when doing sessions on the outdoor tartan, but for resent sessions I've experienced serious issues with data quality. I've booted the device several times and verified that settings looks good. I've configured the watch to use lane 4 and I consistently run in lane 4. See for example the following two sessions on two different locations:

https://connect.garmin.com/modern/activity/10998333013 (here you see consistent lane tracking however data is erroneous)

https://connect.garmin.com/modern/activity/11008137308 (again, there are errors in the data, including logical inconsistencies)

What is going on here? 

Thanks, 
Jeppe

  • For the first one, it looks like the track's aspect ratio differs from what the watch is expecting. The recorded track has a narrower width on the minor axis, a longer major axis, and tighter curvature on the turns.

  • Hej Jeppe,

    Looking at your faulty recording - It looks like that it is only the first few laps that are wrong.

    My guess is that you did not let your watch soak for a few minutes before you started your running - your EPO and GPC files was probably not updated. An easy fix to that is either the soaking or sync with your mobile phone to get the files updated.

  • Thanks for the reply! The first one is from the diamond league venue called "Bislett", the tracks aspect ratio should be international standard there. The *second* one is a smaller venue and that may have a different aspect ratio. However, it doesn't explain why I end up with data errors like average pace, total time being shorter than moving time etc.    

  • Thanks parentoft, appreciate your reply. The watch was indeed properly soaked before I started. I can't say for the EPO and GPC files, however the watch is paired with my phone and I ran with both devices on me. I can also see from the track overlayed on the map that the GPS is quite spot on, I cannot understand that this can be the root cause for the data errors I see. The distance is much greater than I actually ran, the average pace is 2:08 /km (I wish), the total time is less than moving time (moving time is actually correct) etc.