This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Route planning elevation difference between Connect and Strava

Hi,

I'd love to stop using Strava and move entirely over to Garmin Connect but I can't.  The reason is simple - there is a noticeable elevation discrepancy between routes planned in Strava and the same routes planned in Connect.

For example, I have a route in Strava that shows the elevation gain to be 1580 ft, whereas Connect shows the same route as 1200 ft. I have another route in Strava that indicates an elevation gain of 2,500 ft which in Connect is shown as 1,700ft. 

I have ridden both routes and confirmed that the elevation gain shown in Strava is the correct one.

I appreciate the discrepancy is relatively minor, but it means I have no confidence using Connect to plan routes in unfamiliar areas.  

Has anyone else found this?  I expect the cause to be the underlying mapping data that Connect is using, but if Strava can get it right, surely Garmin can too?

Cheers,

Phil