Elevation completely wrong

Is that the corrected elevation from inside Garmin Connect? Do you have "Elev Corrections : Enabled"? If not, you should turn it on so that it's the garmin website that's calculating the elevation base on the route, not your watch using GPS. You wouldn't want any GPS-only watch doing elevation anyway; you need a barometric watch to get usable elevation readings for running. Based on your heart rate it sure looks like you were running hills though. Strava, endomondo, etc should all also post-calculate elevations from your route and ignore the GPS's measured elevations. Could be that garmin's site has crap for data for wherever it is that you're running? I know some hills here have poor data on Garmin and RunningAhead, but better measures on other sites.

The 235 uses GPS for elevation, and that's what's in the .fit file.

Garmin Connect applies "elevation correction" (by default) to devices that don't have a baro when you display the data, to show you MUCH better data in many cases.

If the .fit was passed on to endomondo and it doesn't correct for non-baro altitude, what you see there is the one that's wrong..

Just got my FR235, very happy with it until i looked at the elevation recorded for my two runs.
Basically they are not even close to reality, which surprises me a lot. I have the same runs uploaded to strava and endomondo where the elevation is displayed correctly.

I have uploaded a screenshop of the same run form endomondo and from garmin connect.

Anyone experiencing the same issue? And/or have any idea how to fix this?

yeah, i've noticed that Garmin Connect makes even some of my hilliest runs look almost pancake flat.
it looks much more impressive on the mobile app where a relatively flat run can have a profile that looks like the queen stage of the Tour de France.

its just the way the graph is set out with different intervals on the x and y axis that makes one look more impressive than the other but the data is exactly the same.

whenever i need an ego boost i look at my elevation profile on the mobile app

Thank you all for the replies.
Some clarifications:
- The data is automatically uploaded to endomondo and strava
- If you look at the endomondo you see that not only the curve is wrong, it is also the max/min elevation. Endomondo is defiantly not wrong here, It could be that it is not accurate, but it has the same max/min and curve as previous runs done on my 910xt, and besides this is a pure up/down a hill run. It is in other words not the visual effect, that is fooling me, but the actual numbers behind.
- Elevation correction enable/disable does not make any difference
- I have tested some other runs in the same area and are seeing the same thing; garmin express is not only inaccurate, it is completely off.
- I have testet with smart/1 sec as well as Glonass enabled without making any difference.

So am I understanding correctly that my watch is calculation evaluation for GC, and elevation correction should fix this (which apparently is not working as enabling/disabling makes no changes to the graph)?

I have the same problem. Elevation profile on Garmin Connect web-dashboard and Garmin Connect iPhone app is way off. It's wrong both with elevation correction activated and deactivated. When I export the run to Google Earth or Runkeeper elevation profile is correct.

The funny thing is if i create a course of the exact same route with the courses tool in Garmin Connect Dashboard, the elevation profile is correct.

I remembered that I also have automatic upload to Strava as well, and here the elevation is all good.

So for me elevation is shown completely wrong in Garmin Connect and Runkeeper (ref. above), but correctly at Strava.

What can be done to fix this?

- Elevation correction enable/disable does not make any difference

My guess is that Garmin's elevation correction information is not as complete as other places, though that is pretty baffling since garmin's entire business is maps....

My guess is that Garmin's elevation correction information is not as complete as other places, though that is pretty baffling since garmin's entire business is maps....

Another observation. When I disable elevation correction, the min/max elevation data for the run seems correct. However, the elevation graph does not change. I guess the elevation graph uses corrected elevation data by default, and is not affected by changing the elevation correction setting for the run.

When I step outside my house, GPS and every map source I've checked puts me at about 55-58m elevation. Garmin, with corrected elevation data, puts me at 170m.
To be fair I live at the foot of a small mountain, so if Garmin where to place their "corrected" elevation point about 500 meters from my house, 170m would be correct elevation.

Similar issue with Garmin 230: - Elevation discrepancies compared to other watches on the same route?