I upload my garmin 810 data and normally the elevation correction was set to disable, just notices that recent uploads came with elevation corrections enabled. I Tried to disable without success. Is any correction that I should apply?
Edge 200 don't have barometric altimeter, wich is inaccurate, but the difference is very small, because I test it with a friend of mine who owns a edge 500. When I've set the elevation correction to off, it shows me the elevation that my GPS actually acquires when I ride, with the normal error of edge 200, that I know that error is minimal, but now the elevation isn't the number I've in my GPS data. I've always wanted to be off, and show me the number that are in my GPS has, but with this changes of Garmin Connect the numbers aren't equal.
The button now changes between enabled and disabled, just a shame the values are wrong. I commute similar rides each day so have a general idea of the elevation gain, plus RideWithGPS still works fine, so I know the elevation data being displayed is incorrect by some considerable margin. Almost two months still not fixed something that worked perfectly fine for years. Maybe Garmin could try testing software releases before releasing them.
^ BSRU can you put some data up? Screenshots or files. So much of the elevation data is not Garmin's. I agree that a GC web site bug that wasn't fixed for so many weeks is unacceptable, but there are so many variables with elevation data that I'd want to analyse it before blaming Garmin software.
I have been riding the same/similar rides for three years, logging them to Garmin and know it is a Garmin software fault as now the so called "corrected" elevation data is lower than the "uncorrected" data. I also log all my rides onto RideWithGPS and they "correct" the elevation data correctly, as expected from experience. Before the error arrived in February the elevation gain on Garmin Connect and RideWithGPS were virtually identical.
This issue of not being able to disable/enable elevation correction should now be working correctly. For devices with a barometric altimeter, it should be disabled by default.
BSRU - If you could post some examples of the inaccuracies that you are seeing on GC vs RidewithGPS that would be helpful (images, links, GC activity IDs, etc.).
I have a Garmin 800 and elevation correction was enabled by default on this mornings ride. All my logged rides on GC and RWG are set to private. Information from a ride last Friday. GC elevation correction disabled, 1051m(similar to the reading shown on my Garmin) GC elevation correction enabled, 972m RWG, after elevation correction, 1120m
BSRU - The 1051 is what was measured by the device (as you know). When elevation correcting is enabled, GC ignores data reported by the device (for elevation) and displays elevation data based on underlying TOPO data. My suspicion is that RWG is using a slightly different source for TOPO data, which accounts for the discrepency (972 vs 1120).
It is definitely not yet okay. I am able to toggle between enabled and disabled, but the numbers are wrong. I have uploaded a tour this morning directly from my Edge 510 with the iPhone app. In Garmin Connect, the corrections were enabled and i had to disable it manually, which is very annoying. It should be disabled by default.
But now to the elevation gain numbers of this tour: Garmin Edge 510 = 163m Garmin Connect with corrections enabled = 132m Garmin Connect with corrections disabled = 186m
Garmin Connect with corrections disabled should show the same elevation gain as the display of the Edge 510.
Yet again with this mornings ride, GC is not correcting the elevation correctly. By default it is "enabled". Garmin 800 device stated 358m gain. Without correction, GC stated 345m of gain. With correction GC stated 358m of gain. Yet with RideWithGPS, Before correction, 358m of gain, After correction 434m of gain.
How can GC be correct if the gain when correction is enabled is the same as stated on the device.
It's been like this since the beginning of February, it is shocking that they broke it in the first instance but still almost two months later no fix available is very poor.
BSRU - The 1051 is what was measured by the device (as you know). When elevation correcting is enabled, GC ignores data reported by the device (for elevation) and displays elevation data based on underlying TOPO data. My suspicion is that RWG is using a slightly different source for TOPO data, which accounts for the discrepency (972 vs 1120).
That would be plausible except that I have about three years of previous experience of the elevation correction feature working correctly, before the maintenance in early February.
