Anyone know how TR assigns elevation gain?
Seems to be a consistent and considerable difference between the two platforms (Garmin and TR) cheers
I can’t remember all the terminology to insert here but I do know that different GPS and mapping systems interpret topology in different ways. It’s not an exact and consistent science out there among various platforms (surprise surprise!)
Some account for things like bridges and others don’t. In the case of crossing a bridge for example you would see less elevation than if the map assumed you went all the way down to the valley floor and back up rather than just across the bridge. Not sure that applies here but just throwing that out there as a possible contributing factor.
1 Like
Thanks, there were other various related posts so I guess I should have checked first but good to see I wasn’t the only person experiencing this
ya, I ran into this very thing when planning a long trip in ridewithgps. There was crazy discrepancies between RWGPS and Strava and I had to research to find out why. With a 60lb bike it really matters if the route has 9800ft of elevation or 12000!
1 Like
It is kind of interesting though that TR is recalculating rather than just taking what Garmin feeds in