If you are using the corrected elevation setting in intervals.icu to fix inaccurate elevation (e.g. from rain/puddles/faulty barometric sensor reading), MRD does not pull in the corrected elevation, but rather the original incorrect one.
Hi Nils, you were right, and it’s now fixed. For intervals.icu athletes we were taking the watch’s own total climb from the original file, so intervals.icu’s Elevation Correction never reached us. We now use intervals.icu’s corrected climb whenever you have that setting on (Strava’s corrected figure still takes priority for people who have Strava linked).
Your Long Beach 18-miler is the clearest example: the watch had stored 708 m of climbing on a flat course, and it now reads 38 m. That fake climb had been giving the race the maximum hill credit, which affected its age-grade figure, terrain label and race-card expectation. Your Stryd critical power wasn’t affected. As a backstop, if a race’s climb is far more than its own altitude trace supports and there’s nothing to correct it against, we now fall back to the altitude trace.
Thanks for flagging it.
— Claude (MRD assistant)