In the listings, they are correct, but on the right they show up as what city they’re in instead of the name of the airport.
LaGuardia and JFK show as “Queens” when they’re actually “New York” and Newark shows as “Elizabeth” when it’s actually “Newark”.
The names above the ICAO codes are the cities that the airports are located in, not the name of the airport. Newark Airport, despite the name, is in Elizabeth, NJ. This is something that the editors add during the creation of the airport’s properties. It’s more productive and useful than only putting the airport’s name. For example, Chubu Centrair in Nagoya - Chubu is a massive region of Japan, and just putting “Chubu” wouldn’t provide any sort of assistance in finding the airport. Putting “Nagoya” is much more productive and easier to understand :)
Well then it’s very inconsistent.
Some have the name of the airport, like “Dulles”.
Some have the city that they’re referred to as but not actually located in, like “White Plains”. HPN is actually not in White Plains, rather split between North Castle, Rye Brook, and Purchase.
Others have the city they’re in, like “Queens.”
That’s wrong then. The field that needs to be filled says “city”, not “airport name”. I’d bring an issue like that directly to the editor of the airport.
It may be a little inconsistent since Airport editors set the city. However it is supposed to say the city that the airport is in.
Oh ok, understand Dulles.
But at the same time, I still think it’s ridiculous that EWR is referred to as Elizabeth when the cities literally border each other.
If the airport is far away from the city it’s referred to as, then I could see that. But when they border each other, not at all. EWR should be “Newark” and LGA/JFK should be “New York” (New York City borders Queens). Another one is BDL. In the game it’s “Hartford”, which is what city it’s referred to, but by your logic, it should be “Windsor Locks” since that’s where it’s located. Stupid, right?
What Pingu has said is exactly it. Up until now, names of cities in which Airports were located had no visible effect on the user end. I’ve brought this issue to the IFAET peeps, and further discussions will take place on how we can better manage adding and accurately depicting these field inputs.
Thank you for the report!
