Forum:Global and regional issues/The two systems of airport codes

From OpenGeofiction
Revision as of 03:35, 28 December 2021 by Alessa (talk | contribs) (Archiving and prompting continuing discussion)
Jump to navigation Jump to search
ForumsGlobal and regional issues → Global and regional issues/The two systems of airport codes


Since we're starting afresh with the new wiki, one of the things I would like to bring up is the two systems of airport codes that we have (WAAT and ANACA). I understand that in the real world we have IATA and ICAO that both have listings of codes (not to mention internal codes used in larger jurisdictions like France, Russia, and the US). Looking at the history of how these codes developed, my feeling is that it happened more through bureaucratic means with a small intent to create regional divisions. My feeling is that, for much of what we do, the systems are basically redundant. Yes, I recognize that their usages in the real world are slightly distinct, but this is only because organizations have kept them that way. They didn't have to evolve into distinct entities.

Do we really need to copy the real-world parallel here? I'm open to ideas as to why we could or should, but I'm wondering if a four-letter system based on regionality (as an example) might have developed naturally early on. The three-letter code grants us over 17,000 options globally; doing a four-letter code grants those 17,000 options for each region. This means we're unlikely to run out anytime soon on either system.

Thus, my proposal is two-fold: if there is a desire for a regionally-oriented airport code, then we should default to the four-letter code altogether; if there is not, then we default to the three-letter code. I personally don't care which way we go, but I don't believe it is necessary to have two systems in place.

Thanks, everyone for your feedback! If there's a consensus starting to form below, we'll proceed accordingly. — Alessa (talk) 17:35, 23 November 2021 (UTC)

UPDATE (27 December 2021): The community has voted to use three-letter codes for commercial airports. This does not affect general aviation airports, military airports, or any further decisions about integration with rail or other modes of transport. (The previous discussion is logged on the talk page.)

Continuing discussion

I would like to continue the discussion about how we should handle airport codes but break them up into two larger conversations. — Alessa (talk) 03:35, 28 December 2021 (UTC)

General aviation and other airports

One idea that has come about was to use some type of designator with numerals to mark general aviation airports (e.g. 2GK). I wonder how much we would need to micromanage GA airports in general. I can't imagine a 2GK code in the eastern FSA impacting even a potential 2GK being used in Mecyna. General aviation airports generally don't have the range that other airfields. Thoughts? — Alessa (talk) 03:35, 28 December 2021 (UTC)

Multimodal integration

Let's also continue the discussion about integration with other modes of transport, such as using the previous suggested XLCX for HSR access at LCX. Thoughts? — Alessa (talk) 03:35, 28 December 2021 (UTC)