Dynamic airport generation
The Dynamic Airport Generation system (DAG) is a graphic-engine system used to generate airport models from a database. The database may be updated dynamically, independent of the terrain on which the airports sit.
This system can integrate with OpenFlight terrains given certain modifications or with the Global world system without modifictions.
This system is introduced from SIMbox version 5.6.1. It is also available through certain hotfixes for SIMbox version 5.6.
Contents
Architecture
Loading mechanism
The system constantly checks for airports around displayed areas. Once a camera moves close enough to an airport (between 20-25 km by default) the system generates the airport model. The airport model is then displayed and saved to a cache for faster reloads in the future. The cache itself is deleted if either the terrain or airport database change.
Geometry generation
The DAG system supports the generation of various elements in the airfield. These include runways, taxi lines, pavement markings, taxi and runway lights, slope indicators and various approach light systems. The system does not support airport signs or structures.
Database source
The DAG system relies on an access database for its information. The data in this database is mostly derived from X-Plane airport files (version 850). The X-Plane data is a freely available data which is in itself produced from a variety of sources as well as community contributers.
DAG setup
Terrain generation
The dynamic airport generation system requires that the area in which the airports exist will be completely flat. The terrains using the DAG system need to be generated to include that data.
Simigon can provide a shapefile that defines these flattened areas. Contact support (support@simigon.com) to request this file.
DAG configuration
Enabling the DAG system is done on a per-terrain basis. The DAG is turned off by default. The setting can be configured through the Terrain Optimization Tool (TOT) which Simigon provides.
In certain situations you may be required to block some of the airports from being produced by the DAG system. For example, when your terrain already includes specific airport models. To block specific airports from being generated dynamically by the DAG, add a file to the terrain directory called "GISGeneration.cfg". Then add the following lines to the file:
[Airport Generation]
{ICAO 1} = False
{ICAO 2} = False
{ICAO 3} = False
...
replace the {ICAO #} with the ICAO of the airport you need to block.
Editing airport information
SimiGon's database is used to generate dynamically-generated airports as produced from the X-Plane data format (Version 850).
SimiGon does not provide an X-Plane data editor. However there are several editors available for free that you can download from the web. The most highly recommended editor is the world editor 1.0 (WED), available here.
If you intend to use this tool please consult the World editor (X-Plane) page.
Integration of user content
As mentioned in the section above, the data is imported from a textual format into a relational database. In case a specific airfield is missing some details, you may use an external tool that produces a data file with the same format that X-Plane uses. Once you edited and exported the specific airfield (or airfields) into a data file (typically .DAT), you may merge it into the existing database. Merging is a process that involves removing the existing airfield information and importing the new dataset from the file you created.
Use the command-line tool found under the BIN folder with the following format:
NavAidsDataImporter.exe merge <database full path> apt:<data file full path>
For example, if the database is under C:\Program Files\SimiGon\Sitec\Resource\GIS RunTime DB\Nav.mdb
and the data file is under C:\Program Files\SimiGon\Sitec\Resource\GIS RunTime DB\Source\Overrides\MyAirfields.dat
NavAidsDataImporter.exe merge " C:\Program Files\SimiGon\Sitec\Resource\GIS RunTime DB\Nav.mdb" apt:"C:\Program Files\SimiGon\Sitec\Resource\GIS RunTime DB\Source\Overrides\MyAirfields.dat"