Originally Posted by
Seattle Forrest
No you don't need a bike computer for this at all. You can guess. Knowing your elevation relative to your starting and ending point is the most convenient way though.
It's only "convenient" in fairly unsual situations.
Originally Posted by
Seattle Forrest
You're confused about something really basic, so we'll use the example I posted earlier to see if you can understand. Riding over Washington Pass from the valley floor meant starting at approximately 2,100 feet and ending at approximately 5,500 feet. Again the climb has steep parts and not so steep parts so distance is less useful for pacing than just knowing your altitude.
You are still not getting that
this is not a typical case!
It is probably easier to use an elevation profile that it is to keep track of the elevation reading.
Originally Posted by
Seattle Forrest
If you're at 2,800 feet you've just started and better not be burning matches.
That you've just started is enough.
Originally Posted by
Seattle Forrest
You obviously don't have personal experience with big climbs on a bike but the concept is easy to grasp.
You obviously have no idea about my personal experiences.
Originally Posted by
Seattle Forrest
I've heard about a ride called the Six Gap Century in GA with lots of vert.
Rides like the Six Gap Century are a good example of why your technique of trying to keep track of elevation readings isn't anything anybody really would do.