Understanding ClimbPro on the Edge - Updated for build 5.50

Looks like it was changed in 4.10, feel like providing an update?

The document should still be correct at 4.10 as nothing in ClimbPro changed from 3.55 (beta) to 4.10 public release.

If you do see any issues or have any questions please let me know.

In order for ClimbPro to work it needs to know the future elevation profile that you will be taking. If you load a course it can assume that this will be the profile that you will be following. If you are free riding it has no way of knowing which turns etc you will take.

Strava Segments are really a series of individual courses that the Edge loads when it finds you are near the start point of one.

Views of ClimbPro are possible. The infrastructure is there. There is an event message in the FIT activity file for the approach, start and end of a climb. Currently no one has made use of these events in their applications or web sites.

I saw this in action today, and I must say i really like this feature. Thanks for the write up.

How would you create a route using Strava route builder and use someone elses barometric elevation data?  Or is Strava route builder only needed if you want to do Strava segments at the same time as ClimbPro?  What application or how do you build a route using someone's ride file that contains barometric sensor data?  Wonder why or if strava doesn't have elevation data collected from all our devices that have barometeric sensors and do some math on ever climb by x number or people and get a very accurate approximation of the real elevation?

Great job aweatherall in this document! Now i can just fwd-it to my friends instead of trying to explain it(and focus on the beer after the ride)

Awesome guide!
Thanks a lot for your work!