When I start course, Edge shows Remaing ascent 50%higher than is true value. As I am riding through couse, Remaing Ascent is slowly lowered that I end up with correct total ascent an zero remaing. I have courses created mostly in Basecamp, transfered to Edge 1030 manualy (newfiles), some from GC and sent to device, but always with same results. Does anybody have function Ascent remaing working correctly?
Where is the course coming from? There is currently a bug in Garmin Connect that is over inflating the elevation gain when exporting a GC authored course to the Edge. This issue is not an Edge side issue, but rather a problem with the data it is getting from GC.
Sometimes the coursed are created on the Garmin website, sometimes Strava. Most recently I did the Highlands Gran Fondo in New Jersey. The advertised climb was 7500 ft, the Ascent Remaining initiated at 24,000 ft, and the Garmin calculated 8400 ft at the end of the event.
Ascent remaining works okay with ridewithgps routes. I upload the rwgps .fit files directly to the Newfiles folder.
It's only as accurate as the rwgps data, which can be somewhat wrong at times. Especially with routes that have lots of short, rolling hills. It's hard to get the exact elevation data for all these tiny hills. The recorded total elevation for the ride is often 5-10% higher than the route estimate.
If only rwgps would update their elevation data, can't they fine tune it from their uploaded ride data? It's excellent on some nearby roads, way less accurate in other areas near me.
Still, total ascent and ascent remaining is pretty close, and I find they are useful numbers to look at.
