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

Question about how Garmin calculates elevation gain.

Everything I've read about this suggesgts that running watches use the barometric sensor inside the watch to detect elevation changes. So I have two main things to say about this.

First, it seems incomprehensible to me that a sensor that tiny can detect the pressure changes involved in changing elevation by a few feet. But okay, if it can it can. But what about hyperlocal variations in pressure? For example, anyone who has run in a forest knows you sometimes run through spots where the air is much cooler for whatever reason, and there, the pressure is likely to be higher - how does the watch not register a sudden drop in elevation?

More broadly, there are at least two other ways Garmin could get elevation change: topographical data, and accelerometer data. As far as I know there is detailed topo data for almost everywhere in the world, or at least everywhere in Europe and North America. Why not use it? Re accelerometer data, if accelerometers can sense things as granular as running dynamics, surely they can also sense elevation changes.

I would love to know why Garmin relies solely on barometric pressure for this instead of using all available sources of data (barometric, topo maps, and accelerometer) and then algorithmically interpolating.

  • Here's a link to a Garmin page that answers some of your questions (i.e. the Digital Elevation Map (DEM) is used to calibrate the barometric altimeter, and you can choose when):

    support.garmin.com/.../

  • As far as I know there is detailed topo data for almost everywhere in the world

    There is. But Garmin at least used to have pretty bad DEM data in some parts of the world. If you create course on Garmin Connect Web, it always elevation corrected with Garmin's DEM and you can't block/disable that. If the DEM Garmin have in your region then your courses elevation is bad aaaand that then again breaks all the nice PacePro stuff.

    Haven't looked into this for some time as it was bad and Garmin didn't mind that and they didn't seem to have any plans to have better DEM or give options to not to break the elevation of courses imported and so on. If one really wanted proper elevations for the course it needed to be done somewhere else and then imported manually directly to the watch.

    So I would say, it's nice that Garmin doesn't rely to that bad data. YMMV.