This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Elevation incorrect

Since a few months the elevation of recorded activities on my Forerunner 255 is often way off (and I think that messes up other metrics as well). I often record 100m of climbing and 150 meter descending on a 5k run on totally flat terrain.

I don't think it's hardware related, because my watch reads the correct elevation when I calibrate the altimeter. For example: I calibrate with the Run-widget already opened, using the GPS. It reads 5-7m which is pretty accurate. In the recorded actitvity you see the elevation drop to ridiculous numbers like -70m (yes, the Netherlands are below sea level, but not that much).

Some examples:
https://connect.garmin.com/modern/activity/13045802958

https://connect.garmin.com/modern/activity/12942179303

The issue occurs since a few FW updates ago, I'm on the most currect version now 17.26.

Is this a known issue? Any solutions?

0 ovekvam over 1 year ago

The pressure based altimeter is less accurate in very windy conditions. Also make sure the sensor holes are not clogged.

0 RobinFM over 1 year ago in reply to ovekvam

Thank you for your answer. As far as I can see the sensor holes are clean. With a 'less accurate' altimeter I would expect random elevation readings, but all my recorded runs have the same pattern. Correct values for the first 5-10 minutes and then the elevation drops to ridiculous readings. This behavior is pretty predictable, that wouldn't be the case if it was dependent on the wind, I think? And until a few updates ago the issue wasn't there.

0 ovekvam over 1 year ago in reply to RobinFM

No, wind will typically give quite random noise. It is most noticeable on the floor count.

0 1313667 11 months ago

I have exactly the same. Were you able to resolve this?

0 1313667 11 months ago

I have exactly the same. Were you able to resolve this?

0 RobinFM 11 months ago in reply to 1313667

Well, yes and no... ;)

I contacted Garmin support and they replaced my watch with a new (refurbished actually) one.

It's several months since the swap and unfortunately I'm noticing some weird elevation readings again sometimes.