Thanks Frank! now we can easily check it. It will be useful for flight plans/missions/tasks building.
In my case, since I want to convert other sims tasks to AFS4, it will help me check the feasibility even without opening the sim.
Hi Frank, thank you very much for that.
It also helps with the creation and revision of new airfields, to quickly check whether something is already available in FS 4.
From my point of view, the Aerofly FS Airport Code Validator is a good starting point for further development in which I, as the creator of airfields, would like this to be extended to airfields without ICAO code in the next step.
On the part of IPACS, I would like to be prepared not to use self-invented codes at such airfields, but to base them on existing databases, which are not perfect, but are nevertheless widespread.
I apply this order to the codes in my now more than 1200 airfields of all kinds built:
My experience is that if airfields do not have an ICAO code, they almost always occur in METAR & TAF and have an individual country-specific code there, which also almost always matches the code in OurAirports. Only in very few cases (e.g. special landings at huts in the Swiss Alps) may it be necessary to come up with a code yourself.
I will illustrate this with the example of the Teck airfield:
This example shows:
In this case I would choose DE-0986 (in FS 4 then DE0986) because I personally see METAR & TAF before OurAirports. But since the respective other codes are free in both systems, I could also decide differently. And of course it would also be helpful to standardise the two codes, which is feasible.
My experience is that if airfields do not have an ICAO code, they almost always occur in METAR & TAF and have an individual country-specific code there, which also almost always matches the code in OurAirports.
Currently around 1-2% of the airport codes of Aerofly FS cannot be resolved using the Ourairports DB. Using a solid pattern to identify airfields would improve the accuracy of external services like weather import or flight planning in outside tools.
The map of the Aerofly airports in the Missionsgerät cannot display airports which cannot be found in the Ourairports DB (because there is no other source for geo coordinates), so airports with made-up identifiers are invisible there. (If there is any interest in these airports I can supply the list of identifiers.)
In the FS 4 database ...
... the airfields listed below have easily recognisable no code that occurs either in OurAirports or in METAR&TAF.
