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

Auto Correction Inaccuracy?

Ok, so I have a route that is only 4.7 miles and I have done it 6 times this year. It involves 1 big hill and a small one as well as a few ups and downs in the road. As I use the Edge 200 I choose to use Garmin's "Auto Correction" Service.

So, can anyone explain why on such a small route that my elevation is sometimes 5 metres out when strava's service gets them all within a foot - and that's probably accurate depending on how much I sway in the road. I know it's not much now but on longer rides it's pretty frustrating that it can't give me a simple accurate answer when they made the product I purchased from them. 5 metres is a long way off for a 15 - 17 minute ride. (30 - 35 metres) Depending on how much they feel like trolling me. :confused::confused::confused:
  • Are you talking about the elevation that Garmin Connect says after you upload your activitiy to it?

    The most consistent elevation data will always be when the elevation data comes only from a map. Once you start throwing GPS calculations for elevation into the mix you will see disparity.

    Strava might exclusively be using the topo data from a map. Garmin Connect might be using a blend of topo data and gps data. I don't know. But any altitude derived from GPS will have deviation from one moment to the other.
  • Thanks for the relpy.

    But to be honest this isn't really what my question was going to be... Originally I had elevation data off for some and on for others - but I thought it was on for all of them... So I had to edit what I wrote and it's kind of pointless now but still. An extra post is an extra...... post? All I need to do is get the elevation from Strava. Thanks for the answer though, at least I'm not the only one.