XSG-12051
Incorrect Airport ID in Global Scenery latest POST airport ICAO code change
Closed
Scenery bug report
Reported by:
T_McTry
on June 8, 2021 6:47 PM
Assigned to:
Julian Lockwood
Reported by:
T_McTry
on June 8, 2021 6:47 PM
Assigned to:
Julian Lockwood
Jan Vogel June 9, 2021 11:21 AM
The ICAO code in the meta data was changed, but this airport is not yet included with the latest distribution. Also (see the bug report about Harare) 3rd party avionics need to read the meta data for ICAO, not the airport ID (it will never change!).
T_McTry June 10, 2021 12:04 AM
Fair comment about dev's needing to address ICAO ID...but why shouldn't X Plane also reflect up to date Airport ID coding too, and not outdated data.
Jan Vogel June 10, 2021 7:25 AM
That is a long story, I try the nutshell: The XPlane scenery system needs a unique ID to tie airports to a certain spot on the ground (so you avoid having two airports shown at the same spot if you have multiple versions like a custom one and the global airport one). This is the airport ID. Unfortunately, what is now the “airport ID” used to be the only ID for airports, so some legacy navigational apps (like the ones you mentioned) still read this by default. Also some airports dont have the meta data ICAO (or FAA) YET - so in this case the navigational app needs to “fall back” to the airport ID (because it is likely right).
T_McTry June 12, 2021 4:46 PM
I hear you @Jan Vogel, and thank you for replying.
Still think it is messy...but given there is a workaround, I guess I will have to live using that option