You are reading a single comment by @snoops and its replies.
Click here to read the full conversation.
snoops-
Thanks, that's where I'm at with it too - doesn't appear to be a fix.
Had a response from Wahoo, from which I gather this is a known issue. For the benefit of others this is their recommended fix:
"*Thanks for getting in touch.
At this time I don't have a concrete timeline I can quote for the release of the fix, but I can assure you that we plan on including it in an update soon.
In the meanwhile, I've linked your ticket to our developer ticket, which helps us track those who are being impacted by this issue.
In case you encounter this again before our fix is released, you can resolve the issue with the following workaround:- Stop rolling and save the ride recording
- Reboot the ROAM
- Page over to the MAPS screen, and wait until the "Acquiring GPS" message disappears
- Load your route again
- Press start, then start moving*"
- Stop rolling and save the ride recording
user20714
Thanks. I'm at peace that I definitely rode the climb (https://www.strava.com/segments/28880824) 84 times so have scratched the Everesting itch. Would be nice to be able to prove/share it though.
The data is weirdly inconsistent. The clearest view of the issue I have been able to show is on Garmin Connect, where you can see the last 6 laps missing the location data:
https://connect.garmin.com/modern/activity/7319090298
What's odd is that Garmin seems to overwrite the elevation recorded on the device to come up with a different total of 28,434ft.
It's all totally arbitrary and there doesn't seem to be a huge amount of point stressing about inaccuracies between different GPS recording devices, but on the other hand #ifitsnotonstrava...