Garmin Edge 500 Incorrect Elevation Spikes

paudie2005

Hi, does anyone have trouble with there garmin and incorrect elevation spikes? On my latest ride Garmin has me tracked as climbing over 100m in the space of 0.1 of a mile...fairly good going if it were true! You can see on the attached the incorrect spikes just before 5 and 10 miles. When I use the elevation correction it just gives a greater elevation gain which is way off. I have tried the garmin forums and garmin themselves but got nowhere, any pointers appreciated.

Thanks

Mugser

The barometric sensor it seems gives us extra elevation over the distance you can correct it on the garmin connect site in the page for the individual activity. (bottom left of the page) This does the elevations according to the maps instead. See pic.
But what I've been doing lately, cos the differences in elevations over a 100k spin with the club could have been twice the amount for me as compared to other club members, is uploading the activity directly from the device using the Strava website.

paudie2005

Mugser wrote: »

The barometric sensor it seems gives us extra elevation over the distance you can correct it on the garmin connect site in the page for the individual activity. (bottom left of the page) This does the elevations according to the maps instead. See pic.
But what I've been doing lately, cos the differences in elevations over a 100k spin with the club could have been twice the amount for me as compared to other club members, is uploading the activity directly from the device using the Strava website.

Thanks Pal,
Yeah I was using the elevation correction. When I use this lately its giving me a way higher elevation gain than club mates. Even the last short spin before elevation correction the elevation gain is 667m after correction 1474m, Strava picks it as 667m but thats been uploaded from the unit. Im pretty sure the 1474m is incorrect comparing it with other riders and the route, just strange that the correction is more incorrect, seen on garmin that the 500 doesn't need the use of the correction but would be dubious.

clog

I found that if I set an elevation point eg.(outside my house) and then let the garmin pick it up before I set off, that the readings from then on are less extreme. I wouldn't say it is perfect but fewer spikes.