What about Gradient Lag?

Think it’s a datafield, not an app.

I think it’s only taken from the route data in the ClimbPro / elevation profile because it’s likely to be more accurate. Measuring altitude with barometer (which is vulnerable to temperature and air pressure changes) or GPS (which is fantastic in the horizontal plane at 90° to the satellites, but rubbish in the vertical plane. Cruise missiles don’t use GPS to tell them how high above the terrain they are) isn’t great. But not for the elevation data field. Think that does use the barometric altimeter.

I could be wrong.

Nice video but I don't understand what's its purpose. How is it related to the gradient lag issue?

Just to clarify as a number of different topics crossed in this thread.

The elevation profile shown when following a course or when using power guide, where the Edge shows your progression along that profile uses the elevation data from the course.

The elevation data recorded in the activity comes from the barometric sensor.

Gradient is computed using the barometric data as input to the calculation.

@Michael_Kalina

I'm wondering if something might be wrong with your unit. Have you tried cleaning the barometric port.

Place the Edge in warm water for around 5 minutes. Gentle swish it around then stand it upright with the USB port open to allow it to drain and dry.

@Michael_Kalina :

at the same time @aweatherall wrote his posting, I was writing to Michale: something is wrong with your device.
My Edge 1040 lags elevation display, too - but faaaaar less than your device!

I have researched, Elevation lag is a common issue for all *30 and *40 edges
But for fenix and epix it is totally fine and they give brilliant performance in terms of elevation

Good to know - for Fenix watch owners. 

Sucks - for Edge model xx30 and xx40 owners.

Where are you Garmin-Matthew, Garmin-Blake and/or all other Garmin-xxx…s?