110m ascent... on a flat track

Turn off auto-calibration during the activity. Set it to calibrate at the start of the activity. And while you’re acquiring a GPS signal, wait an extra minute or two before starting the activity. That should fix this issue.

Mhm: 10.000m:400m= 25 laps. 110m:25= 4,4m/lap. I really don´t know, but I think this is normal and within tolerance (?).

Perhaps someone else can share a 400m lap course to compare the ascent?

Volker said:

4,4m/lap. I really don´t know, but I think this is normal

No, this is not normal. That's almost two floors climbed per lap!!! Where I live it's really flat. When I run in the streets I usually get 10-20 m elevation gain per 10 km. When I run on a stadium track I get near zero elevation gain per lap on average.

I am curious about that Altitude correction you speak of. How do one do it?

M

Hi,
there is a small icon in Garmin Connect web, on the activity page, on the right - just below the watch picture. What it does is, as far as I am aware, replace the altimeter / barometer data from your watch by the elevation change based on your GPS track.

Thanks!

I think it uses digital map elevation, not your GPS

If you look in to your elevation graph there are a lot of spikes, they shouldn't be there, that causes the problem. There is a thread or two about this problem and the culprit could be due to sweat in baro holes.

However this shouldn't be the case since in the other threads in the first 20 min the behaviour was the expected one.

There are also a lot of spikes in the HR graph and in the pace. 

What kind of sensors are you using? 

Look at my multiple posts about spikes in elevation profile...

I had to sold the Fenix 6X after one year of claims with Garmin without any feedback. They replaced twice the gps in warranty and had always the same... they didn’t care about analyzing the issue, they just replaced w/o caring of the customer.

i think is a design flaw with sweat pushed into the baro holes, as I documented. All useless, no answers from Garmin. I got a rid of the brand going back to Suunto, much more reliable products bug free, and not testing products with customers on the market.

I am aware of the "spikes" issue, I think it's different here, more related to auto calibration during activity. What is weird is that the wrong elevation (more or less 4 meters) is always the same at every lap, at the same place, so I believe the calibration uses wrong DEM data.
The HR and pace graphs are pretty accurate, I'm using a HRM dual strap for HR and a stryd for pace, so no issue for me on that side.