He definitely should’ve done a couple of extra laps.
It sounds like he’s not too stressed.
I’ve got stand alone GPS with high res maps and I wouldn’t trust that to be accurate enough with elevation. It could be interesting to compare that elevation data compared to my head unit though.
I think it could be a better solution to take elevation readings at two points without any GPS obstructions and then base the laps on the difference.
On our Saturday group rides, most people are running Garmins, I run a Wahoo. Among 10 riders, there are no duplicates in elevation gained. I can’t put too much stock in the accuracy of the head units as a result.
without violating any NDAs let me just say make sure your Garmin device gets good airflow. Expect Wahoos to record a little lower elevation gain. If you want to record maximum elevation consider a garmin 510.
But if 10 riders ride the same hill 30 Saturdays in a year, it’s not unreasonable to expect that the mean of all those barometric tracks would be quite close to the actual gain on a particular segment.
Wow, just watched this. Amazing. I`m planning to ride the route this summer/autumn following the GB Duro route but avoiding the towns. Certainly don’t want to go into Manchester!
Looks like he was way ahead of the rest of the field
I`ll let you know.
It may be next year now, Unless I find time in September, but I also do motorsport so may not get time.
If I do it , I will do it to enjoy, not do crazy long hours
And CyclingTips / Hells 500 have confirmed. They were also apparently incredibly careful with the elevation this time:
Ahead of Morton’s second attempt, Hells 500 verified the new segment using highly accurate LiDAR data and expertise from the co-founder of OpenTopography, Chris Crosby. Strava marks the segment as gaining 189 m, but the data show it actually gains 190 m per lap, which means Morton needed 46.57 laps to hit the height of Everest.