startgrid, developer of the most excellent game Endless ATC (also on Steam and Android) has recently added the ability to import custom airports as well as provided about 3000 raw airport configuration files. They're not intended as ready-to-play airports, but more as a starting point to create a new airport file. The files in this collection are automatically composed out of free databases, and the quality and completeness may differ per file. In any case, the files are not finished, so you'll have to add more properties (like SIDs and runway configurations) yourself. Best practice would be to pick one airport you would like to work on from the collection, copy that file to the game, and start expanding it, bit by bit, with more data. You can also start from scratch, googling all data and properties yourself.
Use a text editor, together with the included example.txt file as a guide, to create a working file in the locations folder of the game. The example file is pretty big, but most of the properties in it are only optional. In theory, just a runway and an airport code is enough data to create a minimal, playable file. You can always decide to add more detail later. First thing to do is to make sure the '#code = ' item in the [airport1] section is un-commented to make the airport appear in-game at the bottom of the airport menu. So just remove the # at the beginning of that line. Carefully put each item in the correct section, in the same format as the example. Start the game every now and then to make sure it still works as expected.
- Open an issue describing the work you want to do (or want done, but it will be faster if you participate!)
- Create your feature branch:
git checkout -b my-new-feature - Commit your changes:
git commit -am 'Add some feature' - Push to the branch:
git push origin my-new-feature - Submit a pull request :D
- All files that have been customized should be placed in the final folder.
- The directory structure below that follows ISO 3166-3 naming conventions in continent/country
- The file should have the four character ICAO code
- "Fantasy" or other airports that cannot be placed in this structure should go into final/custom For example, Zurich airport is placed in final/EU/CHE/LSZH.txt. Los Angeles is placed in final/US/CA/KLAX.txt
It is highly encourage to remove the first seven lines of comments, since we are no longer using an "automatically generated airport file" at this point. Is it encouraged to cite any references that you used while creating your file, including the airchart, airliner data, and even airport website. If you wish to include personal information (such as your contact information), this is allowed, although not necessary.
TODO: Write license