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?
This is a known error and started sometime between 3 and 5 Feb probably during the GC maintenance shutdown. I have an Edge 510 with exactly the same issue.
However: I reckon it might be a button display issue. Make a note of your elevation gain, click Disabled and see if the gain changes. I reckon that mine actually defaults to Disabled even though it says Enabled, based on the shape of my regular commute (the local survey data are incorrect on part of a climb).
When I repeatedly click Disabled it toggles between Enabled and Disabled.
Same issue here. The worst is that I rode a 28 miles flat route and garmin connect says I had 11,000 elevation gain. Unable to contact support to report it: http://connect.garmin.com/activity/445792277
As to the 11,000 foot elevation gain, those kind of things usually happen on devices that have not had sufficient time to establish the gps altitude and more correctly calibrate the barometric sensor. There is a small gap at the start of your data that suggests the timer was started before a gps signal had been established.
Some still have such issues even when giving significant time after getting the satellite lock. This may be alleviated by enabling autopause, setting up elevation points for the start of your rides and then before you begin moving, start the timer and autopause should immediately kick in to pause it, then when it gives you the message elevation point found, start your ride.
As to the elevation corrections on the GC website, BALDRYK seems to be correct. For me, at least, the buttons are functioning and after the screen refreshes, my elevation data does reflect the change, but the button highlighting does not reflect the change. The problem becomes, after a few times remembering what it's actually showing.
It's not a big deal for me, but for those of you it is a big deal for, you should be emailing or calling Garmin Support. Posting here does not ensure Garmin gets the message. For the most part this is a user forum, all the active mods I see are volunteers with no connection to Garmin.
edit..... okay I guess I'm wrong about the gap at the start of the data..... mine has that too and I know my edge has been started and lock established for at least 3 to 5 minutes. So I am wrong for suggesting the timer may have been started before the gps lock established.
As to the 11,000 foot elevation gain, those kind of things usually happen on devices that have not had sufficient time to establish the gps altitude and more correctly calibrate the barometric sensor. There is a small gap at the start of your data that suggests the timer was started before a gps signal had been established.
edit..... okay I guess I'm wrong about the gap at the start of the data..... mine has that too and I know my edge has been started and lock established for at least 3 to 5 minutes. So I am wrong for suggesting the timer may have been started before the gps lock established.
Yep I always wait the GPS acquired msg before starting my ride.
Anyway to fix that data ? You can see in the graph the elevation is always show around 0, so not sure where it is getting this 11,000 ft elevation.
oh I see that, in the first seconds.. probably it is. It never happened before.
You have a 4800m spike at the start of your ride. (ETA you can see this by expanding the elevation graph.) Could be a gps establishing issue?
In Strava they have a option to fix gps and it is ok now, but on Garmin Connect I can't find any option to fix the bad elevation data.I will need to edit it and change to 0 manually.
Actually, a crop option for the start and end of the ride, as you can do with strava, would be useful. Maybe I'll stick in a new feature request. (I assume that the feature is not there at the moment and I just haven't found it.)
Above are some GC displays. Left: As initially recorded (279m) Centre: Clicking on Elevation Corrections Disabled (349m) Right: Clicking on Elevation Corrections Disabled again (284m)
Strava: 284m Strava elevation gain on one long segment: 294m (ie strava must be using my 510 not its own data for the ride gain of 284m) ridewithgps.com (based on gpx export from GC): 308m
Actually, a crop option for the start and end of the ride, as you can do with strava, would be useful. Maybe I'll stick in a new feature request. (I assume that the feature is not there at the moment and I just haven't found it.)
