4,400
edits
(Created page with ''''Introduction to the Scenery/Airports folder and explanation by Martin, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17407.html original message] on d…') |
m (Robot: Cosmetic changes) |
||
Line 9: | Line 9: | ||
In other words, we're 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. | In other words, we're 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. | ||
Those entities we identified as overlapping between the visual representation of airfields in the Scenery and the respective data files in the Base Package are:< | Those entities we identified as overlapping between the visual representation of airfields in the Scenery and the respective data files in the Base Package are:<br /> | ||
1.) Threshold positions and orientation (typical startup positions),< | 1.) Threshold positions and orientation (typical startup positions),<br /> | ||
2.) ILS positions and orientation (apparently depends on runways),< | 2.) ILS positions and orientation (apparently depends on runways),<br /> | ||
3.) Taxiway ground network (we don't want AI airliners to taxi off the tarmac),< | 3.) Taxiway ground network (we don't want AI airliners to taxi off the tarmac),<br /> | ||
4.) Aircraft parking positions (to avoid airliners parking on the grass or inside the terminal building).< | 4.) Aircraft parking positions (to avoid airliners parking on the grass or inside the terminal building).<br /> | ||
We're storing this information in a couple of XML files in a newly created 'Airports/' directory alongside the well known 'Terrain/' and 'Objects/' directories. The new directory is being organized using sort | We're storing this information in a couple of XML files in a newly created 'Airports/' directory alongside the well known 'Terrain/' and 'Objects/' directories. The new directory is being organized using sort | ||
Line 22: | Line 22: | ||
'''For the transition periode a new property is introduced. Durks | '''For the transition periode a new property is introduced. Durks [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg25478.html original message] on devel-list.''' | ||
[...] | [...] | ||
Line 28: | Line 28: | ||
[Since FlightGear 2.0.0], you can choose which set of data to use, by changing the property ''/sim/use-custom-scenery-data''. | [Since FlightGear 2.0.0], you can choose which set of data to use, by changing the property ''/sim/use-custom-scenery-data''. | ||
Whenever this boolean property is set to ''false'', ground network data will be read from <code>AI/Airports/[ICAO]</code>, < | Whenever this boolean property is set to ''false'', ground network data will be read from <code>AI/Airports/[ICAO]</code>, <br />and when set to ''true'', it is read from <code>Scenery/Airports/[I]/[C]/[A]/[ICAO].groundnet.xml</code>. | ||
Currently, this property controls the following: | Currently, this property controls the following: | ||
* Reading of startup information: When set to "true", | * Reading of startup information: When set to "true", the runway dimension data in apt.dat are overwritten by those in the Scenery/Airports/[I]/[C]/[A], so that we have more flexibility in regenerating the terrain tiles without having to force the updated runway positions back into apt.dat. | ||
* Use of ground networks | * Use of ground networks | ||
* the runway use files. | * the runway use files. |