I notice on my ride readings there's often a spike on speed, showing an average of 12-13 MPH and "top speed" of 120MPH+. Do you know what's causing this, or how to avoid? Thank you
120mph would mean a displacement of 53.6 metres per second, and even at an accuracy of within 15 metres for GPS location tracking, we still should not see that magnitude of error. I'd therefore guess that with whatever device and mode you're using, speed is being determined by cadence (and wheel size), so I'd check the cadence chart for the activity and see if you see a spike.
I don't ride, and I don't know which tracking device you're using, but on about one quarter or third of my runs, I'd get one or two recorded cadence value anomalies of ≥220 from my Forerunner 235 per workout – and not always when I'm running at speed, but sometimes just while I was walking part of the course.
I notice on my ride readings there's often a spike on speed, showing an average of 12-13 MPH and "top speed" of 120MPH+. Do you know what's causing this, or how to avoid? Thank you
It might help if you tell us a little more about your device and whether you're using a speed sensor attachment or GPS for the speed.
If you're using the GPS and you have a poor signal lock I'd imagine that inaccurate readings could show you a few dozen meters away from where you really are and appear to be moving between the inaccurate points at 120mph.
Strava from my experience ignores these data outliers - in heart rate at least, Garmin does not.
