Earlier quoted context omitted.
Strava also shares the latitude/elevation during the run. (Screenshot in case you dont have Strava https://imgur.com/PuuKo5r ) What I find interesting and don't really understand is why the elevation keeps going down during the run, even though he stayed on the same track. Anyone have an idea why that could be?
The elevation in this case is just a proxy for storing the barometric pressure, which is because the actual air pressure is the important thing to track if you are trying to normalize against athletic performance. If the watch logged the GPS altitude, it would be a lot more accurate, but less useful as the air density would only be estimated..
This is why most portals like Strava run a data correction by overriding the elevation data of the GPS track by tracing the path over their internal elevation model.
The barometric elevation calculation is usually much more accurate and is constantly calibrated on the watch. This breaks down a little if you run for over 24 hours and the weather changes a lot. The drift over the 24 hours of this run amounts to about 8m over 2 hours, which doesn't really matter. And while air pressure can be used to normalize performance of the athletes, the absolute values measured by the barometer are usually pretty inaccurate, while the relative changes are quite accurate. Therefore, they can be used to measure climb/descent, but not really for an absolute air density measurement.
Source: I have worked on a GPS wearable (without barometric pressure sensor).