as the data backend and being able to render the scenery at runtime would be fantastic. Having the OSM database, probably augmented with our scenemodels, elevation model, navdb, apt.dat, groundnet etc. Scenemodels and terrasync are going down. Single airport to generate the scenery for a specific airport. All airports in area generates all the airports within the boundaries as set on the start tab. If you can provide the above, are able to provide help, or have any serious ideas for a replacement, please get in touch via the forum topic or the mailing list topic Home-made airports: if you created an airport in WorldEditor, use the.
![flightgear kede airport scenery flightgear kede airport scenery](https://www.mediafire.com/convkey/14ad/a24dsc9idddd43e6g.jpg)
All Channel Islands (Jersey, Guernsey, Alderney, Sark, etc).
![flightgear kede airport scenery flightgear kede airport scenery](https://i.ytimg.com/vi/1UxpzXIeAsM/maxresdefault.jpg)
Warning - not for the low end computers I can barely run it myself. In other words, deriving an absolute minimal subset, basically: the geographic information that is required to match with the scenery airport layout, from the respective sources and store this in a 'traditional' file format that, as usual, allows every contributor to verify his contributions before submitting to some general repository. By the end of this year (2015), the FlightGear Project's hosting for the scenemodels database and website and the TerraSync repository will no longer be available. Various scenery packages (last update December 2020) I thought Id put all my own scenery packages into one post to avoid any extra threads, and can just keep updating this thread.