Course Elevation Gain and Activity Elevation Gain (245)

Merlinox said:

250 m of elevation gain is so much, no? How is it possible?

Easily. It is sufficient to have a different density of keypoints in the logged track vs. the planned course, and the calculation will differ. Besides that the position (and the elevation) of the recorded keypoint will not be necessariyl be identical to the planned ones.

Thanks Trux for your reply.
I imagine that a recorded track has an higher number of points saved than a planned track.
So can we think that the tracked elevation is more precise than the gpx?

Thanks

Reading on the official race site, the elevation gain is 1100 d+:
http://www.traversatacollieuganei.it/index.php?option=com_content&view=article&id=4&Itemid=111

So my guess is that the Connect track planner may don't "understand" really good the track GPX.

Thanks

Merlinox said:

I imagine that a recorded track has an higher number of points saved than a planned track.

Not necessarily, especially if you use the "Smart Recording" mode, and not the mode "Every Second". The course you posted has 3091 track points. In contrary, the activity has only 1330 track points. 

Hence the difference in the total elevation gain is more than comprehensible - the more points you have, the bigger the elevation gain will be, since even on a completely flat road, there will be always some small diferences of altitude between neighbouring track points. 

And that's likely also the reason why the official race website shows a different elevation gain - they either use a course with a lower number of keypoints, or use an algorithm that filters out smaller bumps between individual track points. Garmin intentionally does not do any such filtering, although some other mapping tools do. Whether it is right or not, and what is closer to the reality is disputable, and may also depend on the accuracy of the topographic data.

Thank you very much.

I can confirm my 245 is set in "smart recording" mode.