Did a 6 mile hike over a modest mountain peak and used ClimbPro on a course created with GCM (hike activity type). ClimbPro made some strange choices about how to break up the course, IMO. The major gain from base to summit was 1600' not including any small up-and-downhill segments, which brought the total gain to about 1900'. Climbpro chose to split this up into 3 climbs. #1 @ 1568 feet over 2.3 miles, #2 @ 46 feet over 0.13 mi, and #3 @ 107' over 0.27 mi.
You can see the locations of these climbs in the screen below
The choices made by ClimbPro don't make a lot of sense to me. Climbs #2 and #3 are very short distances and very minor elevation gains. The grade might be relevant for a cyclist or a runner, but given how short they are, likely not. 46' of gain might qualify as a hill in Tampa or NYC, but in the context of a ~1900 ft gain hike, it's nothing.
We should be able to set thresholds for grade and total gain so that ClimbPro won't arbitrarily break the course up into tiny climbs. Ideally we could also manually subdivide the course into climbs by waypoints or something, but even a basic ability to set climb generation parameters (minimum absolute gain/distance/grade or minimum % gain of total course) would be a major improvement. In this example, it might have been nice to split the 1st climb up into 2 climbs by average grade, then not generate the original #2 and #3 at all. At the very least, climb #2 should not have been there.
The "no more climbs" screen would be more useful if it contained better information about descents - i.e. "DescentPro", because lots of courses have equal climbs and descents and the descents are very relevant. A cyclist is definitely going to want to know about descents, but a runner/hiker/etc may also care if there's a significant downhill section coming up. Having a beautiful course elevation profile seems like a waste if it doesn't show relevant data once you've done the uphill sections. On a hike like this one (and MOST mountain hikes), the last 50% of the course is descent!
The distance at the bottom of the navigation/elevation screen should have both total distance AND distance remaining, or distance covered AND distance remaining. There's plenty of screen real estate and it doesn't make sense not to show more information. Since it shows ascent done (green up arrow) and ascent remaining (blue up arrow) it should probably also show descent remaining. If you add distance completed and distance remaining it's even more like a terrain-shaped progress bar of the course.
These would be great to have on F6X and I bet there is still enough room on the 240/260px displays
