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

910 recording too long, but data ok in strava

Former Member
Former Member
Hi all

I use a forerunner 910xt to record my cycling activities. I have noticed on the last couple of group rides that i have been on that the distance has been inflated both on the watch during the activity, and on garmin connect once the data has uploaded. The max speed has also been inflated, for instance today i 'hit' 80+mph 9 times, clearly incorrect.

It appears that these inflated speeds has caused the inflated distances (but as im only speculating it could be the other way around - for example if the watch is 'jumping' gps points, then the increased perceived distance over the same time period could result in a spike in calculated speed).

Interestingly though when the same data is uploaded to Strava then it is interpreted correctly, the correct distance and no speed spikes. How can Strava interpret the data correctly and GC not? its the same data...

Here are links to the same activity on GC and Strava
http://connect.garmin.com/activity/633182153
http://www.strava.com/activities/219375938

when i am on solo rides there has been no errors. One thing i have noticed on both times when the distance/speed error has occured is that the 910 has asked me if id like to pair my power meter (i havent got one). Also I have noticed that the data shows a cadence speed (i havent got a cadence meter and it doesnt show a cadence speed on my solo cycling efforts). Dont know if these are significant but have included nontheless.

Can anyone help me get the correct data (most important for me is to have the correct data on the watch during the activity if im honest)

Thanks in advance folks
  • Former Member
    0 Former Member over 10 years ago
    Data is correct in other apps that I sync to eg run keeper. Why is not interpreted correctly in gc?
  • I'm guessing it is a problem with the speed data, which is most likely coming from a speed or speed/cadence sensor. I looked through the data, and I'm seeing speed values as high as 65.53m/s (146.586mi/hr). This could be caused by all sorts off issues associated with a speed/cadence sensor, but a bad wheel circumference setting is likely.

    I'm guessing the reason that you see the issues on Garmin Connect is that they use the speed data, and the other services calculate the speed based on GPS position and time.

    Travis
  • Former Member
    0 Former Member over 10 years ago
    hi thanks for the response, sorry i have only just logged on to see it

    im using a 910xt so i havent got a wheel setting, not that ive seen anyway. And ive not got a cadence sensor on my bike. I am riding in a group though so unless it is picking up data from another persons Ant stuff.

    so from your comment it looks as if the gps is recording correctly, as it is used by strava etc who have interprettedd the data ok.