It does not necessary work as you would think as the model is very vague and this causes GPS elevation to be very vague
I already did the math, on the Pikes Peak ascent where you climb 7,815 ft…
I think the following post I found over in the F3HR forums does a good job summarizing why it doesn't matter for running...
Even for hiking, the efficacy is probably dubious due to trees and what not already bastardizing your GPS signal.
Glad to see the math. Thanks!
I think this could matter (a little) for navigation: if your paper map or marked trail signage tells you that a trail segment is x km to the next intersection, then using the wrong distance measure would throw off your navigation. If you have the map on your watch, I'm guessing it'll have any marked trail on it, so you could use watch GPS (and if you aren't using GPS due to battery or temperature, then maybe 3d distance doesn't work either? Or it could be altimeter-based? I haven't checked). So I guess useful to use the right setting on steep terrain if you didn't download the map...