View Single Post
  #2  
Old 11-13-2023, 04:21 PM
Varrattu's Avatar
Varrattu Varrattu is offline
Approved Member
 
Join Date: Feb 2011
Posts: 171
Default

In my first post, I made a little oversight there. I mistakenly referred to the return value of the field <Parameter(part.ParameterTypes.Z_AltitudeMSL> as "Pressure Altitude." As a matter of fact, the quantity of geometric altitude (Z) is given to facilitate the computation of, for example, distance between or height of objects.

So, the value (Z)=5000m needs to be translated into the corresponding geopotential altitude (H)=4996m.

The good news: this doesn't significantly alter the result of my calculation example...
__________________
Windows 10 Pro 64-bit
Intel Core i7-8700K CPU @ 3.70GHz
2x4gb DDR3-1600
GeForce GTX 970 4095 MB
Logitech G35 Headset
Logitech G940 Flight System (fw 1.42)
Mad Catz Strike7 Keyboard
Headtracker DIY 6DOF & OpenTrack 2.3.10
Reply With Quote