Old 12-29-16 | 06:21 PM
  #17  
Heathpack's Avatar
Heathpack
Has a magic bike
 
Joined: Aug 2013
Posts: 12,590
Likes: 425
From: Los Angeles

Bikes: 2018 Scott Spark, 2015 Fuji Norcom Straight, 2014 BMC GF01, 2013 Trek Madone

Originally Posted by Sy Reene
It's not so much about "worrying" about it.. for me at least, it was just curiosity as to whether there is a simple and established best-practice that everyone should be doing to most closely capture elevation / climbing (ie. GPS correction or not).
Well I didn't claim you were worrying about it. It's just that I can't imagine why it would really matter to be "accurate" about it.

Distance, I can understand. I want to know when I'm getting close to the finish line in a TT. Or make the correct turn, if I'm trying to navigate a new area.

Power- that must be accurate and reliable, Im making training & racing decisions with that data.

Speed, I can understand. Maybe I've made and modification to the bike and I want to get a sense as to how it impacted speed.

Even temperature has some usefulness, because I can compare how I feel today when it's 47 degrees and it can help me decide how to dress tomorrow if its forecast to be 42 degrees.

But elevation gain? There's almost nothing I would do with that information that needs to be more accurate than 15% +/-. So I can't really see troubleshooting it or taking any steps to try to make that info more "accurate". Knowing that I deviate systematically from Ride with GPSs totals or my friends' Garmins is good enough.
Heathpack is offline  
Reply