![]() |
Garmin Edge 1000 Elevation Error
Anyone know how to improve the accuracy of the accumulated elevation gain on my Garmin Edge 1000? I know a variety of algorithms are used in different devices, but my Garmin seems to consistently be about 30% low.
Thanks, Mark W |
Originally Posted by Mark W
(Post 18658865)
Anyone know how to improve the accuracy of the accumulated elevation gain on my Garmin Edge 1000? I know a variety of algorithms are used in different devices, but my Garmin seems to consistently be about 30% low.
Thanks, Mark W |
Compared to other riders on the same ride--my garmin consistently registers less elevation gain. Today's ride had a moderate change of temperature (45 to 75 deg), but a friend on the same ride recorded 3412 ft of gain compared to my 2592. He uses a similar garmin 1000.
|
Originally Posted by Mark W
(Post 18658942)
Compared to other riders on the same ride--my garmin consistently registers less elevation gain. Today's ride had a moderate change of temperature (45 to 75 deg), but a friend on the same ride recorded 3412 ft of gain compared to my 2592. He uses a similar garmin 1000.
|
Using the Garmin Connect correction, it changed my elevation gain by 6 ft, so not much difference.
|
I'm guessing the 1000 has the ability to input known elevation points? My 500 does. You can find the location of the NGS Benchmarks and input precise elevation points into the Garmin (find the point on the website, , or the better-than-nothing option, use the What is my elevation website to put in your approximate elevation. This helped quite a bit with my 500, as I found that on out and back routes, I was always descending markedly less than I was climbing or vice-versa.
|
Originally Posted by spdntrxi
(Post 18658969)
there is a function to enable elevation correction in garmin connect.. try it and see what happens. Maybe you buddy is enabling it or vice versa
|
Originally Posted by DrIsotope
(Post 18661106)
I'm guessing the 1000 has the ability to input known elevation points?
|
Originally Posted by njkayaker
(Post 18661421)
That correction in Gamin connect is intended for devices without barometers.
|
Originally Posted by Looigi
(Post 18661907)
Not true. Pressure altimeters in Garmin units are subject to drift. What altitude correction does is adjusts the altimeter's data by matching it up to topographic data in the website's map database along the route. You might see this on a ride where you return to where you started and the raw data shows different elevations at the start and end of the ride. Applying correction will remove this error.
It really exists for units which only use GPS for elevation (which is inaccurate). There is no indication that it's useful for "drift" at all. If drift was a general problem and the correction was useful in fixing it, it would not be off by default (it would be on by default). People are naively thinking that something called a "correction" is always good. In this case, it makes the GPS data better and the barometeric data worse. Understanding Sport Device GPS Elevation Issues | DC Rainmaker Note that Garmin Connect will automatically set the elevation correction to ‘Disabled’ for devices that have barometric altimeters, such as the Edge 500: In general, if you want the most accurate elevation data you can get, you’re going to have to go with the Edge 500 or Edge 705 devices. But if you want portability and versatility, you’re probably better off sticking with the Forerunner line and then correcting the elevation later on the computer. |
I found this pretty interesting.
GPS Elevation Accuracy Test: Smartphone Apps vs. Dedicated GPS | Singletracks Mountain Bike News |
My out-and-back yesterday resulted in a net elevation change of 10 ft, and that was most likely due to the fact I didn't start my watch until a few seconds into the ride.
I have the forerunner 910xt with a barometer. (No elevation correction.) I did notice that it was reading 80 feet higher than one of the signs at the top of one of the peaks, but that could have been just a high pressure system blowing in. https://connect.garmin.com/modern/activity/1111162267 Have you looked up what the elevation change SHOULD have been for that ride using an actual map? |
Originally Posted by njkayaker
(Post 18662028)
There is no indication that it's useful for "drift" at all.
Do you realize your link is six years old??? For best results it recommends using out of date hardware that isn't being made anymore. :rolleyes: |
When I did Washington Pass from Mazama, my Garmin Fenix 3 watch recorded 3,369 feet of elevation gain. According to the best topo maps, the correct value is 3,374 feet.
EDIT: My Edge 800 recorded 3,358 feet. Both are pretty impressive but the watch did a slightly better job than the cyclocomputer. Which is consistent with my experience with both devices. On that particular day, you would expect a barometeric altimeter to slightly underestimate elevation gain due to the temperature. |
Originally Posted by Seattle Forrest
(Post 18662733)
You shouldn't give advice on things you don't understand.
Do you realize your link is six years old??? For best results it recommends using out of date hardware that isn't being made anymore. :rolleyes: That information still applies. It's still disabled for devices without barometers. Do you realize that you should find a newer link that says people should use it? |
My Garmin Touring (no barometer) generally shows about 20% less total elevation than I get when I upload the same ride to ridewithgps. Don't know which is accurate, maybe neither.
|
Originally Posted by njkayaker
(Post 18661421)
That correction in Gamin connect is intended for devices without barometers.
I hope you're capable of understanding the distinction. |
| All times are GMT -6. The time now is 05:39 AM. |
Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.