Dan just having a look at the elevation issue - I forgot the Garmin 200 doesn’t use barometric readings so I guess there’s a few issues at play. Elevation drift over the length of ride and bad weather are definitely an factor.
I found this post on mtbr regarding this issue -
Yeah, I’m suspect of the elevation corrections of both sites.
"Here’s the recent 30mi ride I was talking about:
Running that same file through Topofusion’s Climbing Analysis yields the following table:
TopoFusion: 2430 ft
Straight GPS: 2463 ft
Straight DEM: 3205 ft
Maptech: 1004 ft
TopoUSA: 3360 ft
Training Center: 1577 ft
Custom Algorithm: 2430 ft "
I ran my GPX file through the same software and got the following results
TopoFusion: 6527 ft
Straight GPS: 9450 ft
Straight DEM: 20052 ft
Maptech: 11913 ft
TopoUSA: 22582 ft
Strava/Garmin: 6536 ft
Custom Algorithm: 6536 ft
So I guess the lesson here is don’t get hung up on elevation data. One good thing is that Topofusion software is quite nifty.