Why doesn't heart data adjust to changes in altitude

[SteveCar]

Given that Fitbit has my location data, why doesn't it take account of altitude and adjust heart data to reflect changes in altitude. Over the holidays I was in higher altitudes, between 4500 and 8000 feet above sea level (up from 1200 ft where I live). Fitbit app kept telling my my resting heart rate was high, blood oxy was low, readiness was low, etc. However, this is simply an effect of being at a high altitude. Why doesn't the programming reflect this change due to altitude?

[MakMak]

Hi, @SteveCar! I'm guessing that would be a pretty complicated change, since it would have to track your location all the time, figure out where you typically live and what the altitude is, then correlate that to where you are and what the change is. I've seen people complain about it going the other way, too, when they're from somewhere like Colorado and visiting the coast. I'd say it's more of a point of interest and move on, although you're welcome to add the suggestion to the Product Feedback forum.

[LZeeW]

Hi @SteveCar!  I'm a physiologist and those are real changes, not an effect.  Physiologists use oxygen partial pressure when describing altitude physiology.  Effective percent oxygen makes more sense in everyday conversation.  Air is 20.9% oxygen at sea level.  Your effective oxygen percent is 17.3% at 4500 ft and 15.4% at 8000 ft.  Your Fitbit was telling you the truth.

[SteveCar]

• Sorry @LZeeW  that I was unclear. I knew that these physiology changes were real and that the Fitbit device was accurately measuring those changes. It was pretty interesting to see them change. I just wish the programming would take account of the data it has about location (and therefore some general idea of the altitude) when interpreting that data for daily readiness, cardio fitness, etc. I did just move on and continue my activity (rock climbing) @MakMak, but I will consider the product suggestion idea. Thank you.