FlightGear wiki - User contributions [en]

Howto:Using QGIS to process NLCD data

2022-02-05T17:35:12Z

Sfrsfr:

This tutorial will describe '''how to use data from the [https://www.usgs.gov/centers/eros/science/national-land-cover-database?qt-science_center_objects=0#qt-science_center_objects National Land Cover Database (NLCD)] to create US scenery''' that is on par with the existing European scenery.

The default scenery (World Scenery 2.0) in FlightGear is of higher quality in some areas than others. For example, European scenery is generally of very high quality due to the use of [https://land.copernicus.eu/pan-european/corine-land-cover CORINE land cover data]. Compared to the European scenery, the US scenery is much less detailed and less accurate. Thankfully, there is a wealth of freely-available geographical information for the US that can be used to improve the scenery.

== Getting set up for scenery generation ==
=== Prerequisites ===
Please read and understand the [[Using TerraGear|Using TerraGear wiki article]]. This tutorial will follow the same process but replace the "Landuse data" section with custom shapefiles generated from NLCD data.

=== Tools ===
This tutorial will make use of the following GIS software:
# QGIS (version 3.10)
# GRASS (version 7.8, used as a QGIS plugin)
# TerraGear

=== Elevation data ===
Elevation data for the entire world is available from the Shuttle Radar Topology Mission (SRTM). It is highly recommended to use the void-filled version of these datasets, which can be obtained from the [https://earthexplorer.usgs.gov/ USGS EarthExplorer] (note: it is required to create a login to download data from that page). The void-filled datasets reduce or eliminate the small gaps that can occur in scenery generated using the original SRTM datasets. The elevation data is in GeoTIFF format. To convert it to hgt format as expected by TerraGear, use gdal_translate as follows:

gdal_translate -of SRTMHGT input_file.tif output_file.hgt

For the output file, TerraGear might expect it to follow a certain naming convention, like N38W080.hgt. The data from USGS follows a naming convention like n38_w080_3arc_v2.tif. The following (sh/bash shell) script will batch convert all the files in the working directory following the expected naming convention:

for file in *.tif; do
base=$(echo $file | cut -f 1 -d '.')
NORTH=$(echo $base | cut -f 1 -d '_' | cut -f 2 -d 'n')
WEST=$(echo $base | cut -f 2 -d '_' | cut -f 2 -d 'w')
gdal_translate -of SRTMHGT $file N${NORTH}W${WEST}.hgt
done

== NLCD data ==
You can download the NLCD data [https://www.mrlc.gov/data?f%5B0%5D=category%3Aland%20cover here]. At the time of this writing, the latest dataset is from 2016. For the continental US, you should choose the dataset labeled "NLCD 2016 Land Cover (CONUS)." There is also a separate dataset for Alaska. The download is a large (>1 GB) zip file. After downloading, unzip the files.

=== Processing the data ===
* Fire up QGIS and select the WGS 84 template. If you don't have a template to choose from, don't worry about it, as we'll be setting the coordinate reference system for the project later. Just create a new project in that case.
* In the menu bar, select Project -> Properties -> CRS. Pick WGS 84 - EPSG:4326 as the project coordinate reference system.
<gallery>
49532654886 e94a32328d o.png|Setting the CRS
</gallery>
* Set a basemap. An easy way to do this is to double click on XYZ Tiles -> OpenStreetMap in the browser on the left. You can also get them via the QuickMapServices plugin.
* Browse to the location where you have unzipped the NLCD data in the QGIS project browser and double click the .img file to load it as a layer.
* Right-click on the NLCD layer -> Set CRS -> Set Layer CRS and select NAD83 / Conus Albers - EPSG:5070 -> Transformation 1. This will place the layer in the right location on top of the basemap. Note: it may not look like it's in the right spot until you zoom in on it.
<gallery>
49532655611 64dc27a6fd o.png|NLCD data loaded in QGIS
</gallery>
* Now we need to clip the data to the region of interest. The best way to do this is to by clicking the New Shapefile Layer button (see screenshot below). In the dialog, change Geometry type to Polygon and save it as a shapefile, and then click OK.
* Click the Toggle Editing button to edit the layer.
* Click the Add Polygon Feature button to create a polygon. Now you can click on the map to create a polygon covering the area of interest. When you are done, you can right-click to stop adding vertices.
* If you want to edit the vertex locations, you can click the Vertex Tool button, right-click on your polygon, and then edit the coordinates in the table on the bottom left of the GUI window.
* When you are done editing the layer, click the Save Layer Edits button (next to the Toggle Editing button).
'''Note''': when you are learning the process, start with a small polygon, say 1x1 degrees. Some of the steps take a very long time if processing very large sections of this data.
<gallery>
New layer.png|New shapefile layer
Shapefile dialog.png|Shapefile dialog
Toggle editing.png|Toggle editing
Add polygon.png|Add polygon
Vertex tool.png|Vertex tool
</gallery>
*Once the polygon is completed, the next step is to clip the NLCD layer using this polygon. Select the NLCD layer and choose Raster -> Extraction -> Clip Raster by Mask Layer. Make sure the input layer is your NLCD layer and the mask layer is the polygon you have created. For Source CRS choose the Conus Albers CRS of the original NLCD layer, and for Target CRS choose the Project CRS, EPSG:4326. Near the bottom of the dialog box, where under Clipped (mask) it says [Save to temporary file], click the button to the right and choose Save to File. Select IMG files as the filter and save it somewhere in your working directory with a descriptive name like NLCD_clip.img. Click Run. Once it completes, if you hide the original NLCD layer and the polygon, you should see the new clipped layer. As long as it worked correctly, you can now safely remove the big original NLCD layer. The image below shows a small sample section in Idaho that has been clipped using this method.
<gallery>
49532154383 b437eb21b7 o.png|Clipped NLCD data
</gallery>
*If you zoom in on the data, you will see that it is highly detailed but also pixelated due to the raster format. It needs to be simplified and smoothed out to look good in FlightGear and also to reduce the polygon count on the resulting shapefiles. We will first do some smoothing of the raster itself, and then we'll do additional smoothing after converting to vector format. In the Processing Toolbox, find GRASS -> r.neighbors. The clipped NLCD layer should be selected for both of the top input dropdowns. For Neighborhood Operation, select median with a Neighborhood size of 5. As before, you may want to choose an actual IMG file to save the output to instead of a temporary file. Click Run.
'''Note''': never use an averaging neighborhood operation, as the raster values are uniquely associated with a specific type of landcover. The averaging operation will introduce new values that do not correspond to a landcover type.
*Now we'll run r.neighbors once more on the resulting layer using the mode Neighborhood Operation with a Neighborhood of 3. The result should look a lot smoother and a bit less detailed than the original dataset (but still very highly detailed compared to the default scenery). An image from the sample dataset is below. This area shows McCall, Idaho and the south end of Payette Lake.
<gallery>
49539367447 cde1c6666a o.png|After r.neighbors operations
</gallery>
*We're now ready to convert the raster data to vector. In the Processing Toolbox, find Grass -> r.to.vect. Choose the output layer from the last step (median neighbors filter), choose area as the feature type, and check the option "Smooth corners of area features." This will make the output vector a little less pixely than the input. As before, you may want to save to a real shapefile instead of a temporary one. Click Run. This step will take longer than any of the previous ones to process.
*We could use this vector data as is, but it's still a bit blocky and unnatural looking. Instead, we'll do a couple processing steps on the vector data. GRASS -> v.generalize. Choose the default douglas algorithm with a tolerance of 0.0003 (this is in degrees, since our CRS is in degrees). You may want to play around with different values of tolerance until you find something that works best. Click Run. If errors result, it will create a new layer, which can be deleted. '''Note''': this step will take a very long time for large areas.
*Now we'll use v.generalize one more to smooth the simplified layer. This time, choose the chaiken algorithm with the same tolerance. Click Run. '''Note''': this step will take a very long time for large areas.
<gallery>
Vectorized.png|Vectorized NLCD data
Simplified.png|Simplified NLCD data
Smoothed.png|Smoothed NLCD data
</gallery>
*At this point, it is a good idea to compare the smoothed vector layer to the original NLCD raster data and make sure the smoothing steps have not introduced too much error in the shape of coastlines and other features. If they have, you may need to redo some or all of the last several steps (r.neighbors, r.to.vect, and v.generalize) adjusting the number of neighbors and tolerance until you get satisfactory results. However, I've found these parameters to produce quite good results.
*We now have a high-resolution vectorized dataset that can be used to define landclasses in FlightGear. We just need to save individual shape files representing each landclass. At this point, it is a good idea to have the NLCD map with the legend displayed to match to values in the shapefiles. That map can be found here:
https://www.mrlc.gov/viewer/
*You will also want to have default_priorities.txt from your TerraGear installation open to map NLCD landclass types to available materials in FlightGear. Some artistic license is possible here, but I use this mapping:
{| class="wikitable"
|-
! NLCD Value !! Legend label !! FlightGear material
|-
| 11 || Open Water || Lake or Ocean
|-
| 12 || Perennial Ice/Snow || SnowCover or Glacier
|-
| 21 || Developed, Open Space || Greenspace
|-
| 22 || Developed, Low Intensity || Town
|-
| 23 || Developed, Medium Intensity || SubUrban
|-
| 24 || Developed, High Intensity || Urban
|-
| 31 || Barren Land (Rock/Sand/Clay) || Rock or Sand (depends on location)
|-
| 32 || Unconsolidated Shore || Sand
|-
| 41 || Deciduous Forest || DeciduousForest
|-
| 42 || Evergreen Forest || EvergreenForest
|-
| 43 || Mixed Forest || MixedForest
|-
| 51,52 || Dwarf Scrub/Shrub/Scrub || Scrub
|-
| 71 || Grasslands/Herbaceous || Grassland
|-
| 72-74 || Herbaceous/Moss/Lichens (AK only) || I haven't used these, so check default_priorities.txt if you find them in your data
|-
| 81 || Pasture/Hay || DryCrop
|-
| 82 || Cultivated Crops || IrrCrop
|-
| 90 || Woody Wetlands || Marsh
|-
| 95 || Emergent Herbaceous Wetlands || Bog
|}
*To actually select and export individual shapefiles for each type, do the following:
**Select the final smoothed vector data layer. Click the Deselect Features from All Layers button near the top middle of the QGIS toolbar. Then click the button right next to it, Select Features by Value. In the dialog, enter the number from the NLCD legend in the value field, make sure the filter says Equal to (=), and then click Select Features and Close. Alternatively, if you want to combine multiple NLCD values into a single output shapefile, rather than clicking Close, you could enter in another value and then choose Add to Current Selection in the dropdown next to Select Features.
**Once you have the desired features selected, right click on the smoothed vector layer, click Export -> Save Selected Features As, choose the ESRI shapefile format, and save it somewhere under the project directory with a name corresponding to the appropriate area type in default_priorities.txt (e.g. data/shapefiles/Lake.shp). For CRS, choose the project CRS EPSG:4326 - WGS 84.
**Repeat this process until you've gone over all the values in the NLCD data legend. When finished, you should have individual layers representing different area types covering the entire area of interest. The result for the sample area is shown in the image below.
<gallery>
Nlcd shapefiles.jpg|Shapefiles from NLCD data
</gallery>

=== Converting with ogr-decode ===

If you have saved the shapefiles with a name corresponding to a material in default_priorities.txt, then they can be batch-converted with ogr-decode as follows:

# work and shapefiles directories
WORK=./work
DATADIR=./data/shapefiles/NLCD
# Process landcover
for file in $DATADIR/*.shp; do
fname=$(basename $file)
area_type=$(echo $fname | cut -f 1 -d '.')
if [ -d $WORK/$area_type ]; then
rm -rf $WORK/$area_type
fi
ogr-decode --area-type $area_type work/$area_type $file
done

(The script above is a bash/sh script for Linux. Something similar could probably done with a .bat script on Windows. The locations of the work and data directories will need to be edited if you use a different directory structure.)

=== Building with tg-construct ===

The final step in building the terrain is to run tg-construct. This process is described in the [[Using TerraGear|Using TerraGear wiki article]]. This should be done after adding an supplementary shapefiles, as described in the next section. When running tg-construct, you will want to use the '''--ignore-landmass''' flag so that lakes and other waterbodies are not assumed to be at sea level.

== Supplementary data ==

You will probably want to supplement your custom scenery with some other data. Sources include:

* National Hydrography Data for waterways and waterbodies. Though NLCD includes water landcover, it is not as accurate or complete as NHD, and the smoothing process described above will cause thin rivers to turn into "islands." I recommend using the NHDArea and NHDWaterbody datasets but skipping the line data. The data is in shapefile format, which can be viewed and manipulated with QGIS. Be sure to filter the data to remove extraneous elements. It includes things like marshes, dams, and intermittent streams that probably should not be included. The NHD data can be accessed here: [https://www.usgs.gov/core-science-systems/ngp/national-hydrography/access-national-hydrography-products Access National Hydrography Products]. To filter the data, you will want to refer to this page: [https://nhd.usgs.gov/userGuide/Robohelpfiles/NHD_User_Guide/Feature_Catalog/Hydrography_Dataset/Complete_FCode_List.htm NHD FCodes].

* [https://www.openstreetmap.org OpenStreetMap] for roads. QGIS can open .osm and .pbf files extracted from OpenStreetMap and edit them just like all the other datasets that have been discussed here. These can be "baked into" the terrain using TerraGear, or you can use:

* [https://osm2city.readthedocs.io/en/latest/index.html osm2city], an autogen tool for FlightGear that creates buildings, roads, bridges, pylons, docks, and other details from OpenStreetMap data. This tool has a bit of a learning curve and does not flow through QGIS, but it can really make your project shine.

== Sample results ==
<gallery>
McCall, Idaho, default WS 2.0 scenery.png|McCall, Idaho with default WS2.0 scenery
McCall, Idaho custom scenery.png|McCall, Idaho with NLCD + osm2city scenery
Cape Cod.png|Cape Cod with NLCD and osm2city
Laurel Bed Lake.png|Laurel Bed Lake in western Virginia
Ec135-manhattan.jpg|EC135 near Central Park in Manhattan, New York
C182s-atlantic-city.jpg|Cessna 182S over Atlantic City, New Jersey
</gallery>

== Available scenery using NLCD data ==

* Pennsylvania, New Jersey, and New York City by montagdude: [https://github.com/montagdude/FGScenery-PA_NJ_NYC project page], [https://forum.flightgear.org/viewtopic.php?f=5&t=38041 forum topic]
* Virginia, Maryland, Delaware, and the District of Columbia by montagdude: [https://github.com/montagdude/FGScenery-VA_MD_DE project page], [https://forum.flightgear.org/viewtopic.php?f=5&t=37322 forum topic]
* Rhode Island and Southeastern Massachusetts by montagdude: [https://github.com/montagdude/FGScenery-RIandSEMass project page], [https://forum.flightgear.org/viewtopic.php?f=5&t=36977 forum topic]
* Kansas and Ohio scenery by wlbragg: [[User:Wlbragg]]
* Tennessee scenery by xDraconian: [[US-Tennessee_Custom_Scenery]], [https://forum.flightgear.org/viewtopic.php?f=5&t=35521 forum topic]

== Related content ==
=== Forum topic ===
* {{forum link|t=36913|title=How to create US scenery with NLCD land cover data and QGIS}}

[[Category:TerraGear]]
[[Category:Scenery enhancement]]

Howto:Use TerraGear without wanting to kill yourself

2022-02-05T17:32:12Z

Sfrsfr:

My aim was to go through this whole process successfully with as little manual labour (don’t have the knowledge to go fine tuning in QGIS? no problem! neither did I) as possible. "Automation ftw" has been my perspective entering this endeavour.

Special thanks to some brilliant lads who walked these roads long before I did, for helping me discover the way! Shoutout [[User:Fahim Dalvi|Fahim]], [[User:D-ECHO|D-ECHO]], and [[User:Legoboyvdlp|legoboyvdlp]], among several others (you know who you are) – in fact, big up the whole FG community.

Hopefully, some of you will find this guide helpful – though at the time of writing, it appears that TerraGear is on the verge of becoming obsolete any minute now. So, if nothing else, it can serve as a time capsule of sorts – a way of recollecting how this task used to be done. Cheers! –– [[User:IskenderWang|IskenderWang]] ([[User talk:IskenderWang|talk]])

== Directory structure ==

Inside your working directory for TerraGear you will simply need three subdirectories – one for your starting '''data''' which you will process as necessary, one for the '''work''' that the TG tools will achieve which provides it with the actual recipe for constructing your scenery, and one for the '''output''' or end product after running tg-construct (the final step) to generate your terrain. My directory structure in the midst of generating several sceneries was looking as pictured.

[[File:TG directory structure.png|thumb|right|A directory format one could expect to utilize while working with TG]]

As you can see, what I like to do is compartmentalise the various sceneries I’ve created/aim to create in their own subdirectories in ''/data'' so to prevent any confusion and easily keep them separate them as I use the TG tools. Since you’re generating terrain one at a time though, I’d strongly recommend clearing out your ''/work'' directory completely in between each.

== Gather all the necessary starting data ==

The materials you will need to embark on your TG journey are:
# '''Elevation data''': Numerous sources for that but the best option will probably still be [http://viewfinderpanoramas.org/dem3.html viewfinderpanorama].
# '''All the airports in the area you aim to build''': Best to use some tool like [[TerraMaster]] for this, but keep in mind that Docker TG (even running terragear:latest) seems to only support up to XP apt.dat version 1100 – it unfortunately won’t work with 1130 which is the version most of the latest and greatest airports on [https://gateway.x-plane.com the gateway] will come with, whereas if you compiled the latest TG you should be all good in this respect.
# '''[https://osmdata.openstreetmap.de/download/land-polygons-complete-4326.zip World landmass polygon]''': This is great since it serves as your base layer and also has very accurate coastlines.
# '''Shapefiles''': This is where things get interesting, there are numerous sources one can defer to. In the past, people mainly relied on vmap0 and there was a nice mapserver that made it easy to acquire. Nowadays, the mapserver’s gone by the looks of it. Today, while you can still choose [https://gis-lab.info/qa/vmap0-eng.html vmap0], far better options exist for most areas nowadays thanks to the availability of [https://download.geofabrik.de OSM shapefiles] (solid option almost anywhere these days) as well as [[Coordination of Information on the Environment|CORINE]] (Europe), [[Howto:Using QGIS to process NLCD data|NLCD]] (U.S.), and [[User:D-ECHO/Canada Land Cover|LCC]] (Canada), though these others can be a bit less straightforward to obtain and work with – thankfully, if you’d like to try them out there’s documentation for all of those supplied by some top blokes in the FG community.

== Process your elevation data ==

When you unpack your elevation data, make sure to somehow place ALL the hgt files you intend to use in the relevant folder for the scenery in question, with no subdirectories dividing them – using <code>mv</code> and the wildcard to move all the contents of the needed folders from VFP to where they belonged worked just fine for me; quick and efficient.

For only this step, you could use this command: <code>docker run -i -v ~/terragear-work:/terragear-work/ -t flightgear/terragear:ws20 /bin/bash</code>

Since this is guaranteed to not have buggy elevation tools, so it’s really your call – you could do it just in case, especially if you’re working exclusively with Docker.

for f in ${PWD}/data/SRTM-3/scenery-in-question/*.hgt; do hgtchop 3 "${f}" "${PWD}/work/SRTM-3"; done
terrafit work/SRTM-3

Now for everything else: <code>docker run -i -v ~/terragear-work:/terragear-work/ -t flightgear/terragear:latest /bin/bash</code>

== Process your airports ==

Once you’ve collected all your airports from the gateway and you’re confident that they’ll work with genapts (perhaps through trial and error) you can just place all the zips in a burner directory and create an airports directory inside of that – then if you have zsh you can simply run my script here in the command line:

#!/bin/zsh
for file in *.zip
do
FILENAME=$( echo $file | sed s/.zip// )
ICAO=$( echo $file | sed s/_Scenery_Pack.zip// )
unzip $file
cd $FILENAME/"Earth nav data"
mv apt.dat ../../airports/$ICAO.dat
cd ../..
trash $FILENAME
done
trash ./*zip

and there you have it – all your .dat’s are there and sorted correctly by ICAO, which you can then transfer to your TG ''/data/airports'' folder.

Another way which is even better in a perfect world is to cut out the middleman by using the [https://github.com/mherweg/d-laser-fgtools dlaser tools], however this will always fetch the latest ones, which may not work for you if you’re using Docker TG.

Either way, this step may or may not be cumbersome depending on the amount of ''.dat'' files you’ll need, which can often include not just airports and airfields but also other things such as helipads – for instance, my Hong Kong scenery needed only 5 in total, while 12 tiles of scenery for Florida required 177 (!!) rasclart .dat files, which meant that using the ''gateway_pull.py'' script was a must (you'll need to run it through Python 2 though).

Then, once you’re ready, simply run this command:

for i in ./data/airports/scenery-in-question/*.dat; do genapts850 --threads --input=$i --work=./work --dem-path=SRTM-3; done

== Determine your bounding box coordinates ==

You may have already done this step in the very beginning, but if not, now would be a good time.
'''Think of the corners as bottom left, upper right, longitude BEFORE latitude.'''

In my case, for the Hong Kong scenery, the relevant coordinates were <code>113 21</code> and <code>115 23</code>.

== Crop your shapefiles ==

Before we dive more deeply into shapefiles, an important thing to mention is that while the .shp files will be the “stars of the show” in a sense, many of the other files it will come with are also NECESSARY! This means you should not try to delete files that may have seemed redundant to the uninitiated (i.e. me, at that point), and that if you’re going to move shapefiles between directories you’ll have to copy/move ALL of the ones that you will need which come in a set (by having the same filename, just different extensions). After all, most of those other files are there for a good reason, and not just to provide alternative options for GIS users as I had initially assumed. This had me stumped for a little while, wondering why this next tool wasn’t working and almost concerned that I wouldn’t be able to advance beyond this step, UNTIL I came across [https://gis.stackexchange.com/questions/262505/python-cant-read-shapefile/262509 this post on Stack Exchange] and it all made sense, so big up Michael Stimson as well for the helpful answer.

Something to note so that you don’t have to make that same mistake :) First, make sure you're inside ''/data/shapefiles'' (run a quick <code>cd</code> if not). Then, we simply run:

ogr2ogr -clipsrc 113 21 115 23 hk.shp land_polygons.shp

and so on for ALL the others as well – you can even use colons to run them all in one go, as I did. Be patient, though, because if your initial region & shapefiles are large then it can take longer than you may have expected at first.

== Split your shapefiles ==

At this point, you can put your cropped project shapefiles in their own directory and then delete or keep the full shapefiles depending on if you intend to use them again or not – that said, you should probably keep the land polygons (default) shapefile for future use since it can act as the base for the whole world, but for your cropped landmass shapefile for THIS scenery you can make a separate directory. I called mine simply “landmass” and now it may look something like what you see in the screenshot.

[[File:Shapefiles folder.png|thumb|center|The directory for shapefiles and how it could look at the extraction/splitting step]]

Here is Fahim's wonderful script, which allows us to perform this step:

#!/bin/bash
# Check arguments
if [ $# -lt 2 ]; then
echo "Usage: bash extract_features_shapefile.sh <path-to-shapefile> <path-to-output-dir>"
exit
fi
src_shp=$1
dest_dir=$2
# Extract available feature list in supplied shapefile
echo "Extracting available features..."
feature_list=$(ogrinfo -al $src_shp | grep 'fclass (String)' | tr -s ' ' | cut -d' ' -f5 | sort | uniq)
echo "Found following features:"
for feat in ${feature_list}; do
echo $feat
done
# Create shapefile per feature from supplied shapefile
echo "Creating new shapefiles..."
mkdir -p $dest_dir
for feat in ${feature_list}; do
echo "Processing $feat..."
mkdir -p $dest_dir/osm_$feat
ogr2ogr -where "FCLASS LIKE '"$feat"'" $dest_dir/osm_$feat/osm_$feat.shp $src_shp
done

Now you can use it on each of your shapefiles in the project directory, like this:

bash extract_features_shapefile.sh hk/gis_osm_landuse_a_free_1-hk.shp .

and so on.

This step prepares us to translate each of the specific types of land classes we need to the FlightGear format, as defined by Material definitions, while also deciding which ones to prune – bear in mind that many of these we can (and should) exclude because leaving them in the final recipe would add too much complexity.

== Map and decode your shapefiles ==

Once you reach this stage, you may now have a shit-ton of directories – that was certainly the case for me, as the screenshot illustrates.

[[File:Shapefiles split.png|thumb|center|Oh my, that seems like a lot]]

Not to fear – the light at the end of this tunnel is in sight already. Now we have to do something called [[OSM to materials mapping|mapping]], which is basically the translation I mentioned earlier, and then run ALL these inputs through the TG tool called ogr-decode.

This step can be time-consuming: deciding what to exclude [from the decoding step], and how to map the landclasses you do include.
You don’t need expertise in QGIS by any means – however, it can certainly come in handy with helping you view all your split shapefiles by importing them in and then tinkering with the layer visibilities to decide on what you don’t need/would add too much complexity versus what is necessary, because remember, performance in FG is of the essence as well (always keep that in mind during this step).

[[File:QGIS example for TG 1.png|thumb|right|Obviously we'd never need all this, that's why we had further split up these shapefiles]]

'''BRO TIP''': I didn’t realise this myself at first as a n00b to the toolkit, but I was advised by legoboyvdlp that osm_unclassified actually includes numerous roads and isn’t as irrelevant as the name would suggest, in fact it’s better to include this and PRUNE osm_residential for improved performance.

[[File:QGIS example for TG 2.png|thumb|left|Here you can see a big difference, not to mention I also ended up pruning the selected osm_residential landclass]]

When you map, try to use more standard landclass names as much as possible since those cover mostly everything – unless you have something specific in mind (such as for a custom scenery with its own set of material definitions), try to avoid using any landclasses that aren’t even mentioned in the [https://sourceforge.net/p/flightgear/terragear/ci/next/tree/src/BuildTiles/Main/default_priorities.txt default priorities file].
That said, if you insist on using other landclasses for whatever reason, you can always create your custom priorities file and add your own landclasses to it, and then just tell tg-construct to use that instead.
We’ll likely be doing this in bulk, so it makes a ton of sense to create a script for this (shoutout to D-ECHO who I would say has championed this approach) and place it in the TOP level of the TG working directory (so it’s level with ''/data'', ''/work'', ''/output'').

Then, all the arguments will essentially follow this sort of format exactly:

ogr-decode --max-segment 500 --area-type Default work/Default data/shapefiles/landmass/
ogr-decode --max-segment 500 --line-width 12 --area-type Asphalt work/Asphalt data/shapefiles/osm_motorway/

and so on for ALL the other landclasses, hoping you’ve mapped it all correctly.
So once that’s set, you simply run the script:

./decode_osm_data.sh

(note: if you're doing it like this make sure it’s executable first, a quick <code>chmod +x</code> may come in handy – I like to do this here instead of invoking bash because when I was on Ubuntu in a zsh shell it may have been more efficient for it to simply work through the same shell, entirely up to your preference though)

== Generate your terrain ==

At long last! This step requires us to use the final utility in the TG workflow, <code>tg-construct</code>, and I like to use a modified version of D-ECHO’s script for this as well:

./tg-construct.sh

In my case, the one command I was truly running was as follows:

tg-construct --work-dir=./work --output-dir=./output/Terrain --min-lon=113 --max-lon=115 --min-lat=21 --max-lat=23 --threads=3 --priorities=/usr/local/share/TerraGear/default_priorities.txt AirportArea SRTM-3 AirportObj Default Ocean Hole Road-Motorway Road-Trunk Road-Residential Road-Primary Road-Secondary Road-Tertiary Road-Service Road-Pedestrian Road-Steps Road-Unclassified Airport Pond Lake DryLake Reservoir IntermittentLake IntermittentStream Watercourse Canal Cliffs Glacier PackIce PolarIce Ocean Estuary Urban SubUrban Town Fishing Construction Industrial Port Dump FloodLand Lagoon Bog Marsh SaltMarsh Sand Saline Littoral Dirt Rock Lava OpenMining BuiltUpCover Transport Cemetery DryCrop IrrCrop Rice MixedCrop Vineyard Bamboo Mangrove ComplexCrop NaturalCrop CropGrass CropWood AgroForest Olives GolfCourse Greenspace GrassCover Grassland ScrubCover Scrub ShrubGrassCover SavannaCover Orchard DeciduousForest DeciduousBroadCover EvergreenForest EvergreenBroadCover MixedForest RainForest BarrenCover HerbTundra Sclerophyllous Heath Burnt SnowCover Island Default Void Null Unknown River Freeway Road Asphalt Railroad Stream

When I changed computers, the only thing I had to alter here was the thread count and the path to the default priorities file.

Now just sit back n relax and enjoy everything, you feel me, because you know what’s about to happen.

[[File:TG success.png|thumb|Success]]

And have patience, because this could take a while! '''Seriously!!'''
For legoboyvdlp, Ireland took a whole week (nonstop!!) to generate! And even for a relatively small scale such as Hong Kong and some of the surrounding area, because the Pearl River Delta is rather dense and data-rich, it took me 24 hours on my 2017 Macbook Pro just for it to reach stage 2 (the second stage out of three, the last of which generates the BTG files), at which point it inexplicably killed the process! So I was left with no choice but to bring out the heavy artillery, and on my beefier rig (8 core CPU, running at 14 threads) at last I was able to complete the whole process in just about three hours (wow!) with Ubuntu in WSL, compiled from source using the download_and_compile script, followed by adding ''install/terragear/bin'' to my user <code>$PATH</code> (in .zshrc, for me) – this way, all the terragear tools can be called normally.

So you see, the quickness of this step will depend entirely on a) the processing power at your disposal and b) the size and richness of the scenery you aim to generate. It may fail along the way for reasons you don’t understand – that’s OK, as long as you know you followed the process correctly just try again and most likely, it should work after some time.

[[Category:TerraGear]]
[[Category:Scenery_enhancement]]

Suggested software

2022-02-05T15:37:23Z

Sfrsfr: /* Scenery and Airport Editing */

==== Frontends ====
* [[FlightGear Launch Control]], FGrun is a graphical frontend to run FlightGear Flight Simulator.
* [http://code.google.com/p/fgcomgui FGComGUI] [http://forum.flightgear.org/viewtopic.php?f=6&t=5746]
* [[Airport Diagram Generator]] [http://forum.flightgear.org/viewtopic.php?f=6&t=5377]
* [[TerraGear GUI]]
* [[TerraMaster]] Java software allows you to manage scenery downloads without TerraSync

==== Using FlightGear ====
* [[FlightGear Admin Wizard|FGAdmin]]
* [[FGCOM]]
* [[MPmap]]

==== Mapping Software ====
* [[Atlas]] ([http://atlas.sourceforge.net Atlas]) aims to produce and display high quality charts of the world for users of FlightGear, an open source flight simulator. This is achieved through two main parts: The map creator (simply called Map) and the Atlas viewer.
* [[Kelpie Flight Planner]]
* [[Airport Diagram Generator]]
* Flightgear Mapping ([http://rubyforge.org/projects/fgmap fgmapping]): Provide a real-time map of flight position in Flightgear. It is based on tiles from Openstreetmap, downloads them in the background, provides navigation aids and runways, allows setting of waypoints and tracks the flight.

==== Scenery and Airport Editing ====
* [[TerraGear]] ([http://www.terragear.org TerraGear]) is a collection of open source tools and rendering libraries which can transform publically available GIS data in 3d representations (i.e. 3d models or 3d maps) of the earth for use in real time rendering projects. TerraGear can import 3d data sets such as DEM terrain grids, 2d polygon data sets such as coastlines, city outlines, lake outlines, and 2d raster data sets such as the 1km NAOO land use/land cover data. It also has tools for generating realistic airports, runways, and lighting based on available FAA data. <
** See [[Building Terragear]] for a walkthrough on obtaining a working copy of the TerraGear tools, and [[Using Terragear]] for an outline of the scenery building process.
* [[FGAirports]] edit Airport groundnet files required for AI Traffic. A replacement for Taxidraw.
* [[Taxidraw]] ([http://taxidraw.sourceforge.net/ Taxidraw]) deprecated
* [[AirportEditor]] ([http://www.greghawkes.com/flightgear/tools/airporteditor.html AirportEditor]) a [[Java]]-based airport editor for FlightGear [http://www.mail-archive.com/flightgear-users@lists.sourceforge.net/msg06118.html]
* [[WorldEditor]]

=== General ===
* 7-zip
* [[Blender]]
* [[GIMP]] ('''G'''NU '''I'''mage '''M'''anipulation '''P'''rogram, The Gimp)
* [[Open Office]]

== See also ==
* [[FlightGear related projects]]

[[Category:Lists]]
[[Category:Software]]

Howto:Complete TerraGear example using docker

2022-01-29T16:38:55Z

Sfrsfr: /* Process Airport Data */ added missing '.dat' file extension to command line

This article aims to serve as a quick starting point for people wanting to build scenery using the dockerized version of the TerraGear scenery toolchain. This will allow users to build scenery on all popular operating systems including Windows, macOS and Linux without the hassle of building the terragear toolchain themselves. This is in no way a comprehensive introduction, but should be enough to get one used to the scenery generation process.

[[File:Saint Helena Island generated using dockerized TerraGear.jpg|thumb|Saint Helena island generated using the docker image for the TerraGear toolchain]]

== Background ==
TerraGear requires three pieces of data for scenery generation:

# Elevation data: This data defines how high each point in the scenery or land is. One source for such data is http://viewfinderpanoramas.org/Coverage%20map%20viewfinderpanoramas_org3.htm.
# Landclass data: This data defines what kind of "land" is under each point in the scenery or land is. For example, some point might be "urban" class, or "forest" class. One source for such data is http://download.geofabrik.de/, which is derived from OSM.
# Airport data: This data defines the position of runways, taxiways and other assorted airport information. One source for such data is the XPlane gateway.

TerraGear consists of five tools:

# hgtchop - Processing elevation data
# terrafit - Processing elevation data
# genapts - Processing airport data
# ogr-decode - Processing landclass data
# tg-construct - Generating the final scenery.

== Scenery location ==
We will build Saint Helena Island, an island in the Atlantic Ocean. Specifically, we will be building the island around [https://en.wikipedia.org/wiki/Saint_Helena_Airport Saint Helena Airport] (ICAO: '''FHSH''').

Its location is: DMS 15° 57′ 33″ S, 5° 38′ 45″ W, Decimal -5.645833 -15.959167

A good vantage point to see progress is to start FG with the following options:

--lon=-5.62000000 --lat=-16.00000000 --altitude=4000 --heading=310

The bounds for our build will be:
* Latitude: -6 to -5
* Longitude: -17 to -15

Let <code>$SCENERY_BUILD_DIR</code> be the directory containing all of our working files for this project.

== Getting docker running ==
The first step is to have docker installed and accessible through the command line. Run the following command to fetch the terragear toolchain:
docker pull flightgear/terragear:ws20

Next, start a docker container to access the terragear tools:

docker run -i -v $SCENERY_BUILD_DIR:/terragear-work/ -t flightgear/terragear:ws20 /bin/bash

Once this command runs successfully, the command line will now be a "window" into the docker container, allowing you to run the entire terragear toolchain. Because of the <code>-v</code> argument (bind mount), the container can see the contents of <code>$SCENERY_BUILD_DIR</code> will be visible at <code>/terragear-work/</code> inside the container.

== Process Elevation Data ==
The elevation data can be obtained from [http://viewfinderpanoramas.org/Coverage%20map%20viewfinderpanoramas_org3.htm ViewFinderPanoramas], specifically, the [http://viewfinderpanoramas.org/dem3/SD30.zip SD30] and [SE30 http://viewfinderpanoramas.org/dem3/SE30.zip] tiles cover this island.

Extract and add to <code>$SCENERY_BUILD_DIR/data/SRTM-3/*.hgt</code>. Run the following commands in the docker container:

cd /terragear-work/
for f in data/SRTM-3/*.hgt; do hgtchop 3 "${f}" "work/SRTM-3"; done
terrafit work/SRTM-3 -m 50 -x 22500 -e 1

== Process Airport Data ==
'''FHSH''' is not available in FlightGear's <code>apt.dat</code>, so the airport information has to be fetched from elsewhere. The XPlane gateway is one possible source. For this sample project, we can use the following data from https://github.com/accek/fg-nav-fixups:

1 1023 1 0 FHSH St Helena
100 45.00 2 0 0.00 1 2 1 02 -15.96694276 -005.64575428 100 0 2 9 0 2 20 -15.94934298 -005.64615237 300 0 2 9 0 2
110 1 0.00 358.7100 New Taxiway 4
111 -15.96166211 -005.64927678
111 -15.96340503 -005.64926307
111 -15.96340434 -005.64836151
111 -15.96290056 -005.64836043
111 -15.96284142 -005.64854134
111 -15.96265507 -005.64854103
113 -15.96155909 -005.64854086
110 2 0.00 358.7100 New Taxiway 3
111 -15.94934844 -005.64635879 3 102
111 -15.94935248 -005.64663563 3 102
111 -15.94995561 -005.64662024 3 102
113 -15.95019415 -005.64634336
110 2 0.00 358.7100 New Taxiway 2
111 -15.96693818 -005.64554618 3 102
111 -15.96693596 -005.64524600 3 102
111 -15.96628657 -005.64526997 3 102
113 -15.96603006 -005.64556883
110 2 0.00 358.7100 New Taxiway 1
111 -15.96305635 -005.64765837 3 102
111 -15.96240410 -005.64767341 3 102
112 -15.96226078 -005.64761762 -15.96220044 -005.64756860 3 102
111 -15.96219925 -005.64745814 3 102
111 -15.96219005 -005.64624609 3 102
112 -15.96223439 -005.64613746 -15.96227201 -005.64609544 3 102
111 -15.96236947 -005.64606567
111 -15.96184016 -005.64607709 3 102
112 -15.96195708 -005.64616687 -15.96199469 -005.64621034 3 102
111 -15.96199881 -005.64627387 3 102
111 -15.96200448 -005.64744540 3 102
112 -15.96197248 -005.64759953 -15.96193665 -005.64765444 3 102
111 -15.96183543 -005.64768917 3 102
111 -15.96154350 -005.64769949 3 102
111 -15.96155909 -005.64854086
111 -15.96265507 -005.64854103
111 -15.96265481 -005.64818499
113 -15.96306600 -005.64818480 3 102
130 Airport Boundary
111 -15.95876878 -005.64712051
111 -15.96005216 -005.64729370
111 -15.96043831 -005.64731000
111 -15.96048880 -005.64864132
111 -15.96154716 -005.64921198
111 -15.96159626 -005.65014384
111 -15.96388391 -005.64953797
111 -15.96430513 -005.64699927
111 -15.96882642 -005.64692255
111 -15.96885682 -005.64412109
111 -15.94564642 -005.64456651
113 -15.94563863 -005.64716916
120 Hold
111 -15.96200516 -005.64660225 4 103
115 -15.96218383 -005.64660129
120 Linear Feature 5
111 -15.96210864 -005.64767019 1 101
112 -15.96206007 -005.64782922 -15.96201482 -005.64792776 1 101
115 -15.96188449 -005.64810582
120 Linear Feature 4
111 -15.96210864 -005.64767019 1 101
112 -15.96213878 -005.64782592 -15.96215760 -005.64789051 1 101
115 -15.96229199 -005.64808544
120 Linear Feature 3
111 -15.96156820 -005.64813668 20
111 -15.96263721 -005.64810368 20
111 -15.96263233 -005.64792345 20
115 -15.96304480 -005.64791075
120 Linear Feature 2
111 -15.96210864 -005.64767019 1 101
111 -15.96210128 -005.64660525 1 105
115 -15.96209919 -005.64630388
120 Linear Feature 1
111 -15.96154408 -005.64588717 1 105
111 -15.96184445 -005.64588139 1 105
112 -15.96204503 -005.64596036 -15.96210198 -005.64604073 1 105
111 -15.96209919 -005.64630388 1 105
112 -15.96217524 -005.64595582 -15.96225060 -005.64588070 1 105
111 -15.96236918 -005.64587174 1 105
115 -15.96269552 -005.64586403
21 -15.95361317 -005.64657631 3 180.0000 3.0 Papi
21 -15.95359638 -005.64551140 2 180.0000 3.0 Papi
21 -15.96347774 -005.64645343 2 -1.2600 3.0 Papi
20 -15.96192491 -005.64660719 90.0000 0 3 {@R}20-02{@@}{@Y}APRON
20 -15.96225995 -005.64660719 90.0000 0 3 {@R}20-02{@@}{@Y}APRON
14 -15.96312208 -005.64867411 82.02 0 Tower Viewpoint
15 -15.96179344 -005.64822577 -50.36 Ramp Start 1
1300 -15.96238032 -005.64819725 -129.45 gate jets Ramp Start 2
15 -15.96285880 -005.64779046 -181.04 Ramp Start 3
19 -15.95196179 -005.64670036 0 New Windsock 2
19 -15.96603475 -005.64630065 0 New Windsock 1

Copy and paste the above into <code>$SCENERY_BUILD_DIR/data/airports/FHSH.dat</code>. We can now run <code>genapts</code>:

genapts850 --input=data/airports/FHSH.dat --work=./work --dem-path=SRTM-3 --min-lon=-6 --max-lon=-5 --min-lat=-17 --max-lat=-15
genapts850 --input=data/airports/FHSH.dat --work=./work --dem-path=SRTM-3 --airport=FHSH

== Process Landclass Data ==
We can download landclass data from GeoFabrik, specifically from http://download.geofabrik.de/africa/saint-helena-ascension-and-tristan-da-cunha.html. Download the *.shp files and extract them into <code>$SCENERY_BUILD_DATA/data/shapefiles</code>. Each type of file should go into its own folder. For example, copy all <code>gis_osm_places_a_free_1.*</code> files into <code>$SCENERY_BUILD_DATA/data/shapefiles/gis_osm_places_a_free_1/*</code>, as this is the format that TerraGear expects the files to be in. Usually, we would use a landmass (See Notes below) shapefile as our Default, but to simplify things for this tutorial, we can use the <code>gis_osm_places_a_free_1.shp</code> file, as the landmass file and this file are identical for this particular island. We are now ready to run <code>ogr-decode</code>:

ogr-decode --max-segment 500 --area-type Default work/Default data/shapefiles/gis_osm_places_a_free_1/

We have to run <code>ogr-decode</code> for every land class (so urban, forest, lakes, roads etc). At each time, we need to specify the shapefile (the last argument in the above command) and the corresponding area material type that FlightGear recognizes ("Default") in the above command. For this tutorial, we will run the command just once to get the construct the entire island as a "Default" landclass.

== Bringing it all together ==
We can finally run <code>tg-construct</code> to bring everything together
tg-construct --priorities=/usr/local/share/TerraGear/default_priorities.txt --work-dir=./work --output-dir=./output/Terrain --min-lon=-6 --max-lon=-5 --min-lat=-17 --max-lat=-15 AirportArea AirportObj Default SRTM-3

The <code>$SCENERY_BUILD_DIR/output</code> will now contain the built scenery. Point your FG instance to this path using <code>--fg-scenery</code> and take a look at the built scenery!

== Notes ==
* There are two docker images, <code>flightgear/terragear:ws20</code> and <code>flightgear/terragear:latest</code>. The former corresponds to the 2.0 world scenery build, while the later points to the latest code. The latest container has several improvements and GDAL tools which can be used to manipulate shapefiles, but also unfortunately has bugs in the hgtchop and terrafit tools for SRTM-3 data. The best way is to use <code>flightgear/terragear:ws20</code> for elevation data processing, and <code>flightgear/terragear:latest</code> for everything else.
* The [https://osmdata.openstreetmap.de/data/land-polygons.html OSM coastlines data] is a good source for the landmass ("Default") terrain, but is a single file for the entire world.
* You can use the following command (found in the latest terragear docker image) to "crop" the shapefile to an area of interest:
ogr2ogr -clipsrc -6 -17 -5 -15 cut_landmass.shp land_polygons.shp
* As mentioned in the introduction, this tutorial is just a starting point. Have a look at the other TerraGear wiki articles. A good resource is also provided [https://forum.flightgear.org/viewtopic.php?t=35618 on the forum], which uses TerraGear GUI. You can use the concepts learned from there and run the commands in the docker image.

Autopush

2021-09-01T21:14:16Z

Sfrsfr: /* Implementations */ added (github) Embraer E-Jet family

'''Autopush''' aims to develop a generic pushback for [[JSBSim]] and [[YASim]] aircraft, with the following characteristics:

# Do the pushback procedure automatically.
# Scale to different aircraft with minimum changes to their logic.
# Use no computer resources in flight.

== Implementing Autopush ==
See <code>{{gitlab source|user=mdanil|repo=flightgear-autopush|path=README.TXT|text=README.TXT}}</code> in the development repository.

== Implementations ==
September 2021 the following aircraft have Autopush implemented:

{| class="wikitable sortable"
! --aircraft= || Aircraft || Hangar
|-
| Tu-144D || [[Tupolev Tu-144D]] || Tu-144D
|-
| A320-family|| [[A320-family|Airbus A320]] || [[FGAddon]]
|-
| IDG-A33X || [[IDG-A33X|Airbus A330]] || Octal450
|-
| MD-11 || [[MD-11|McDonnell Douglas MD-11]] || Octal450
|-
| B777 || [[Boeing 777]] || [[FGAddon]]
|-
| 747-400 || [[Boeing 747-400]] || [[FGAddon]]
|
|-
| E-Jet family || Embraer E-Jet || [https://github.com/YV3399/E-jet-family-YV Github]
|}

== Related content ==
=== Wiki articles ===
* [[Howto:Implement pushback]] - A different system
* [[Pushback]] - A drivable model that unfortunately can not do pushback

=== Forum topics ===
* {{forum link|title=Autopush help|t=37144}} (March 2020)
* {{forum link|title=Autopush: Automated pushback|t=34630}} (August 2018-July 2019) - Development topic

=== Source code ===
* {{gitlab source|user=mdanil|repo=flightgear-autopush}}

[[Category:Aircraft enhancement]]

Bindings

2021-09-01T19:06:25Z

Sfrsfr: Explain order of execution of multiple bindings

'''Bindings''' define what happens when a user:
* [[Howto: Make a clickable panel|Clicks an object]] in the [[scenery]] or in an [[aircraft]].
* Presses a key/button on the keyboard or [[joystick]].
* Clicks a [[menu]] item
* Interacts with a dialog (clicking a button, selecting list entries etc)

In other words, '''bindings''' are simply the term for '''actions''' that are associated with certain '''events''' in FlightGear.

There are different types of events supported by various subsystems, but the resulting action that can be triggered will typically involve either a hard-coded command (a so called fgcommand), or a block of scripted code (using [[Nasal]]). Bindings can be parameterized/customized using properties as arguments that are passed to each binding as a props.Node object.
And Nasal code can also be registered to become available as a dedicated fgcommand.

An object, button or key can have multiple bindings assigned to them. The bindings will be executed in the order in which they appear in the XML file. Bindings may contain [[conditions]] to make them conditionally executed. Each binding must specify a command node with its particular type, see below.

{{Note|Planes are free to override key bindings to fullfill their needs. The Space Shuttle for instance has no mixture control, so the m-key switches from translational to rotational hand controller.
The key only performs as mixture control if the plane has mixture settings and if the plane didn't re-assign the key - so dependent on what plane you try, it may or may not. Usually the aircraft-specific help spells it out.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=298436#p298436
|title = <nowiki> Re: trouble with m-key </nowiki>
|author = <nowiki> Thorsten </nowiki>
|date = Nov 9th, 2016
|added = Nov 9th, 2016
|script_version = 0.40
}}</ref>
}}

This article gives a small overview of frequently used bindings. Please refer to {{readme file|commands}} for additional information and refer to $FG_SRC/Main/commands.cxx for a complete list of available bindings.

All given codes are examples, found on various places in the [[FlightGear]] package.

== Commands ==
Below are some useful commands, some also with their equivalent Nasal call. A more complete listing can be found in the readme file, {{readme file|commands}}.

To learn more about adding your own custom fgcommands to the source code, see [[Howto:Add new fgcommands to FlightGear]].

=== replay ===
Toggles replay.
<syntaxhighlight lang="xml">
<binding>
<command>replay</command>
</binding>
</syntaxhighlight>
<syntaxhighlight lang="nasal">
fgcommand("replay");
</syntaxhighlight>

=== dialog-close ===
Closes the active dialog.
<syntaxhighlight lang="xml">
<binding>
<command>dialog-close</command>
</binding>
</syntaxhighlight>
<syntaxhighlight lang="nasal">
fgcommand("dialog-close");
</syntaxhighlight>

=== dialog-show ===
Shows a dialog, which should be present in <tt>''[[$FG_ROOT]]/gui/dialogs''</tt>. In addition, from FlightGear 2.8, dialog files located in <tt>''<aircraft directory>/gui/dialogs''</tt> are also loaded. This should be used for dialogs specific to a certain aircraft.
<syntaxhighlight lang="xml">
<binding>
<command>dialog-show</command>
<dialog-name>location-in-air</dialog-name>
</binding>
</syntaxhighlight>
<syntaxhighlight lang="nasal">
fgcommand("dialog-show", props.Node.new({"dialog-name": "location-in-air"}));
</syntaxhighlight>

; dialog-name : The name of the dialog, as designated in its XML file.

=== nasal ===
[[Nasal]] is frequently used for complicated systems, because it can execute virtually any function and allows running previously-defined Nasal functions.
<syntaxhighlight lang="xml">
<binding>
<command>nasal</command>
<script>b777.afds.input(0,1);</script>
</binding>
</syntaxhighlight>

; script : The Nasal script to execute.
: {{inote|Make sure that the script does not conflict with the {{wikipedia|List of XML and HTML character entity references#Predefined entities in XML|predefined XML entities}}. If it does, you can either put it in a {{wikipedia|CDATA|CDATA section}} or use a non-interpreted version (e.g., <code>&gt;</code> in place of <code>></code>).}}

The {{func link|cmdarg()}} function is often useful in these situations to extract offset values passed to the binding. It returns the specific <tt><binding></tt> node, which contains a <tt><setting></tt> node at runtime if used in a joystick axis that represents the value of that axis.

In joysticks and keyboard keys, the script is run in a specific namespace; please see [[Howto:Understand Namespaces and Methods]] for more information on namespaces.

=== property-adjust ===
Increases or decreases a property's value with a given step. Maximum and minimum values are optional.
<syntaxhighlight lang="xml">
<binding>
<command>property-adjust</command>
<property>/autopilot/settings/heading-bug-deg</property>
<step>1</step>
<min>0</min>
<max>360</max>
<wrap>true</wrap>
</binding>
</syntaxhighlight>

; property : Property that will be changed.
; step : Amount to increase or decrease the property's value. Defaults to 0.
; offset : Offset from the property's current value. If '''step''' is not given, this is multiplied by '''factor'''.
; factor : When '''step''' is not given, '''offset''' is multiplied by this. Defaults to 1.
; min : The minimum allowed value. Defaults to "no minimum."
; max : The maximum allowed value. Defaults to "no maximum."
; wrap : If true, the value will be wrapped when it passes min or max; both min and max must be present for this to work. Defaults to false.
; mask : This argument accepts three value: "integer," "decimal" and "all" (default). "integer" means that '''step''' or '''offset * factor''' is applied to the part of the property's current value left of the decimal point first. "decimal" does the same, but applies it to the prt to the right of the decimal point. "all" simply applies it to the whole number. This parameter does not seem to affect the resulting new value of the property, and so is not needed.

=== property-assign ===
One of the most important commands. It sets a property to a predefined value or to the value of another property.<ref>{{flightgear source
| path = src/Main/fg_commands.cxx
| line = 446
}}</ref>
<syntaxhighlight lang="xml">
<binding>
<command>property-assign</command>
<property>/autopilot/settings/target-speed-kt</property>
<value>0</value>
</binding>
</syntaxhighlight>
or<syntaxhighlight lang="xml">
<binding>
<command>property-assign</command>
<property>autopilot/input/hdg</property>
<property>instrumentation/heading-indicator/hdg-autopilot</property>
</binding>
</syntaxhighlight>

=== property-cycle ===
Cycles between a list of values and assigns one to a property. The value-list can vary in length. If the current value is "value1", it will change to "value2"; if it is "value2", it will change to "value3", and so on. If the current value is not in the list, it will jump to the first one.
<syntaxhighlight lang="xml">
<binding>
<command>property-cycle</command>
<property>/autopilot/autobrake/setting</property>
<value type="string">ARM</value>
<value type="string">DISARM</value>
<value type="string">OFF</value>
</binding>
</syntaxhighlight>
As of May 2013, the command supports additional behaviours to simplify use with the new [[Knob_/_slider_animation|knob and slider animations]]. The wrapping behaviour can be disabled by setting <wrap>0</wrap>, and the command uses the 'offset' argument to select a direction of movement. This means a property-cycle bound to a multi-position knob will function as expected for movement in both directions.

=== property-interpolate ===
Interpolates to a value with a given rate of change (per second).
<syntaxhighlight lang="xml">
<binding>
<command>property-interpolate</command>
<property>/controls/flight/aileron-trim</property>
<value type="double">0</value>
<rate>0.5</rate>
</binding>
</syntaxhighlight>

Instead of using <rate>, one could use <time>, to specify the time (in seconds) it takes to go to the new value, independent of the current value.
<syntaxhighlight lang="xml">
<binding>
<command>property-interpolate</command>
<property>/controls/flight/aileron-trim</property>
<value type="double">0</value>
<time>2</time>
</binding>
</syntaxhighlight>

You can also interpolate to a value given by a property.
<syntaxhighlight lang="xml">
<binding>
<command>property-interpolate</command>
<property>/controls/flight/aileron-trim</property>
<property>/controls/flight/default-aileron-trim</property>
<rate>0.5</rate>
</binding>
</syntaxhighlight>

=== property-multiply ===
Multiply the value of a property by a given factor.
<syntaxhighlight>
<binding>
<command>property-multiply</command>
<property>/controls/flight/aileron</property>
<factor>0.5</factor>
<min>-1</min>
<max>1</max>
<mask>all</mask>
<wrap>true</wrap>
</binding>
</syntaxhighlight>
*'''factor:''' the amount to multiply by.
*'''min:''' minimum value.
*'''max:''' maximum value.
*'''mask:'''
** '''integer:''' mutiply only left of the decimal point.
** '''decimal:''' multiply only the right of the decimal point.
** '''all:''' multiply the entire value.
*'''wrap:''' true if the value should be wrapped if it passes min/max. It is required to set both min and max in that case.

=== property-randomize ===
Assigns a random value (between min and max) to a property.
<syntaxhighlight lang="xml">
<binding>
<command>property-randomize</command>
<property>/orientation/pitch-deg</property>
<min>0</min>
<max>360</max>
</binding>
</syntaxhighlight>

=== property-scale ===
Set the value of a property based on an axis, often used in [[joystick]] configuration files.
<syntaxhighlight lang="xml">
<binding>
<command>property-scale</command>
<property>/controls/flight/aileron</property>
<offset>0.001</offset>
<factor>-1</factor>
<power>3</power>
</binding>
</syntaxhighlight>

* '''offset:''' the offset to shift by, before applying the factor.
* '''factor:''' the factor to multiply by (use negative to reverse).
* '''squared:''' if true will square the resulting value (same as power=2).
* '''power:''' the resulting value will be taken to the power of this integer value (overrides squared).

Remember: <tt>(property^power + offset) * factor = result</tt>

=== property-swap ===
Swaps the values of two properties, useful for radio panels.
<syntaxhighlight lang="xml">
<binding>
<command>property-swap</command>
<property>/instrumentation/comm/frequencies/selected-mhz</property>
<property>/instrumentation/comm/frequencies/standby-mhz</property>
</binding>
</syntaxhighlight>

=== property-toggle ===
Toggles the value of a property on each click, between true (1) and false (0).
<syntaxhighlight lang="xml">
<binding>
<command>property-toggle</command>
<property>/controls/gear/gear-down</property>
</binding>
</syntaxhighlight>
Or - if defined - it toggles between two custom values.
<syntaxhighlight lang="xml">
<binding>
<command>property-toggle</command>
<property>/controls/gear/gear-down</property>
<value>2</value>
<value>3</value>
</binding>
</syntaxhighlight>

===request-metar ===
{{cquote|
<syntaxhighlight lang="nasal">
fgcommand("request-metar", props.Node.new({"path": "/foo/mymetar", "station": "LOWI"}));
</syntaxhighlight>

If you pass an existing path, the station ID will be updated, and if you pass the same station ID as before, no additional request is made. As usual for metar-properties, there's a time-to-live and valid flags you can check, and the metar refreshes automatically every 900 seconds. You can also write to the station ID directly to change station, update the time-to-live, and wait for the valid signal.

There's also an unregister command ('clear-metar') to cancel the binding into the property tree.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38372.html|title=<nowiki>[Flightgear-devel] Requesting arbitrary metar</nowiki>|author=James Turner|date=Sun, 23 Sep 2012 08:56:48 -0700}}</ref>|James Turner}}

<references/>

== Related content ==
=== Wiki ===
* [[Conditions]]
* [[Howto:Make a clickable panel]]
* [[Howto:Reassign keyboard bindings]]

=== Forum topics ===
* {{forum link|t=37443|title=Order of multiple bindings}}
* {{forum link|t=37447|title=Amending to key bindings}} - Partially about indices (<code><nowiki><binding n="<index>"></nowiki></code>) for bindings.

=== Readme file ===
* {{readme file|commands}}

=== Source ===
Note that many commands are defined elsewhere. The readme file has a more complete listing.

* {{flightgear source|path=src/Main/fg_commands.hxx}}
* {{flightgear source|path=src/Main/fg_commands.cxx}}

[[Category:Development]]
[[Category:XML]]
[[Category:FlightGear keyboard]]
[[Category:Joysticks and Yokes]]

Bindings

2021-09-01T18:52:01Z

Sfrsfr: /* property-cycle */ removed remark about wrapping

'''Bindings''' define what happens when a user:
* [[Howto: Make a clickable panel|Clicks an object]] in the [[scenery]] or in an [[aircraft]].
* Presses a key/button on the keyboard or [[joystick]].
* Clicks a [[menu]] item
* Interacts with a dialog (clicking a button, selecting list entries etc)

In other words, '''bindings''' are simply the term for '''actions''' that are associated with certain '''events''' in FlightGear.

There are different types of events supported by various subsystems, but the resulting action that can be triggered will typically involve either a hard-coded command (a so called fgcommand), or a block of scripted code (using [[Nasal]]). Bindings can be parameterized/customized using properties as arguments that are passed to each binding as a props.Node object.
And Nasal code can also be registered to become available as a dedicated fgcommand.

You can assign multiple bindings to one object, button or key. Bindings may contain [[conditions]] to make them conditionally executed. Each binding must specify a command node with its particular type, see below.

{{Note|Planes are free to override key bindings to fullfill their needs. The Space Shuttle for instance has no mixture control, so the m-key switches from translational to rotational hand controller.
The key only performs as mixture control if the plane has mixture settings and if the plane didn't re-assign the key - so dependent on what plane you try, it may or may not. Usually the aircraft-specific help spells it out.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=298436#p298436
|title = <nowiki> Re: trouble with m-key </nowiki>
|author = <nowiki> Thorsten </nowiki>
|date = Nov 9th, 2016
|added = Nov 9th, 2016
|script_version = 0.40
}}</ref>
}}

This article gives a small overview of frequently used bindings. Please refer to {{readme file|commands}} for additional information and refer to $FG_SRC/Main/commands.cxx for a complete list of available bindings.

All given codes are examples, found on various places in the [[FlightGear]] package.

== Commands ==
Below are some useful commands, some also with their equivalent Nasal call. A more complete listing can be found in the readme file, {{readme file|commands}}.

To learn more about adding your own custom fgcommands to the source code, see [[Howto:Add new fgcommands to FlightGear]].

=== replay ===
Toggles replay.
<syntaxhighlight lang="xml">
<binding>
<command>replay</command>
</binding>
</syntaxhighlight>
<syntaxhighlight lang="nasal">
fgcommand("replay");
</syntaxhighlight>

=== dialog-close ===
Closes the active dialog.
<syntaxhighlight lang="xml">
<binding>
<command>dialog-close</command>
</binding>
</syntaxhighlight>
<syntaxhighlight lang="nasal">
fgcommand("dialog-close");
</syntaxhighlight>

=== dialog-show ===
Shows a dialog, which should be present in <tt>''[[$FG_ROOT]]/gui/dialogs''</tt>. In addition, from FlightGear 2.8, dialog files located in <tt>''<aircraft directory>/gui/dialogs''</tt> are also loaded. This should be used for dialogs specific to a certain aircraft.
<syntaxhighlight lang="xml">
<binding>
<command>dialog-show</command>
<dialog-name>location-in-air</dialog-name>
</binding>
</syntaxhighlight>
<syntaxhighlight lang="nasal">
fgcommand("dialog-show", props.Node.new({"dialog-name": "location-in-air"}));
</syntaxhighlight>

; dialog-name : The name of the dialog, as designated in its XML file.

=== nasal ===
[[Nasal]] is frequently used for complicated systems, because it can execute virtually any function and allows running previously-defined Nasal functions.
<syntaxhighlight lang="xml">
<binding>
<command>nasal</command>
<script>b777.afds.input(0,1);</script>
</binding>
</syntaxhighlight>

; script : The Nasal script to execute.
: {{inote|Make sure that the script does not conflict with the {{wikipedia|List of XML and HTML character entity references#Predefined entities in XML|predefined XML entities}}. If it does, you can either put it in a {{wikipedia|CDATA|CDATA section}} or use a non-interpreted version (e.g., <code>&gt;</code> in place of <code>></code>).}}

The {{func link|cmdarg()}} function is often useful in these situations to extract offset values passed to the binding. It returns the specific <tt><binding></tt> node, which contains a <tt><setting></tt> node at runtime if used in a joystick axis that represents the value of that axis.

In joysticks and keyboard keys, the script is run in a specific namespace; please see [[Howto:Understand Namespaces and Methods]] for more information on namespaces.

=== property-adjust ===
Increases or decreases a property's value with a given step. Maximum and minimum values are optional.
<syntaxhighlight lang="xml">
<binding>
<command>property-adjust</command>
<property>/autopilot/settings/heading-bug-deg</property>
<step>1</step>
<min>0</min>
<max>360</max>
<wrap>true</wrap>
</binding>
</syntaxhighlight>

; property : Property that will be changed.
; step : Amount to increase or decrease the property's value. Defaults to 0.
; offset : Offset from the property's current value. If '''step''' is not given, this is multiplied by '''factor'''.
; factor : When '''step''' is not given, '''offset''' is multiplied by this. Defaults to 1.
; min : The minimum allowed value. Defaults to "no minimum."
; max : The maximum allowed value. Defaults to "no maximum."
; wrap : If true, the value will be wrapped when it passes min or max; both min and max must be present for this to work. Defaults to false.
; mask : This argument accepts three value: "integer," "decimal" and "all" (default). "integer" means that '''step''' or '''offset * factor''' is applied to the part of the property's current value left of the decimal point first. "decimal" does the same, but applies it to the prt to the right of the decimal point. "all" simply applies it to the whole number. This parameter does not seem to affect the resulting new value of the property, and so is not needed.

=== property-assign ===
One of the most important commands. It sets a property to a predefined value or to the value of another property.<ref>{{flightgear source
| path = src/Main/fg_commands.cxx
| line = 446
}}</ref>
<syntaxhighlight lang="xml">
<binding>
<command>property-assign</command>
<property>/autopilot/settings/target-speed-kt</property>
<value>0</value>
</binding>
</syntaxhighlight>
or<syntaxhighlight lang="xml">
<binding>
<command>property-assign</command>
<property>autopilot/input/hdg</property>
<property>instrumentation/heading-indicator/hdg-autopilot</property>
</binding>
</syntaxhighlight>

=== property-cycle ===
Cycles between a list of values and assigns one to a property. The value-list can vary in length. If the current value is "value1", it will change to "value2"; if it is "value2", it will change to "value3", and so on. If the current value is not in the list, it will jump to the first one.
<syntaxhighlight lang="xml">
<binding>
<command>property-cycle</command>
<property>/autopilot/autobrake/setting</property>
<value type="string">ARM</value>
<value type="string">DISARM</value>
<value type="string">OFF</value>
</binding>
</syntaxhighlight>
As of May 2013, the command supports additional behaviours to simplify use with the new [[Knob_/_slider_animation|knob and slider animations]]. The wrapping behaviour can be disabled by setting <wrap>0</wrap>, and the command uses the 'offset' argument to select a direction of movement. This means a property-cycle bound to a multi-position knob will function as expected for movement in both directions.

=== property-interpolate ===
Interpolates to a value with a given rate of change (per second).
<syntaxhighlight lang="xml">
<binding>
<command>property-interpolate</command>
<property>/controls/flight/aileron-trim</property>
<value type="double">0</value>
<rate>0.5</rate>
</binding>
</syntaxhighlight>

Instead of using <rate>, one could use <time>, to specify the time (in seconds) it takes to go to the new value, independent of the current value.
<syntaxhighlight lang="xml">
<binding>
<command>property-interpolate</command>
<property>/controls/flight/aileron-trim</property>
<value type="double">0</value>
<time>2</time>
</binding>
</syntaxhighlight>

You can also interpolate to a value given by a property.
<syntaxhighlight lang="xml">
<binding>
<command>property-interpolate</command>
<property>/controls/flight/aileron-trim</property>
<property>/controls/flight/default-aileron-trim</property>
<rate>0.5</rate>
</binding>
</syntaxhighlight>

=== property-multiply ===
Multiply the value of a property by a given factor.
<syntaxhighlight>
<binding>
<command>property-multiply</command>
<property>/controls/flight/aileron</property>
<factor>0.5</factor>
<min>-1</min>
<max>1</max>
<mask>all</mask>
<wrap>true</wrap>
</binding>
</syntaxhighlight>
*'''factor:''' the amount to multiply by.
*'''min:''' minimum value.
*'''max:''' maximum value.
*'''mask:'''
** '''integer:''' mutiply only left of the decimal point.
** '''decimal:''' multiply only the right of the decimal point.
** '''all:''' multiply the entire value.
*'''wrap:''' true if the value should be wrapped if it passes min/max. It is required to set both min and max in that case.

=== property-randomize ===
Assigns a random value (between min and max) to a property.
<syntaxhighlight lang="xml">
<binding>
<command>property-randomize</command>
<property>/orientation/pitch-deg</property>
<min>0</min>
<max>360</max>
</binding>
</syntaxhighlight>

=== property-scale ===
Set the value of a property based on an axis, often used in [[joystick]] configuration files.
<syntaxhighlight lang="xml">
<binding>
<command>property-scale</command>
<property>/controls/flight/aileron</property>
<offset>0.001</offset>
<factor>-1</factor>
<power>3</power>
</binding>
</syntaxhighlight>

* '''offset:''' the offset to shift by, before applying the factor.
* '''factor:''' the factor to multiply by (use negative to reverse).
* '''squared:''' if true will square the resulting value (same as power=2).
* '''power:''' the resulting value will be taken to the power of this integer value (overrides squared).

Remember: <tt>(property^power + offset) * factor = result</tt>

=== property-swap ===
Swaps the values of two properties, useful for radio panels.
<syntaxhighlight lang="xml">
<binding>
<command>property-swap</command>
<property>/instrumentation/comm/frequencies/selected-mhz</property>
<property>/instrumentation/comm/frequencies/standby-mhz</property>
</binding>
</syntaxhighlight>

=== property-toggle ===
Toggles the value of a property on each click, between true (1) and false (0).
<syntaxhighlight lang="xml">
<binding>
<command>property-toggle</command>
<property>/controls/gear/gear-down</property>
</binding>
</syntaxhighlight>
Or - if defined - it toggles between two custom values.
<syntaxhighlight lang="xml">
<binding>
<command>property-toggle</command>
<property>/controls/gear/gear-down</property>
<value>2</value>
<value>3</value>
</binding>
</syntaxhighlight>

===request-metar ===
{{cquote|
<syntaxhighlight lang="nasal">
fgcommand("request-metar", props.Node.new({"path": "/foo/mymetar", "station": "LOWI"}));
</syntaxhighlight>

If you pass an existing path, the station ID will be updated, and if you pass the same station ID as before, no additional request is made. As usual for metar-properties, there's a time-to-live and valid flags you can check, and the metar refreshes automatically every 900 seconds. You can also write to the station ID directly to change station, update the time-to-live, and wait for the valid signal.

There's also an unregister command ('clear-metar') to cancel the binding into the property tree.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38372.html|title=<nowiki>[Flightgear-devel] Requesting arbitrary metar</nowiki>|author=James Turner|date=Sun, 23 Sep 2012 08:56:48 -0700}}</ref>|James Turner}}

<references/>

== Related content ==
=== Wiki ===
* [[Conditions]]
* [[Howto:Make a clickable panel]]
* [[Howto:Reassign keyboard bindings]]

=== Forum topics ===
* {{forum link|t=37443|title=Order of multiple bindings}}
* {{forum link|t=37447|title=Amending to key bindings}} - Partially about indices (<code><nowiki><binding n="<index>"></nowiki></code>) for bindings.

=== Readme file ===
* {{readme file|commands}}

=== Source ===
Note that many commands are defined elsewhere. The readme file has a more complete listing.

* {{flightgear source|path=src/Main/fg_commands.hxx}}
* {{flightgear source|path=src/Main/fg_commands.cxx}}

[[Category:Development]]
[[Category:XML]]
[[Category:FlightGear keyboard]]
[[Category:Joysticks and Yokes]]

Knob / slider animation

2021-08-25T21:52:08Z

Sfrsfr: /* Examples */ removed unrelated 2nd binding

The new (in 2.11) '''knob animation''' and '''slider animation''' are helpers to reduce repetition in XML files, and provide a separation point for behaviour versus user interface. The idea is to specify a single animation element representing the knob, dial or slider, with bindings for various actions, and allow the GUI to decide which user interactions map to those behaviours. In particular the mapping could be adjusted by platform (Mac vs Linux), device type (laptop, trackpad, trackball or touch-screen) or a GUI preference. All objects using the animation would hence have standard user-interaction across all aircraft, which is not the case at present.

=== Rotate / Translate animation ===

The core animation values are identical to the standard 'rotate' (for a knob) and 'translate' (for a slider) animations. They can be omitted without problem if you want to keep the animations separate for some reason, e.g. different pick objects to animated objects in the model. This also means the knob could be used with more complex compound animations.

=== Binding Actions ===

Using the <action> group, a single set of bindings are run for movement of the knob/slider in either direction. An 'offset' property is exposed, with a value of either 1 or -1. For many common cases, such as a property-adjust command, this will work for both directions of movement, with suitable scale and min/max limits.

If you need different behaviours for increase vs decrease, add bindings to the <increase> and <decrease> groups instead. Note both systems can be used in parallel - all the bindings fire.

A <release> binding is available which fires when the button is released, for spring-loaded knobs (commonly used for engine starters) which return to a position after selection.

Note that if you are using a property-adjust binding, you must use <factor> to control the numerical change, since this scales the <offset> parameter. If you use <step>, bidirectional control via the same binding will '''not''' work. If for some reason your actions are asymmetric, then you will need separate increase and decrease bindings as described above. However, an asymmetric instrument might not be a good choice for these animations, for the sake of end-user understanding!

=== Shifted Mode ===

By default, in shifted mode, the normal bindings above are repeated. The default repeat is 10, but this can be changed with the <shift-repeat> property. This is deliberately coded to behave exactly the same as clicking the button a number of times, so the 'offset' in the action bindings is still 1 or -1. This is to simplify code for bindings having to deal with steps at the end of the range.

If the above mechanism is too simple, or you wish shifted mode to do something different to unshifted mode, you can specify explicit bindings instead. As soon as you specify an explicit shifted binding, the default 'repeat' behaviour is skipped. Examples of alternate shifted mode would be many MCP or GPS knobs, where pushed/pulled mode might change a totally different setting, eg fractional vs integer part of a radio frequency, or bank limit instead of selected heading.

The group names are <shift-action>, <shift-increase> and <shift-decrease>

=== Dragging ===

Dragging the object generates value changes, based on the direction of mouse movement. The mapping from pixel movement to offset values is controlled by the <drag-scale-px> property, which divides the pixel movement. Hence, smaller values mean faster movement (harder to hit a precise value accurately) and larger values mean slower movement (easier to hit a particular value, but more mouse movement needed). The default value is 10px to cause a change.

By default the drag direction is left-right (since most people have better mobility in that direction, and screens are wider than tall), but each slider or knob can over-ride this. For example, for throttle or mixture controls built-into a panel, up-down movement will feel more natural. Set <drag-direction> to 'vertical' or 'horizontal'.

=== Compatibility ===

Do ''not'' refer to modifier-state or button-state properties in your bindings. This violates the control separation which is the aim of these animations. If you include such references in your bindings, you make it very likely your knobs/sliders will break for some future user with a different platform- or input- configuration. You can't assume how many mouse buttons they have, or how their modifier keys are mapped, so the only safe thing is not to make any assumptions at all.

This might mean creating multiple in-cockpit animations for a single real-world knob in the worst case, in which case design with great care. For example the KLN-89B has a 'dual' knob (outer and inner rings) and the inner knob can be pulled out. (Some Airbus MCP panels have something similar, but the knob can be pushed ''or'' pulled). In the case of the KLN-89, the solution would be two separate knob animations, with the outer one probably having a large surrounding pick-proxy object to ensure it can be hit comfortably in a front-on view. Shifted mode on the inner knob then correspond to 'pulled out' mode in real-life.

Another option (which would also work for the Airbus) would be to make the centre of the knob pick-able separately, to drive pushing/pulling the knob, and then have the knob animation pick cover the outer circumference. This is not ideal but still much more usable than adding conditional bindings on alternate mouse buttons or modifiers! Good use of tooltips will also help here, i.e. the tooltip for the knob would include some text like 'click here to pull out'.

== Examples ==
Basic usage:

Cycles the property between 0..3 and rotates the knob object in steps of 60° (property value x factor).
The knobs 3D model must be positioned at the '0' position in order to move in sync.

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf8"?>
<PropertyList>
<animation>
<name>Wiper Left</name>
<type>knob</type>
<object-name>wiper.left</object-name>
<property>controls/switches/wiper-left</property>
<factor>60</factor>
<axis>
<object-name>wiper.left.axis</object-name>
</axis>
<action>
<binding>
<command>property-cycle</command>
<property>controls/switches/wiper-left</property>
<value>0</value>
<value>1</value>
<value>2</value>
<value>3</value>
<wrap>false</wrap>
</binding>
</action>
</animation>
</PropertyList>
</syntaxhighlight>

Another basic example:

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf8"?>
<PropertyList>
<animation>
<type>knob</type>
<object-name>ALT-SEL</object-name>
<value>0.0</value> 
<center>
<x-m>0.0</x-m><y-m>0.027</y-m><z-m>0.0238</z-m>
</center>
<axis>
<x>-1</x><y>0</y><z>0</z>
</axis>

<action>
<binding>
<command>property-adjust</command>
<property>/autopilot/settings/target-altitude-ft</property>
<factor>100</factor>
<min>0</min>
<max>40000</max>
<wrap>false</wrap>
</binding>
</action>

<increase>
<binding>
<command>nasal</command>
<script>debug.dump('was increased', cmdarg().getNode('offset').getValue());</script>
</binding>
</increase>

<decrease>
<binding>....</binding>
</decrease>
</animation>
</PropertyList>
</syntaxhighlight>

Custom shifted-usage
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf8"?>
<PropertyList>
<animation>
<type>knob</type>
<object-name>Radio.TUNE</object-name>
<value>0.0</value>
<center>...</center>
<axis>...</axis>

<action>
<binding>
<command>property-adjust</command>
<property>/instrumentation/nav[0]/standby-frequency-mhz</property>
<factor>1</factor>
<min>108</min>
<max>122</max>
<wrap>true</wrap>
</binding>
</action>

<shift-action>
<binding>
<command>property-adjust</command>
<property>/instrumentation/nav[0]/standby-frequency-mhz</property>
<factor>0.05</factor>
</binding>
</shift-action>

</animation>
</PropertyList>
</syntaxhighlight>

Spring-loaded position:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf8"?>
<PropertyList>
<animation>
<type>knob</type>
<object-name>APU-Start</object-name>
<property>/controls/apu/rotary-start</property>



<action>
<binding>
<command>property-adjust</command>
<property>/controls/apu/rotary-start</property>
<min>0</min>
<max>2</max>
</binding>
</action>


<release>
<binding>
<command>property-adjust</command>
<property>/controls/apu/rotary-start</property>
<step>0</step>
<min>0</min>
<max>1</max>
</binding>
</release>
</animation>
</PropertyList>
</syntaxhighlight>

Slider (good for breakers):
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf8"?>
<PropertyList>
<animation>
<type>slider</type>
<object-name>brk-ku-elec</object-name>
<property>/fdm/jsbsim/systems/mechanical/ku-antenna-elec-cb</property>
<factor>0.006</factor>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
<action>
<binding>
<command>property-toggle</command>
<property>/fdm/jsbsim/systems/mechanical/ku-antenna-elec-cb</property>
</binding>
</action>
</animation>
</PropertyList>
</syntaxhighlight>

Slider used as a "Spring/contact" switch (reverts to 0 on exit):
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf8"?>
<PropertyList> <animation>
<type>slider</type>
<object-name>a6-att-ref</object-name>
<property>/fdm/jsbsim/systems/adi/att-ref</property>
<factor>0.002</factor>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
<action>
<binding>
<command>property-assign</command>
<property>/fdm/jsbsim/systems/adi/att-ref</property>
<value>1</value>
</binding>
<binding>
<command>nasal</command>
<script>
SpaceShuttle.coas_att_ref();
SpaceShuttle.click("avionics");
</script>
</binding>
</action>
<release>
<binding>
<command>property-adjust</command>
<property>/fdm/jsbsim/systems/adi/att-ref</property>
<step>0</step>
<min>0</min>
<max>0</max>
</binding>
</release>
<hovered>
<binding>
<command>set-tooltip</command>
<tooltip-id>a6-att-ref</tooltip-id>
<label>Attitude Reference</label>
</binding>
</hovered>
</animation>
</PropertyList>
</syntaxhighlight>
Note: For the release you can simply use another property-assign with a value of 0.

== Related content ==
* [[Howto:Animate models]]
* [[Tooltips]]

[[Category:Aircraft enhancement]]

Knob / slider animation

2021-08-25T21:33:00Z

Sfrsfr: /* Examples */ added a true basic example with explanations

The new (in 2.11) '''knob animation''' and '''slider animation''' are helpers to reduce repetition in XML files, and provide a separation point for behaviour versus user interface. The idea is to specify a single animation element representing the knob, dial or slider, with bindings for various actions, and allow the GUI to decide which user interactions map to those behaviours. In particular the mapping could be adjusted by platform (Mac vs Linux), device type (laptop, trackpad, trackball or touch-screen) or a GUI preference. All objects using the animation would hence have standard user-interaction across all aircraft, which is not the case at present.

=== Rotate / Translate animation ===

The core animation values are identical to the standard 'rotate' (for a knob) and 'translate' (for a slider) animations. They can be omitted without problem if you want to keep the animations separate for some reason, e.g. different pick objects to animated objects in the model. This also means the knob could be used with more complex compound animations.

=== Binding Actions ===

Using the <action> group, a single set of bindings are run for movement of the knob/slider in either direction. An 'offset' property is exposed, with a value of either 1 or -1. For many common cases, such as a property-adjust command, this will work for both directions of movement, with suitable scale and min/max limits.

If you need different behaviours for increase vs decrease, add bindings to the <increase> and <decrease> groups instead. Note both systems can be used in parallel - all the bindings fire.

A <release> binding is available which fires when the button is released, for spring-loaded knobs (commonly used for engine starters) which return to a position after selection.

Note that if you are using a property-adjust binding, you must use <factor> to control the numerical change, since this scales the <offset> parameter. If you use <step>, bidirectional control via the same binding will '''not''' work. If for some reason your actions are asymmetric, then you will need separate increase and decrease bindings as described above. However, an asymmetric instrument might not be a good choice for these animations, for the sake of end-user understanding!

=== Shifted Mode ===

By default, in shifted mode, the normal bindings above are repeated. The default repeat is 10, but this can be changed with the <shift-repeat> property. This is deliberately coded to behave exactly the same as clicking the button a number of times, so the 'offset' in the action bindings is still 1 or -1. This is to simplify code for bindings having to deal with steps at the end of the range.

If the above mechanism is too simple, or you wish shifted mode to do something different to unshifted mode, you can specify explicit bindings instead. As soon as you specify an explicit shifted binding, the default 'repeat' behaviour is skipped. Examples of alternate shifted mode would be many MCP or GPS knobs, where pushed/pulled mode might change a totally different setting, eg fractional vs integer part of a radio frequency, or bank limit instead of selected heading.

The group names are <shift-action>, <shift-increase> and <shift-decrease>

=== Dragging ===

Dragging the object generates value changes, based on the direction of mouse movement. The mapping from pixel movement to offset values is controlled by the <drag-scale-px> property, which divides the pixel movement. Hence, smaller values mean faster movement (harder to hit a precise value accurately) and larger values mean slower movement (easier to hit a particular value, but more mouse movement needed). The default value is 10px to cause a change.

By default the drag direction is left-right (since most people have better mobility in that direction, and screens are wider than tall), but each slider or knob can over-ride this. For example, for throttle or mixture controls built-into a panel, up-down movement will feel more natural. Set <drag-direction> to 'vertical' or 'horizontal'.

=== Compatibility ===

Do ''not'' refer to modifier-state or button-state properties in your bindings. This violates the control separation which is the aim of these animations. If you include such references in your bindings, you make it very likely your knobs/sliders will break for some future user with a different platform- or input- configuration. You can't assume how many mouse buttons they have, or how their modifier keys are mapped, so the only safe thing is not to make any assumptions at all.

This might mean creating multiple in-cockpit animations for a single real-world knob in the worst case, in which case design with great care. For example the KLN-89B has a 'dual' knob (outer and inner rings) and the inner knob can be pulled out. (Some Airbus MCP panels have something similar, but the knob can be pushed ''or'' pulled). In the case of the KLN-89, the solution would be two separate knob animations, with the outer one probably having a large surrounding pick-proxy object to ensure it can be hit comfortably in a front-on view. Shifted mode on the inner knob then correspond to 'pulled out' mode in real-life.

Another option (which would also work for the Airbus) would be to make the centre of the knob pick-able separately, to drive pushing/pulling the knob, and then have the knob animation pick cover the outer circumference. This is not ideal but still much more usable than adding conditional bindings on alternate mouse buttons or modifiers! Good use of tooltips will also help here, i.e. the tooltip for the knob would include some text like 'click here to pull out'.

== Examples ==
Basic usage:

Cycles the property between 0..3 and rotates the knob object in steps of 60° (property value x factor).
The knobs 3D model must be positioned at the '0' position in order to move in sync.

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf8"?>
<PropertyList>
<animation>
<name>Wiper Left</name>
<type>knob</type>
<object-name>wiper.left</object-name>
<property>controls/switches/wiper-left</property>
<factor>60</factor>
<axis>
<object-name>wiper.left.axis</object-name>
</axis>
<action>
<binding>
<command>property-cycle</command>
<property>controls/switches/wiper-left</property>
<value>0</value>
<value>1</value>
<value>2</value>
<value>3</value>
<wrap>false</wrap>
</binding>
<binding>
<command>property-toggle</command>
<property>sim/sound/knob1</property>
</binding>
</action>
</animation>
</PropertyList>
</syntaxhighlight>

Another basic example:

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf8"?>
<PropertyList>
<animation>
<type>knob</type>
<object-name>ALT-SEL</object-name>
<value>0.0</value> 
<center>
<x-m>0.0</x-m><y-m>0.027</y-m><z-m>0.0238</z-m>
</center>
<axis>
<x>-1</x><y>0</y><z>0</z>
</axis>

<action>
<binding>
<command>property-adjust</command>
<property>/autopilot/settings/target-altitude-ft</property>
<factor>100</factor>
<min>0</min>
<max>40000</max>
<wrap>false</wrap>
</binding>
</action>

<increase>
<binding>
<command>nasal</command>
<script>debug.dump('was increased', cmdarg().getNode('offset').getValue());</script>
</binding>
</increase>

<decrease>
<binding>....</binding>
</decrease>
</animation>
</PropertyList>
</syntaxhighlight>

Custom shifted-usage
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf8"?>
<PropertyList>
<animation>
<type>knob</type>
<object-name>Radio.TUNE</object-name>
<value>0.0</value>
<center>...</center>
<axis>...</axis>

<action>
<binding>
<command>property-adjust</command>
<property>/instrumentation/nav[0]/standby-frequency-mhz</property>
<factor>1</factor>
<min>108</min>
<max>122</max>
<wrap>true</wrap>
</binding>
</action>

<shift-action>
<binding>
<command>property-adjust</command>
<property>/instrumentation/nav[0]/standby-frequency-mhz</property>
<factor>0.05</factor>
</binding>
</shift-action>

</animation>
</PropertyList>
</syntaxhighlight>

Spring-loaded position:
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf8"?>
<PropertyList>
<animation>
<type>knob</type>
<object-name>APU-Start</object-name>
<property>/controls/apu/rotary-start</property>



<action>
<binding>
<command>property-adjust</command>
<property>/controls/apu/rotary-start</property>
<min>0</min>
<max>2</max>
</binding>
</action>


<release>
<binding>
<command>property-adjust</command>
<property>/controls/apu/rotary-start</property>
<step>0</step>
<min>0</min>
<max>1</max>
</binding>
</release>
</animation>
</PropertyList>
</syntaxhighlight>

Slider (good for breakers):
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf8"?>
<PropertyList>
<animation>
<type>slider</type>
<object-name>brk-ku-elec</object-name>
<property>/fdm/jsbsim/systems/mechanical/ku-antenna-elec-cb</property>
<factor>0.006</factor>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
<action>
<binding>
<command>property-toggle</command>
<property>/fdm/jsbsim/systems/mechanical/ku-antenna-elec-cb</property>
</binding>
</action>
</animation>
</PropertyList>
</syntaxhighlight>

Slider used as a "Spring/contact" switch (reverts to 0 on exit):
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf8"?>
<PropertyList> <animation>
<type>slider</type>
<object-name>a6-att-ref</object-name>
<property>/fdm/jsbsim/systems/adi/att-ref</property>
<factor>0.002</factor>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
<action>
<binding>
<command>property-assign</command>
<property>/fdm/jsbsim/systems/adi/att-ref</property>
<value>1</value>
</binding>
<binding>
<command>nasal</command>
<script>
SpaceShuttle.coas_att_ref();
SpaceShuttle.click("avionics");
</script>
</binding>
</action>
<release>
<binding>
<command>property-adjust</command>
<property>/fdm/jsbsim/systems/adi/att-ref</property>
<step>0</step>
<min>0</min>
<max>0</max>
</binding>
</release>
<hovered>
<binding>
<command>set-tooltip</command>
<tooltip-id>a6-att-ref</tooltip-id>
<label>Attitude Reference</label>
</binding>
</hovered>
</animation>
</PropertyList>
</syntaxhighlight>
Note: For the release you can simply use another property-assign with a value of 0.

== Related content ==
* [[Howto:Animate models]]
* [[Tooltips]]

[[Category:Aircraft enhancement]]

De/Command Line Options

2021-08-19T13:10:59Z

Sfrsfr: /* 1.) fgfscr = die reine "Optionsliste" */ it's fgfsrc, not fgfscr

== Befehls Optionen für FlightGear ==

Für alle einigermaßen komplexe Programme gibt es Optionen mit denen der Benutzer deren Start und Ausführung beeinflussen kann. Für FlightGear gibt es dazu derzeit über 150 verschiedene Optionen, von denen aber sicherlich niemand alle benötigt. Aber einige davon benutzt wohl jeder, z.B. um ein bestimmtes Flugzeug, einen Flugplatz, Wetter, Zeit etc. zu definieren. Dagegen werden viele Optionen weniger benutzt, z.B. bezüglich Netzwerkeinstellungen, Fehlersuche, etc.

Der einfachste Weg um diese Optionen einzustellen ist die Benutzung einer „Grafischen Benutzer Oberfläche“ ('''GUI''' = Graphical User Interface). Dies ist
* das Zusatzprogramm „'''fgrun'''“
** auch genannt “'''FlightGear Wizard'''” (FlightGear-Assistent) oder auch formell “'''FlightGear Launch Control'''” (FlightGear Start Kontrolle).
** Bei Mac OS X ist dies der “'''GUI Launcher'''” (Starter).

Alle diese Versionen haben sehr ähnliche Funktionen, aber in einer etwas anderen „Hülle“. Bei Windows und Mac OS X ist dieses „fgrun“ bereits in der Grundausstattung des FlightGear integriert! Sollten Sie es nachträglich installieren wollen, dann sehen Sie: http://sourceforge.net/projects/fgrun/. Mittels dieses Zusatzprogrammes brauchen Sie sich nicht um die nachfolgend aufgeführten einzelnen „Optionen“ kümmern – Sie müssen dann nur noch die gewünschten Funktionen aussuchen!

Benutzer, die nicht über "fgrun" verfügen oder sehr ungewöhnliche Optionen verwenden wollen, müssen die Optionen direkt mit dem Befehl eingeben. Also z.B.
::'''fgfs --option1 --option2''' ''<small>... e.t.c. <br />(wie gesagt: etwa 150 Optionen sind möglich! Siehe die nachfolgende Liste)</small>''
Falls Sie Hilfe brauchen zur Eingabe einer Befehlszeile oder zur Erstellung einer Datei sehen Sie http://wiki.flightgear.org/index.php/Command_line
<br /><br />
Sie können sich das Leben aber deutlich einfacher gestallten, wenn Sie sich statt dessen Dateien anlegen, die die gewünschten Optionen beinhalten und einfach abzuändern sind! Dazu gibt es 2 Möglichkeiten:
<br /><br />
==='''1.) fgfsrc''' = die reine "Optionsliste"===
FlightGear sucht beim Start immer nach einer Datei „fgfsrc“. Wenn es diese Datei findet benutzte es automatisch die darin enthaltenen Optionen. Leider sind der Ort und Name der Datei für die Betriebssysteme unterschiedlich:
* Für '''Windows''' muss diese Datei '''„system.fgfsrc“''' heißen und im Verzeichnis '''„FG_ROOT“''' abgespeichert sein
* Für '''linux''' muss der Name '''„.fgfsrc“''' sein und in Ihrem '''Privat-Verzeichnis''' abgespeichert sein (also z.B. „~/.fgfsrc“). ('''Beachten Sie''' den Punkt am Anfang des Namens – es ist also eine „unsichtbare“ Datei, bei der Sie Ihren „File Browser“ evtl. extra auffordern müssen diese anzuzeigen!).
* Für '''MAC OS X''' kenne ich diese Möglichkeit nicht
<br />Eine solche Datei würde etwa wie folgt aussehen:
::{| border=1
|-
|align="center"|'''„fgfsrc“''' bzw. '''„system.fgfsrc“'''
|-
||
--fg-root=/usr/share/FlightGear/data
<br />--fg-szenery=/usr/share/FlightGear/Szenerie
<br />--airport=EDDF
<br />--parkpos=B46
<br />--aircraft=SenecaII
<br />--control=joystick
<br />--disable-random-objects
<br />--prop:/sim/rendering/random-vegetation=false
<br />--disable-specular-highlight
<br />--enable-ai-models
<br />--enable-real-weather-fetch
<br /><small>''...(e.t.c.)''</small>
|}
<br />
=== 2.) Eine komplette Startdatei ===
Sie können eine komplette Startdatei erstellen, die der vorstehenden „fgfsrc“ sehr ähnlich ist - aber zusätzlich mit dem Start-Befehl in der ersten Zeile. Auf diese Art können Sie an der Datei immer wieder (kleinere) Änderungen vornehmen und unter anderem Namen abspeichern --> auf diese Weise können Sie sich "fertige Startdateien mit passenden Optionen für jede Gelegenheit" generieren!
<br /><br />Auch diese Befehls-Datei ist weitestgehend unabhängig vom Betriebssystemen, aber beachten Sie:
* der Startbefehl steht in unterschiedlichen Verzeichnissen
* Beim Abspeichern ihrer neu erstellten Datei achten Sie darauf, dass der zu verwendende Dateityp vom Betriebssystem abhängt:
** '''Windows:''' Benutzen Sie den “WordPad” Editor, da Dateien die mit dem Standard “Editor” erstellt wurden zumindest auf anderen Systemen zu Fehlern führen können!). Speichern Sie die erstellte Datei als '''*.bat''' Datei (z.B. “EDDF.bat”)
** '''Unix/Linux:''' Speichern Sie die Datei als '''*.txt''' Datei (z.B. “EDDF.txt”, obwohl der Typ bei den meisten Unix/Linux-Systemen keine Rolle spielt!). Allerdings müssen Sie bei vielen dieser Systeme die Datei als “ausführbare Datei” deklarieren: Rechter Maus-Klick auf das Datei-Icon auf dem Desktop (oder im von Ihnen gewählten Verzeichnis) → Eigenschaften → Sicherheit → Ausführbar (oder sinngemäß).
** '''Mac OS X:''' Meines Wissens gibt es die Möglichkeit einer solchen Befehlsdatei hier nicht.
* Für einen einfachen Zugriff auf die Datei speichern sie diese auf dem Desktop (oder in einem Verzeichnis Ihrer Wahl).
Der Inhalt der Befehls-Datei könnte, abhängig von der eingegeben Anzahl der Befehle, in etwa so aussehen:
::{| border=1
|-
|align="center"|'''UNIX/Linux: “EDDF.txt”'''||align="center"|'''Windows: “EDDF.bat”'''
|-
||/usr/local/bin/fgfs \ <br />--fg-root=/usr/share/FlightGear/data \ <br />--fg-szenery=/usr/share/FlightGear/Szenerie \ <br />--airport=EDDF \ <br />--parkpos=B46 \ <br />--aircraft=SenecaII \ <br />--control=joystick \ <br />--disable-random-objects \ <br />--prop:/sim/rendering/random-vegetation=false \ <br />--disable-specular-highlight \ <br />--enable-ai-models \ <br />--enable-real-weather-fetch<br /><small>''...(e.t.c.)''</small>
||C:\Programme\FlightGear\bin\Win32\fgfs.exe ^ <br />--fg-root=C:\Programme\FlightGear\data ^ <br />--fg-szenery=C:\Programme\FlightGear\Szenerie ^ <br />--airport=EDDF ^ <br />--parkpos=B46 ^ <br />--aircraft=SenecaII ^ <br />--control=joystick ^ <br />--disable-random-objects ^ <br />--prop:/sim/rendering/random-vegetation=false ^ <br />--disable-specular-highlight ^ <br />--enable-ai-models ^ <br />--enable-real-weather-fetch<br /><small>''...(e.t.c.)''</small>
|}
'''Beachten Sie:'''
Sie können die Befehlsdateien zwischen Unix/Linux und Windows austauschen, allerdings kopieren Sie die Datei nicht einfach und benennen sie um – sondern kopieren Sie den Inhalt der einen Datei in eine “neue”, die im Editor des Zielsystems geöffnet wurde! Ansonsten können unerwünschte, unsichtbare Steuerzeichen zu Problemen führen!
Tauschen Sie dann die ersten 3 Zeilen aus (denn die Verzeichnisse sind unterschiedlich!)
und wechseln die Zeichen für “Zeile Fortsetzen” zu “\” bzw. “^”

<br /><br />
=== Die Liste der Optionen ===
Falls Sie einen Befehl suchen der im Folgenden nicht aufgelistet ist, benutzen Sie eine Befehlszeile als ob Sie FlightGear starten wollten (siehe oben) und fügen als Option nur Folgendes hinzu:
:'''-h''' listed die wichtigsten derzeit installierten Befehle auf (oder: --help)
:'''-h -v''' listed alle derzeit installierten Befehle auf (oder: -h --verbose)
<br /><br />
<font color=green>'''Im Folgenden markiert "grün" die Standardeinstellung (default)!'''</font>

==== Generelle Optionen ====
:'''--language=code'''
::Definiert die Sprache für diese Sitzung. z.B. de, nl, pl, it, fr, en, de. Dies funktioniert erst seit FlightGear Ver. 2. Siehe alle Sprach-Codes auf: http://svn.wikimedia.org/svnroot/mediawiki/trunk/phase3/languages/Names.php

:'''--version'''
::Zeigt die derzeitig installierte Version des FlightGear an. Zusätzlich wird der Pfad zum Datenverzeichnisses FG_ROOT und zum Privatverzeichnis des Benutzers angezeigt. Alle sonstigen Befehle werden ignoriert. z.B. wird angezeigt:
::{| border="1"
|-
|align="center"|'''FGFS 1.9 auf UBUNTU'''||align="center"|'''FGFS 2.0 auf Windows-XP'''
|-
||1.9.1<br />FG_ROOT=/usr/share/FlightGear/data<br />FG_HOME=/home/<small>IhrName</small>/.fgfs
||FlightGear version: 2.0.0

FG_ROOT=D:\FlightGear_2\data
<br />FG_HOME=C:/Dokumente und Einstellungen/<small>IhrName</small>/Anwendungsdaten/flightgear.org
<br />FG_SCENERY=D:/FlightGear_2/data/Scenery:D:/FlightGear_2/data/Scenery/Terrain:D:/
<br />FlightGear_2/data/Scenery/Objects:
<br />SimGear version: "2.0.0"
<br />PLIB version: 185
|}
::<small>Ich hab keine Ahnung warum die rechte, Windows-typische Liste die "\" hier teilweise als Linux-typische "/" erscheinen lässt! Meines Erachtens ist die Information trotzdem so wertvoll und verständlich, dass sich jede Klage erüberigt!</small>

:'''--fg-root=pfad'''
::Definiert wo das Datenverzeichnis ist. Wird nur benötigt wenn das Programm nicht mit den Standard-Vorgaben installiert wurde (oder Sie mehrere Datenverzeichnisse benutzen). Übliche Verzeichnisse hierfür sind:
:::'''Linux:''' /usr/share/games/FlightGear ''(oder ähnlich)''
:::'''Windows:''' C:\Programme\FlightGear\Data ''(für XP, andere ähnlich)''

:'''--fg-scenery=path'''
::Definiert wo die Szenerie-Dateien sind. Dies ist üblicherweise vorstehendes [[$FG_ROOT]]+Scenery - kann aber Ihren Erfordernissen angepasst worden sein. Vergleichen sie vorstehende "--version Tabelle": Dort sind zwei Verzeichnisse für FG_SCENERY definiert, getrennt mit einem Doppelpunkt!

:'''--browser-app=path'''
::Definiert wo der Internet-Browser ist, den Sie benutzen wollen. Wird nur benötigt wenn Sie für FlightGear nicht den Standard-Browser benutzen wollen. Dann können Sie z.B. für Windows definieren: ''--browser-app=C:\Program Files\Internet Explorer\iexplore.exe''.

:'''<font color=green>--enable-save-on-exit</font>      --disable-save-on-exit'''
::Erlaubt das Speichern der während der Sitzung benutzten Einstellungen, um diese beim nächsten Start als Anfangs-Einstellungen zu laden. Wenn Sie die Programme mit “Abbruch” (das “X” oben rechts im Programmfenster) beenden, werden die Einstellungen auf keinen Fall gesichert!

:'''--control=mode'''
::Definiert mit welchem primären Steuergerät Sie fliegen: joystick, keyboard ''(Tastatur)'', oder mouse ''(Maus)''. '''Achtung:''' Das Gerät wird nur erkannt, wenn es vor dem Starten des FlightGear angeschlossen ist!

:'''--enable-auto-coordination      <font color=green>--disable-auto-coordination'''</font>
::Aktiviert/DeAktiviert die automatische Koordination zwischen Quer- und Seitenruder. Dies erleichtert ein sauberes Kurvenfliegen – erschwert aber Landungen bei Seitenwind! Empfehlenswert für Benutzer ohne einem “3-achsigem” Joystick bzw. ohne “Fußpedale”.

:'''<font color=green>--units-feet</font>      --units-meters'''
::Definiert das internationale “feet” oder das europäische“meter” als Standard-Maßangabe. Insbesondere wenn Sie an “Multiplayer Events” (Veranstaltungen mit mehreren Teilnehmern) teilnehmen wollen, empfehlen wir dringend die Standardeinstellung “feet” beizubehalten!

:'''--config=path'''
::Lädt zusätzliche Konfigurations-Dateien für sehr spezielle Modelle. Die Pfadangabe startet hier mit “./”, dies steht für “FG_ROOT”. Also z.B.:
:::--config=./Aircraft/X15-set.xml

==== Flugzeuge und andere Modelle ====
:'''--aircraft=model     (Synonym: --vehicle=model)'''
::Definiert das gewünschte Flugzeug, z.B. ''"--aircraft=c172p"''. Sie finden alle verfügbaren Modelle als Unterverzeichnis im Verzeichnis FG_ROOT/Aircraft. In diesem Unterverzeichnis finden Sie auch die vorhandenen Model-Varianten als xyz-set.xml Datei. Für die c172p finden Sie z.B.
:::eine c172p-set.xml (das Master-Model),
:::und eine c172p-2dpanel-set.xml,
:::und eine c172p-panel-only-set.xml.
::Alle diese Dateien mit der Endung “-set.xml” definieren unterschiedliche Modelle des gleichen Flugzeuges. Sie können also 3 verschiedene c172p Modelle aufrufen (die Endung “-set.xml” lassen Sie weg):
:::# --aircraft=c172p
:::# --aircraft=c172p-2dpanel
:::# --aircraft=c172p-panel-only
::Sehen Sie auch die nachfolgende Option ''--show-aircraft'':

:'''--show-aircraft'''
::Listet eine nach Namen sortierte Liste der derzeit auf Ihrem PC verfügbaren Modelle, inklusive der Untermodelle.

:'''--livery=Name'''
::Definiert die gewünschte “Livree” = Außenanstrich, Beschriftung, etc. Siehe die Namen im Verzeichnis ''FG__ROOT/Aircraft/Model-Name/Models/Liveries''. Funktioniert noch nicht in Version 1.9.1.

:'''--min-status=status'''
::Listet im Zusammenhang mit ''--show-aircraft'' nur die Modelle, die den angegebenen Minimal-Status aufweisen. Erlaubte Stati sind: alpha, beta, early-production, production. (Werden Sie nicht ungeduldig: Das Suchen und Auflisten dauert eine Weile wenn Sie viel Modelle installiert haben!)

:'''--aircraft-dir=Pfad'''
::Setzt den Pfad zu dem Flugzeug-Verzeichnis. Als Standard wird “FG_ROOT/Aircraft” angenommen. Benutzen Sie es also nur, wenn Sie davon abweichende Verzeichnisse benutzen.

==== Anfangsposition und Ausrichtung ====
:'''<font color=green>--on-ground</font>     --in-air'''
::Startet das Model “am Boden (=ground)” oder bereits “in der Luft (=air)”. Falls Sie “in air” definieren, sollten Sie auch weitere Angaben machen (wie Höhe, Geschwindigkeit, etc.).

:'''--airport=ABCD'''
::Definiert den Startflugplatz mittels des [http://de.wikipedia.org/wiki/ICAO] '''ICAO''' Cods. Falls Sie einen “kleinen” US-Flugplatz ohne ICAO-Code benötigen, versuchen Sie es mit einer “3” anstatt des üblichen “K” als Anfangsbuchstaben.

:'''--parkpos=Ann     '''(Synonym: '''--parking-id=Ann)'''
::Definiert einen Parkplatz, ein Terminal oder ein Gate an dem ein Flug begonnen oder beendet wird. Falls für Ihren Flugplatz ein solches “parking” existiert, sollten Sie unbedingt dies als Startposition angeben, so dass Sie nicht auf einer Landebahn “erscheinen” auf der sich gerade jemand “in short Final” (Endanflug) befindet – derbe Wünsche sind Ihnen dann gewiss! Angaben zu den vorhandenen Parkpositionen finden Sie in der Datei ''FG_SCENERY/Airports/I/C/A/ICAO/ICAO.parking.xml''. Für EDDF wäre dies z.B.: ''FG_ROOT/Airports/E/D/D/EDDF.parking.xml''. Ein Beispiel wäre also:
:::--airport=EDDF --parkpos=B43

:'''--runway=nnA'''
::Startet an der Landbahnschwelle der “nnA” Landbahn (z.B.”25R” oder “18” in EDDF). Falls Sie keine --runway (oder noch besser --parkpos) -Angaben machen, wählt FlightGear die entsprechend dem Wind günstigste Landbahn des gewählten Flugplatzes selbst aus (siehe Problematik unter --parkpos).

:'''--lon=degrees     --lat=degrees'''
::Definiert einen Startpunkt irgendwo auf der Welt durch die Angabe des Längen- und Breitengrades. (Üblicherweise benutzen Sie für West- und Süd-Grad-Angaben ein Minus-Zeichen)

:'''--vor=ID      --ndb=ID      --fix=ID'''
::ID definiert einen Navigationspunkt, von dem aus die Position des Modells definiert wird (Entfernung, Richtung, etc.). Beachten Sie dass dies die ID sein muss! Also z.B. südlich von EDDF die mehrdeutige ID “RID” anstatt des eindeutigen Namens “RIED”!

:'''--offset-distance=mi     --offset-azimuth=deg'''
::Definiert den Startpunkt bezüglich der Entfernung und Richtung zu einem –airport, --vor, --ndb, --fix, --carrier.

:'''--altitude=nn'''
::Startet auf einer bestimmten Höhe. Diese Angabe setzt automatisch auch ''--in-air''. Die Höhen-Angabe ist in “feet” falls Sie nicht ausdrücklich ''--units-meters'' definiert haben. Sie sollten zusätzlich mindestens auch eine Geschwindigkeit (--vc) definieren,um nicht wie ein Stein zu Boden zu stürzen.

:'''--vc=knots      --mach=num'''
::Definiert die Anfangs-Geschwindigkeit in Knoten oder Mach.

:'''--heading=degrees      --roll=degrees      --pitch=degrees'''
::Definiert die anfängliche Ausrichtung des Models. Falls Sie nichts eingeben wird für alle 3 der Standardwert “0” gesetzt, dies würde bedeuten: waagerechter geradeaus Flug nach Norden.

:'''--glideslope=degrees      --roc=fpm'''
::Definiere den gewünschten Gleitpfad in Grad° oder in “feet per minute”. Die angegebenen Werte können positiv oder negativ sein

:'''--uBody=X     --vBody=Y      --wBody=Z'''
::Definiert die Anfangs-Geschwindigkeit für alle drei Achsen in “feet per second” - es sei denn sie haben zusätzlich “--units-meters” definiert, dann sind die Höhen-Werte in meter.

:'''--vNorth=N      --vEast=E      --vDown=D'''
::Definiert die Vector-Geschwindigkeiten für alle Richtungen: Norden (- = Süden), Osten(- = Westen), Steigen (- = Sinken). Alle Angaben sind in “feet per seconds”, es sei denn Sie haben zusätzlich “--units-meters” definiert, dann sind die Höhen-Werte in meter.

:'''--carrier=NAME'''
::Definiert den Flugzeugträger auf dem gestartet werden soll.

==== Zeitangaben ====
:'''--timeofday=param
::Überschreibt alle folgenden Zeitangaben mit standardisierten Tageszeiten. Erlaubte Eingaben sind: real (Systemzeit), dawn (Morgenröte 05:30), morning (Vormittag 07:00), noon (Mittag 12:00), afternoon (Nachmittag 15:20), dusk (Abend 18:40), evening (Nacht 19:50), midnight (Mitternacht 00:00).

:'''--time-match-local      <font color=green>--time-match-real</font>'''
::Überschreibt alle folgenden Zeitangaben: Mit der Standardeinstellung “real” wird die FlightGear-Zeit gleich der Systemzeit gesetzt – und bleibt mit dieser synchron. Dies ist sehr wünschenswert wenn Ihr “virtueller Flug” in Ihrer tatsächlichen örtlichen Umgebung statt findet (und Ihre PC-Zeit entsprechend der örtlichen Zeit eingestellt ist!). Wenn Sie jedoch irgendwo fern ab in der Welt herum-fliegen kann die Zeit am virtuellen Flugort von der lokalen Zeit um viele Stunden abweichen.
::In diesem Falle verwenden Sie also besser die “local” Einstellung – wenn Sie wissen wollen wie es dort “jetzt” aussieht! Ist insbesondere auch bei MP-Events empfehlenswert, da dann Alle die gleiche Zeit haben und gleiches sehen!

:'''--start-date-gmt=yyyy:mm:dd:hh:mm:ss'''
:'''--start-date-lat=yyyy:mm:dd:hh:mm:ss'''
:'''--start-date-sys=yyyy:mm:dd:hh:mm:ss'''
::Spezifiziert die genaue Zeit, auf die die Simulationszeit beim Start gesetzt wird.
::::“gmt” ist die Standard Weltzeit (Greenwich Mean Time)
::::“lat” ist die Zeit auf dem Längengrad (in etwa die Zeit wo geflogen wird)
::::“sys” ist Ihre Sytemzeit

:'''--time-offset=[+-]hh:mm:ss'''
::Addiert/Subtrahiert die angegebene Zeit zu den oben gesetzten Zeiten.

==== “Einfrieren” (freeze) ====
:'''--enable-freeze      <font color=green>--disable-freeze</font>'''
::Falls dies aktiv (“enable”) ist started FlightGear im “Pause” Modus und muss erst mit “p” zum Leben erweckt werden. Alle mit “freeze” eingefrorenen Aktionen, können mit einzelnen Funktion aufgehoben werden. Wenn Sie z.B. “--enable-freeze” definieren und gleichzeitig “--vs=200” dann bleiben alle Funktionen aktiv, die für die Geschwindigkeit gebraucht werde. Beachten Sie aber, dass manche Modelle sich nicht starten lassen, wenn "freeze" aktiv ist!

:'''--enable-fuel-freeze      <font color=green>--disable-fuel-freeze</font>'''
::Definiert ob während des Fluges Treibstoff verbraucht wird. Wenn “enabled” dann könne Sie mit leeren Tanks so lange fliegen wie sie wollen – was äußerst umweltfreundlich ist – aber auch absolut unwirklich. Echte Simulations-Freunde benutzen dies nicht, da sie auch sehen wollen wie unterschiedlich sich ein Flugzeug verhält , je nachdem ob die Tanks voll oder leer sind. Gerade bei Landungen und Starts macht sich dies deutlich bemerkbar!

:'''--enable-clock-freeze      <font color=green>--disable-clock-freeze</font>'''
::Definiert ob die Uhr normal läuft – oder angehalten wird. (Führt bei Ver.1.9 dazu, dass der Startbildschirm stehen bleibt! – Also nicht funktionsfähig!)

==== Umwelt / Wetter ====
:'''--enable-real-weather     -fetch <font color=green>--disable-real-weather-fetch</font>'''
::Aktivire/DeAktiviere das Herunterladen und ständige Aktualisieren echter Wetterdaten. Dementsprechend werden die Wettereinstellungen im FlightGear vorgenommen/geändert. Dies macht nur Sinn wenn Sie eine ständige Verbindung zum Internet haben – ansonsten siehe die nächste Option.

:'''--metar=MetarString'''
::Gegenüber dem Vorstehenden können Sie hier ohne Internet eine Wetter-Meldung eingeben, die Sie z.B. über Radio oder Telefon, etc. bekommen haben. Diese gilt dann für den ganzen Flug. Das Format ist z.B.:
:::--metar="EDDF 040728Z 29010KT 9999 CLR 19/M01 A2992"
:::''“Frankfurt am Tag 4 (des Monats) um 7:28 GMT: Wind aus 290° mit 10 Knoten, Sicht > 10 km, Keine Bewölkung, Temperatur 19°, Taupunkt -1°, QNH 29.92”''
::Es können zwischen Europäischen und Amerikanischen Formaten kleine Unterschiede auftreten (z.B. km, QNH millibar/Hektopascal, u.ä.)

:'''--ceiling=FT ASL[:Dicke FT]'''
::Definiert eine Wolkendecke auf der angegebenen Höhe über ASL (Meereshöhe) in Fuss. Dazu kann auch die Dicke der Wolkendecke in Fuss definiert werden.

:'''--wind=Grad@kt'''
::"--wind=270@10" würde z.B. bedeuten: Wind aus Westen mit 10 Knoten

:'''--turbulence=n.n'''
::Definiert Turbulenzen zwischen 0.0 (“calm”=schwach) bis 1.0 (“severe”=sehr stark)
:'''--random-wind'''
::Durch Zufallsgenerator erzeugter Wind aus unterschiedlichen Richtungen mit unterschiedlichen Stärken.

:'''--season=param'''
::Definiert die Jahreszeit, das heißt vereinfacht: Weiße oder grüne Landschaft! Erlaubt sind nur “summer” (Sommer = Standardeinstellung) und “winter”

:'''<font color=green>--visibility=meters</font>      --visibility-miles=miles'''
::Setzt die Angabe der Sichtweite in Metern oder Meilen. Achtung: Standard ist in Meter!

==== Features (Ausstattung) ====
:'''<font color=green>--enable-ai-models</font>      --disable-ai-models'''
::Aktiviere/DeAktiviere die Anzeige von AI-Modellen. AI (artificial Intelligence) = KI (künstliche Intelligenz) – dies sind Modelle ohne einem “menschlichen Piloten” die mit einem vorgegebenen Flugplan herum-fliegen (oder parken). Bei “Multiplayer Events” ist es besser diese Funktion auszuschalten, da die Mitspieler andere AI-Modelle oder Flüge sehen. Um dies sicher-zustelle setzen Sie zusätzlich: '''--props:/sim/traffic-manager/enabled=false'''.

:'''--ai-scenario=name'''
::Aktiviert spezielle AI-Szenarien in denen Sie fliegen. (z.B. --ai-scenario=droptank_demo). Für eine Liste der verfügbaren Demos siehe das Verzeichnis FG_Root/AI (die dortigen *.xml Dateien!)

:'''--enable-random-objects      <font color=green>--disable-random-objects</font>'''
::Aktiviere/DeAktiviere das zufällige Einfügen von Objekten (wie z.B. Gebäude, Bäume, etc.)

==== Rendering / Wiedergabe Optionen ====
Beachten Sie, dass sich die folgenden Optionen deutlich auf die Prozessor-Auslastung auswirken können und auch die Grafikkarte überbelasten können! Wenn Sie mit ihrer FPS nicht mehr zufrieden sind, versuchen Sie einzelne Optionen zu minimieren.
:'''--aspect-ratio-multiplier=n'''
::Definiert den Multiplikator für das Seitenverhältnis Ihres Bildschirmes

:'''--bpp=depth'''
::Definiert wie viele Bits per Pixel verwendet werden.

:'''<font color=green>--enable-clouds</font>      --disable-clouds'''
::Aktiviert/DeAktiviert Wolkenschichten

:'''--enable-clouds3d      <font color=green>--disable-clouds3d</font>'''
::Aktiviert/DeAktiviert 3D Wolken. Diese sind sehr sehr schön anzusehen - können aber ältere Systemen (abhängig von deren GL SL Shader) überfordern!

:'''--enable-distance-attenuation      <font color=green> --disable-distance-attenuation'''</font>
::Aktiviere/DeAktiviere eine realistischere Anflug- und Landebahn-Lichter Dämpfung während Sie noch entfernt vom Flughafen sind.

:'''--enable-enhanced-lighting      <font color=green>--disable-enhanced-lighting</font>'''
::Aktiviere/DeAktiviere verstärkte Anflug- und Landebahn-Beleuchtung

:'''--enable-fullscreen      <font color=green>--disable-fullscreen</font>'''
::Aktiviere/DeAktiviere(Standard) den “Vollbild-Modus” Ihres Bildschirmes.

:'''--enable-game-mode      <font color=green>--disable-game-mode</font>'''
::Aktiviere/DeAktiviere den Vollbild-Modus für 3DFX Grafik-Karten (nur für frühere VOODOO-Graphics)

:'''--enable-mouse-pointer      <font color=green>--disable-mouse-pointer</font>'''
::Aktiviere/DeAktiviere den extra Mauszeiger. Sinnvoll nur bei älteren 3DFX Grafik-Karten (nur für frühere VOODOO-Graphics)

:'''<font color=green>--enable-splash-screen</font>      --disable-splash-screen'''
::Aktiviere/DeAktiviere das rotierende 3DFX-Logo wenn die Beschleunigungs-Stufe der Grafik-Karte initialisiert wird (nur für frühere VOODOO-Graphics)

:'''<font color=green>--enable-horizon-effect</font>      --disable-horizon-effect'''
::Aktiviere/DeAktiviere Vergrößerungs-Effekte bei Sternen nahe des Horizonts

:'''<font color=green>--enable-panel</font>      --disable-panel'''
::Ein-/Ausblenden des Instrumentenbrettes

:'''<font color=green>--enable-skyblend</font>      --disable-skyblend'''
::Aktiviere/DeAktiviere Nebel- und Dunst- Effecte

:'''<font color=green>--enable-specular-highlight</font>      --disable-specular-highlight'''
::Aktiviere/DeAktiviere spiegelnde Reflektionen auf strukturierten Oberflächen

:'''<font color=green>--enable-textures</font>      --disable-textures'''
::Aktiviere/DeAktiviere die Anzeige von Gewebe-Strukturen

:'''--enable-wireframe     <font color=green>--disable-wireframe'''</font>
::Aktiviere/DeAktiviere die Anzeige des “Drahtgitter-Modus”. Probieren Sie es mal, wenn Sie sehen wollen wie die Struktur Ihres Modells aussieht!

:'''--fog-disable      --fog-fastest      <font color=green>--fog-nicest'''</font>
::Variiert die Komplexität der Nebel-Darstellung: Um die Redering-Aufwendungen für den PC und die Grafikkarte zu reduzieren, verschwinden entfernte Landschaften im Dunst/Nebel. Wenn Sie dagegen “fog-disable” aktivieren, können Sie zwar weiter sehen – aber dafür geht evtl. Ihre FPS-Rate in die Knie. “fog-fastest” ist ein Kompromiss dazwischen: Nicht ganz realistischer Nebel/Dunst – aber dafür verbesserte FPS.

:'''--fov=Grad      <font color=green>(Standard=55°)</font>'''
::Setzt den Blickwinkel (Field of View) in Grad°

:'''--geometry=WWWxHHH'''
::Definiert die Bildschirm-Auflösung, z.B.: --geometry=1024x768

:'''<font color=green>--shading-smooth</font>      --shading-flat'''
::"--shading-flat” (flächige Schattierungen) ist deutlich schneller – aber weniger schön!!

:'''--texture-filtering=N      <font color=green>(Standard N=1)</font>'''
::Definiert die Einstellung des richtungsabhängigen Heraus-Filterns von Gewebestrukturen. Gültige Werte sind: 1, 2, 4, 8, oder 16.

:'''--view-offset=xxx'''
::Erlaubt das Verändern des Vorwärts-Blickes (view) als eine Abweichung von “gerade aus”. Gültige Werte sind: LEFT (links), RIGHT (rechts), CENTER (zentriert), oder eine Angabe in Grad°. Diese Angaben werden insbesondere bei der Benutzung mehrerer Bildschirme verwendet.

==== HUD Optionen (Head-Up-Display) ====
:'''--enable-hud      <font color=green>--disable-hud'''</font>
::Aktiviert/DeAktiviert die Instrumenten-Anzeige auf der Frontscheibe

:'''<font color=green>--enable-hud-3d</font>      --disable-hud-3d'''
::Aktiviert/DeAktiviert die HUD-Anzeige in 3D

:'''<font color=green>--enable-anti-alias-hud</font>      --disable-anti-alias-hud'''
::Aktivieren/DeAktivieren Höhen- und Tiefen-Filter um “Alias-Effekte” (Doppelbilder) zu vermeiden (siehe http://de.wikipedia.org/wiki/Alias-Effekt )

:'''--hud-tris'''
::Aktiviert die Anzeige der Anzahl der HUD-Bildpunkte

:'''--hud-culled'''
::Aktiviert die Anzeige der ausgewählten HUD-Bildpunkte

==== Radios ====
Mit Optionen können nur die "aktiven" Frequenzen gesetzt werden. Wenn Sie auch die "Standby" Frequencen setzen wollen müssen sie die Property setzen (siehe --props:... unter "features").
:'''--com1=Frequenz      --com2=Frequenz'''
::Setzt die 2 Kommunikations-Frequenzen (für ATC, FGCOM, etc.)

:'''--nav1=[radial:]Frequenz      --nav2=[radial:]Frequenz'''
::Setzt die 2 Navigations-Frequenzen (für VOR oder ILS). Bei vielen Modellen kann der Autopilot nur mit “nav1” zusammenarbeiten. Achten Sie darauf, dass ein angegebenes Radial vor der Frequenz stehen muss, z.B.: --nav1=248:109.50 (ist ILS EDDF 25R)

:'''--adf=[radial:]Frequenz'''
::Setzt die ADF-Frequenz. Einige Flugmodelle bieten auch ein zweites ADF in einem speziellen Einstellungs-Fenster oder zum Einstellen direkt auf dem Instrumentenbrett.

:'''--dme=nav1|nav2|Frequenz'''
::Sehr oft sind VOR und DME integriert in eine Station/Frequenz. Falls Ihr Flugzeug nur eine einzige DME-Anzeige hat, müssen Sie definieren von welchem NAV die Entfernungsangabe verwendet werden soll. Für Allein stehende DME's geben Sie die Frequenz des DME an.

==== Audio ====
Die hier gezeigten Einstellungen betreffen nur die “FlightGear internen” Geräusche. Andere Funktionen wie z.B. FGCOM, Festival, etc. sind davon nicht betroffen!
:'''<font color=green>--enable-sound</font>      --disable-sound'''
::Aktiviere/DeAktiviere die Umgebungsgeräusche im Model.

:'''--show-sound-devices'''
::Liste die vorhandenen Audio-Geräte auf – erst ab Version 2 verfügbar.

:'''--sound-device=device'''
::Weist FlightGear an, dieses Audio-Gerät zu benutzen (wenn mehrere vorhanden sind). Ist auch erst ab Version 2 verfügbar!

:'''<font color=green>--enable-intro-music</font>      --disable-intro-music'''
::Aktiviere/DeAktiviere das Abspielen eins Musikstückes während des FGFS-Starts – diese Option ist unabhängig von den anderen Audio-Einstellungen.

==== Netzwerk Optionen ====
:'''--callsign=IhrCode'''
::Definieren Sie Ihren “Rufnamen” für die Sitzung, sollten maximal nur 7 alphanummerische Zeichen sein.

:'''--multiplay=dir,Hz,host,port,'''
::Definiert die Verbindung zu den Multiplayer-Servern, siehe [http://wiki.flightgear.org/index.php/Mpmap] '''MPmap'''

:'''--httpd=port'''
::Ein Standard HTTP-Server zur generellen Nutzung. Standard Port = 5500.

:'''--telnet=port'''
::Ein Standard Telnet-Server für das Auflisten aller “Internal Properties” im Internet-Browser – dies erleichtert das Durchsuchen der Properties ungemein. Standard Port = 5501.

:'''--jpg-httpd=port'''
::Ein Standard HTTP-server zur generellen Nutzung. Standard Port = 5502.

:'''--proxy=[user:password@]host:port'''
::Spezifiziert den Proxy-Server, falls Sie einen benutzen (müssen)

:'''Sonder Verbindungen “socket”'''
::'''--generic'''=socket,out,10,localhost,16661,udp,'''fgcom'''
:::siehe http://wiki.flightgear.org/index.php/Fgcom
::'''--atlas'''=socket,out,1,localhost,5505,udp
:::siehe http://wiki.flightgear.org/index.php/Atlas

==== Navigationsgerät Eingaben ====
:'''--wp=ID[@alt]'''
::Definiert einen an-zufliegenden “waypoint” (Wegpunkt). “ID” können alle Navigationspunkte sein, wie z.B. Flugplatz, VOR, NDB, etc. Der optionale Zusatz “@alt” definiert eine Höhe die an dem Punkt erreicht worden sein soll. z.B.: ''--wp=MTR@4000'' heißt: Überfliege den VOR “MTR” (Metro bei Frankfurt) auf 4000 ft Höhe”. Sie können mehrere aufeinander folgende “waypoints” eingeben, indem Sie den Befehl entsprechend oft wiederholen.
:'''--flight-plan=[file]'''
::Anstatt einzelne “waypoints” einzugebend, wie vorstehend beschrieben, können Sie hier eine Datei angeben, in der diese Punkte definiert sind. Somit könne Sie sich viele verschieden Flugpläne für verschiedene Flüge parat halten. Diese Dateien sind einfache Textdateien in der in jeder Zeile ein "WayPoint" steht. z.B.:
::::{| border=1
|-
|style "width:400px" | Cadit <br /> SPI@32000 <br /> UIN <br /> <small>... e.t.c.</small>
|}
:::<small>''Vergleiche Abflug SID "ROCKY4" von KIND.''</small>
::Diese Dateien speichern Sie am Besten in das Verzeichnis ''FG_ROOT/AI/FlightPlans'' unter irgendeinem Namen, z.B. den obigen als "KIND-DEP.wp". Sie können die Datei dann auch aus dem FlightGear heraus aufrufen: Menü --> Autopilot --> Route Manger --> Load list. <small>(Keine Ahnung warume es kein "Save List" gibt!!)</small>

==== Flug-Modell (FDM) ====
:'''--fdm=abcd'''
::Überschreibt welches zentrale Simulations-Programm benutzt werden soll. Zur Auswahl stehen: jsb, larcsim, yasim, magic, balloon, external, pipe, ada, null . Diese Auswahl müssen Sie nicht treffen, da die gestarteten Flugmodelle dies selbst tun.

:'''--aero=aircraft'''
::Überschreibt welches flugtechnische Model verwendet werden soll. Diese Auswahl müssen Sie nicht treffen, da die gestarteten Flugmodelle dies selbst tun.

:'''--model-hz=n'''
::Die Geschwindigkeit, mit der das FDM läuft. Dies wird angegeben in “Iterationen per Sekunde”.

:'''--speed=n'''
::Betreibe das FDM mit einem Mehrfachen (n) der normalen Zeit.

:'''--trim      <font color=green>--notrim'''</font>
::Definieren Sie "trim" nur für das JSBSim-Model!!! Wird normalerweise vom Modell automatisch gesteuert!

==== Fehler- und Test-Optionen ====
:'''--failure=system'''
::Simuliert den Ausfall eines Betriebssystems während des Fluges. Kann langweilige Flüge sehr interessant machen! Erlaubte Ausfall-Systeme sind: pitot, static, vacuum, electrical. Sie können mehrere Systeme definieren (bzw. zum Ausfallen auffordern – aber Sie wissen nie wann die sich dann dazu entschließen es zu tun!).

:'''--enable-fpe'''
::Erlaube den Abbruch des Programms wenn ein “Floating Point Exception” (Gleitkomma-Fehler) auftritt.

:'''--fgviewer'''
::Anstatt des ganzen FlightGear-Simulator wird nur der einfache “OSG viewer” (OSG Betrachter) geladen und ausgeführt. Dies ist hilfreich beim Testen neuer Flugmodelle.

:'''--log-level=LEVEL'''
::Definiert welche (und damit wie viele) Fehler protokolliert werden sollen. Erlaubte Werte sind: bulk, debug, info, warn, alert. Bei “alert” werden nur die schweren Fehler gemeldet, bei “bulk” wird alles ausgedruckt.

:'''--prop:[type:]name=wert'''
::Mit diesem Befehl können Sie jeden Wert jeder Eigenschaft (“Property”) des FlightGear initialisieren – und das heißt Sie sollten wissen was Sie tun! Ein paar (unkritische) Beispiele:
:::--prop:/engines/engine[0]/running=true → startet den ersten Motor direkt beim Initialisieren
:::--prop:/consumables/fuels/tank[0]/level-gal=10 → füllt Tank eins mit 10 gal.
:::--prop:/consumables/fuels/tank[1]/level-gal=10 → füllt Tank zwei mit 10 gal.
:::--prop:/instrumentation/comm[1]/frequencies/standby-mhz=121.8 → setzt die Bodenfrequenz (GND) in EDDF auf standby im COM2.
::Optional können Sie mit “type” den Datentyp des Wertes angeben. Erlaubt sind double, string, boolean (falls Sie nicht wissen was das ist → dies sollte nur ein Fachmann tun! Normalerweise findet FlightGear selbst den richtigen Typ).
:::z.B: --prop:boolean:/sim[0]/ai/enabled=true → aktiviert die KI-Modelle

:'''--trace-read=prop      --trace-write=prop'''
::Protokolliere alle Lese- (read) und/oder alle Schreib- (write) Zugriffe auf die angegebene Properties. Sie könne diese Option mehrfach benutzen um gleichzeitig mehrere Properties zu verfolgen.

[[Category:FlightGear]]
[[Category:Lists]]

[[en:Command line options]]
[[pl:Opcje wiersza poleceń]]

Howto:Add sound effects to aircraft

2021-08-15T11:00:21Z

Sfrsfr: /* Configuration tags */ <position> clarify coordinate system; add note about inverted Y axis

You can '''add sound effects to aircraft''' by adding the sound samples and configuring the sound effects in XML files. The sound effects can be conditional and the sound's pitch and volume can depend on properties in the property tree.

{{note|This text is partially incorrect/outdated. Especially how the final volume/pitch is calculated. Make sure to also read the {{fgdata source|Docs/README.xmlsound|text=official documentation}}.}}

Some sound effects are added other ways. For example, sounds from avionics like navigation radio receivers are automatically added when you add those radios.

{{FGCquote|1= The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/28505220/ | title = <nowiki>Re: [Flightgear-devel] Stereo sounds no longer supported?</nowiki> | author = <nowiki>syd adams</nowiki> | date = Dec 7th, 2011 }}}}

{{FGCquote|1= The old way was that the stereo sound would always play the left channel on the left side. Now you split the sound and place it in 3D space. When you turn your head, the speaker the left side sound comes out of changes with you|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257291#p257291 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>bugman</nowiki> | date = Sep 14th, 2015 }}}}

{{FGCquote|1= All sounds must now be mono point sources, and stereo simply requires the two sound sources to be positioned in the 3D environment. |2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34100151/ | title = <nowiki>[Flightgear-devel] Audit and proposal for handling non-supported stereo sound files in FGAddon via the 3D sound engine.</nowiki> | author = <nowiki>Edward d'Auvergne</nowiki> | date = May 10th, 2015 }}}}

{{FGCquote|1= We use OpenAL for 3D positional audio and most OpenAL implementations can only handle one stereo file.Also Stereo files will not work in 3d space, so they will not be positional.But most aircraft developers did not know that and used several stereo files expecting everything to work properly but the truth was that in most implementations just one of those stereo files was played.And if you think of it, stereo separation does not work for boarding music either since it plays left channel to your left ear and right channel to your right ear. But in reality boarding music is played left channel to the left audio channel in the aircraft and right channel to the right audio channel in the aircraft.This works the same as normal stereo if you enter the aircraft, but will, reverse once you turn around.So the solution is to split up the stereo file into two mono files and play the proper channel at the proper side of the passenger compartment.|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257289#p257289 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>erik</nowiki> | date = Sep 14th, 2015 }}}}

== Sound configuration files ==
The sound configuration files are [[PropertyList XML files]].

The top level sound configuration file is composed of a <code><fx></code> and a <code><name></code> tag, a <code><path></code> to a sound sample file and zero or more <code><volume></code> and/or <code><pitch></code>definitions.

Paths are relative to [[$FG_ROOT]], but absolute paths may also be used.

Comments are bracketed with <code></code>.

=== Example ===
This example would define an engine sound effect for a piston engine driven aeroplane.

The sound effect representing the engine is located in <code>$FG_ROOT/Sounds</code> and is named <code>wasp.wav</code>. The effect is started when the property <code>/engines/engine/running</code> becomes non-zero.

When that happens, the sound will be played looped (see <code><mode></code>) until the property returns zero again. As you can see the volume is dependent on the property <code>/engines/engine/mp-osi</code>, and the pitch of the sound depends on the property <code>/engines/engine/rpm</code>.

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>
<fx>
<engine>
<name>engine</name>
<path>Sounds/wasp.wav</path>
<mode>looped</mode>
<condition>
<property>/engines/engine/running</property>
</condition>
<volume>
<property>/engines/engine/mp-osi</property>
<factor>0.005</factor>
<min>0.15</min>
<max>0.5</max>
<offset>0.15</offset>
</volume>
<pitch>
<property>/engines/engine/rpm</property>
<factor>0.0012</factor>
<min>0.3</min>
<max>5.0</max>
<offset>0.3</offset>
</pitch>
</engine>
</fx>
</PropertyList>
</syntaxhighlight>

=== Inclusion from the aircraft-set.xml file ===
In order for the sound configuration to be used, it has to be included from the [[aircraft-set.xml]] file.

This can be done by adding the path to the file relative to the aircraft's base path within the <code><sim></code> tags in the aircraft-set.xml file..

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>

<sim>

<sound>
<path type="string">My-sound-config.xml</path>
</sound>

</sim>

</PropertyList>
</syntaxhighlight>

== Configuration tags ==

; <code><fx></code>
: Named FX subtree living under /sim/sound

; <code>< ... ></code>
: This is the event separator. The text inside the brackets can be anything, but it is advised to give it a meaningful name like: crank, engine, rumble, gear, squeal, flap, wind or stall.

: The value can be defined multiple times, thus anything which is related may have the same name (grouping them together).

; <code><name></code>
: This defines the name of the event. This name is used internally and, although it can me defined multiple times in the same file, should normally have an unique value.

: Multiple definitions of the same name will allow multiple sections to interfere in the starting and stopping of the sample.

: This method can't be used to control the pitch or volume of the sample, but instead multiple volume or pitch section should be included inside the same event.

: The types "raise" and "fall" will stop the playback of the sample regardless of any other event. This means that when the type "raise" is supplied, sample playback will stop when the event turns false. Using the type "fall" will stop playback when the event turns true.

: IMPORTANT
:: If the trigger is used for anything else but stopping the sound at a certain event, all sections with the same name ''should'' have exactly the same sections for everything but property and type.

:: In the case of just stopping the sample at a certain event, the sections for path, volume and pitch may be omitted.

; <code><path></code>
: This defined the path to the sound file. The path is relative to the FlightGear root directory but could be specified absolute.

: The sound format must be mono.

; <code><condition></code>
: Define a condition that triggers the event.

: For a complete description of the FlightGear conditions, please read docs-mini/README.conditions or read the [[Conditions]] article on the wikie.

: An event should define either a condition or a property.

; <code><property></code>
: Define which property triggers the event, and refers to a node in the FlightGear property tree.

: Action is taken when the property is non zero.

: A more sophisticated mechanism to trigger the event is described in <condition></code>

; <code><mode></code>
: This defines how the sample should be played:

:; once
:: The sample is played once. This is the default.

:; looped
:: The sample plays continuously, until the event turns false.

:; in-transit
:: the sample plays continuously, while the property is changing its value.

; <code><type></code>
: This defines the type of this sample, each type also have seperate volume slider in sound settings menu:

:; fx
:: This is the default type and doesn't need to be defined.

:; avionics
:: Sounds set to this type don't have a position and orientation but are treated as if it's mounted to the aircraft panel.

:: It is up to the user to define if it can always be heard or only when in cockpit view.

:; atc
:: Is used by the ATC chatter add-on.

; <code><delay-sec></code>
: Delay after which the sound starts playing.

: This is useful to let a property start two sounds at the same time, where the second is delayed until the first stopped playing.

; <code><volume></code> / <code><pitch></code>
: Volume or Pitch definition.

: Currently there may be up to 5 volume and up to 5 pitch definitions defined within one sound event.

: There are two important results from each <volume> and <pitch> section: the offset and the value. Normally all offset values from the different volume/pitch are added together to create the total offset. The values from each <volume> or <pitch> section are multiplied together to create an final value. Then the volume (or pitch, respectively) is set to total offset + final value.

: A special condition occurs when the value of factor is negative, in which case the offset doesn't get added to the other offset values but instead will be used in the multiplication section.

: Pitch final output can range from 0 to 2. 1 represents the original pitch of the sound file. Offset defaults to 1, meaning that if no specific <pitch> parameters are given the file will be played at its original pitch.

: Volume final output can range from 0 to 1. 1 represents full volume and 0 is silence.

:; <code><expression></code>
:: Defines an expression, and will replace all other tags in this volume/pitch tag.

:; <code><property></code>
:: Defines which property supplies the value for the calculation.

:: Either a <property> or an <internal> should be defined. If none is defined, the property reverts to its default. For volume this is 0, meaning the sound will not be audible at all.

:: The value is treated as a floating point number.

:; <code><internal></code>
:: Defines which internal variable should be used for the calculation.

:: The value is treated as a floating point number.

:: The following internals are available at this time:

::; dt_play
::: The number of seconds since the sound started playing.

::; dt_stop
::: The number of seconds after the sound has stopped.

:; <code><type></code>
:: Defines the function that should be used upon the property before it is used for calculating the net result:

::; lin
::: Linear handling of the property value. This is the default.

::; ln
:: Convert the property value to a natural logarithmic value before scaling it.

::: Anything below 1 will return zero.

::; log
::: convert the property value to a true logarithmic value before scaling it. (log base 10)

::: Anything below 1 will return zero.

::; inv
::: Inverse linear handling (1/x).

::; abs
:: Absolute handling of the value (always positive).

::; sqrt
::: Calculate the square root of the absolute value before scaling it.

:; <code><factor></code>
:: Defines the multiplication factor for the property value.

:: A special condition is when scale is defined as a negative value. In this case the result of |<scale>| * <property) will be subtracted from <default>

:; <code><offset></code>
:: The initial value for this sound.

:: This value is also used as an offset value for calculating the end result.

:; <code><random></code>
:: Add a bit of randomness to the offset. Only used for pitch.

:; <code><min></code>
:: Minimum allowed value.

:: This is useful if sounds start to sound funny. Anything lower will be truncated to this value.

:; <code><max></code>
:: Maximum allowed value.

:: This is useful if sounds gets to loud. Anything higher will be truncated to this value.

:: Keep in mind that min & max are applied first, then offset. So for example if min = 0, max = 0.5 and offset = 1.0, then the resulting values will range 1 to 1.5.

; <code><position></code>
: Specify the position of the sounds source relative to the 3D models center.

: The coordinate system used is a left hand coordinate system where +Y = left, -Y = right, -Z = down, +Z = up, -X = forward, +X = aft. Distances are in meters.

: It's important to note that for sounds the Y axis is inverted compared to e.g. object animation coordinates (see also [[Howto:3D_Aircraft_Models]]).

: The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!

: Also take notice that the values should not be 0.0, since that can produce sound artifacts on some sound cards.

; <code><x></code>
: X dimension offset (-X = forward, +X = aft, in meters)

; <code><y></code>
: Y dimension offset (+Y = left, -Y = right)

; <code><z></code>
: Z dimension offset (-Z = down, +Z = up)

; <code><orientation></code>
: Specify the orientation of the sounds source.

: The zero vector is default, indicating that a Source is not directional.

: Specifying a non-zero vector will make the Source directional in the X,Y,Z direction

; <code><x></code>
: X dimension

; <code><y></code>
: Y dimension

; <code><z></code>
: Z dimension

; <code><inner-angle></code>
: The inner edge of the audio cone in degrees (0.0 - 360.0).

: Any sound withing that angle will be played at the current gain.

; <code><outer-angle></code>
: The outer edge of the audio cone in degrees (0.0 - 360.0).

: Any sound beyond the outer cone will be played at "outer-gain" volume.

; <code><outer-gain></code>
: The gain at the outer edge of the cone.

; <code><reference-dist></code>
: Set a reference distance of sound in meters. This is the distance where the volume is at its maximum. Default is 60.

: Volume is clamped to this maximum for any distance below.

: Volume is attenuated for any distance above.

: Attenuation depends on reference and maximum distance. See OpenAL specification on "AL_INVERSE_DISTANCE_CLAMPED" mode for details on exact computation.

; <code><max-dist></code>
: Set the maximum audible distance for the sound in meters. Default is 6000.

: Sound is cut-off above this distance.

== Creating a configuration file ==

To make things easy, there is a default value for most entries to allow a
sane configuration when a certain entry is omitted.

{| class="wikitable"
! Tag !! Default value
|-
| '''<type>''' || lin
|-
| '''<factor>''' || 1.0
|-
| '''<offset>''' || 0.0 for volume, 1.0 for pitch
|-
| '''<min>''' || 0.0
|-
| '''<max>''' || 0.0 (don't check)
|}

Calculations are made the following way (for both pitch and volume):
<syntaxhighlight lang="cpp">
value = 0;
offs = 0;

for (n = 0; n < max; n++) {
if (factor < 0) {
value += offset[n] - abs(factor[n]) * function(property[n]);
} else {
value *= factor[n] * function(property[n]);
offs += offset[n];
}
}

volume = offs + value;
if (volume > 1.0) vol = 1.0;
</syntaxhighlight>
where function can be one of: lin, ln, log, inv, abs or sqrt

== Multiplayer sound ==
The multiplayer sound file works just as the normal sound file, except it should reside in <code>/sim/model/sound</code> instead of <code>/sim/sound</code>. Make sure it depends on properties that are [[Howto:Transmit_properties_over_MP|transmitted over MP]].

== Recommended audio file formats ==
{{note|The sound sample '''must be in mono''' format. This is because it can not be put in a 3D context otherwise. Also, as of at least June 2015 '''stereo samples will not be played'''.}}

There some considerations on the quality to the audio files. As a rule of thumb, any computer is able to playback sounds in DVD-quality (48 kHz/24 bits).
Macs still has trouble reading 32 bit files. Most standard sound cards also can't playback 32 bit files.

From a listeners point of view, anything above 44.1 kHz and 24 bits is only useful for high end music. Personally, I would think that 44.1 kHz with 16 bits should be more than enough to play engine sounds and alarms from the cockpit. Consider the disk-space against the gain in audio quality!

== Preventing sounds from playing when sim starts ==
Some times it can be hard to prevent sounds from playing right away, if the condition starts to evaluate to true. A hack to get this to work is to multiply the volume with a property that you in nasal set to true some seconds after the sim has been initialized.

== Bugs in the sound system ==
* The Doppler effect if you pass an aircraft in high speed sometimes is way too high pitch.
* None of the position coordinates must not be 0.0 as described above.

== Related content ==
=== Wiki articles ===
* [[Conditions]]
* [[Expressions]]
* [[Howto:Reload sound configuration without restarting]]

=== Readme file ===
* {{readme file|xmlsound}}

=== Source code ===
* {{simgear file|simgear/sound/xmlsound.hxx}}
* {{simgear file|simgear/sound/xmlsound.cxx}}
* {{flightgear file|src/Sound/fg_fx.hxx}}
* {{flightgear file|src/Sound/fg_fx.cxx}}

[[Category:Aircraft enhancement]]

Howto:Add sound effects to aircraft

2021-08-10T20:39:48Z

Sfrsfr: added Note about outdated article and refer to the official documentation

You can '''add sound effects to aircraft''' by adding the sound samples and configuring the sound effects in XML files. The sound effects can be conditional and the sound's pitch and volume can depend on properties in the property tree.

'''NOTE:''' this text is partially incorrect/outdated. Especially how the final volume/pitch is calculated. Make sure to also read the [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.xmlsound official documentation].

Some sound effects are added other ways. For example, sounds from avionics like navigation radio receivers are automatically added when you add those radios.

{{FGCquote|1= The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/28505220/ | title = <nowiki>Re: [Flightgear-devel] Stereo sounds no longer supported?</nowiki> | author = <nowiki>syd adams</nowiki> | date = Dec 7th, 2011 }}}}

{{FGCquote|1= The old way was that the stereo sound would always play the left channel on the left side. Now you split the sound and place it in 3D space. When you turn your head, the speaker the left side sound comes out of changes with you|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257291#p257291 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>bugman</nowiki> | date = Sep 14th, 2015 }}}}

{{FGCquote|1= All sounds must now be mono point sources, and stereo simply requires the two sound sources to be positioned in the 3D environment. |2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34100151/ | title = <nowiki>[Flightgear-devel] Audit and proposal for handling non-supported stereo sound files in FGAddon via the 3D sound engine.</nowiki> | author = <nowiki>Edward d'Auvergne</nowiki> | date = May 10th, 2015 }}}}

{{FGCquote|1= We use OpenAL for 3D positional audio and most OpenAL implementations can only handle one stereo file.Also Stereo files will not work in 3d space, so they will not be positional.But most aircraft developers did not know that and used several stereo files expecting everything to work properly but the truth was that in most implementations just one of those stereo files was played.And if you think of it, stereo separation does not work for boarding music either since it plays left channel to your left ear and right channel to your right ear. But in reality boarding music is played left channel to the left audio channel in the aircraft and right channel to the right audio channel in the aircraft.This works the same as normal stereo if you enter the aircraft, but will, reverse once you turn around.So the solution is to split up the stereo file into two mono files and play the proper channel at the proper side of the passenger compartment.|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257289#p257289 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>erik</nowiki> | date = Sep 14th, 2015 }}}}

== Sound configuration files ==
The sound configuration files are [[PropertyList XML files]].

The top level sound configuration file is composed of a <code><fx></code> and a <code><name></code> tag, a <code><path></code> to a sound sample file and zero or more <code><volume></code> and/or <code><pitch></code>definitions.

Paths are relative to [[$FG_ROOT]], but absolute paths may also be used.

Comments are bracketed with <code></code>.

=== Example ===
This example would define an engine sound effect for a piston engine driven aeroplane.

The sound effect representing the engine is located in <code>$FG_ROOT/Sounds</code> and is named <code>wasp.wav</code>. The effect is started when the property <code>/engines/engine/running</code> becomes non-zero.

When that happens, the sound will be played looped (see <code><mode></code>) until the property returns zero again. As you can see the volume is dependent on the property <code>/engines/engine/mp-osi</code>, and the pitch of the sound depends on the property <code>/engines/engine/rpm</code>.

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>
<fx>
<engine>
<name>engine</name>
<path>Sounds/wasp.wav</path>
<mode>looped</mode>
<condition>
<property>/engines/engine/running</property>
</condition>
<volume>
<property>/engines/engine/mp-osi</property>
<factor>0.005</factor>
<min>0.15</min>
<max>0.5</max>
<offset>0.15</offset>
</volume>
<pitch>
<property>/engines/engine/rpm</property>
<factor>0.0012</factor>
<min>0.3</min>
<max>5.0</max>
<offset>0.3</offset>
</pitch>
</engine>
</fx>
</PropertyList>
</syntaxhighlight>

=== Inclusion from the aircraft-set.xml file ===
In order for the sound configuration to be used, it has to be included from the [[aircraft-set.xml]] file.

This can be done by adding the path to the file relative to the aircraft's base path within the <code><sim></code> tags in the aircraft-set.xml file..

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>

<sim>

<sound>
<path type="string">My-sound-config.xml</path>
</sound>

</sim>

</PropertyList>
</syntaxhighlight>

== Configuration tags ==

; <code><fx></code>
: Named FX subtree living under /sim/sound

; <code>< ... ></code>
: This is the event separator. The text inside the brackets can be anything, but it is advised to give it a meaningful name like: crank, engine, rumble, gear, squeal, flap, wind or stall.

: The value can be defined multiple times, thus anything which is related may have the same name (grouping them together).

; <code><name></code>
: This defines the name of the event. This name is used internally and, although it can me defined multiple times in the same file, should normally have an unique value.

: Multiple definitions of the same name will allow multiple sections to interfere in the starting and stopping of the sample.

: This method can't be used to control the pitch or volume of the sample, but instead multiple volume or pitch section should be included inside the same event.

: The types "raise" and "fall" will stop the playback of the sample regardless of any other event. This means that when the type "raise" is supplied, sample playback will stop when the event turns false. Using the type "fall" will stop playback when the event turns true.

: IMPORTANT
:: If the trigger is used for anything else but stopping the sound at a certain event, all sections with the same name ''should'' have exactly the same sections for everything but property and type.

:: In the case of just stopping the sample at a certain event, the sections for path, volume and pitch may be omitted.

; <code><path></code>
: This defined the path to the sound file. The path is relative to the FlightGear root directory but could be specified absolute.

: The sound format must be mono.

; <code><condition></code>
: Define a condition that triggers the event.

: For a complete description of the FlightGear conditions, please read docs-mini/README.conditions or read the [[Conditions]] article on the wikie.

: An event should define either a condition or a property.

; <code><property></code>
: Define which property triggers the event, and refers to a node in the FlightGear property tree.

: Action is taken when the property is non zero.

: A more sophisticated mechanism to trigger the event is described in <condition></code>

; <code><mode></code>
: This defines how the sample should be played:

:; once
:: The sample is played once. This is the default.

:; looped
:: The sample plays continuously, until the event turns false.

:; in-transit
:: the sample plays continuously, while the property is changing its value.

; <code><type></code>
: This defines the type of this sample, each type also have seperate volume slider in sound settings menu:

:; fx
:: This is the default type and doesn't need to be defined.

:; avionics
:: Sounds set to this type don't have a position and orientation but are treated as if it's mounted to the aircraft panel.

:: It is up to the user to define if it can always be heard or only when in cockpit view.

:; atc
:: Is used by the ATC chatter add-on.

; <code><delay-sec></code>
: Delay after which the sound starts playing.

: This is useful to let a property start two sounds at the same time, where the second is delayed until the first stopped playing.

; <code><volume></code> / <code><pitch></code>
: Volume or Pitch definition.

: Currently there may be up to 5 volume and up to 5 pitch definitions defined within one sound event.

: There are two important results from each <volume> and <pitch> section: the offset and the value. Normally all offset values from the different volume/pitch are added together to create the total offset. The values from each <volume> or <pitch> section are multiplied together to create an final value. Then the volume (or pitch, respectively) is set to total offset + final value.

: A special condition occurs when the value of factor is negative, in which case the offset doesn't get added to the other offset values but instead will be used in the multiplication section.

: Pitch final output can range from 0 to 2. 1 represents the original pitch of the sound file. Offset defaults to 1, meaning that if no specific <pitch> parameters are given the file will be played at its original pitch.

: Volume final output can range from 0 to 1. 1 represents full volume and 0 is silence.

:; <code><expression></code>
:: Defines an expression, and will replace all other tags in this volume/pitch tag.

:; <code><property></code>
:: Defines which property supplies the value for the calculation.

:: Either a <property> or an <internal> should be defined. If none is defined, the property reverts to its default. For volume this is 0, meaning the sound will not be audible at all.

:: The value is treated as a floating point number.

:; <code><internal></code>
:: Defines which internal variable should be used for the calculation.

:: The value is treated as a floating point number.

:: The following internals are available at this time:

::; dt_play
::: The number of seconds since the sound started playing.

::; dt_stop
::: The number of seconds after the sound has stopped.

:; <code><type></code>
:: Defines the function that should be used upon the property before it is used for calculating the net result:

::; lin
::: Linear handling of the property value. This is the default.

::; ln
:: Convert the property value to a natural logarithmic value before scaling it.

::: Anything below 1 will return zero.

::; log
::: convert the property value to a true logarithmic value before scaling it. (log base 10)

::: Anything below 1 will return zero.

::; inv
::: Inverse linear handling (1/x).

::; abs
:: Absolute handling of the value (always positive).

::; sqrt
::: Calculate the square root of the absolute value before scaling it.

:; <code><factor></code>
:: Defines the multiplication factor for the property value.

:: A special condition is when scale is defined as a negative value. In this case the result of |<scale>| * <property) will be subtracted from <default>

:; <code><offset></code>
:: The initial value for this sound.

:: This value is also used as an offset value for calculating the end result.

:; <code><random></code>
:: Add a bit of randomness to the offset. Only used for pitch.

:; <code><min></code>
:: Minimum allowed value.

:: This is useful if sounds start to sound funny. Anything lower will be truncated to this value.

:; <code><max></code>
:: Maximum allowed value.

:: This is useful if sounds gets to loud. Anything higher will be truncated to this value.

:: Keep in mind that min & max are applied first, then offset. So for example if min = 0, max = 0.5 and offset = 1.0, then the resulting values will range 1 to 1.5.

; <code><position></code>
: Specify the position of the sounds source relative to the aircraft center.

: The coordinate system used is a left hand coordinate system where +Y = left, -Y = right, -Z = down, +Z = up, -X = forward, +X = aft. Distances are in meters.

: The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!

: Also take notice that the values should not be 0.0, since that can produce sound artifacts on some sound cards.

; <code><x></code>
: X dimension offset (-X = forward, +X = aft, in meters)

; <code><y></code>
: Y dimension offset (+Y = left, -Y = right)

; <code><z></code>
: Z dimension offset (-Z = down, +Z = up)

; <code><orientation></code>
: Specify the orientation of the sounds source.

: The zero vector is default, indicating that a Source is not directional.

: Specifying a non-zero vector will make the Source directional in the X,Y,Z direction

; <code><x></code>
: X dimension

; <code><y></code>
: Y dimension

; <code><z></code>
: Z dimension

; <code><inner-angle></code>
: The inner edge of the audio cone in degrees (0.0 - 360.0).

: Any sound withing that angle will be played at the current gain.

; <code><outer-angle></code>
: The outer edge of the audio cone in degrees (0.0 - 360.0).

: Any sound beyond the outer cone will be played at "outer-gain" volume.

; <code><outer-gain></code>
: The gain at the outer edge of the cone.

; <code><reference-dist></code>
: Set a reference distance of sound in meters. This is the distance where the volume is at its maximum. Default is 60.

: Volume is clamped to this maximum for any distance below.

: Volume is attenuated for any distance above.

: Attenuation depends on reference and maximum distance. See OpenAL specification on "AL_INVERSE_DISTANCE_CLAMPED" mode for details on exact computation.

; <code><max-dist></code>
: Set the maximum audible distance for the sound in meters. Default is 6000.

: Sound is cut-off above this distance.

== Creating a configuration file ==

To make things easy, there is a default value for most entries to allow a
sane configuration when a certain entry is omitted.

{| class="wikitable"
! Tag !! Default value
|-
| '''<type>''' || lin
|-
| '''<factor>''' || 1.0
|-
| '''<offset>''' || 0.0 for volume, 1.0 for pitch
|-
| '''<min>''' || 0.0
|-
| '''<max>''' || 0.0 (don't check)
|}

Calculations are made the following way (for both pitch and volume):
<syntaxhighlight lang="cpp">
value = 0;
offs = 0;

for (n = 0; n < max; n++) {
if (factor < 0) {
value += offset[n] - abs(factor[n]) * function(property[n]);
} else {
value *= factor[n] * function(property[n]);
offs += offset[n];
}
}

volume = offs + value;
if (volume > 1.0) vol = 1.0;
</syntaxhighlight>
where function can be one of: lin, ln, log, inv, abs or sqrt

== Multiplayer sound ==
The multiplayer sound file works just as the normal sound file, except it should reside in <code>/sim/model/sound</code> instead of <code>/sim/sound</code>. Make sure it depends on properties that are [[Howto:Transmit_properties_over_MP|transmitted over MP]].

== Recommended audio file formats ==
{{note|The sound sample '''must be in mono''' format. This is because it can not be put in a 3D context otherwise. Also, as of at least June 2015 '''stereo samples will not be played'''.}}

There some considerations on the quality to the audio files. As a rule of thumb, any computer is able to playback sounds in DVD-quality (48 kHz/24 bits).
Macs still has trouble reading 32 bit files. Most standard sound cards also can't playback 32 bit files.

From a listeners point of view, anything above 44.1 kHz and 24 bits is only useful for high end music. Personally, I would think that 44.1 kHz with 16 bits should be more than enough to play engine sounds and alarms from the cockpit. Consider the disk-space against the gain in audio quality!

== Preventing sounds from playing when sim starts ==
Some times it can be hard to prevent sounds from playing right away, if the condition starts to evaluate to true. A hack to get this to work is to multiply the volume with a property that you in nasal set to true some seconds after the sim has been initialized.

== Bugs in the sound system ==
* The Doppler effect if you pass an aircraft in high speed sometimes is way too high pitch.
* None of the position coordinates must not be 0.0 as described above.

== Related content ==
=== Wiki articles ===
* [[Conditions]]
* [[Expressions]]
* [[Howto:Reload sound configuration without restarting]]

=== Readme file ===
* {{readme file|xmlsound}}

=== Source code ===
* {{simgear file|simgear/sound/xmlsound.hxx}}
* {{simgear file|simgear/sound/xmlsound.cxx}}
* {{flightgear file|src/Sound/fg_fx.hxx}}
* {{flightgear file|src/Sound/fg_fx.cxx}}

[[Category:Aircraft enhancement]]

Howto:Add sound effects to aircraft

2021-08-10T17:22:06Z

Sfrsfr: /* Configuration tags */ type, not time

You can '''add sound effects to aircraft''' by adding the sound samples and configuring the sound effects in XML files. The sound effects can be conditional and the sound's pitch and volume can depend on properties in the property tree.

Some sound effects are added other ways. For example, sounds from avionics like navigation radio receivers are automatically added when you add those radios.

{{FGCquote|1= The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/28505220/ | title = <nowiki>Re: [Flightgear-devel] Stereo sounds no longer supported?</nowiki> | author = <nowiki>syd adams</nowiki> | date = Dec 7th, 2011 }}}}

{{FGCquote|1= The old way was that the stereo sound would always play the left channel on the left side. Now you split the sound and place it in 3D space. When you turn your head, the speaker the left side sound comes out of changes with you|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257291#p257291 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>bugman</nowiki> | date = Sep 14th, 2015 }}}}

{{FGCquote|1= All sounds must now be mono point sources, and stereo simply requires the two sound sources to be positioned in the 3D environment. |2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34100151/ | title = <nowiki>[Flightgear-devel] Audit and proposal for handling non-supported stereo sound files in FGAddon via the 3D sound engine.</nowiki> | author = <nowiki>Edward d'Auvergne</nowiki> | date = May 10th, 2015 }}}}

{{FGCquote|1= We use OpenAL for 3D positional audio and most OpenAL implementations can only handle one stereo file.Also Stereo files will not work in 3d space, so they will not be positional.But most aircraft developers did not know that and used several stereo files expecting everything to work properly but the truth was that in most implementations just one of those stereo files was played.And if you think of it, stereo separation does not work for boarding music either since it plays left channel to your left ear and right channel to your right ear. But in reality boarding music is played left channel to the left audio channel in the aircraft and right channel to the right audio channel in the aircraft.This works the same as normal stereo if you enter the aircraft, but will, reverse once you turn around.So the solution is to split up the stereo file into two mono files and play the proper channel at the proper side of the passenger compartment.|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257289#p257289 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>erik</nowiki> | date = Sep 14th, 2015 }}}}

== Sound configuration files ==
The sound configuration files are [[PropertyList XML files]].

The top level sound configuration file is composed of a <code><fx></code> and a <code><name></code> tag, a <code><path></code> to a sound sample file and zero or more <code><volume></code> and/or <code><pitch></code>definitions.

Paths are relative to [[$FG_ROOT]], but absolute paths may also be used.

Comments are bracketed with <code></code>.

=== Example ===
This example would define an engine sound effect for a piston engine driven aeroplane.

The sound effect representing the engine is located in <code>$FG_ROOT/Sounds</code> and is named <code>wasp.wav</code>. The effect is started when the property <code>/engines/engine/running</code> becomes non-zero.

When that happens, the sound will be played looped (see <code><mode></code>) until the property returns zero again. As you can see the volume is dependent on the property <code>/engines/engine/mp-osi</code>, and the pitch of the sound depends on the property <code>/engines/engine/rpm</code>.

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>
<fx>
<engine>
<name>engine</name>
<path>Sounds/wasp.wav</path>
<mode>looped</mode>
<condition>
<property>/engines/engine/running</property>
</condition>
<volume>
<property>/engines/engine/mp-osi</property>
<factor>0.005</factor>
<min>0.15</min>
<max>0.5</max>
<offset>0.15</offset>
</volume>
<pitch>
<property>/engines/engine/rpm</property>
<factor>0.0012</factor>
<min>0.3</min>
<max>5.0</max>
<offset>0.3</offset>
</pitch>
</engine>
</fx>
</PropertyList>
</syntaxhighlight>

=== Inclusion from the aircraft-set.xml file ===
In order for the sound configuration to be used, it has to be included from the [[aircraft-set.xml]] file.

This can be done by adding the path to the file relative to the aircraft's base path within the <code><sim></code> tags in the aircraft-set.xml file..

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>

<sim>

<sound>
<path type="string">My-sound-config.xml</path>
</sound>

</sim>

</PropertyList>
</syntaxhighlight>

== Configuration tags ==

; <code><fx></code>
: Named FX subtree living under /sim/sound

; <code>< ... ></code>
: This is the event separator. The text inside the brackets can be anything, but it is advised to give it a meaningful name like: crank, engine, rumble, gear, squeal, flap, wind or stall.

: The value can be defined multiple times, thus anything which is related may have the same name (grouping them together).

; <code><name></code>
: This defines the name of the event. This name is used internally and, although it can me defined multiple times in the same file, should normally have an unique value.

: Multiple definitions of the same name will allow multiple sections to interfere in the starting and stopping of the sample.

: This method can't be used to control the pitch or volume of the sample, but instead multiple volume or pitch section should be included inside the same event.

: The types "raise" and "fall" will stop the playback of the sample regardless of any other event. This means that when the type "raise" is supplied, sample playback will stop when the event turns false. Using the type "fall" will stop playback when the event turns true.

: IMPORTANT
:: If the trigger is used for anything else but stopping the sound at a certain event, all sections with the same name ''should'' have exactly the same sections for everything but property and type.

:: In the case of just stopping the sample at a certain event, the sections for path, volume and pitch may be omitted.

; <code><path></code>
: This defined the path to the sound file. The path is relative to the FlightGear root directory but could be specified absolute.

: The sound format must be mono.

; <code><condition></code>
: Define a condition that triggers the event.

: For a complete description of the FlightGear conditions, please read docs-mini/README.conditions or read the [[Conditions]] article on the wikie.

: An event should define either a condition or a property.

; <code><property></code>
: Define which property triggers the event, and refers to a node in the FlightGear property tree.

: Action is taken when the property is non zero.

: A more sophisticated mechanism to trigger the event is described in <condition></code>

; <code><mode></code>
: This defines how the sample should be played:

:; once
:: The sample is played once. This is the default.

:; looped
:: The sample plays continuously, until the event turns false.

:; in-transit
:: the sample plays continuously, while the property is changing its value.

; <code><type></code>
: This defines the type of this sample, each type also have seperate volume slider in sound settings menu:

:; fx
:: This is the default type and doesn't need to be defined.

:; avionics
:: Sounds set to this type don't have a position and orientation but are treated as if it's mounted to the aircraft panel.

:: It is up to the user to define if it can always be heard or only when in cockpit view.

:; atc
:: Is used by the ATC chatter add-on.

; <code><delay-sec></code>
: Delay after which the sound starts playing.

: This is useful to let a property start two sounds at the same time, where the second is delayed until the first stopped playing.

; <code><volume></code> / <code><pitch></code>
: Volume or Pitch definition.

: Currently there may be up to 5 volume and up to 5 pitch definitions defined within one sound event.

: There are two important results from each <volume> and <pitch> section: the offset and the value. Normally all offset values from the different volume/pitch are added together to create the total offset. The values from each <volume> or <pitch> section are multiplied together to create an final value. Then the volume (or pitch, respectively) is set to total offset + final value.

: A special condition occurs when the value of factor is negative, in which case the offset doesn't get added to the other offset values but instead will be used in the multiplication section.

: Pitch final output can range from 0 to 2. 1 represents the original pitch of the sound file. Offset defaults to 1, meaning that if no specific <pitch> parameters are given the file will be played at its original pitch.

: Volume final output can range from 0 to 1. 1 represents full volume and 0 is silence.

:; <code><expression></code>
:: Defines an expression, and will replace all other tags in this volume/pitch tag.

:; <code><property></code>
:: Defines which property supplies the value for the calculation.

:: Either a <property> or an <internal> should be defined. If none is defined, the property reverts to its default. For volume this is 0, meaning the sound will not be audible at all.

:: The value is treated as a floating point number.

:; <code><internal></code>
:: Defines which internal variable should be used for the calculation.

:: The value is treated as a floating point number.

:: The following internals are available at this time:

::; dt_play
::: The number of seconds since the sound started playing.

::; dt_stop
::: The number of seconds after the sound has stopped.

:; <code><type></code>
:: Defines the function that should be used upon the property before it is used for calculating the net result:

::; lin
::: Linear handling of the property value. This is the default.

::; ln
:: Convert the property value to a natural logarithmic value before scaling it.

::: Anything below 1 will return zero.

::; log
::: convert the property value to a true logarithmic value before scaling it. (log base 10)

::: Anything below 1 will return zero.

::; inv
::: Inverse linear handling (1/x).

::; abs
:: Absolute handling of the value (always positive).

::; sqrt
::: Calculate the square root of the absolute value before scaling it.

:; <code><factor></code>
:: Defines the multiplication factor for the property value.

:: A special condition is when scale is defined as a negative value. In this case the result of |<scale>| * <property) will be subtracted from <default>

:; <code><offset></code>
:: The initial value for this sound.

:: This value is also used as an offset value for calculating the end result.

:; <code><random></code>
:: Add a bit of randomness to the offset. Only used for pitch.

:; <code><min></code>
:: Minimum allowed value.

:: This is useful if sounds start to sound funny. Anything lower will be truncated to this value.

:; <code><max></code>
:: Maximum allowed value.

:: This is useful if sounds gets to loud. Anything higher will be truncated to this value.

:: Keep in mind that min & max are applied first, then offset. So for example if min = 0, max = 0.5 and offset = 1.0, then the resulting values will range 1 to 1.5.

; <code><position></code>
: Specify the position of the sounds source relative to the aircraft center.

: The coordinate system used is a left hand coordinate system where +Y = left, -Y = right, -Z = down, +Z = up, -X = forward, +X = aft. Distances are in meters.

: The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!

: Also take notice that the values should not be 0.0, since that can produce sound artifacts on some sound cards.

; <code><x></code>
: X dimension offset (-X = forward, +X = aft, in meters)

; <code><y></code>
: Y dimension offset (+Y = left, -Y = right)

; <code><z></code>
: Z dimension offset (-Z = down, +Z = up)

; <code><orientation></code>
: Specify the orientation of the sounds source.

: The zero vector is default, indicating that a Source is not directional.

: Specifying a non-zero vector will make the Source directional in the X,Y,Z direction

; <code><x></code>
: X dimension

; <code><y></code>
: Y dimension

; <code><z></code>
: Z dimension

; <code><inner-angle></code>
: The inner edge of the audio cone in degrees (0.0 - 360.0).

: Any sound withing that angle will be played at the current gain.

; <code><outer-angle></code>
: The outer edge of the audio cone in degrees (0.0 - 360.0).

: Any sound beyond the outer cone will be played at "outer-gain" volume.

; <code><outer-gain></code>
: The gain at the outer edge of the cone.

; <code><reference-dist></code>
: Set a reference distance of sound in meters. This is the distance where the volume is at its maximum. Default is 60.

: Volume is clamped to this maximum for any distance below.

: Volume is attenuated for any distance above.

: Attenuation depends on reference and maximum distance. See OpenAL specification on "AL_INVERSE_DISTANCE_CLAMPED" mode for details on exact computation.

; <code><max-dist></code>
: Set the maximum audible distance for the sound in meters. Default is 6000.

: Sound is cut-off above this distance.

== Creating a configuration file ==

To make things easy, there is a default value for most entries to allow a
sane configuration when a certain entry is omitted.

{| class="wikitable"
! Tag !! Default value
|-
| '''<type>''' || lin
|-
| '''<factor>''' || 1.0
|-
| '''<offset>''' || 0.0 for volume, 1.0 for pitch
|-
| '''<min>''' || 0.0
|-
| '''<max>''' || 0.0 (don't check)
|}

Calculations are made the following way (for both pitch and volume):
<syntaxhighlight lang="cpp">
value = 0;
offs = 0;

for (n = 0; n < max; n++) {
if (factor < 0) {
value += offset[n] - abs(factor[n]) * function(property[n]);
} else {
value *= factor[n] * function(property[n]);
offs += offset[n];
}
}

volume = offs + value;
if (volume > 1.0) vol = 1.0;
</syntaxhighlight>
where function can be one of: lin, ln, log, inv, abs or sqrt

== Multiplayer sound ==
The multiplayer sound file works just as the normal sound file, except it should reside in <code>/sim/model/sound</code> instead of <code>/sim/sound</code>. Make sure it depends on properties that are [[Howto:Transmit_properties_over_MP|transmitted over MP]].

== Recommended audio file formats ==
{{note|The sound sample '''must be in mono''' format. This is because it can not be put in a 3D context otherwise. Also, as of at least June 2015 '''stereo samples will not be played'''.}}

There some considerations on the quality to the audio files. As a rule of thumb, any computer is able to playback sounds in DVD-quality (48 kHz/24 bits).
Macs still has trouble reading 32 bit files. Most standard sound cards also can't playback 32 bit files.

From a listeners point of view, anything above 44.1 kHz and 24 bits is only useful for high end music. Personally, I would think that 44.1 kHz with 16 bits should be more than enough to play engine sounds and alarms from the cockpit. Consider the disk-space against the gain in audio quality!

== Preventing sounds from playing when sim starts ==
Some times it can be hard to prevent sounds from playing right away, if the condition starts to evaluate to true. A hack to get this to work is to multiply the volume with a property that you in nasal set to true some seconds after the sim has been initialized.

== Bugs in the sound system ==
* The Doppler effect if you pass an aircraft in high speed sometimes is way too high pitch.
* None of the position coordinates must not be 0.0 as described above.

== Related content ==
=== Wiki articles ===
* [[Conditions]]
* [[Expressions]]
* [[Howto:Reload sound configuration without restarting]]

=== Readme file ===
* {{readme file|xmlsound}}

=== Source code ===
* {{simgear file|simgear/sound/xmlsound.hxx}}
* {{simgear file|simgear/sound/xmlsound.cxx}}
* {{flightgear file|src/Sound/fg_fx.hxx}}
* {{flightgear file|src/Sound/fg_fx.cxx}}

[[Category:Aircraft enhancement]]

Addon

2021-08-06T15:49:43Z

Sfrsfr: /* List of Addons */ Added entry for Fencemaker

[[File:Fgaddonslogo202x89.png|right]]
To make it easier to create '''addons''' there is since FlightGear 2017.3 a new way to create addons. In essence FlightGear will load an overlay XML into the property tree and start a well known Nasal function.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314620#p314620
|title = <nowiki> Re: New Feature: Addon - "API" </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>

We now have a simple way to add addons to FlightGear without the need to mess around with <code>FGData/Nasal</code> or <code>FGHome/Nasal</code> directories.<ref name="Forum_announcement">{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314563#p314563
|title = <nowiki> New Feature: Addon - "API" </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 18th, 2017
}}</ref>

{{TOC limit|3}}

== Installing and using an addon ==
Download and copy the addon to a directory on your computer.

If you use the launcher, select the Add-ons page from the icon bar on the left, then find the section Add-on Module folders and click the Add(+) button. Select the folder where you put the addon. Once the addon is shown in the list, make sure its check box is selected.

Use the command line switch <code>--addon=/path/to/some/addon</code>.<ref name="Forum_announcement"/>

== Creating an addon ==
There is a very simple Skeleton addon available in FGAddon to be used as a template.<ref name="Forum_announcement"/> See {{fgaddon source|path=Addons/Skeleton}}.

A leading slash (<code>/</code>) in this section indicates the base directory of the directory structure of the addon.

=== Minimum configuration ===
An addon may be installed in a directory anywhere on your hard disk and need at least two files:

* <code>/addon-config.xml</code> - A standard [[PropertyList XML files|PropertyList XML file]] to be used to populate or modify the [[property tree]]. (Same as to be used in <code>--config=foo.xml</code>)
* <code>/addon-main.nas</code> - The Nasal hook for the logic. This file needs a function called <code>main()</code> which will be called from the global addon initializer (<code>addons.nas</code>)

=== Additional common files ===
* <code>/addon-metadata.xml</code> - A PropertyList XML file with metadata about the addon it.
* <code>/addon-menubar-items.xml</code> - A PropertyList XML file describing menus to be added to the FlightGear menu bar.
* <code>/gui/dialogs/<my-foobar-dialog>.xml</code> - PropertyList XML files to create custom dialogs.

=== Good to know ===
The new addon mechanism lets you add a <code>addon-config.xml</code> to override the settings in <code>defaults.xml</code> and other files.

That will allow an addon to
* Override key bindings (as in the spoken ATC addon)
* Add or override autopilots and property rules
* Introduce XML state machines

Unless your really want to add/change/remove those at runtime, this should cater for most use cases.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314902#p314902
|title = <nowiki> Re: Spoken </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 23rd, 2017
|added = Jul 23rd, 2017
|script_version = 0.40
}}</ref>

We have some instructions how to use SVN [[FGAddon|in our wiki]]. It covers mostly aircraft development but the workflow is pretty much the same for addons.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314647#p314647
|title = <nowiki> Re: Spoken ATC </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>

== Addon initialization ==
On initialization fgfs takes care of:
* Through {{flightgear source|path=src/Main/options.cxx|text=<code>options.cxx</code>}}:<ref name="Forum_announcement"/>
** Creating a property under <code>/addons/addon[n]/path=/path/to/some/addon</code>
** Loading <code>/path/to/some/addon/addon-config.xml</code> into the property tree (same as <code>--config=/path/to/some/addon/addon-config.xml</code>)
** Adding <code>/path/to/some/addon</code> to the list of allowed directories (same as <code>--fg-aircraft=/path/to/some/addon</code>)
* Through {{fgdata source|path=Nasal/addons.nas|text=<code>addons.nas</code>}}:
** Loading <code>/foo/bar/baz/addon-main.nas</code> into namespace <code>__addon[ADDON_ID]__</code>
** Calling <code>main(addonGhost)</code> from <code>/foo/bar/baz/addon-main.nas</code>.

== APIs ==
{{hatnote|For more details about these APIs, see the readme file, {{readme file|add-ons}}.}}
=== C++ API ===
There is a C++ API on FlightGear's side that handle some on the addon related tasks manly through the <code>AddonManager()</code>, <code>Addon()</code> and <code>AddonVersion()</code> classes.

=== Nasal API ===
The Nasal add-on API lives in the 'addons' namespace and can for example do queries to <code>AddonManager()</code> and read data from <code>addons.Addon</code> objects. It can for example compare addon versions if there is dependencies.

== Background ==
{{See also|Howto:Creating a simple modding framework}}

ATC chatter was removed in 2015, see fgdata commit: [https://sourceforge.net/p/flightgear/fgdata/ci/81607f734e13add9be02816ddaec305d05bc4e47/ 81607f734e13add9be02816ddaec305d05bc4e47]

And the devel list messages referenced in the commit log.
the other relevant commit is this: b60736ba7add2a7cd39af3d8a974d5be3ea46e8b
It would not be very difficult to restore this functionality, or even generalize/improve it significantly (which was the scope of the original discussion on the devel list)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=288388#p288388
|title = <nowiki> Re: Whatever happened to radom radio </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Jun 11th, 2016
|added = Jun 11th, 2016
|script_version = 0.40
}}</ref>

The restored functionality could be distributed as a tarball that is extracted into $FG_ROOT - alternatively, into $FG_HOME, because Nasal files there are treated as overlays, which basically means that you can install user-specific extensions there without having to tamper with $FG_ROOT, it would only take very minor changes to turn the chatter feature into a corresponding "addon" - not unlike fgcamera ...<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=288392#p288392
|title = <nowiki> Re: Whatever happened to radom radio </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Jun 11th, 2016
|added = Jun 11th, 2016
|script_version = 0.40
}}</ref>

We should absolutely stop telling anyone to edit preferences.xml in FG_ROOT; any documentation or advice which says to should be changes ASAP. <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=192632#p192632
|title = <nowiki> Re: NavCache:init failed:Sqlite error:Sqlite API abuse </nowiki>
|author = <nowiki> zakalawe </nowiki>
|date = Oct 26th, 2013
|added = Oct 26th, 2013
|script_version = 0.40
}}</ref>

As of 12/2017, the addon API is in the process of being significantly updated <ref>https://sourceforge.net/p/flightgear/mailman/message/36146017/</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/36150159/</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/36150444/</ref>

== List of Addons ==
You can find the official repository at {{fgaddon source|path=Addons}}

* ATC Chatter (ported by Torsten) {{progressbar|100}}
* [[Cargo Towing Addon]] <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?t=36824
|title = <nowiki> Re: Cargo Towing Addon </nowiki>
|author = <nowiki> Wayne Bragg (wlbragg) </nowiki>
|date =
|added =
|script_version = 0.40
}}</ref>
* cockpit-view (work in progress by wkitty42)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=316498#p316498
|title = <nowiki> Re: </nowiki>
|author = <nowiki> wkitty42 </nowiki>
|date = Aug 13th, 2017
|added = Aug 13th, 2017
|script_version = 0.40
}}</ref>
* [[Earthview#Customization]] - High resolution customization
* [[FaceTrackNoIR]] (ported by HHS)<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/36454826/
|title = <nowiki> Re: </nowiki>
|author = <nowiki> Unknown, HHS</nowiki>
|date = Nov 1th, 2018
}}</ref> - An addon to interface this [[Head tracking|head tracker]] with FlightGear
* [https://forum.flightgear.org/viewtopic.php?f=5&t=24792 Fencemaker] (Eases creating Fence-like scenery objects. Originally by VaLeo, converted to an addon by sfr) - ([https://www.mediafire.com/file/cf0la63v9g352md/fencemaker_addon.zip/file download])<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?f=5&t=24792&start=45#p390066
|title = <nowiki> Re: </nowiki>
|author = <nowiki> Stefan Frank </nowiki>
|maintainer = <nowiki> Stefan Frank </nowiki>
|date = Aug 8th, 2021
}}</ref>
* [https://github.com/slawekmikula/flightgear-addon-fgcamera FGCamera] - ([https://github.com/slawekmikula/flightgear-addon-fgcamera/blob/master/Docs/manual.md manual]) - [[FGCamera | Wiki Page]]
* [[FGPlot]]
* [[Ground Services]] (ported by ThomasS)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=316400#p316400
|title = <nowiki> Re: </nowiki>
|author = <nowiki> ThomasS </nowiki>
|date = Aug 12th, 2017
|added = Aug 12th, 2017
|script_version = 0.40
}}</ref>
* {{fgaddon source|path=Addons/Headtracker/|text=Headtracker addon}} Helps integrate FaceTrackNoIR and opentrack with FlightGear.
* [[Landing Rate addon]] [https://forum.flightgear.org/viewtopic.php?f=6&t=33101&p=327787#p327787]
* [https://gitlab.com/mdanil/flightgear-hax mdanilov hax!]: landing evaluation and aircraft development tools, TerraSync toggler
* [[Model Cockpit View]]
* [[Oscilloscope addon]] - Allows displaying a property of Nasal function over time
* [[PAR instrument]] - Precision Approach Radar and Ground Controlled Approach
* [[Red Griffin ATC]] - Speaking Air Traffic Controller<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?f=6&t=36755
|title = <nowiki> Re: </nowiki>
|author = <nowiki> RedGriffin </nowiki>
|date = Jan 6th, 2020
|added = Jan 6th, 2020
|script_version = 1.0.0 RC2
}}</ref>
* [[Spoken ATC]] (ported by Torsten)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314095#p314095
|title = <nowiki> Re: </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 10th, 2017
|added = Jul 10th, 2017
|script_version = 0.40
}}</ref>
* [[Spoken GCA]] - An offline ground controlled approach (GCA) addon
* [[YASim Development Tools]] (by jsb)
* [https://github.com/slawekmikula/flightgear-addon-vfrflight VFRFlight integration] - ([https://github.com/slawekmikula/flightgear-addon-vfrflight/blob/master/doc/manual.md manual])
* [https://github.com/slawekmikula/flightgear-addon-protocolkml KML Exporter (Google Earth)] - ([https://github.com/slawekmikula/flightgear-addon-protocolkml/blob/master/doc/manual.md manual])
* [https://github.com/slawekmikula/flightgear-addon-vfrnavigator VFR Flying Helper] - ([https://github.com/slawekmikula/flightgear-addon-vfrnavigator/blob/master/doc/usage.md manual])
* [https://github.com/slawekmikula/flightgear-addon-linuxtrack LinuxTrack Head Tracker integration] - ([https://github.com/slawekmikula/flightgear-addon-linuxtrack/blob/master/doc/manual.md manual])
* [https://github.com/slawekmikula/flightgear-addon-hudheli Additional Heli HUD's] - ([https://github.com/slawekmikula/flightgear-addon-hudheli/blob/master/doc/manual.md manual]) - encapsulation of HeliHUD package as an addon
* [https://gitlab.com/mdanil/flightgear-mickey Tiny HUD for mouse flying in FlightGear] - Visual feedback for mouse flying, to make up for mouse's lack of self-centering
* [https://github.com/slawekmikula/flightgear-addon-littlenavmap LittleNavMap integration] - ([https://github.com/slawekmikula/flightgear-addon-littlenavmap/blob/master/doc/manual.md manual])

== Experimental Addons ==

Addons which are in the development stage/unfinished but can be used as a quick view of addon functionality
* [https://github.com/slawekmikula/flightgear-addon-missions FlightGear Missions addon] - Add-on for missions/adventures code

== Ideas ==
=== Hooking into features using legacy OpenGL code ===
{{See also|Unifying the 2D rendering backend via canvas}}
In 09/2018, James suggested that legacy features using raw OpenGL calls (e.g. HUD/2D panels) could be easily replaced via scripted Canvas/Nasal solutions at the mere cost of providing a mechanism to hook into the legacy code implementing these features (namely, the HUD/instrumentation subsystems) <ref>https://sourceforge.net/p/flightgear/mailman/message/36399261/</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/36399261/</ref>

=== Catalog & Package Manager support ===
if this works with more complex, pre-existing addons such as [[Bombable]], where the file layout is a replica of the old FGData layout, these types of mature addons might be better as SourceForge FlightGear sub-projects rather than being copied into FGAddon. Maybe the config file and nasal script could be used to automate the installation process ?<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35953179/
|title = <nowiki> Re: [Flightgear-devel] Simple API for creating FlightGear
addons/plugins </nowiki>
|author = <nowiki> Edward d'Auvergne </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>
The [[Bombable]] addon is one of the most popular addons out there, and a large number of aircraft in FGAddon have bombable support, so it is worth not forgetting about. Especially if the addon system one day becomes automated through a [[Catalog metadata|catalog.xml type system]]<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35953650/
|title = <nowiki> Re: [Flightgear-devel] Simple API for creating FlightGear
addons/plugins </nowiki>
|author = <nowiki> Edward d'Auvergne </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>

== References ==
{{Appendix}}

== Related content ==
=== Wiki articles ===
* [[FG Add-on FAQ]]
* [[FlightGear configuration via XML]]
* [[FlightGear configuration via XML#preferences.xml]]
* [[Nasal]]
* [[Property tree]]
* [[Properties persistent between sessions]]
* [[PropertyList XML File]]

=== Forum topics ===
* {{forum link|t=32561|title=New Feature: Addon - "API"}}

=== Readme files ===
* {{readme file|add-ons}}
* {{readme file|gui}} - Details on how to add menus and custom dialogs.

=== Source code ===
==== FGAddon ====
* {{fgaddon source|path=Addons/Skeleton}} - Skeleton addon to be used as a template.

==== FGData ====
* {{fgdata source|path=Nasal/addons.nas}}

==== FlightGear ====
* {{flightgear source|path=src/Main/options.cxx}}
* {{flightgear source|path=src/Add-ons/}}

[[Category:FlightGear addons| ]]

Autopilot configuration reference

2021-08-04T12:15:35Z

Sfrsfr: /* Monostable flip flop <monostable> */ corrected position of explanatory text to be before the example code

{{Systems_Modeling_Disclaimer}}

[[File:FgPlot.jpg|400px|thumb|[[FGPlot]] can be used to plot the value properties while tuning an autopilot.]]

{{forum|46|Autopilot & Route Manager}}
{{Autoflight Navigation}}

: ''For a guide on how to model an autopilot using these elements, see [[Howto:Design an autopilot]].''

The '''property rules''' used for '''autopilot configuration''' can also be used for other kinds of systems modeling. The controllers and filters allow for both simple and complex systems to be modeled. By using the output from one as the input to another one, very complex systems such as fly-by-wire systems with different control laws can be modeled.

This page serves as a reference for the elements of [[FlightGear]] XML [[autopilot]] and property rule configuration files. It describes all elements available within the autopilot configuration file supported in the bleeding edge [[Git]] sources. Some of the elements may not be available in the current release version of FlightGear.

For built-in runtime plotting of FlightGear properties (including FDM/Autopilot properties), check out [[FGPlot]] (available in FlightGear 2.11+).

== Autopilot vs. property-rule configurations ==
The main difference between XML based autopilot and property-rule systems is the update rate:

* Autopilot configurations run at [[FDM]] rate
* Property-rule configurations run at frame rate

=== Performance considerations ===
Using property-rule elements for things that does not have to run a FDM rate can improve the frame rate, in particular for complex systems and on weaker computers. Depending on FlightGear settings and the hardware, the FDM rate is about 2–10 times higher than the frame rate.

It is possible to implement a system using both autopilot and property-rule based elements. They can communicate with each other using [[Property tree|properties]]. The only disadvantage is that they will be split between an autopilot and a property-rule configuration file.

For example would a fly-by-wire flight control system element augmenting an unstable aircraft need to run at FDM rate, while an element depending on the flap extension would work just as well at frame rate.

== Adding a configuration to an aircraft ==
A configuration is added to an aircraft by adding the path to an XML configuration file to the <code><Aircraft>-set.xml</code> file.

=== Adding an autopilot configuration ===
Autopilot configuration files are added to the aircraft by adding

<syntaxhighlight lang="xml">
<autopilot n="100">
<path>Aircraft/MyAircraft/Systems/my-autopilot.xml</path>
</autopilot>
</syntaxhighlight>

to the

<syntaxhighlight lang="xml">
<sim>
<systems>

<autopilot n="100">
<path>Aircraft/MyAircraft/Systems/my-autopilot.xml</path>
</autopilot>
</systems>
</sim>
</syntaxhighlight>

node of your <code>aircraft-set.xml</code> file. Note, that more than one <syntaxhighlight lang="xml" inline><autopilot></syntaxhighlight> node may be present, each will create a new instance of the autopilot subsystem when running FlightGear. They run in the order of appearance under <syntaxhighlight lang="xml" inline><systems></syntaxhighlight>. For example, lateral and vertical autopilot modes could live in separate files, as could a yaw-damper system.

{{note|While the above seems to be the recommended standard, it has occasionally lead to trouble, not to index additional autopilot configurations. Anyway, it shouldn't hurt to do so.<br>
FG first loads generic configs, which get indexed atomatically as they appear. Then you override these generic configs with your own, which may lead to strange behaviour, if you for example overwrite the weather rules with an autopilot-helper configuration. Not only will you have no weather anymore, but also 2 systems that will most likely overwrite each others results all the time. Check the property-tree at /sim/systems/autopilot[*]
}}

=== Adding a property-rule configuration ===
Property-rules can also be used in which case they will run at frame rate. You can use these to process properties so their values can be used by other systems outside of the autopilot scope (for example to create smooth animations for switches that normally have discrete values)

To achieve this load your filters configuration by adding:

<syntaxhighlight lang="xml">
<property-rule n="100"> 
<name>My property rule</name> 
<path>Systems/my-propertyrules.xml</path> 
</property-rule>
</syntaxhighlight>
(Do NOT use the filename "propertyrules.xml")

to the :

<syntaxhighlight lang="xml">
<sim>
<systems>

<property-rule n="100"> 
<name>My property rule</name> 
<path>Systems/my-propertyrules.xml</path> 
</property-rule>
</systems>
</sim>
</syntaxhighlight>

node of your <code><aircraft>-set.xml</code> file. Note that you can add multiple <syntaxhighlight lang="xml" inline><property-rule></syntaxhighlight> elements, similar to the <syntaxhighlight lang="xml" inline><autopilot></syntaxhighlight> as described above.

{{tip|Configurations can be enabled and disabled through the boolean properties <code>/sim/systems/autopilot[''n'']/serviceable</code> and <code>/sim/systems/property-rule[''n'']/serviceable</code>, where''n'' is the index for a configuration}}

== Structure of a configuration file ==
Autopilot configurations live in a separate file, formatted using the well known XML syntax like so many other FlightGear files with a <syntaxhighlight lang="xml" inline><PropertyList></syntaxhighlight> node as a root element. A basic skeleton file looks like this:

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>
<params include="MyParams.xml"> 
<controls>
<aileron>controls/flight/aileron</aileron>
<rudder>controls/flight/rudder</rudder>
<elevator>controls/flight/elevator</elevator>
</controls>
</params>



</PropertyList>
</syntaxhighlight>

The location and the name of the configuration file is up to the developer. A descriptive name like <code>autopilot.xml</code> might be a good choice. Most developers put these files into the <code>Systems</code> folder of the aircraft.

{{tip|Using [[PropertyList XML files#Aliased properties|aliased property names]] is good style and makes the configuration file more readable. The params section may be included from an external file to avoid duplication of code.

For complex systems, spread over multiple autopilot and/or property-rule configuration files, this can greatly aid debugging and maintenance.}}

{{tip|Commenting the configuration file to document the purpose elements and groups of elements and what they are intended to do can also aid debugging and maintenance.}}

== Available elements ==
All elements may contain the attributes "include" and "alias".
The "include" property takes a file name as a parameter. This can be used to read the document tree of an external XML file into the node containing the "include" attribute. The included file must have a PropertyList node as the root node. All nodes under this PropertyList node will be added to the node containing the "include" attribute.
The "alias" attribute refers to an element defined elsewhere in this XMl document. Alias references are in a path-style syntax, either as a relative or absolute path. Absolute paths start with a slash, like <syntaxhighlight lang="xml" inline><foo alias="/params/bar/baz"/></syntaxhighlight>. Use the colon to move through the document tree, similar to file system paths like <syntaxhighlight lang="xml" inline><foo alias="../../bar/baz"/></syntaxhighlight>.

Any top-level element can appear in an autopilot XML file, but only the following elements will be recognised and used:
* <syntaxhighlight lang="xml" inline><pid-controller></syntaxhighlight>
* <syntaxhighlight lang="xml" inline><pi-simple-controller></syntaxhighlight>
* <syntaxhighlight lang="xml" inline><filter></syntaxhighlight>
* <syntaxhighlight lang="xml" inline><predict-simple></syntaxhighlight>
* <syntaxhighlight lang="xml" inline><logic></syntaxhighlight>
* <syntaxhighlight lang="xml" inline><flipflop></syntaxhighlight>
* <syntaxhighlight lang="xml" inline><state-machine></syntaxhighlight>

== Common elements used by all elements ==

=== Name of filter and controller <name> ===
The <syntaxhighlight lang="xml" inline><name></syntaxhighlight> element is optional, but should be added to give the controller a distinct name. It is only used in debug output.

<syntaxhighlight lang="xml">
<name>NAV hold</name>
</syntaxhighlight>

=== Update interval ===
The <syntaxhighlight lang="xml" inline><update-interval-secs></syntaxhighlight> element is also optional, defaults to 0 which usually means 120Hz for autopilot and every frame for property-rules.

<syntaxhighlight lang="xml">
<update-interval-secs type="double">0.1</update-interval-secs>
</syntaxhighlight>

=== Feedback <feedback-if-disabled> ===
The <syntaxhighlight lang="xml" inline><feedback-if-disabled></syntaxhighlight> element advises the controller to feed back the output property value to the active input property if the condition defined in the <syntaxhighlight lang="xml" inline><enable></syntaxhighlight> tag evaluates to false. This is usually required for controllers like servo drivers behind a PID-controller to give that PID-controller a valid starting value when it becomes enabled. The absence of this element or anything but the word <syntaxhighlight lang="xml" inline>true</syntaxhighlight> within this element results in feedback disabled.

<syntaxhighlight lang="xml">
<feedback-if-disabled>true</feedback-if-disabled>
</syntaxhighlight>

=== Printing debug output <debug> ===
If the <syntaxhighlight lang="xml" inline><debug></syntaxhighlight> element is present and if it contains the word <syntaxhighlight lang="xml" inline>true</syntaxhighlight>, the containing controller prints out some diagnostic information on the console for each processing loop.

<syntaxhighlight lang="xml">
<debug>true</debug>
</syntaxhighlight>

=== Input and reference properties or values <input> and <reference> ===
Each controller has two input "lines", denoted by the tags <syntaxhighlight lang="xml" inline><input></syntaxhighlight> and <syntaxhighlight lang="xml" inline><reference></syntaxhighlight>. The arithmetic difference of these two values is used by the respective controller to compute it's output. Unfortunately due to historical reasons, the sign of input and reference is not consistent for all controllers. While the pid-controller and the pi-simple-controller compute "reference-input", the filter controller computes "input-reference". Each element is optional with a default value of zero. These elements are made of so called ''input values'' described further down in this document.

Example for a simple differential amplifier, computing output = (input-reference)*2

<syntaxhighlight lang="xml">
<filter>
<type>gain</type>
<gain>2.0</gain>
<input>/some/input</input>
<reference>/some/output</reference>
<output>/some/output</output>
</filter>
</syntaxhighlight>

=== Output property <output> ===
The <syntaxhighlight lang="xml" inline><output></syntaxhighlight> element names the properties, the computed value should be written to. More than one <syntaxhighlight lang="xml" inline><output></syntaxhighlight> may be present, each named property will be assigned the computed value.

<syntaxhighlight lang="xml">
<output>controls/flight/elevator</output>
</syntaxhighlight>

=== Enabling and disabling a filter <enable> ===
Controllers can be enabled or disabled using property values. This element <syntaxhighlight lang="xml" inline><enable></syntaxhighlight> may contain a <syntaxhighlight lang="xml" inline><prop></syntaxhighlight> and a <syntaxhighlight lang="xml" inline><value></syntaxhighlight> element. The controller is enabled, if the value of the named property equals the given value. This feature is considered deprecated and might go away in future releases. The preferred way of defining the enable-condition is by adding a <syntaxhighlight lang="xml" inline><condition></syntaxhighlight> element to the <syntaxhighlight lang="xml" inline><enable></syntaxhighlight> element. This <syntaxhighlight lang="xml" inline><condition></syntaxhighlight> follows the same syntactical rules as the one used in model animations and can model complex expression trees.
To enable a wing leveler only if the current bank angle does not exceed 30° of bank, use this condition

<syntaxhighlight lang="xml">
<enable>
<condition>
<less-than>
<property>orientation/bank-angle-deg</property>
<value>30.0</value>
</less-than>
<greater-than>
<property>orientation/bank-angle-deg</property>
<value>-30.0</value>
</greater-than>
</condition>
</enable>
</syntaxhighlight>

=== Input values ===
Input values for controllers may be specified in several notations. Values may be supplied as constants, from properties or by means of simple linear transformations. Conditions allow the selection of one of multiple input sources. The following text will use the <syntaxhighlight lang="xml" inline><reference></syntaxhighlight> element as an example but it may be substituted by any other input element like <syntaxhighlight lang="xml" inline><Kp></syntaxhighlight>, <syntaxhighlight lang="xml" inline><gain></syntaxhighlight> etc. Input values will be interpreted as double values.

==== A constant value <value> or <reference> ====
A constant value is defined by just adding the value as text to the input element:

<syntaxhighlight lang="xml">
<reference>
<value>3.5</value>
</reference>
</syntaxhighlight>

The shortcut syntax is also valid:

<syntaxhighlight lang="xml">
<reference>3.5</reference>
</syntaxhighlight>

If the text can be parsed by <code>strtod()</code> to a double value, it will be used as a constant value, otherwise it will be interpreted as a property value (see next paragraph)

==== A property value ====
To evaluate the value of a property, place the name of the property into the text element:

<syntaxhighlight lang="xml">
<reference>
<property>/my/property</property>
</reference>
</syntaxhighlight>

The shortcut syntax is also valid:
<syntaxhighlight lang="xml">
<reference>/my/property</reference>
</syntaxhighlight>

{{note|The shortcut syntax is only valid, if neither <syntaxhighlight lang="xml" inline><property></syntaxhighlight> nor <syntaxhighlight lang="xml" inline><value></syntaxhighlight> element exists.
If both <syntaxhighlight lang="xml" inline><property></syntaxhighlight> '''and''' <syntaxhighlight lang="xml" inline><value></syntaxhighlight> element exist, the property will be initialized with the given value with scale and offset applied correctly.
Properties don't have to exist, the will be created as needed.}}

{{note|For backward compatibility, the notation <syntaxhighlight lang="xml" inline><prop></syntaxhighlight> instead of <syntaxhighlight lang="xml" inline><property></syntaxhighlight> is also valid but considered deprecated and might go away in future releases.}}

==== Linear transformation of the input value <offset> ====
Input values may be scaled and shifted before they are processed by the controller using the formula <tt>y = value * scale + offset</tt>
To use a Celsius temperature property in a controller which expects the temperature in Fahrenheit you might use

<syntaxhighlight lang="xml">
<reference>
<property>/environment/temperature-degc</property>
<scale>1.8</scale>
<offset>32</offset>
</reference>
</syntaxhighlight>

==== Periodical transformation of the input value <period> ====
Periodical (like angular) input values can be transformed to appear in the correct phase before they are processed by the controller by adding or subtracting multiples of the period to the input value until the values is in the requested periods interval.
The following example converts the heading which comes in the range of [0..360] into the range of [-180..+180]. This will cause a heading of 270 to be processed as a value of -90.

<syntaxhighlight lang="xml">
<reference>
<property>/orientation/heading-deg</property>
<period>
<min>-180.0</min>
<max>180.0</max>
</period>
</reference>
</syntaxhighlight>

==== Input clamping <min> and <max> ====
To clamp the input to a minimum value, maximum value or both, the tags <syntaxhighlight lang="xml" inline><min></syntaxhighlight> and <syntaxhighlight lang="xml" inline><max></syntaxhighlight> can be used. Clamping will occur after the linear transformation has been applied. Note the difference of input clamping to output clamping. While input clamping is applied '''before''' the signal reaches the controller, output clamping will be applied to the output signal '''after''' it has been processed.

The following code will keep the input to the controller in the range of 60 to 80 degrees Fahrenheit:

<syntaxhighlight lang="xml">
<reference>
<property>/environment/temperature-degc</property>
<scale>1.8</scale>
<offset>32</offset>
<min>60</min>
<max>80</max>
</reference>
</syntaxhighlight>

==== Absolute values <abs> ====
To use the absolute (unsigned) value of the input, add <syntaxhighlight lang="xml" inline><abs type="bool">true</abs></syntaxhighlight>.

<syntaxhighlight lang="xml">
<reference>
<property>/autopilot/internal/course-error-deg</property>
<abs type="bool">true</abs>
</reference>
</syntaxhighlight>

==== Recursive definition ====
The elements <syntaxhighlight lang="xml" inline><scale></syntaxhighlight>, <syntaxhighlight lang="xml" inline><offset></syntaxhighlight>, <syntaxhighlight lang="xml" inline><min></syntaxhighlight> and <syntaxhighlight lang="xml" inline><max></syntaxhighlight> itself can be defined as input values. This code uses as reference the value of course-error-deg, scaled by two and an offset applied which is calculated as the product of the bank-angle-de and the property some/property which itself is limited within the range of -1.5 .. +1.5.

<syntaxhighlight lang="xml">
<reference>
<property>/autopilot/internal/course-error-deg</property>
<scale>2.0</scale>
<offset>
<property>orientation/bank-angle-deg</property>
<scale>
<property>some/property</property>
<min>-1.5</min>
<max>1.5</max>
</scale>
</offset>
</reference>
</syntaxhighlight>

==== Conditional input values <condition> ====
The direct inputs of controller and filter elements support so called input value lists. This is useful, if the input should be connected to one of many separate inputs like autopilots connected to NAV1, NAV2 or the GPS. A standard <syntaxhighlight lang="xml" inline><condition></syntaxhighlight> element is allowed within an input value element. The input value list will be traversed until the first input value with a successful condition is found. The behavior is much like the switch statement in programming languages.

<syntaxhighlight lang="xml">
<reference>
<condition>
<property>/autopilot/coupled-to-gps</property>
</condition>
<property>instrumentation/gps/desired-track-deg</property>
</reference>
<reference>
<condition>
<property>/autopilot/coupled-to-nav2</property>
</condition>
<property>instrumentation/nav[1]/radials/selected-deg</property>
</reference>
<reference>instrumentation/nav[0]/radials/selected-deg</reference>
</syntaxhighlight>

Note the unconditional last <syntaxhighlight lang="xml" inline><reference></syntaxhighlight> element which acts as an "if all others fail, use NAV1" anchor. If no input value return with a successful condition, the input value is undefined.

The <syntaxhighlight lang="xml" inline><scale></syntaxhighlight>, <syntaxhighlight lang="xml" inline><offset></syntaxhighlight>, <syntaxhighlight lang="xml" inline><min></syntaxhighlight> and <syntaxhighlight lang="xml" inline><max></syntaxhighlight> elements of input values itself currently don't support input value lists.

==== Expressions <expression> ====
Complex math or lookup tables may be represented using the [[expression]] syntax. The expression has to be enclosed in <syntaxhighlight lang="xml" inline><expression></syntaxhighlight> tag.

=== Output values ===
After processing of a component, the resulting value passes a transformation stage where it can be clipped or normalized into a given period. Periodic values such as angular properties may be normalized into a given period by adding a <syntaxhighlight lang="xml" inline><period></syntaxhighlight> element, defining the lower and upper bounds of the period. Additionally, a maximun and a minimum value may be given which will guarantee that the output value will ever exceed a defined value.

{{note|Both periodical normalization and clipping may be defined. If both are given, the value will be normalized first and the clipping will be applied to the normalized value.}}

The following example shifts the computed value into the interval of [-180..180] thereafter being limited into the interval of [-30..30]. The following table contains some computed values and the resulting written value:

{| class="prettytable"
! computed !! written
|-
| -350 || 10
|-
| -270 || 30
|-
| -90 || -30
|-
| -29 || -29
|-
| 29 || 29
|-
| 90 || 30
|-
| 350 || -10
|}

<syntaxhighlight lang="xml">
<output>/some/property</output>
<period>
<min>-180</min>
<max>180</max>
</period>
<min>-30</min>
<max>30</max>
</syntaxhighlight>

This example shows how to use a table to vary an output with height. At sea level, the output is 0.045, at 22400 the output is 0.1196, and at 56000 ft the output is 0.7

<syntaxhighlight lang="xml">
<filter>
<name>GAy</name>
<debug>false</debug>
<type>gain</type>
<gain>1.0</gain>
<input>
<expression>
<table>
<property>/instrumentation/altimeter/indicated-altitude-ft</property>
<entry><ind>0.0</ind><dep>0.045</dep></entry>
<entry><ind>22400</ind><dep>0.1196</dep></entry>
<entry><ind>56000</ind><dep>0.7</dep></entry>
</table>
</expression>
</input>
<output>
<property>/autopilot/gain/GAy</property>
</output>
</filter>
</syntaxhighlight>

== Logic controller <logic> ==
The logic controller provides a simple way of creating property values from the result of the condition expression in the <syntaxhighlight lang="xml" inline><input></syntaxhighlight> element. The condition expression is evaluated once per iteration and the result is written as a boolean value to the named output property or properties. An optional <syntaxhighlight lang="xml" inline><inverted></syntaxhighlight> element inverts the logic. The default is "not inverted".

Example: output = not( ( a is true ) or ( ( b greater than c ) and ( d is true ) )

<syntaxhighlight lang="xml">
<logic>
<inverted>true</inverted>
<input>
<property>a</property>
<or>
<greater-than>
<property>b</property>
<property>c</property>
</greater-than>
<property>d</property>
</or>
</input>
<output>output</output>
</logic>
</syntaxhighlight>

== Flip flop logic <flipflop> ==
A flip flop is a controller that has two stable states so it can be used as a one bit memory. Four types of flip flops are implemented: '''RS''', '''JK''', '''D''' and '''T'''. All use positive logic and operate on the raising edge of the clock signal if a clock is used.
All input lines, including the clock line, are encoded as condition constructs.
If negative logic for the input line is required, wrap the condition into a <syntaxhighlight lang="xml" inline><not></syntaxhighlight> tag to invert the logic.

{{note|The type, for example '''RS''', is case sensitive.}}
{{note|Using <syntaxhighlight lang="xml" inline><condition></syntaxhighlight> tags will break the logic.}}

=== RS flip flop <RS> ===
This flip flop sets its output according to the set (S) or reset (R) input lines. If the set line is set, the output gets set. If the reset line is set, the output gets reset. If no line is set, the output stays unchanged. For the special case where set and reset lines are both set, two types of RS flip flops exist: for the RS flip flop (<syntaxhighlight lang="xml" inline><type>RS</type></syntaxhighlight>), the reset line is dominant and the output is reset. Alternatively, a SR flip flop (<syntaxhighlight lang="xml" inline><type>SR</type></syntaxhighlight>) has a dominant set line and the output gets set if set and reset line are set.

Example: simple RS flip flop

<syntaxhighlight lang="xml">
<flipflop>
<type>RS</type> 
<S>
<property>/myflipflop/set</property>
</S>
<R>
<property>/myflipflop/reset</property>
</R>
<output>/myflipflop/output</output>
</flipflop>
</syntaxhighlight>

=== JK flip flop <JK> ===
The JK flip flop is an extension of the RS flip flop. In addition to the set and reset lines of the RS flip flop it uses J, K and a clock input.
The J line serves as a clock dependent set input while the K line does the reset job. Optionally, a clock input may be provided. State changes do not occur immediately, but on the next raising edge of the clock signal. The state of J=K=true causes the output to toggle it's current state on the next raising edge of the clock signal.
If no clock signal is provided, the frame rate serves as the clock input.

Example: simple JK flip flop with negative edge clock

<syntaxhighlight lang="xml">
<flipflop>
<type>JK</type>
<J>
<property>/myflipflop/set</property>
</J>
<K>
<property>/myflipflop/reset</property>
</K>
<clock>
<not>
<property>/myflipflop/clock</property>
</not>
</clock>
<output>/myflipflop/output</output>
</flipflop>
</syntaxhighlight>

=== D flip flop <D> ===
The D flip flop transfers the state of the input signal '''D''' to the output line at the next raising edge of the clock signal, which is mandatory for this flip flop.

Example: simple D flip flop with inverted output

<syntaxhighlight lang="xml">
<flipflop>
<type>D</type>
<D>
<property>/myflipflop/data</property>
</D>
<clock>
<property>/myflipflop/clock</property>
</clock>
<output>/myflipflop/output</output>
<inverted type="bool">true</inverted>
</flipflop>
</syntaxhighlight>

=== T flip flop <T> ===
The T flip flop toggles the state of the output signal at the next raising edge of the clock signal, which is mandatory for this flip flop.

Example: simple T flip flop

<syntaxhighlight lang="xml">
<flipflop>
<type>T</type>
<clock>
<property>/myflipflop/clock</property>
</clock>
<output>/myflipflop/output</output>
</flipflop>
</syntaxhighlight>

=== Monostable flip flop <monostable> ===
A monostable flip flop has only one stable state which will be reentered after a well defined time. The stable state in current implementation is the output set 'false' or 0. The Monostable is an extension of the JK flip flop. Additionally to the input values defined there, an InputValue for the definition of the pulse time is mandatory.

The moment the time for the astable state starts counting depends on the input used to set the output. If the output is set from the SET input of the RS flipflop, the output is kept true for the defined time ''after'' the SET input enters it's false state. The total time the output is true equals the time, the SET input is true plus the time defined in the <time> element.
If the output is set from the J and clock inputs of the JK flipflop, the timer starts on the raising edge of the clock input. The output signal will be true for exactly the time defined in the <syntaxhighlight lang="xml" inline><time></syntaxhighlight> element.

{{note|The optional <syntaxhighlight lang="xml" inline><R></syntaxhighlight> and <syntaxhighlight lang="xml" inline><K></syntaxhighlight> inputs may be used to reset the output before the internal timer expired. This will also reset the timer to zero, so no additional event will be triggered after the defined timer interval.}}
The following example shows how a monostable can be used to enable a certain property (/myflipflop/output) if another property (/myflipflop/s) is true for at least the specified amount of time:<syntaxhighlight lang="xml">
<flipflop>
<name>Test mf</name>
<type>monostable</type>
<time>
<property>/myflipflop/pulsetime-sec</property>
<value>10</value>
</time>
<S><property>/myflipflop/s</property></S>
<J><property>/myflipflop/j</property></J>
<clock><property>/myflipflop/clock</property></clock>
<output>/myflipflop/output</output>
</flipflop>
</syntaxhighlight>

In the example below the monostable is inverted, which means the stable state is true instead of false. The key idea here is to keep the monostable in its unstable state (false) by keeping the set line true, which is the case when /myflipflop/s is false. Then, when /myflipflop/s becomes true the set line becomes false, which causes the timer to start. When the timer expires (in this case 10 seconds) the monostable will enter its stable state (true). At any time when the set line becomes true (when /myflipflop/s becomes false) the monostable will immediately enter its unstable state (false) again, resulting in /myflipflop/output to become false immediately.

<syntaxhighlight lang="xml">
<flipflop>
<name>Test mf</name>
<type>monostable</type>
<inverted type="bool">true</inverted>
<S>
<not>
<property>/myflipflop/s</property>
</not>
</S>
<time>
<value>10.0</value>
</time>
<output>
<property>/myflipflop/output</property>
</output>
</flipflop>
</syntaxhighlight>

== Filters <filter> ==

=== Pure gain filter <gain> ===
A gain filter multiplies the <syntaxhighlight lang="xml" inline><input></syntaxhighlight> value by a given factor or gain <syntaxhighlight lang="xml" inline><gain></syntaxhighlight> and returns the output to <syntaxhighlight lang="xml" inline><output></syntaxhighlight>. More than one <syntaxhighlight lang="xml" inline><gain></syntaxhighlight> element formatted as in [[Autopilot Configuration Reference#Input Values|Input Values]] may be present. Within a <syntaxhighlight lang="xml" inline><condition></syntaxhighlight> evaluating as true the first <syntaxhighlight lang="xml" inline><gain></syntaxhighlight> will define the used gain.

<syntaxhighlight lang="xml">
<filter>
<type>gain</type>
<gain>6.28</gain>
<input>radius</input>
<output>circumfence</output>
</filter>
</syntaxhighlight>

=== First order low pass filter <exponential> ===
The exponential filter is a typical [http://en.wikipedia.org/wiki/Low-pass_filter low pass filter]. The magic Euler number and the associated mathematical function exp() plays a major role here. As the name implies, lower frequencies can pass this filter while higher frequencies are cut. The frequency where only half of the input signal reaches the output is called cutoff frequency. This cutoff frequency is defined by the parameter <syntaxhighlight lang="xml" inline><filter-time></syntaxhighlight> and resolves as cutoff-frequency = 1/(2*pi*cutoff-frequency).

Example: a 1Hz first order low pass filter

<syntaxhighlight lang="xml">
<filter>
<type>exponential</type>
<filter-time>0.16</filter-time>
<input>/some/input</input>
<output>/some/output/</output>
</filter>
</syntaxhighlight>

=== Second order low pass filter <double-exponential> ===
The double exponential filter is a low pass filter like the exponential filter with a steeper slope of the filter diagram. It acts basically like two chained exponential filters and it is some times called second order filter.

The configuration is the same for exponential and double-exponential filters, just the type entry differs.

<syntaxhighlight lang="xml">
<filter>
<type>double-exponential</type>
<filter-time>0.16</filter-time>
<input>/some/input</input>
<output>/some/output/<output>
</filter>
</syntaxhighlight>

=== First order high pass filter <high-pass> ===
The high pass filter is a typical [http://en.wikipedia.org/wiki/High-pass_filter high pass filter]. The magic euler number and the associated mathematical funtion exp() plays a major role here. As the name implies, higher frequencies can pass this filter while lower frequencies are cut. The frequency where only half of the input signal reaches the output is called cutoff frequency. This cutoff frequency is defined by the parameter <syntaxhighlight lang="xml" inline><filter-time></syntaxhighlight> and resolves as cutoff-frequency = 1/(2*pi*cutoff-frequency). It is commonly known as a wash-out filter or a 1st order lead filter

Example: a 1Hz first order high pass filter

<syntaxhighlight lang="xml">
<filter>
<type>high-pass</type>
<filter-time>0.16</filter-time>
<input>/some/input</input>
<output>/some/output/</output>
</filter>
</syntaxhighlight>

=== Lead-Lag filter <lead-lag> ===
The lead-lag filter is a typical [https://en.wikipedia.org/wiki/Lead%E2%80%93lag_compensator] lead lag filter. As the name implies it is a combination of a lead (high-pass) filter and a lag (low-pass) filter.

Example: a lead lag filter k(s+a)/s+b).
The gain is k, filter-time-a is a, and filter-time-b is b.

In an autopilot is is often used to sharpen up the response to an input.

<syntaxhighlight lang="xml">
<filter>
<name>loc-deg leadlag</name>
<debug>false</debug>
<type>lead-lag</type>
<gain>5</gain>
<filter-time-a>5.0</filter-time-a>
<filter-time-b>1.0</filter-time-b>
<input>
<property>/autopilot/internal/loc-deg</property>
</input>
<output>
<property>/autopilot/internal/loc-deg-leadlag</property>
</output>
</filter>
</syntaxhighlight>

=== Integrator filter <integrator> ===
The integrator filter provides integration with time.

Example: an integrator filter k(1/s).

In this example, the normal input (<syntaxhighlight lang="xml" inline><property>/autopilot/internal/p-deg_sec</property></syntaxhighlight>)is disconnected and replaved by (output x 10) input when relay Rb is closed. This has the effect of rapidly ramping the integrator output to zero.

<syntaxhighlight lang="xml">
<filter>
<name>synthetic bank from roll rate</name>
<debug>false</debug>
<type>integrator</type>
<gain>1.0</gain>
<input>
<condition>
<property>/autopilot/internal/Rb</property>
</condition>
<property>/autopilot/internal/p-deg_sec</property>
</input>
<input> 
<expression>
<product>
<value>-10.0</value>
<property>/autopilot/internal/phi-deg_synth</property>
</product>
</expression>
</input>
<output>
<property>/autopilot/internal/phi-deg_synth</property>
</output>
<u_min>-180</u_min>
<u_max>180</u_max>
</filter>
</syntaxhighlight>

=== Moving average filter <moving-average> ===
Calculates average of specified number of values.

Currently the average length can only be given as number of samples and not time.

<syntaxhighlight lang="xml">
<filter>
<type>moving-average</type>
<samples>120</samples>
<input>/some/input</input>
<output>/some/output</output>
</filter>
</syntaxhighlight>

=== Rate limit filter <noise-spike> ===
A better name for a noise spike filter would probably have been "rate limit filter". This is exactly what it does: limit the rate of change of the output value. The relevant configuration element is <syntaxhighlight lang="xml" inline><max-rate-of-change></syntaxhighlight> setting the maximum rate of change of the output property per second.

Example: A transition from 0 to 4 at the input property results in a linear increase of the output property over 8 seconds from 0 to 4 at a rate of 0.5/sec.

<syntaxhighlight lang="xml">
<filter>
<type>noise-spike</type>
<max-rate-of-change>0.5</max-rate-of-change>
<input>/some/input</input>
<output>/some/output</output>
</filter>
</syntaxhighlight>

=== Reciprocal filter <reciprocal> ===
Compute the reciprocal (1/x) value of the input property. If x is zero, no computation is performed. The optional <syntaxhighlight lang="xml" inline><gain></syntaxhighlight> element may be used to scale the value. Output computes as gain divided by input.

Example: compute the flight time per pound of burned fuel from the fuel flow

<syntaxhighlight lang="xml">
<filter>
<type>reciprocal</type>
<gain>1.0</gain>
<input>/engines/engine[0]/fuel-flow-pph</input>
<output>/engines/engine[0]/fuel-flow-hpp</output>
</filter>
</syntaxhighlight>

=== Derivative filter <derivative> ===
Compute first time derivative of the input property, that is change per unit of time. Time is measured in seconds. A <syntaxhighlight lang="xml" inline><filter-time></syntaxhighlight> acts as gain and must be given because it has default 0.

Example: compute derivative of static port pressure

<syntaxhighlight lang="xml">
<filter>
<type>derivative</type>
<input>systems/static[0]/pressure-inhg</input>
<output>autopilot/internal/pressure-rate</output>
<filter-time>1.0</filter-time>
</filter>
</syntaxhighlight>

=== Damped oscillation filter ===

Integrates x" + ax' + bx + c = 0

<syntaxhighlight lang="xml">
<filter>
<type>damped-oscillation</type>
<input>systems/get</input>
<a>1</a>
<b>2</b>
<c>3</c>
<output>autopilot/internal/oscillation</output>
</filter>
</syntaxhighlight>

== PID controller <pid-controller> ==
The [http://en.wikipedia.org/wiki/PID_controller PID controller] is the swiss army knife of automation and this implementation is suitable for most situations. It has a builtin anti-windup logic, and usage of <syntaxhighlight lang="xml" inline><max></syntaxhighlight> and <syntaxhighlight lang="xml" inline><min></syntaxhighlight> elements for clamping the output is mandatory. The most important thing to know is that this controller 'does not' compute absolute output values but an offset from the current value of the output property. This can lead to unexpected behavior if the current value of the output property is unknown when the controller is enabled. This behavior is different to that of the pi-simple-controller.

The xml element creating a pid controller is <syntaxhighlight lang="xml" inline><pid-controller></syntaxhighlight>.

Legal elements are:

{| class="prettytable"
! <syntaxhighlight lang="xml" inline><Kp></syntaxhighlight>
| The overall gain for the proportional, integral and derivative part
|-
! <syntaxhighlight lang="xml" inline><Ti></syntaxhighlight>
| Integrator time
|-
! <syntaxhighlight lang="xml" inline><Td></syntaxhighlight>
| Derivator time
|-
! <syntaxhighlight lang="xml" inline><Ts></syntaxhighlight>
| Sampling interval (default: sample at frame rate)
|-
! <syntaxhighlight lang="xml" inline><alpha></syntaxhighlight>
| Scaling factor for Td (defaults to 0.1)
|-
! <syntaxhighlight lang="xml" inline><beta></syntaxhighlight>
| Reference weighing factor for the proportional component (defaults to 1.0)
|-
! <syntaxhighlight lang="xml" inline><gamma></syntaxhighlight>
| Reference weighing factor for the derivate component (defaults to 0.0)
|}

== PI controller <pi-simple-controller> ==
This controller implements a PI controller. Other than the PID controller, it computes absolute output values, regardless of the value of the output property. It can by configured as an I-only, P-only or PI-controller. It has anti windup logic if <syntaxhighlight lang="xml" inline><min></syntaxhighlight> and <syntaxhighlight lang="xml" inline><max></syntaxhighlight> elements are present.
The xml element creating a PI controller is <syntaxhighlight lang="xml" inline><pi-simple-controller></syntaxhighlight>
Legal elements are:

{| class="prettytable"
! <syntaxhighlight lang="xml" inline><Kp></syntaxhighlight>
| Gain of the proportional component
|-
! <syntaxhighlight lang="xml" inline><Ki></syntaxhighlight>
| Gain of the integrator component
|}

== Predictor <predict-simple> ==
Estimates the future value for a given property based on its current (or averaged) rate of change.

Legal elements are:

{| class="prettytable"
! <syntaxhighlight lang="xml" inline><seconds></syntaxhighlight>
| The time to be estimated ahead
|-
! <syntaxhighlight lang="xml" inline><filter-gain></syntaxhighlight>
| Smoothing factor (0.0-1.0, 1.0=no smoothing)
|}

Example: compute estimated speed 5 seconds ahead

<syntaxhighlight lang="xml">
<predict-simple>
<name>predicted air speed 5 seconds ahead</name>
<debug>false</debug>
<input>velocities/airspeed-kt</input>
<output>autopilot/internal/airspeed-5-sec-ahead</output>
<seconds>5.0</seconds>
<filter-gain>0.1</filter-gain>
</predict-simple>
</syntaxhighlight>

== State Machine <state-machine> ==
For a description of what a state machine can do, look here: [http://en.wikipedia.org/wiki/Finite-state_machine].

{{note|Current behaviour with enter, exit and update tags differs from this documentation. Refer to the developer mailing list [https://sourceforge.net/p/flightgear/mailman/message/35557652/] before implementing bindings in state machines.}}

<syntaxhighlight lang="xml">
<state-machine>
<branch>/my-statemachine</branch>
<state>
<name>init</name>
<enter>
<binding></binding>
<binding></binding>
</enter>
<exit>
<binding></binding>
</exit>
<update>
<binding></binding>
</update>
</state>
<state>
<name>finished</name>
<enter>Zero to many bindings, fired upon state enter</enter>
<exit>Zero to many bindings, fired upon state exit</exit>
<update>Zero to many bindings, fired upon every state change</update>
</state>
<transition>
<name>ready</name>
<source>init</source>
<target>finished</target>
<exclude-target type="bool">true</exclude-target>
<condition>
<greater-than>
<property>/sim/time/elapsed-sec</property>
<value>30</value>
</greater-than>
</condition>
<binding>Zero to many bindings, fired upon state change</binding>
</transition>
</state-machine>
</syntaxhighlight>

Legal elements for the state machine are:

{| class="prettytable"
! <syntaxhighlight lang="xml" inline><branch></syntaxhighlight>
| A path to a property node where the internal states of the machine gets written to. Can be empty.
|-
! <syntaxhighlight lang="xml" inline><state></syntaxhighlight>
| Two ore more state elements are required for a minimal state machine
|-
! <syntaxhighlight lang="xml" inline><transition></syntaxhighlight>
| Any number of transition elements. Describes how to change from one state to another.
|}

Legal elements for the state element are:

{| class="prettytable"
! <syntaxhighlight lang="xml" inline><name></syntaxhighlight>
| Required, gives the state a name for reference
|-
! <syntaxhighlight lang="xml" inline><enter></syntaxhighlight>
| Optional, zero to many enter elements containing a SGBinding to fire upon state enter
|-
! <syntaxhighlight lang="xml" inline><exit></syntaxhighlight>
| Optional, zero to many exit elements containing a SGBinding to fire upon state exit
|-
! <syntaxhighlight lang="xml" inline><update></syntaxhighlight>
| Optional, zero to many update elements containing a SGBinding to fire upon state change
|}

Legal elements for the transition element are:

{| class="prettytable"
! <syntaxhighlight lang="xml" inline><name></syntaxhighlight>
| Required, gives the transition a name for reference
|-
! <syntaxhighlight lang="xml" inline><source></syntaxhighlight>
| Optional, zero to many source elements containing the name of a source state. If no source state is definied, this transition applies to all states.
|-
! <syntaxhighlight lang="xml" inline><target></syntaxhighlight>
| Required, exactly one target element defining the target state
|-
! <syntaxhighlight lang="xml" inline><condition></syntaxhighlight>
| Required, contains a SGCondition when this state change occours
|-
! <syntaxhighlight lang="xml" inline><exclude-target></syntaxhighlight>
| Optional, boolean flag defaults to true. Indicates if this transition should be evaluated even if current state equals target
|-
! <syntaxhighlight lang="xml" inline><binding></syntaxhighlight>
| Optional, zero to many binding elements containing a SGBinding to fire when this transition triggers
|}

== Proposed extensions ==
This sections contains new features for the autopilot to be implemented. Nobody knows if and when this will happen. Consider this as a collection of ideas as a base for discussion on the mailing list, the forum or IRC.

=== Expose to Nasal ===
Given that Nasal is a widely-known bottleneck, people should not use it for implement FDM/AP or route-manager functionality in scripting space. However, for the time being, the underlying C++ code is not exposed to scripting space, so that aircraft developers tend to reinvent the wheel. Thus, it would make sense to expose the AP/property-rule/state machine subsystems to scripting space using the [[Nasal/CppBind]] framework, to ensure that existing C++ code can be used for such purposes:

{{FGCquote
|1= I have recently committed some code to allow runtime loading of <strike>autopilots</strike> property rules and have a Nasal binding for that in mind.
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=149376#p149376
| title = <nowiki>Re: 2 Questions: vacuum & electrical</nowiki>
| author = <nowiki>Torsten</nowiki>
| date = Feb 2nd, 2012
}}
}}

== Related content ==
=== Wiki articles ===
* [[Autopilot PID controller tuning resources]]
* [[Howto:Design an autopilot]]
* [[Howto:Implement a Fly-By-Wire System for Airliners]]
* [[State machines]]

=== Readme file ===
* {{readme file|digitalfilters}}

=== Source code ===
* {{flightgear source|src/Autopilot/digitalfilter.hxx}}
* {{flightgear source|src/Autopilot/autopilot.cxx}}

[[Category:Aircraft enhancement]]

Howto:Reload sound configuration without restarting

2021-07-29T20:14:48Z

Sfrsfr: clarify alternate method

__NOTOC__

'''Reloading the sound configuration without restarting''' can be a massive time saver for those working on sound configuration files.

The Nasal console method described below no longer works. Instead you can reload the Aircraft model (Debug -> Reload Aircraft Model).

== Using the Nasal console ==
Note: this method does not work anymore.

The following line of Nasal code can be entered in the [[Nasal Console|Nasal console]] (found in the Debug [[menu]]).

<syntaxhighlight lang="nasal">
fgcommand("reinit", props.Node.new({ subsystem: "fx" }))
</syntaxhighlight>

Every time the line is executed the sound subsystem ("fx") is restarted and the configuration file reloaded, enabling you to test your changes instantly.

{{tip|Remember to actually save your sound configuration file each time you want to test it, so that FG can see the most recent changes.}}

== Reloading the sound config automatically ==
Here is a Nasal function which will automatically reload the sound configuration file when you make a change:

<syntaxhighlight lang="nasal">
var reload_sound = func {
var sf = getprop('/tmp/sound-xml/path');
if(sf == nil)
{
sf = getprop('/sim/fg-root') ~ '/' ~ getprop('/sim/sound/path');
setprop('/tmp/sound-xml/path', sf);
}
var st = io.stat(sf);
var lm = getprop('/tmp/sound-xml/modified');
if(lm == nil)
{
lm = st[9];
setprop('/tmp/sound-xml/modified', lm);
}
elsif(lm < st[9])
{
setprop('/tmp/sound-xml/modified', st[9]);
fgcommand('reinit', props.Node.new({ subsystem: "fx" }));
}
settimer(reload_sound, 2);
}
reload_sound();
</syntaxhighlight>

== Related content ==
* [[Howto:Add sound effects to aircraft]]

[[Category:Howto|Reload sound config without restarting]]

Howto:Add procedures to the route manager

2021-07-16T11:11:06Z

Sfrsfr: /* Instructions */ added missing 'Airports/' to path

{{Stub}}
{{Autoflight Navigation}}

== Objective ==
A free way to get more SID and STAR procedures for the FlightGear Route Planner<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=313123#p313123
|title = <nowiki> routeplanner stir sid </nowiki>
|author = <nowiki> Sarith </nowiki>
|date = Jun 24th, 2017
|added = Jun 24th, 2017
|script_version = 0.40
}}</ref>

== Background ==
Make some yourself. Charts are easy to find and a quick search will find you the syntax.
This is what FlightGear is all about; doing it yourself and sharing it to others.
A quick search would also find existing packages...<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=313128#p313128
|title = <nowiki> Re: routeplanner stir sid </nowiki>
|author = <nowiki> Parnikkapore </nowiki>
|date = Jun 24th, 2017
|added = Jun 24th, 2017
|script_version = 0.40
}}</ref>

== Instructions ==
SID and STAR procedures are found in the airport's procedures.xml file. There is at most one file per airport and it is located in the airport's root directory:

<scenery directory>/Airports/I/C/A/ICAO.procedures.xml

Where ICAO is your airport code.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=313362#p313362
|title = <nowiki> Re: routeplanner stir sid </nowiki>
|author = <nowiki> Parnikkapore </nowiki>
|date = Jun 28th, 2017
|added = Jun 28th, 2017
|script_version = 0.40
}}</ref>

For example, to import SID or STAR procedures for VTSP (Phuket International Airport), you name the file VTSP.procedures.xml and put it in the <scenery directory>/Airports/V/T/S/ directory. In there you will likely find VTSP.twr.xml but not an existing VTSP.procedures.xml file.
Replace "VTSP" in the directory and procedures.xml file name with your airport code.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=313409#p313409
|title = <nowiki> Re: routeplanner stir sid </nowiki>
|author = <nowiki> Parnikkapore </nowiki>
|date = Jun 29th, 2017
|added = Jun 29th, 2017
|script_version = 0.40
}}</ref>

== File Structure ==

In the explanation below, the name like "ProceduresDB" is the tag - so it's actually <ProceduresDB> in the XML file.
The subsequent parameters, like "build" are attributes - so it's actually <ProceduresDB build=""> in the XML file.

<pre>
ProceduresDB [build] (one of these per file)
|
Airport [ICAOcode] (one of these per file)
|
Sid [Name, Runways (comma separated - example: "08L,08R")] (many of these per Airport)
|
Sid_Waypoint [ID (unique sequential integer)] (many of these per Sid)
|
Name
Type
Latitude
Longitude
Speed
Altitude
AltitudeCons
AltitudeRestriction (one of "above" or "below" or "at")
Hdg_Crs (optional. example value = "1")
Hdg_Crs_Value (optional. heading degrees)
Sp_Turn (optional. example value = "Auto")
...
Sid_Transition [Name] (just one of these per Sid)
|
SidTr_Waypoint [ID] (many of these per Sid_Transition)

Star [Name] (many of these per Airport)
|
Star_Waypoint [ID] (many of these per Star)
...
Star_Transition [Name] (just one of these per Star)
|
StarTr_Waypoint [ID] (many of these per Star_Transition)

Approach [Name] (e.g., ILS08L - uses IL, if appropriate, and the runway name by convention)
|
App_Waypoint [ID]
App_Transition [Name] (just one of these per Approach)
|
AppTr_Waypoint [ID] (many of these per App_Transition)
</pre>

== Bash script ==
ZirconiumX wrote a bash script for putting the XML files into the FG required locations.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=280561#p280561
|title = <nowiki> Re: Non-Navigraph SID/STAR xml files </nowiki>
|author = <nowiki> ZirconiumX </nowiki>
|date = Mar 26th, 2016
|added = Mar 26th, 2016
|script_version = 0.40
}}</ref>

<syntaxhighlight lang="bash">
for file in $(ls *.xml)
do
# First, rename all the files to the correct convention
mv "$file" "${file%.xml}.procedures.xml"

# Then move it to the correct place
icao=${file%.xml}
icao1=$(echo $icao | cut -c 1)
icao2=$(echo $icao | cut -c 2)
icao3=$(echo $icao | cut -c 3)
mkdir -p $icao1/$icao2/$icao3
mv "${icao}.procedures.xml" "$icao1/$icao2/$icao3/${icao}.procedures.xml"
done
</syntaxhighlight>

== Sample procedures.xml File ==

Here is a link to an example to show how to implement what I've outlined above: https://github.com/fgx/fgx-airports/blob/gh-pages/LDS767_AIO_Individual_XML_Airports/KATL.xml<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=313583#p313583
|title = <nowiki> Re: routeplanner stir sid </nowiki>
|author = <nowiki> eric </nowiki>
|date = Jul 2nd, 2017
|added = Jul 2nd, 2017
|script_version = 0.40
}}</ref>

{{Cleanup}}

<syntaxhighlight lang="xml">
<ProceduresDB build='By Pedro Sousa, Wade Chafe, extracted by PROCIO 6a -Ian Mitchell'>
<Airport ICAOcode="KATL">
<Sid Name="BRAVS08LR" Runways="08L,08R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HRSHL</Name>
<Type>Normal</Type>
<Latitude>33.682769</Latitude>
<Longitude>-84.279567</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ESFOR</Name>
<Type>Normal</Type>
<Latitude>33.733953</Latitude>
<Longitude>-84.095019</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>ESTWU</Name>
<Type>Normal</Type>
<Latitude>33.694894</Latitude>
<Longitude>-84.000036</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>ESTUS</Name>
<Type>Normal</Type>
<Latitude>33.494547</Latitude>
<Longitude>-84.064303</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="6">
<Name>BRAVS</Name>
<Type>Normal</Type>
<Latitude>32.990278</Latitude>
<Longitude>-84.207500</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="WALET">
<SidTr_Waypoint ID="1">
<Name>WALET</Name>
<Type>Normal</Type>
<Latitude>32.363333</Latitude>
<Longitude>-83.920556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="BRAVS09L" Runways="09L">
<Sid_Waypoint ID="1">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>1480</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>NOFOR</Name>
<Type>Normal</Type>
<Latitude>33.388489</Latitude>
<Longitude>-84.277547</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>BRAVS</Name>
<Type>Normal</Type>
<Latitude>32.990278</Latitude>
<Longitude>-84.207500</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="WALET">
<SidTr_Waypoint ID="1">
<Name>WALET</Name>
<Type>Normal</Type>
<Latitude>32.363333</Latitude>
<Longitude>-83.920556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="BRAVS09R" Runways="09R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>NOFOR</Name>
<Type>Normal</Type>
<Latitude>33.388489</Latitude>
<Longitude>-84.277547</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>BRAVS</Name>
<Type>Normal</Type>
<Latitude>32.990278</Latitude>
<Longitude>-84.207500</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="WALET">
<SidTr_Waypoint ID="1">
<Name>WALET</Name>
<Type>Normal</Type>
<Latitude>32.363333</Latitude>
<Longitude>-83.920556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="BRAVS26L" Runways="26L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>BDODD</Name>
<Type>Normal</Type>
<Latitude>33.692583</Latitude>
<Longitude>-84.745694</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WEFIV</Name>
<Type>Normal</Type>
<Latitude>33.653625</Latitude>
<Longitude>-84.823667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>WEFOR</Name>
<Type>Normal</Type>
<Latitude>33.535472</Latitude>
<Longitude>-84.811328</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="6">
<Name>BRAVS</Name>
<Type>Normal</Type>
<Latitude>32.990278</Latitude>
<Longitude>-84.207500</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="WALET">
<SidTr_Waypoint ID="1">
<Name>WALET</Name>
<Type>Normal</Type>
<Latitude>32.363333</Latitude>
<Longitude>-83.920556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="BRAVS26R" Runways="26R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>BDODD</Name>
<Type>Normal</Type>
<Latitude>33.692583</Latitude>
<Longitude>-84.745694</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WEFIV</Name>
<Type>Normal</Type>
<Latitude>33.653625</Latitude>
<Longitude>-84.823667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>WEFOR</Name>
<Type>Normal</Type>
<Latitude>33.535472</Latitude>
<Longitude>-84.811328</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="6">
<Name>BRAVS</Name>
<Type>Normal</Type>
<Latitude>32.990278</Latitude>
<Longitude>-84.207500</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="WALET">
<SidTr_Waypoint ID="1">
<Name>WALET</Name>
<Type>Normal</Type>
<Latitude>32.363333</Latitude>
<Longitude>-83.920556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="BRAVS27L" Runways="27L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>BRAVS</Name>
<Type>Normal</Type>
<Latitude>32.990278</Latitude>
<Longitude>-84.207500</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="WALET">
<SidTr_Waypoint ID="1">
<Name>WALET</Name>
<Type>Normal</Type>
<Latitude>32.363333</Latitude>
<Longitude>-83.920556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="BRAVS27R" Runways="27R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>BRAVS</Name>
<Type>Normal</Type>
<Latitude>32.990278</Latitude>
<Longitude>-84.207500</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="WALET">
<SidTr_Waypoint ID="1">
<Name>WALET</Name>
<Type>Normal</Type>
<Latitude>32.363333</Latitude>
<Longitude>-83.920556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="CADIT08LR" Runways="08L,08R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HRSHL</Name>
<Type>Normal</Type>
<Latitude>33.682769</Latitude>
<Longitude>-84.279567</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>KLEGG</Name>
<Type>Normal</Type>
<Latitude>33.812508</Latitude>
<Longitude>-84.280006</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WIILL</Name>
<Type>Normal</Type>
<Latitude>34.023378</Latitude>
<Longitude>-84.440881</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>CADIT</Name>
<Type>Normal</Type>
<Latitude>34.286667</Latitude>
<Longitude>-84.537778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="RESPE">
<SidTr_Waypoint ID="1">
<Name>RESPE</Name>
<Type>Normal</Type>
<Latitude>35.591822</Latitude>
<Longitude>-84.920086</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="CADIT27L" Runways="27L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>WESEK</Name>
<Type>Normal</Type>
<Latitude>33.634847</Latitude>
<Longitude>-84.729267</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WODEB</Name>
<Type>Normal</Type>
<Latitude>33.704686</Latitude>
<Longitude>-84.811375</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>CADIT</Name>
<Type>Normal</Type>
<Latitude>34.286667</Latitude>
<Longitude>-84.537778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="RESPE">
<SidTr_Waypoint ID="1">
<Name>RESPE</Name>
<Type>Normal</Type>
<Latitude>35.591822</Latitude>
<Longitude>-84.920086</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
<Sid_Transition Name="RESPE">
<SidTr_Waypoint ID="1">
<Name>RESPE</Name>
<Type>Normal</Type>
<Latitude>35.591822</Latitude>
<Longitude>-84.920086</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="CADIT27R" Runways="27R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>WESEK</Name>
<Type>Normal</Type>
<Latitude>33.634847</Latitude>
<Longitude>-84.729267</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WODEB</Name>
<Type>Normal</Type>
<Latitude>33.704686</Latitude>
<Longitude>-84.811375</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>CADIT</Name>
<Type>Normal</Type>
<Latitude>34.286667</Latitude>
<Longitude>-84.537778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="RESPE">
<SidTr_Waypoint ID="1">
<Name>RESPE</Name>
<Type>Normal</Type>
<Latitude>35.591822</Latitude>
<Longitude>-84.920086</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
<Sid_Transition Name="RESPE">
<SidTr_Waypoint ID="1">
<Name>RESPE</Name>
<Type>Normal</Type>
<Latitude>35.591822</Latitude>
<Longitude>-84.920086</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="CADIT09R" Runways="09R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ERWIN</Name>
<Type>Normal</Type>
<Latitude>33.634167</Latitude>
<Longitude>-84.100556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>ESSEY</Name>
<Type>Normal</Type>
<Latitude>33.745372</Latitude>
<Longitude>-84.055922</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>CADIT</Name>
<Type>Normal</Type>
<Latitude>34.286667</Latitude>
<Longitude>-84.537778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
</Sid>
<Sid Name="CADIT09L" Runways="09L">
<Sid_Waypoint ID="1">
<Name>ERWIN</Name>
<Type>Normal</Type>
<Latitude>33.634167</Latitude>
<Longitude>-84.100556</Longitude>
<Speed>0</Speed>
<Altitude>1480</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ESSEY</Name>
<Type>Normal</Type>
<Latitude>33.745372</Latitude>
<Longitude>-84.055922</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>CADIT</Name>
<Type>Normal</Type>
<Latitude>34.286667</Latitude>
<Longitude>-84.537778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
</Sid>
<Sid Name="CADIT26L" Runways="26L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>PALGE</Name>
<Type>Normal</Type>
<Latitude>34.007300</Latitude>
<Longitude>-84.538381</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>CADIT</Name>
<Type>Normal</Type>
<Latitude>34.286667</Latitude>
<Longitude>-84.537778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="RESPE">
<SidTr_Waypoint ID="1">
<Name>RESPE</Name>
<Type>Normal</Type>
<Latitude>35.591822</Latitude>
<Longitude>-84.920086</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="CADIT26R" Runways="26R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>PALGE</Name>
<Type>Normal</Type>
<Latitude>34.007300</Latitude>
<Longitude>-84.538381</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>CADIT</Name>
<Type>Normal</Type>
<Latitude>34.286667</Latitude>
<Longitude>-84.537778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="RESPE">
<SidTr_Waypoint ID="1">
<Name>RESPE</Name>
<Type>Normal</Type>
<Latitude>35.591822</Latitude>
<Longitude>-84.920086</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="COKEM08LR" Runways="08L,08R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HRSHL</Name>
<Type>Normal</Type>
<Latitude>33.682769</Latitude>
<Longitude>-84.279567</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>KLEGG</Name>
<Type>Normal</Type>
<Latitude>33.812508</Latitude>
<Longitude>-84.280006</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>NAVVY</Name>
<Type>Normal</Type>
<Latitude>33.964783</Latitude>
<Longitude>-84.516347</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>COKEM</Name>
<Type>Normal</Type>
<Latitude>34.261111</Latitude>
<Longitude>-84.675000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="CARPT">
<SidTr_Waypoint ID="1">
<Name>CARPT</Name>
<Type>Normal</Type>
<Latitude>35.136389</Latitude>
<Longitude>-85.184167</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="COKEM09L" Runways="09L">
<Sid_Waypoint ID="1">
<Name>ERWIN</Name>
<Type>Normal</Type>
<Latitude>33.634167</Latitude>
<Longitude>-84.100556</Longitude>
<Speed>0</Speed>
<Altitude>1480</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ESSEY</Name>
<Type>Normal</Type>
<Latitude>33.745372</Latitude>
<Longitude>-84.055922</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>COKEM</Name>
<Type>Normal</Type>
<Latitude>34.261111</Latitude>
<Longitude>-84.675000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="CARPT">
<SidTr_Waypoint ID="1">
<Name>CARPT</Name>
<Type>Normal</Type>
<Latitude>35.136389</Latitude>
<Longitude>-85.184167</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="COKEM09R" Runways="09R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ERWIN</Name>
<Type>Normal</Type>
<Latitude>33.634167</Latitude>
<Longitude>-84.100556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>ESSEY</Name>
<Type>Normal</Type>
<Latitude>33.745372</Latitude>
<Longitude>-84.055922</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>COKEM</Name>
<Type>Normal</Type>
<Latitude>34.261111</Latitude>
<Longitude>-84.675000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="CARPT">
<SidTr_Waypoint ID="1">
<Name>CARPT</Name>
<Type>Normal</Type>
<Latitude>35.136389</Latitude>
<Longitude>-85.184167</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="COKEM26R" Runways="26R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>COKEM</Name>
<Type>Normal</Type>
<Latitude>34.261111</Latitude>
<Longitude>-84.675000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="CARPT">
<SidTr_Waypoint ID="1">
<Name>CARPT</Name>
<Type>Normal</Type>
<Latitude>35.136389</Latitude>
<Longitude>-85.184167</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="COKEM26L" Runways="26L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>COKEM</Name>
<Type>Normal</Type>
<Latitude>34.261111</Latitude>
<Longitude>-84.675000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="CARPT">
<SidTr_Waypoint ID="1">
<Name>CARPT</Name>
<Type>Normal</Type>
<Latitude>35.136389</Latitude>
<Longitude>-85.184167</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="COKEM27R" Runways="27R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>WESEK</Name>
<Type>Normal</Type>
<Latitude>33.634847</Latitude>
<Longitude>-84.729267</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WODEB</Name>
<Type>Normal</Type>
<Latitude>33.704686</Latitude>
<Longitude>-84.811375</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>COKEM</Name>
<Type>Normal</Type>
<Latitude>34.261111</Latitude>
<Longitude>-84.675000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="CARPT">
<SidTr_Waypoint ID="1">
<Name>CARPT</Name>
<Type>Normal</Type>
<Latitude>35.136389</Latitude>
<Longitude>-85.184167</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="COKEM27L" Runways="27L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>WESEK</Name>
<Type>Normal</Type>
<Latitude>33.634847</Latitude>
<Longitude>-84.729267</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WODEB</Name>
<Type>Normal</Type>
<Latitude>33.704686</Latitude>
<Longitude>-84.811375</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>COKEM</Name>
<Type>Normal</Type>
<Latitude>34.261111</Latitude>
<Longitude>-84.675000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="CARPT">
<SidTr_Waypoint ID="1">
<Name>CARPT</Name>
<Type>Normal</Type>
<Latitude>35.136389</Latitude>
<Longitude>-85.184167</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DAWGS08LR" Runways="08L,08R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HRSHL</Name>
<Type>Normal</Type>
<Latitude>33.682769</Latitude>
<Longitude>-84.279567</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>DAWGS</Name>
<Type>Normal</Type>
<Latitude>33.852500</Latitude>
<Longitude>-83.674444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="SPA">
<SidTr_Waypoint ID="1">
<Name>SPA</Name>
<Type>Normal</Type>
<Latitude>35.033664</Latitude>
<Longitude>-81.927069</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DAWGS09L" Runways="09L">
<Sid_Waypoint ID="1">
<Name>ERWIN</Name>
<Type>Normal</Type>
<Latitude>33.634167</Latitude>
<Longitude>-84.100556</Longitude>
<Speed>0</Speed>
<Altitude>1480</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>DAWGS</Name>
<Type>Normal</Type>
<Latitude>33.852500</Latitude>
<Longitude>-83.674444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="SPA">
<SidTr_Waypoint ID="1">
<Name>SPA</Name>
<Type>Normal</Type>
<Latitude>35.033664</Latitude>
<Longitude>-81.927069</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DAWGS09R" Runways="09R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ERWIN</Name>
<Type>Normal</Type>
<Latitude>33.634167</Latitude>
<Longitude>-84.100556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>DAWGS</Name>
<Type>Normal</Type>
<Latitude>33.852500</Latitude>
<Longitude>-83.674444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="SPA">
<SidTr_Waypoint ID="1">
<Name>SPA</Name>
<Type>Normal</Type>
<Latitude>35.033664</Latitude>
<Longitude>-81.927069</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DAWGS26R" Runways="26R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>KLEGG</Name>
<Type>Normal</Type>
<Latitude>33.812508</Latitude>
<Longitude>-84.280006</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>DAWGS</Name>
<Type>Normal</Type>
<Latitude>33.852500</Latitude>
<Longitude>-83.674444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="SPA">
<SidTr_Waypoint ID="1">
<Name>SPA</Name>
<Type>Normal</Type>
<Latitude>35.033664</Latitude>
<Longitude>-81.927069</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DAWGS26L" Runways="26L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>KLEGG</Name>
<Type>Normal</Type>
<Latitude>33.812508</Latitude>
<Longitude>-84.280006</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>DAWGS</Name>
<Type>Normal</Type>
<Latitude>33.852500</Latitude>
<Longitude>-83.674444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="SPA">
<SidTr_Waypoint ID="1">
<Name>SPA</Name>
<Type>Normal</Type>
<Latitude>35.033664</Latitude>
<Longitude>-81.927069</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DAWGS27R" Runways="27R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>DAWGS</Name>
<Type>Normal</Type>
<Latitude>33.852500</Latitude>
<Longitude>-83.674444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="SPA">
<SidTr_Waypoint ID="1">
<Name>SPA</Name>
<Type>Normal</Type>
<Latitude>35.033664</Latitude>
<Longitude>-81.927069</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DAWGS27L" Runways="27L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>DAWGS</Name>
<Type>Normal</Type>
<Latitude>33.852500</Latitude>
<Longitude>-83.674444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="SPA">
<SidTr_Waypoint ID="1">
<Name>SPA</Name>
<Type>Normal</Type>
<Latitude>35.033664</Latitude>
<Longitude>-81.927069</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DOOLY08LR" Runways="08L,08R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HRSHL</Name>
<Type>Normal</Type>
<Latitude>33.682769</Latitude>
<Longitude>-84.279567</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>DOOLY</Name>
<Type>Normal</Type>
<Latitude>33.691111</Latitude>
<Longitude>-83.632778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GRD">
<SidTr_Waypoint ID="1">
<Name>GRD</Name>
<Type>Normal</Type>
<Latitude>34.251567</Latitude>
<Longitude>-82.154150</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DOOLY09L" Runways="09L">
<Sid_Waypoint ID="1">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>1480</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ERWIN</Name>
<Type>Normal</Type>
<Latitude>33.634167</Latitude>
<Longitude>-84.100556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>DOOLY</Name>
<Type>Normal</Type>
<Latitude>33.691111</Latitude>
<Longitude>-83.632778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GRD">
<SidTr_Waypoint ID="1">
<Name>GRD</Name>
<Type>Normal</Type>
<Latitude>34.251567</Latitude>
<Longitude>-82.154150</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DOOLY09R" Runways="09R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ERWIN</Name>
<Type>Normal</Type>
<Latitude>33.634167</Latitude>
<Longitude>-84.100556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>DOOLY</Name>
<Type>Normal</Type>
<Latitude>33.691111</Latitude>
<Longitude>-83.632778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GRD">
<SidTr_Waypoint ID="1">
<Name>GRD</Name>
<Type>Normal</Type>
<Latitude>34.251567</Latitude>
<Longitude>-82.154150</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DOOLY26R" Runways="26R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>KLEGG</Name>
<Type>Normal</Type>
<Latitude>33.812508</Latitude>
<Longitude>-84.280006</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>DOOLY</Name>
<Type>Normal</Type>
<Latitude>33.691111</Latitude>
<Longitude>-83.632778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GRD">
<SidTr_Waypoint ID="1">
<Name>GRD</Name>
<Type>Normal</Type>
<Latitude>34.251567</Latitude>
<Longitude>-82.154150</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DOOLY26L" Runways="26L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>KLEGG</Name>
<Type>Normal</Type>
<Latitude>33.812508</Latitude>
<Longitude>-84.280006</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>DOOLY</Name>
<Type>Normal</Type>
<Latitude>33.691111</Latitude>
<Longitude>-83.632778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GRD">
<SidTr_Waypoint ID="1">
<Name>GRD</Name>
<Type>Normal</Type>
<Latitude>34.251567</Latitude>
<Longitude>-82.154150</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DOOLY27R" Runways="27R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>DOOLY</Name>
<Type>Normal</Type>
<Latitude>33.691111</Latitude>
<Longitude>-83.632778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GRD">
<SidTr_Waypoint ID="1">
<Name>GRD</Name>
<Type>Normal</Type>
<Latitude>34.251567</Latitude>
<Longitude>-82.154150</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="DOOLY27L" Runways="27L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>DOOLY</Name>
<Type>Normal</Type>
<Latitude>33.691111</Latitude>
<Longitude>-83.632778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GRD">
<SidTr_Waypoint ID="1">
<Name>GRD</Name>
<Type>Normal</Type>
<Latitude>34.251567</Latitude>
<Longitude>-82.154150</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="GEETK08LR" Runways="08L,08R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HRSHL</Name>
<Type>Normal</Type>
<Latitude>33.682769</Latitude>
<Longitude>-84.279567</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>KLEGG</Name>
<Type>Normal</Type>
<Latitude>33.812508</Latitude>
<Longitude>-84.280006</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>GEETK</Name>
<Type>Normal</Type>
<Latitude>33.618742</Latitude>
<Longitude>-85.231333</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VUZ">
<SidTr_Waypoint ID="1">
<Name>VUZ</Name>
<Type>Normal</Type>
<Latitude>33.670186</Latitude>
<Longitude>-86.899800</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="GEETK09L" Runways="09L">
<Sid_Waypoint ID="1">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>1480</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>GEETK</Name>
<Type>Normal</Type>
<Latitude>33.618742</Latitude>
<Longitude>-85.231333</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VUZ">
<SidTr_Waypoint ID="1">
<Name>VUZ</Name>
<Type>Normal</Type>
<Latitude>33.670186</Latitude>
<Longitude>-86.899800</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="GEETK09R" Runways="09R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>GEETK</Name>
<Type>Normal</Type>
<Latitude>33.618742</Latitude>
<Longitude>-85.231333</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VUZ">
<SidTr_Waypoint ID="1">
<Name>VUZ</Name>
<Type>Normal</Type>
<Latitude>33.670186</Latitude>
<Longitude>-86.899800</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="GEETK26R" Runways="26R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>BDODD</Name>
<Type>Normal</Type>
<Latitude>33.692583</Latitude>
<Longitude>-84.745694</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>GEETK</Name>
<Type>Normal</Type>
<Latitude>33.618742</Latitude>
<Longitude>-85.231333</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VUZ">
<SidTr_Waypoint ID="1">
<Name>VUZ</Name>
<Type>Normal</Type>
<Latitude>33.670186</Latitude>
<Longitude>-86.899800</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="GEETK26L" Runways="26L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>BDODD</Name>
<Type>Normal</Type>
<Latitude>33.692583</Latitude>
<Longitude>-84.745694</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>GEETK</Name>
<Type>Normal</Type>
<Latitude>33.618742</Latitude>
<Longitude>-85.231333</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VUZ">
<SidTr_Waypoint ID="1">
<Name>VUZ</Name>
<Type>Normal</Type>
<Latitude>33.670186</Latitude>
<Longitude>-86.899800</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="GEETK27R" Runways="27R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>GEETK</Name>
<Type>Normal</Type>
<Latitude>33.618742</Latitude>
<Longitude>-85.231333</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VUZ">
<SidTr_Waypoint ID="1">
<Name>VUZ</Name>
<Type>Normal</Type>
<Latitude>33.670186</Latitude>
<Longitude>-86.899800</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="GEETK27L" Runways="27L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>GEETK</Name>
<Type>Normal</Type>
<Latitude>33.618742</Latitude>
<Longitude>-85.231333</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VUZ">
<SidTr_Waypoint ID="1">
<Name>VUZ</Name>
<Type>Normal</Type>
<Latitude>33.670186</Latitude>
<Longitude>-86.899800</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="JCKTS08LR" Runways="08L,08R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HRSHL</Name>
<Type>Normal</Type>
<Latitude>33.682769</Latitude>
<Longitude>-84.279567</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>KLEGG</Name>
<Type>Normal</Type>
<Latitude>33.812508</Latitude>
<Longitude>-84.280006</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>JCKTS</Name>
<Type>Normal</Type>
<Latitude>33.446944</Latitude>
<Longitude>-85.196944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="JAMMR">
<SidTr_Waypoint ID="1">
<Name>JAMMR</Name>
<Type>Normal</Type>
<Latitude>33.232136</Latitude>
<Longitude>-86.942319</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="JCKTS09L" Runways="09L">
<Sid_Waypoint ID="1">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>1480</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>JCKTS</Name>
<Type>Normal</Type>
<Latitude>33.446944</Latitude>
<Longitude>-85.196944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="JAMMR">
<SidTr_Waypoint ID="1">
<Name>JAMMR</Name>
<Type>Normal</Type>
<Latitude>33.232136</Latitude>
<Longitude>-86.942319</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="JCKTS09R" Runways="09R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>JCKTS</Name>
<Type>Normal</Type>
<Latitude>33.446944</Latitude>
<Longitude>-85.196944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="JAMMR">
<SidTr_Waypoint ID="1">
<Name>JAMMR</Name>
<Type>Normal</Type>
<Latitude>33.232136</Latitude>
<Longitude>-86.942319</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="JCKTS26R" Runways="26R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>BDODD</Name>
<Type>Normal</Type>
<Latitude>33.692583</Latitude>
<Longitude>-84.745694</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>JCKTS</Name>
<Type>Normal</Type>
<Latitude>33.446944</Latitude>
<Longitude>-85.196944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="JAMMR">
<SidTr_Waypoint ID="1">
<Name>JAMMR</Name>
<Type>Normal</Type>
<Latitude>33.232136</Latitude>
<Longitude>-86.942319</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="JCKTS26L" Runways="26L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>BDODD</Name>
<Type>Normal</Type>
<Latitude>33.692583</Latitude>
<Longitude>-84.745694</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>JCKTS</Name>
<Type>Normal</Type>
<Latitude>33.446944</Latitude>
<Longitude>-85.196944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="JAMMR">
<SidTr_Waypoint ID="1">
<Name>JAMMR</Name>
<Type>Normal</Type>
<Latitude>33.232136</Latitude>
<Longitude>-86.942319</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="JCKTS27R" Runways="27R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>JCKTS</Name>
<Type>Normal</Type>
<Latitude>33.446944</Latitude>
<Longitude>-85.196944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="JAMMR">
<SidTr_Waypoint ID="1">
<Name>JAMMR</Name>
<Type>Normal</Type>
<Latitude>33.232136</Latitude>
<Longitude>-86.942319</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="JCKTS27L" Runways="27L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>JCKTS</Name>
<Type>Normal</Type>
<Latitude>33.446944</Latitude>
<Longitude>-85.196944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="JAMMR">
<SidTr_Waypoint ID="1">
<Name>JAMMR</Name>
<Type>Normal</Type>
<Latitude>33.232136</Latitude>
<Longitude>-86.942319</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="MUNSN08LR" Runways="08L,08R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HRSHL</Name>
<Type>Normal</Type>
<Latitude>33.682769</Latitude>
<Longitude>-84.279567</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>MUNSN</Name>
<Type>Normal</Type>
<Latitude>33.541111</Latitude>
<Longitude>-83.636111</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="IRQ">
<SidTr_Waypoint ID="1">
<Name>IRQ</Name>
<Type>Normal</Type>
<Latitude>33.707361</Latitude>
<Longitude>-82.162056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="MUNSN09L" Runways="09L">
<Sid_Waypoint ID="1">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>1480</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ERWIN</Name>
<Type>Normal</Type>
<Latitude>33.634167</Latitude>
<Longitude>-84.100556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>MUNSN</Name>
<Type>Normal</Type>
<Latitude>33.541111</Latitude>
<Longitude>-83.636111</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="IRQ">
<SidTr_Waypoint ID="1">
<Name>IRQ</Name>
<Type>Normal</Type>
<Latitude>33.707361</Latitude>
<Longitude>-82.162056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="MUNSN09R" Runways="09R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ERWIN</Name>
<Type>Normal</Type>
<Latitude>33.634167</Latitude>
<Longitude>-84.100556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>MUNSN</Name>
<Type>Normal</Type>
<Latitude>33.541111</Latitude>
<Longitude>-83.636111</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="IRQ">
<SidTr_Waypoint ID="1">
<Name>IRQ</Name>
<Type>Normal</Type>
<Latitude>33.707361</Latitude>
<Longitude>-82.162056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="MUNSN26R" Runways="26R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>KLEGG</Name>
<Type>Normal</Type>
<Latitude>33.812508</Latitude>
<Longitude>-84.280006</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>MUNSN</Name>
<Type>Normal</Type>
<Latitude>33.541111</Latitude>
<Longitude>-83.636111</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="IRQ">
<SidTr_Waypoint ID="1">
<Name>IRQ</Name>
<Type>Normal</Type>
<Latitude>33.707361</Latitude>
<Longitude>-82.162056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="MUNSN26L" Runways="26L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>KLEGG</Name>
<Type>Normal</Type>
<Latitude>33.812508</Latitude>
<Longitude>-84.280006</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>MUNSN</Name>
<Type>Normal</Type>
<Latitude>33.541111</Latitude>
<Longitude>-83.636111</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="IRQ">
<SidTr_Waypoint ID="1">
<Name>IRQ</Name>
<Type>Normal</Type>
<Latitude>33.707361</Latitude>
<Longitude>-82.162056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="MUNSN27R" Runways="27R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>MUNSN</Name>
<Type>Normal</Type>
<Latitude>33.541111</Latitude>
<Longitude>-83.636111</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="IRQ">
<SidTr_Waypoint ID="1">
<Name>IRQ</Name>
<Type>Normal</Type>
<Latitude>33.707361</Latitude>
<Longitude>-82.162056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="MUNSN27L" Runways="27L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>MUNSN</Name>
<Type>Normal</Type>
<Latitude>33.541111</Latitude>
<Longitude>-83.636111</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="IRQ">
<SidTr_Waypoint ID="1">
<Name>IRQ</Name>
<Type>Normal</Type>
<Latitude>33.707361</Latitude>
<Longitude>-82.162056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="PNUTT08LR" Runways="08L,08R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HRSHL</Name>
<Type>Normal</Type>
<Latitude>33.682769</Latitude>
<Longitude>-84.279567</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ESFOR</Name>
<Type>Normal</Type>
<Latitude>33.733953</Latitude>
<Longitude>-84.095019</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>ESTWU</Name>
<Type>Normal</Type>
<Latitude>33.694894</Latitude>
<Longitude>-84.000036</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>ESTUS</Name>
<Type>Normal</Type>
<Latitude>33.494547</Latitude>
<Longitude>-84.064303</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="6">
<Name>PNUTT</Name>
<Type>Normal</Type>
<Latitude>33.065000</Latitude>
<Longitude>-84.000000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="MCN">
<SidTr_Waypoint ID="1">
<Name>MCN</Name>
<Type>Normal</Type>
<Latitude>32.691169</Latitude>
<Longitude>-83.647183</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="PNUTT09L" Runways="09L">
<Sid_Waypoint ID="1">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>1480</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>NOFOR</Name>
<Type>Normal</Type>
<Latitude>33.388489</Latitude>
<Longitude>-84.277547</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>PNUTT</Name>
<Type>Normal</Type>
<Latitude>33.065000</Latitude>
<Longitude>-84.000000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="MCN">
<SidTr_Waypoint ID="1">
<Name>MCN</Name>
<Type>Normal</Type>
<Latitude>32.691169</Latitude>
<Longitude>-83.647183</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="PNUTT09R" Runways="09R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>NOFOR</Name>
<Type>Normal</Type>
<Latitude>33.388489</Latitude>
<Longitude>-84.277547</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>PNUTT</Name>
<Type>Normal</Type>
<Latitude>33.065000</Latitude>
<Longitude>-84.000000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="MCN">
<SidTr_Waypoint ID="1">
<Name>MCN</Name>
<Type>Normal</Type>
<Latitude>32.691169</Latitude>
<Longitude>-83.647183</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="PNUTT26R" Runways="26R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>BDODD</Name>
<Type>Normal</Type>
<Latitude>33.692583</Latitude>
<Longitude>-84.745694</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WEFIV</Name>
<Type>Normal</Type>
<Latitude>33.653625</Latitude>
<Longitude>-84.823667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>WEFOR</Name>
<Type>Normal</Type>
<Latitude>33.535472</Latitude>
<Longitude>-84.811328</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="6">
<Name>PNUTT</Name>
<Type>Normal</Type>
<Latitude>33.065000</Latitude>
<Longitude>-84.000000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="MCN">
<SidTr_Waypoint ID="1">
<Name>MCN</Name>
<Type>Normal</Type>
<Latitude>32.691169</Latitude>
<Longitude>-83.647183</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="PNUTT26L" Runways="26L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>BDODD</Name>
<Type>Normal</Type>
<Latitude>33.692583</Latitude>
<Longitude>-84.745694</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WEFIV</Name>
<Type>Normal</Type>
<Latitude>33.653625</Latitude>
<Longitude>-84.823667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>WEFOR</Name>
<Type>Normal</Type>
<Latitude>33.535472</Latitude>
<Longitude>-84.811328</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="6">
<Name>PNUTT</Name>
<Type>Normal</Type>
<Latitude>33.065000</Latitude>
<Longitude>-84.000000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="MCN">
<SidTr_Waypoint ID="1">
<Name>MCN</Name>
<Type>Normal</Type>
<Latitude>32.691169</Latitude>
<Longitude>-83.647183</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="PNUTT27R" Runways="27R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>PNUTT</Name>
<Type>Normal</Type>
<Latitude>33.065000</Latitude>
<Longitude>-84.000000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="MCN">
<SidTr_Waypoint ID="1">
<Name>MCN</Name>
<Type>Normal</Type>
<Latitude>32.691169</Latitude>
<Longitude>-83.647183</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="PNUTT27L" Runways="27L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>PNUTT</Name>
<Type>Normal</Type>
<Latitude>33.065000</Latitude>
<Longitude>-84.000000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="MCN">
<SidTr_Waypoint ID="1">
<Name>MCN</Name>
<Type>Normal</Type>
<Latitude>32.691169</Latitude>
<Longitude>-83.647183</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="RMBLN08LR" Runways="08L,08R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HRSHL</Name>
<Type>Normal</Type>
<Latitude>33.682769</Latitude>
<Longitude>-84.279567</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>KLEGG</Name>
<Type>Normal</Type>
<Latitude>33.812508</Latitude>
<Longitude>-84.280006</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>RMBLN</Name>
<Type>Normal</Type>
<Latitude>33.781944</Latitude>
<Longitude>-85.209444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GAD">
<SidTr_Waypoint ID="1">
<Name>HANKO</Name>
<Type>Normal</Type>
<Latitude>33.826389</Latitude>
<Longitude>-85.660556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>GAD</Name>
<Type>Normal</Type>
<Latitude>33.976403</Latitude>
<Longitude>-86.083558</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="RMBLN09L" Runways="09L">
<Sid_Waypoint ID="1">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>1480</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>RMBLN</Name>
<Type>Normal</Type>
<Latitude>33.781944</Latitude>
<Longitude>-85.209444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GAD">
<SidTr_Waypoint ID="1">
<Name>HANKO</Name>
<Type>Normal</Type>
<Latitude>33.826389</Latitude>
<Longitude>-85.660556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>GAD</Name>
<Type>Normal</Type>
<Latitude>33.976403</Latitude>
<Longitude>-86.083558</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="RMBLN09R" Runways="09R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>RMBLN</Name>
<Type>Normal</Type>
<Latitude>33.781944</Latitude>
<Longitude>-85.209444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GAD">
<SidTr_Waypoint ID="1">
<Name>HANKO</Name>
<Type>Normal</Type>
<Latitude>33.826389</Latitude>
<Longitude>-85.660556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>GAD</Name>
<Type>Normal</Type>
<Latitude>33.976403</Latitude>
<Longitude>-86.083558</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="RMBLN26R" Runways="26R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>BDODD</Name>
<Type>Normal</Type>
<Latitude>33.692583</Latitude>
<Longitude>-84.745694</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>RMBLN</Name>
<Type>Normal</Type>
<Latitude>33.781944</Latitude>
<Longitude>-85.209444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GAD">
<SidTr_Waypoint ID="1">
<Name>HANKO</Name>
<Type>Normal</Type>
<Latitude>33.826389</Latitude>
<Longitude>-85.660556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>GAD</Name>
<Type>Normal</Type>
<Latitude>33.976403</Latitude>
<Longitude>-86.083558</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="RMBLN26L" Runways="26L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>BDODD</Name>
<Type>Normal</Type>
<Latitude>33.692583</Latitude>
<Longitude>-84.745694</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>RMBLN</Name>
<Type>Normal</Type>
<Latitude>33.781944</Latitude>
<Longitude>-85.209444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GAD">
<SidTr_Waypoint ID="1">
<Name>HANKO</Name>
<Type>Normal</Type>
<Latitude>33.826389</Latitude>
<Longitude>-85.660556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>GAD</Name>
<Type>Normal</Type>
<Latitude>33.976403</Latitude>
<Longitude>-86.083558</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="RMBLN27R" Runways="27R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>RMBLN</Name>
<Type>Normal</Type>
<Latitude>33.781944</Latitude>
<Longitude>-85.209444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GAD">
<SidTr_Waypoint ID="1">
<Name>HANKO</Name>
<Type>Normal</Type>
<Latitude>33.826389</Latitude>
<Longitude>-85.660556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>GAD</Name>
<Type>Normal</Type>
<Latitude>33.976403</Latitude>
<Longitude>-86.083558</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="RMBLN27L" Runways="27L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>RMBLN</Name>
<Type>Normal</Type>
<Latitude>33.781944</Latitude>
<Longitude>-85.209444</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="GAD">
<SidTr_Waypoint ID="1">
<Name>HANKO</Name>
<Type>Normal</Type>
<Latitude>33.826389</Latitude>
<Longitude>-85.660556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>GAD</Name>
<Type>Normal</Type>
<Latitude>33.976403</Latitude>
<Longitude>-86.083558</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="SUMMT08LR" Runways="08L,08R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HRSHL</Name>
<Type>Normal</Type>
<Latitude>33.682769</Latitude>
<Longitude>-84.279567</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>KLEGG</Name>
<Type>Normal</Type>
<Latitude>33.812508</Latitude>
<Longitude>-84.280006</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>VOCAL</Name>
<Type>Normal</Type>
<Latitude>33.958733</Latitude>
<Longitude>-84.318919</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>SUMMT</Name>
<Type>Normal</Type>
<Latitude>34.278333</Latitude>
<Longitude>-84.260278</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VXV">
<SidTr_Waypoint ID="1">
<Name>GOVNR</Name>
<Type>Normal</Type>
<Latitude>34.945278</Latitude>
<Longitude>-84.126944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>VXV</Name>
<Type>Normal</Type>
<Latitude>35.904839</Latitude>
<Longitude>-83.894725</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="SUMMT09L" Runways="09L">
<Sid_Waypoint ID="1">
<Name>ERWIN</Name>
<Type>Normal</Type>
<Latitude>33.634167</Latitude>
<Longitude>-84.100556</Longitude>
<Speed>0</Speed>
<Altitude>1480</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ESSEY</Name>
<Type>Normal</Type>
<Latitude>33.745372</Latitude>
<Longitude>-84.055922</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>SUMMT</Name>
<Type>Normal</Type>
<Latitude>34.278333</Latitude>
<Longitude>-84.260278</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VXV">
<SidTr_Waypoint ID="1">
<Name>GOVNR</Name>
<Type>Normal</Type>
<Latitude>34.945278</Latitude>
<Longitude>-84.126944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>VXV</Name>
<Type>Normal</Type>
<Latitude>35.904839</Latitude>
<Longitude>-83.894725</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="SUMMT09R" Runways="09R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ERWIN</Name>
<Type>Normal</Type>
<Latitude>33.634167</Latitude>
<Longitude>-84.100556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>ESSEY</Name>
<Type>Normal</Type>
<Latitude>33.745372</Latitude>
<Longitude>-84.055922</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>SUMMT</Name>
<Type>Normal</Type>
<Latitude>34.278333</Latitude>
<Longitude>-84.260278</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VXV">
<SidTr_Waypoint ID="1">
<Name>GOVNR</Name>
<Type>Normal</Type>
<Latitude>34.945278</Latitude>
<Longitude>-84.126944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>VXV</Name>
<Type>Normal</Type>
<Latitude>35.904839</Latitude>
<Longitude>-83.894725</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="SUMMT26R" Runways="26R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>FANEL</Name>
<Type>Normal</Type>
<Latitude>33.940025</Latitude>
<Longitude>-84.399308</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>SUMMT</Name>
<Type>Normal</Type>
<Latitude>34.278333</Latitude>
<Longitude>-84.260278</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VXV">
<SidTr_Waypoint ID="1">
<Name>GOVNR</Name>
<Type>Normal</Type>
<Latitude>34.945278</Latitude>
<Longitude>-84.126944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>VXV</Name>
<Type>Normal</Type>
<Latitude>35.904839</Latitude>
<Longitude>-83.894725</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="SUMMT26L" Runways="26L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZELAN</Name>
<Type>Normal</Type>
<Latitude>33.811289</Latitude>
<Longitude>-84.582889</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>FANEL</Name>
<Type>Normal</Type>
<Latitude>33.940025</Latitude>
<Longitude>-84.399308</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>SUMMT</Name>
<Type>Normal</Type>
<Latitude>34.278333</Latitude>
<Longitude>-84.260278</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VXV">
<SidTr_Waypoint ID="1">
<Name>GOVNR</Name>
<Type>Normal</Type>
<Latitude>34.945278</Latitude>
<Longitude>-84.126944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>VXV</Name>
<Type>Normal</Type>
<Latitude>35.904839</Latitude>
<Longitude>-83.894725</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="SUMMT27R" Runways="27R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>WESEK</Name>
<Type>Normal</Type>
<Latitude>33.634847</Latitude>
<Longitude>-84.729267</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WODEB</Name>
<Type>Normal</Type>
<Latitude>33.704686</Latitude>
<Longitude>-84.811375</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>SUMMT</Name>
<Type>Normal</Type>
<Latitude>34.278333</Latitude>
<Longitude>-84.260278</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VXV">
<SidTr_Waypoint ID="1">
<Name>GOVNR</Name>
<Type>Normal</Type>
<Latitude>34.945278</Latitude>
<Longitude>-84.126944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>VXV</Name>
<Type>Normal</Type>
<Latitude>35.904839</Latitude>
<Longitude>-83.894725</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="SUMMT27L" Runways="27L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>WESEK</Name>
<Type>Normal</Type>
<Latitude>33.634847</Latitude>
<Longitude>-84.729267</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WODEB</Name>
<Type>Normal</Type>
<Latitude>33.704686</Latitude>
<Longitude>-84.811375</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>SUMMT</Name>
<Type>Normal</Type>
<Latitude>34.278333</Latitude>
<Longitude>-84.260278</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="VXV">
<SidTr_Waypoint ID="1">
<Name>GOVNR</Name>
<Type>Normal</Type>
<Latitude>34.945278</Latitude>
<Longitude>-84.126944</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
<SidTr_Waypoint ID="2">
<Name>VXV</Name>
<Type>Normal</Type>
<Latitude>35.904839</Latitude>
<Longitude>-83.894725</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="THRSR08LR" Runways="08L,08R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HRSHL</Name>
<Type>Normal</Type>
<Latitude>33.682769</Latitude>
<Longitude>-84.279567</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ESFOR</Name>
<Type>Normal</Type>
<Latitude>33.733953</Latitude>
<Longitude>-84.095019</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>ESTWU</Name>
<Type>Normal</Type>
<Latitude>33.694894</Latitude>
<Longitude>-84.000036</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>ESTUS</Name>
<Type>Normal</Type>
<Latitude>33.494547</Latitude>
<Longitude>-84.064303</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="6">
<Name>THRSR</Name>
<Type>Normal</Type>
<Latitude>32.959167</Latitude>
<Longitude>-84.443056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="LUCKK">
<SidTr_Waypoint ID="1">
<Name>LUCKK</Name>
<Type>Normal</Type>
<Latitude>32.300278</Latitude>
<Longitude>-84.416667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="THRSR09L" Runways="09L">
<Sid_Waypoint ID="1">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>1480</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>THRSR</Name>
<Type>Normal</Type>
<Latitude>32.959167</Latitude>
<Longitude>-84.443056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="LUCKK">
<SidTr_Waypoint ID="1">
<Name>LUCKK</Name>
<Type>Normal</Type>
<Latitude>32.300278</Latitude>
<Longitude>-84.416667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="THRSR09R" Runways="09R">
<Sid_Waypoint ID="1">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>LIDAS</Name>
<Type>Normal</Type>
<Latitude>33.635517</Latitude>
<Longitude>-84.269317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>HYZMN</Name>
<Type>Normal</Type>
<Latitude>33.467333</Latitude>
<Longitude>-84.276386</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>THRSR</Name>
<Type>Normal</Type>
<Latitude>32.959167</Latitude>
<Longitude>-84.443056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="LUCKK">
<SidTr_Waypoint ID="1">
<Name>LUCKK</Name>
<Type>Normal</Type>
<Latitude>32.300278</Latitude>
<Longitude>-84.416667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="THRSR26R" Runways="26R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>BDODD</Name>
<Type>Normal</Type>
<Latitude>33.692583</Latitude>
<Longitude>-84.745694</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WEFIV</Name>
<Type>Normal</Type>
<Latitude>33.653625</Latitude>
<Longitude>-84.823667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>WEFOR</Name>
<Type>Normal</Type>
<Latitude>33.535472</Latitude>
<Longitude>-84.811328</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="6">
<Name>THRSR</Name>
<Type>Normal</Type>
<Latitude>32.959167</Latitude>
<Longitude>-84.443056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="LUCKK">
<SidTr_Waypoint ID="1">
<Name>LUCKK</Name>
<Type>Normal</Type>
<Latitude>32.300278</Latitude>
<Longitude>-84.416667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="THRSR26L" Runways="26L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>CROUS</Name>
<Type>Normal</Type>
<Latitude>33.659594</Latitude>
<Longitude>-84.582778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>BDODD</Name>
<Type>Normal</Type>
<Latitude>33.692583</Latitude>
<Longitude>-84.745694</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>WEFIV</Name>
<Type>Normal</Type>
<Latitude>33.653625</Latitude>
<Longitude>-84.823667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="5">
<Name>WEFOR</Name>
<Type>Normal</Type>
<Latitude>33.535472</Latitude>
<Longitude>-84.811328</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="6">
<Name>THRSR</Name>
<Type>Normal</Type>
<Latitude>32.959167</Latitude>
<Longitude>-84.443056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="LUCKK">
<SidTr_Waypoint ID="1">
<Name>LUCKK</Name>
<Type>Normal</Type>
<Latitude>32.300278</Latitude>
<Longitude>-84.416667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="THRSR27R" Runways="27R">
<Sid_Waypoint ID="1">
<Name>(1520)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1520</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>THRSR</Name>
<Type>Normal</Type>
<Latitude>32.959167</Latitude>
<Longitude>-84.443056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="LUCKK">
<SidTr_Waypoint ID="1">
<Name>LUCKK</Name>
<Type>Normal</Type>
<Latitude>32.300278</Latitude>
<Longitude>-84.416667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Sid Name="THRSR27L" Runways="27L">
<Sid_Waypoint ID="1">
<Name>(1540)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1540</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>272</Hdg_Crs_value>
<Sp_Turn>Auto</Sp_Turn>
</Sid_Waypoint>
<Sid_Waypoint ID="2">
<Name>ROJRS</Name>
<Type>Normal</Type>
<Latitude>33.588156</Latitude>
<Longitude>-84.584639</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="3">
<Name>ZALLE</Name>
<Type>Normal</Type>
<Latitude>33.468994</Latitude>
<Longitude>-84.584508</Longitude>
<Speed>250</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Waypoint ID="4">
<Name>THRSR</Name>
<Type>Normal</Type>
<Latitude>32.959167</Latitude>
<Longitude>-84.443056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Sid_Waypoint>
<Sid_Transition Name="LUCKK">
<SidTr_Waypoint ID="1">
<Name>LUCKK</Name>
<Type>Normal</Type>
<Latitude>32.300278</Latitude>
<Longitude>-84.416667</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</SidTr_Waypoint>
</Sid_Transition>
</Sid>
<Star Name="LGC1">
<Star_Waypoint ID="1">
<Name>LGC</Name>
<Type>Normal</Type>
<Latitude>33.049083</Latitude>
<Longitude>-85.206200</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="2">
<Name>HONIE</Name>
<Type>Normal</Type>
<Latitude>33.183778</Latitude>
<Longitude>-85.028603</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="3">
<Name>TIROE</Name>
<Type>Normal</Type>
<Latitude>33.306453</Latitude>
<Longitude>-84.866031</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>ATL</Name>
<Type>Normal</Type>
<Latitude>33.629072</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Transition Name="MEI">
<StarTr_Waypoint ID="1">
<Name>MEI</Name>
<Type>Normal</Type>
<Latitude>32.378450</Latitude>
<Longitude>-88.804269</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>MOBEE</Name>
<Type>Normal</Type>
<Latitude>32.597436</Latitude>
<Longitude>-86.833333</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>YARBE</Name>
<Type>Normal</Type>
<Latitude>32.712444</Latitude>
<Longitude>-85.663686</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>TIMMY</Name>
<Type>Normal</Type>
<Latitude>32.800381</Latitude>
<Longitude>-85.544747</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="GCV">
<StarTr_Waypoint ID="1">
<Name>GCV</Name>
<Type>Normal</Type>
<Latitude>31.097961</Latitude>
<Longitude>-88.486128</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>PAYTN</Name>
<Type>Normal</Type>
<Latitude>31.467875</Latitude>
<Longitude>-87.885531</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>IVLUH</Name>
<Type>Normal</Type>
<Latitude>31.978231</Latitude>
<Longitude>-87.041319</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>OBXAY</Name>
<Type>Normal</Type>
<Latitude>32.755492</Latitude>
<Longitude>-85.718331</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="MGM">
<StarTr_Waypoint ID="1">
<Name>MGM</Name>
<Type>Normal</Type>
<Latitude>32.222283</Latitude>
<Longitude>-86.319731</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>YARBE</Name>
<Type>Normal</Type>
<Latitude>32.712444</Latitude>
<Longitude>-85.663686</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>TIMMY</Name>
<Type>Normal</Type>
<Latitude>32.800381</Latitude>
<Longitude>-85.544747</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="SZW">
<StarTr_Waypoint ID="1">
<Name>SZW</Name>
<Type>Normal</Type>
<Latitude>30.556228</Latitude>
<Longitude>-84.373961</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>WYATT</Name>
<Type>Normal</Type>
<Latitude>31.322900</Latitude>
<Longitude>-84.625111</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>GOONS</Name>
<Type>Normal</Type>
<Latitude>31.867114</Latitude>
<Longitude>-84.805717</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>CLEAV</Name>
<Type>Normal</Type>
<Latitude>32.586575</Latitude>
<Longitude>-85.048219</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="CTY">
<StarTr_Waypoint ID="1">
<Name>CTY</Name>
<Type>Normal</Type>
<Latitude>29.599028</Latitude>
<Longitude>-83.048719</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>WYATT</Name>
<Type>Normal</Type>
<Latitude>31.322900</Latitude>
<Longitude>-84.625111</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>GOONS</Name>
<Type>Normal</Type>
<Latitude>31.867114</Latitude>
<Longitude>-84.805717</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>CLEAV</Name>
<Type>Normal</Type>
<Latitude>32.586575</Latitude>
<Longitude>-85.048219</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
</Star>
<Star Name="MACEY2">
<Star_Waypoint ID="1">
<Name>MACEY</Name>
<Type>Normal</Type>
<Latitude>34.333461</Latitude>
<Longitude>-83.688653</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="2">
<Name>WOMAC</Name>
<Type>Normal</Type>
<Latitude>34.130239</Latitude>
<Longitude>-83.905769</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="3">
<Name>LOGEN</Name>
<Type>Normal</Type>
<Latitude>33.988050</Latitude>
<Longitude>-84.056786</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>ATL</Name>
<Type>Normal</Type>
<Latitude>33.629072</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Transition Name="VXV">
<StarTr_Waypoint ID="1">
<Name>VXV</Name>
<Type>Normal</Type>
<Latitude>35.904839</Latitude>
<Longitude>-83.894725</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>SABIN</Name>
<Type>Normal</Type>
<Latitude>35.249053</Latitude>
<Longitude>-83.810683</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="GQO">
<StarTr_Waypoint ID="1">
<Name>GQO</Name>
<Type>Normal</Type>
<Latitude>34.961336</Latitude>
<Longitude>-85.153364</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>SABIN</Name>
<Type>Normal</Type>
<Latitude>35.249053</Latitude>
<Longitude>-83.810683</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="SPA">
<StarTr_Waypoint ID="1">
<Name>SPA</Name>
<Type>Normal</Type>
<Latitude>35.033664</Latitude>
<Longitude>-81.927069</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>ODF</Name>
<Type>Normal</Type>
<Latitude>34.695872</Latitude>
<Longitude>-83.297661</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="MOL">
<StarTr_Waypoint ID="1">
<Name>MOL</Name>
<Type>Normal</Type>
<Latitude>37.900525</Latitude>
<Longitude>-79.106889</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>JOINN</Name>
<Type>Normal</Type>
<Latitude>37.017750</Latitude>
<Longitude>-80.316278</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>AVERY</Name>
<Type>Normal</Type>
<Latitude>35.817592</Latitude>
<Longitude>-81.891044</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>BEBAD</Name>
<Type>Normal</Type>
<Latitude>35.186603</Latitude>
<Longitude>-82.689528</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="5">
<Name>ODF</Name>
<Type>Normal</Type>
<Latitude>34.695872</Latitude>
<Longitude>-83.297661</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
</Star>
<Star Name="RMG2">
<Star_Waypoint ID="1">
<Name>RMG</Name>
<Type>Normal</Type>
<Latitude>34.162569</Latitude>
<Longitude>-85.119422</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="2">
<Name>ERLIN</Name>
<Type>Normal</Type>
<Latitude>34.085467</Latitude>
<Longitude>-85.019608</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="3">
<Name>DALAS</Name>
<Type>Normal</Type>
<Latitude>33.952250</Latitude>
<Longitude>-84.848022</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>ATL</Name>
<Type>Normal</Type>
<Latitude>33.629072</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Transition Name="BNA">
<StarTr_Waypoint ID="1">
<Name>BNA</Name>
<Type>Normal</Type>
<Latitude>36.136972</Latitude>
<Longitude>-86.684778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>DRAKK</Name>
<Type>Normal</Type>
<Latitude>35.746961</Latitude>
<Longitude>-86.368172</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>NEUTO</Name>
<Type>Normal</Type>
<Latitude>35.078297</Latitude>
<Longitude>-85.833925</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="BWG">
<StarTr_Waypoint ID="1">
<Name>BWG</Name>
<Type>Normal</Type>
<Latitude>36.928742</Latitude>
<Longitude>-86.443433</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>DRAKK</Name>
<Type>Normal</Type>
<Latitude>35.746961</Latitude>
<Longitude>-86.368172</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>NEUTO</Name>
<Type>Normal</Type>
<Latitude>35.078297</Latitude>
<Longitude>-85.833925</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="SALMS">
<StarTr_Waypoint ID="1">
<Name>SALMS</Name>
<Type>Normal</Type>
<Latitude>35.000903</Latitude>
<Longitude>-86.785497</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="MEM">
<StarTr_Waypoint ID="1">
<Name>MEM</Name>
<Type>Normal</Type>
<Latitude>35.015117</Latitude>
<Longitude>-89.983208</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>ABROC</Name>
<Type>Normal</Type>
<Latitude>34.617917</Latitude>
<Longitude>-87.434969</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>CALCO</Name>
<Type>Normal</Type>
<Latitude>34.345333</Latitude>
<Longitude>-86.019222</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
</Star>
<Star Name="SINCA3">
<Star_Waypoint ID="1">
<Name>SINCA</Name>
<Type>Normal</Type>
<Latitude>33.081189</Latitude>
<Longitude>-83.604867</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="2">
<Name>CANUK</Name>
<Type>Normal</Type>
<Latitude>33.216708</Latitude>
<Longitude>-83.808456</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="3">
<Name>HUSKY</Name>
<Type>Normal</Type>
<Latitude>33.330458</Latitude>
<Longitude>-83.980208</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>ATL</Name>
<Type>Normal</Type>
<Latitude>33.629072</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Transition Name="IRQ">
<StarTr_Waypoint ID="1">
<Name>IRQ</Name>
<Type>Normal</Type>
<Latitude>33.707361</Latitude>
<Longitude>-82.162056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>BEYLO</Name>
<Type>Normal</Type>
<Latitude>33.305344</Latitude>
<Longitude>-83.095117</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="AMG">
<StarTr_Waypoint ID="1">
<Name>AMG</Name>
<Type>Normal</Type>
<Latitude>31.536531</Latitude>
<Longitude>-82.508078</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>DBN</Name>
<Type>Normal</Type>
<Latitude>32.560722</Latitude>
<Longitude>-82.833197</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>RIPPI</Name>
<Type>Normal</Type>
<Latitude>32.904256</Latitude>
<Longitude>-83.340717</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="VQQ">
<StarTr_Waypoint ID="1">
<Name>VQQ</Name>
<Type>Normal</Type>
<Latitude>30.212994</Latitude>
<Longitude>-81.890894</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>CHESN</Name>
<Type>Normal</Type>
<Latitude>30.839308</Latitude>
<Longitude>-81.801803</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>BAXLY</Name>
<Type>Normal</Type>
<Latitude>31.745156</Latitude>
<Longitude>-82.339169</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>DBN</Name>
<Type>Normal</Type>
<Latitude>32.560722</Latitude>
<Longitude>-82.833197</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="5">
<Name>RIPPI</Name>
<Type>Normal</Type>
<Latitude>32.904256</Latitude>
<Longitude>-83.340717</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="CRG">
<StarTr_Waypoint ID="1">
<Name>CRG</Name>
<Type>Normal</Type>
<Latitude>30.338861</Latitude>
<Longitude>-81.509950</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>RDNEK</Name>
<Type>Normal</Type>
<Latitude>30.755683</Latitude>
<Longitude>-81.755986</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>CHESN</Name>
<Type>Normal</Type>
<Latitude>30.839308</Latitude>
<Longitude>-81.801803</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>BAXLY</Name>
<Type>Normal</Type>
<Latitude>31.745156</Latitude>
<Longitude>-82.339169</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="5">
<Name>DBN</Name>
<Type>Normal</Type>
<Latitude>32.560722</Latitude>
<Longitude>-82.833197</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="6">
<Name>RIPPI</Name>
<Type>Normal</Type>
<Latitude>32.904256</Latitude>
<Longitude>-83.340717</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="DBN">
<StarTr_Waypoint ID="1">
<Name>DBN</Name>
<Type>Normal</Type>
<Latitude>32.560722</Latitude>
<Longitude>-82.833197</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>RIPPI</Name>
<Type>Normal</Type>
<Latitude>32.904256</Latitude>
<Longitude>-83.340717</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
</Star>
<Star Name="CANUK1">
<Star_Waypoint ID="1">
<Name>SINCA</Name>
<Type>Normal</Type>
<Latitude>33.081189</Latitude>
<Longitude>-83.604867</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="2">
<Name>CANUK</Name>
<Type>Normal</Type>
<Latitude>33.216714</Latitude>
<Longitude>-83.808481</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="3">
<Name>HUSKY</Name>
<Type>Normal</Type>
<Latitude>33.330458</Latitude>
<Longitude>-83.980208</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>EMJAA</Name>
<Type>Normal</Type>
<Latitude>33.421111</Latitude>
<Longitude>-84.117500</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Transition Name="AMG">
<StarTr_Waypoint ID="1">
<Name>AMG</Name>
<Type>Normal</Type>
<Latitude>31.536531</Latitude>
<Longitude>-82.508078</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>DBN</Name>
<Type>Normal</Type>
<Latitude>32.560722</Latitude>
<Longitude>-82.833197</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>RIPPI</Name>
<Type>Normal</Type>
<Latitude>32.904256</Latitude>
<Longitude>-83.340717</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="CRG">
<StarTr_Waypoint ID="1">
<Name>CRG</Name>
<Type>Normal</Type>
<Latitude>30.338861</Latitude>
<Longitude>-81.509950</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>RDNEK</Name>
<Type>Normal</Type>
<Latitude>30.755683</Latitude>
<Longitude>-81.755986</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>CHESN</Name>
<Type>Normal</Type>
<Latitude>30.839308</Latitude>
<Longitude>-81.801803</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>BAXLY</Name>
<Type>Normal</Type>
<Latitude>31.745156</Latitude>
<Longitude>-82.339169</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="5">
<Name>DBN</Name>
<Type>Normal</Type>
<Latitude>32.560722</Latitude>
<Longitude>-82.833197</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="6">
<Name>RIPPI</Name>
<Type>Normal</Type>
<Latitude>32.904256</Latitude>
<Longitude>-83.340717</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="VQQ">
<StarTr_Waypoint ID="1">
<Name>VQQ</Name>
<Type>Normal</Type>
<Latitude>30.212994</Latitude>
<Longitude>-81.890894</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>CHESN</Name>
<Type>Normal</Type>
<Latitude>30.839308</Latitude>
<Longitude>-81.801803</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>BAXLY</Name>
<Type>Normal</Type>
<Latitude>31.745156</Latitude>
<Longitude>-82.339169</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>DBN</Name>
<Type>Normal</Type>
<Latitude>32.560722</Latitude>
<Longitude>-82.833197</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="5">
<Name>RIPPI</Name>
<Type>Normal</Type>
<Latitude>32.904256</Latitude>
<Longitude>-83.340717</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="IRQ">
<StarTr_Waypoint ID="1">
<Name>IRQ</Name>
<Type>Normal</Type>
<Latitude>33.707361</Latitude>
<Longitude>-82.162056</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>BEYLO</Name>
<Type>Normal</Type>
<Latitude>33.305344</Latitude>
<Longitude>-83.095117</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="DBN">
<StarTr_Waypoint ID="1">
<Name>DBN</Name>
<Type>Normal</Type>
<Latitude>32.560722</Latitude>
<Longitude>-82.833197</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>RIPPI</Name>
<Type>Normal</Type>
<Latitude>32.904256</Latitude>
<Longitude>-83.340717</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
</Star>
<Star Name="ERLIN1">
<Star_Waypoint ID="1">
<Name>RMG</Name>
<Type>Normal</Type>
<Latitude>34.162569</Latitude>
<Longitude>-85.119422</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="2">
<Name>ERLIN</Name>
<Type>Normal</Type>
<Latitude>34.085403</Latitude>
<Longitude>-85.019611</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="3">
<Name>DALAS</Name>
<Type>Normal</Type>
<Latitude>33.952250</Latitude>
<Longitude>-84.848022</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>STUTZ</Name>
<Type>Normal</Type>
<Latitude>33.855000</Latitude>
<Longitude>-84.724167</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Transition Name="BWG">
<StarTr_Waypoint ID="1">
<Name>BWG</Name>
<Type>Normal</Type>
<Latitude>36.928742</Latitude>
<Longitude>-86.443433</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>DRAKK</Name>
<Type>Normal</Type>
<Latitude>35.746961</Latitude>
<Longitude>-86.368172</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>NEUTO</Name>
<Type>Normal</Type>
<Latitude>35.078297</Latitude>
<Longitude>-85.833925</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="BNA">
<StarTr_Waypoint ID="1">
<Name>BNA</Name>
<Type>Normal</Type>
<Latitude>36.136972</Latitude>
<Longitude>-86.684778</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>DRAKK</Name>
<Type>Normal</Type>
<Latitude>35.746961</Latitude>
<Longitude>-86.368172</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>NEUTO</Name>
<Type>Normal</Type>
<Latitude>35.078297</Latitude>
<Longitude>-85.833925</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="SALMS">
<StarTr_Waypoint ID="1">
<Name>SALMS</Name>
<Type>Normal</Type>
<Latitude>35.000903</Latitude>
<Longitude>-86.785497</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="MEM">
<StarTr_Waypoint ID="1">
<Name>MEM</Name>
<Type>Normal</Type>
<Latitude>35.015117</Latitude>
<Longitude>-89.983208</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>ABROC</Name>
<Type>Normal</Type>
<Latitude>34.618081</Latitude>
<Longitude>-87.435167</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>CALCO</Name>
<Type>Normal</Type>
<Latitude>34.345333</Latitude>
<Longitude>-86.019222</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
</Star>
<Star Name="HONIE1">
<Star_Waypoint ID="1">
<Name>LGC</Name>
<Type>Normal</Type>
<Latitude>33.049083</Latitude>
<Longitude>-85.206200</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="2">
<Name>HONIE</Name>
<Type>Normal</Type>
<Latitude>33.183778</Latitude>
<Longitude>-85.028603</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="3">
<Name>TIROE</Name>
<Type>Normal</Type>
<Latitude>33.306453</Latitude>
<Longitude>-84.866031</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>WOLMN</Name>
<Type>Normal</Type>
<Latitude>33.407500</Latitude>
<Longitude>-84.730278</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Transition Name="MEI">
<StarTr_Waypoint ID="1">
<Name>MEI</Name>
<Type>Normal</Type>
<Latitude>32.378450</Latitude>
<Longitude>-88.804269</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>MOBEE</Name>
<Type>Normal</Type>
<Latitude>32.597436</Latitude>
<Longitude>-86.833333</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>YARBE</Name>
<Type>Normal</Type>
<Latitude>32.712444</Latitude>
<Longitude>-85.663686</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>TIMMY</Name>
<Type>Normal</Type>
<Latitude>32.800381</Latitude>
<Longitude>-85.544747</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="GCV">
<StarTr_Waypoint ID="1">
<Name>GCV</Name>
<Type>Normal</Type>
<Latitude>31.097961</Latitude>
<Longitude>-88.486128</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>PAYTN</Name>
<Type>Normal</Type>
<Latitude>31.467875</Latitude>
<Longitude>-87.885531</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>IVLUH</Name>
<Type>Normal</Type>
<Latitude>31.978231</Latitude>
<Longitude>-87.041319</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>OBXAY</Name>
<Type>Normal</Type>
<Latitude>32.755492</Latitude>
<Longitude>-85.718331</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="MGM">
<StarTr_Waypoint ID="1">
<Name>MGM</Name>
<Type>Normal</Type>
<Latitude>32.222283</Latitude>
<Longitude>-86.319731</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>YARBE</Name>
<Type>Normal</Type>
<Latitude>32.712444</Latitude>
<Longitude>-85.663686</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>TIMMY</Name>
<Type>Normal</Type>
<Latitude>32.800381</Latitude>
<Longitude>-85.544747</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="CTY">
<StarTr_Waypoint ID="1">
<Name>CTY</Name>
<Type>Normal</Type>
<Latitude>29.599028</Latitude>
<Longitude>-83.048719</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>WYATT</Name>
<Type>Normal</Type>
<Latitude>31.322900</Latitude>
<Longitude>-84.625111</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>GOONS</Name>
<Type>Normal</Type>
<Latitude>31.867114</Latitude>
<Longitude>-84.805717</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>CLEAV</Name>
<Type>Normal</Type>
<Latitude>32.586575</Latitude>
<Longitude>-85.048219</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
</Star>
<Star Name="WOMAC1">
<Star_Waypoint ID="1">
<Name>MACEY</Name>
<Type>Normal</Type>
<Latitude>34.333403</Latitude>
<Longitude>-83.688633</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="2">
<Name>WOMAC</Name>
<Type>Normal</Type>
<Latitude>34.130239</Latitude>
<Longitude>-83.905769</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="3">
<Name>LOGEN</Name>
<Type>Normal</Type>
<Latitude>33.988050</Latitude>
<Longitude>-84.056786</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>ESTHR</Name>
<Type>Normal</Type>
<Latitude>33.880000</Latitude>
<Longitude>-84.171111</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</Star_Waypoint>
<Star_Transition Name="SPA">
<StarTr_Waypoint ID="1">
<Name>SPA</Name>
<Type>Normal</Type>
<Latitude>35.033664</Latitude>
<Longitude>-81.927069</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>ODF</Name>
<Type>Normal</Type>
<Latitude>34.695872</Latitude>
<Longitude>-83.297661</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="MOL">
<StarTr_Waypoint ID="1">
<Name>MOL</Name>
<Type>Normal</Type>
<Latitude>37.900525</Latitude>
<Longitude>-79.106889</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>JOINN</Name>
<Type>Normal</Type>
<Latitude>37.017756</Latitude>
<Longitude>-80.316283</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="3">
<Name>AVERY</Name>
<Type>Normal</Type>
<Latitude>35.817592</Latitude>
<Longitude>-81.891044</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="4">
<Name>BEBAD</Name>
<Type>Normal</Type>
<Latitude>35.186603</Latitude>
<Longitude>-82.689528</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="5">
<Name>ODF</Name>
<Type>Normal</Type>
<Latitude>34.695872</Latitude>
<Longitude>-83.297661</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="VXV">
<StarTr_Waypoint ID="1">
<Name>VXV</Name>
<Type>Normal</Type>
<Latitude>35.904839</Latitude>
<Longitude>-83.894725</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
<StarTr_Waypoint ID="2">
<Name>SABIN</Name>
<Type>Normal</Type>
<Latitude>35.249003</Latitude>
<Longitude>-83.810678</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
<Star_Transition Name="ODF">
<StarTr_Waypoint ID="1">
<Name>ODF</Name>
<Type>Normal</Type>
<Latitude>34.695872</Latitude>
<Longitude>-83.297661</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</StarTr_Waypoint>
</Star_Transition>
</Star>
<Approach Name="ILS08L">
<App_Waypoint ID="1">
<Name>BAHRR</Name>
<Type>Normal</Type>
<Latitude>33.649125</Latitude>
<Longitude>-84.677650</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>REIFF</Name>
<Type>Normal</Type>
<Latitude>33.649306</Latitude>
<Longitude>-84.600389</Longitude>
<Speed>0</Speed>
<Altitude>3700</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>AT</Name>
<Type>Normal</Type>
<Latitude>33.646811</Latitude>
<Longitude>-84.542111</Longitude>
<Speed>170</Speed>
<Altitude>2800</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>RW08L</Name>
<Type>Runway</Type>
<Latitude>33.649539</Latitude>
<Longitude>-84.439025</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>92</Hdg_Crs_value>
<Sp_Turn>Right</Sp_Turn>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>ATL02</Name>
<Type>Normal</Type>
<Latitude>33.695578</Latitude>
<Longitude>-84.440627</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>TROYS</Name>
<Type>Normal</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="8">
<Name>TROYS</Name>
<Type>Hold</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Rad</Hld_Rad_or_Inbd>
<Hld_Rad_value>0</Hld_Rad_value>
<Hld_Turn>Right</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="WOTBA">
<AppTr_Waypoint ID="1">
<Name>FANEW</Name>
<Type>Normal</Type>
<Latitude>33.730794</Latitude>
<Longitude>-84.327614</Longitude>
<Speed>210</Speed>
<Altitude>12000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="2">
<Name>NOFIV</Name>
<Type>Normal</Type>
<Latitude>33.730258</Latitude>
<Longitude>-84.564478</Longitude>
<Speed>0</Speed>
<Altitude>7000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="3">
<Name>NOTRE</Name>
<Type>Normal</Type>
<Latitude>33.730989</Latitude>
<Longitude>-84.749850</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="4">
<Name>WOTBA</Name>
<Type>Normal</Type>
<Latitude>33.730731</Latitude>
<Longitude>-84.847519</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="ILS08R">
<App_Waypoint ID="1">
<Name>CHINN</Name>
<Type>Normal</Type>
<Latitude>33.646497</Latitude>
<Longitude>-84.676100</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>STUMP</Name>
<Type>Normal</Type>
<Latitude>33.646636</Latitude>
<Longitude>-84.600597</Longitude>
<Speed>0</Speed>
<Altitude>3700</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>AT</Name>
<Type>Normal</Type>
<Latitude>33.646811</Latitude>
<Longitude>-84.542111</Longitude>
<Speed>170</Speed>
<Altitude>2800</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>RW08R</Name>
<Type>Runway</Type>
<Latitude>33.646792</Latitude>
<Longitude>-84.438361</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>94</Hdg_Crs_value>
<Sp_Turn>Right</Sp_Turn>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>ATL01</Name>
<Type>Normal</Type>
<Latitude>33.695578</Latitude>
<Longitude>-84.440627</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>TROYS</Name>
<Type>Normal</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="8">
<Name>TROYS</Name>
<Type>Hold</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Rad</Hld_Rad_or_Inbd>
<Hld_Rad_value>0</Hld_Rad_value>
<Hld_Turn>Right</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="WOTBA">
<AppTr_Waypoint ID="1">
<Name>FANEW</Name>
<Type>Normal</Type>
<Latitude>33.730794</Latitude>
<Longitude>-84.327614</Longitude>
<Speed>210</Speed>
<Altitude>12000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="2">
<Name>NOFIV</Name>
<Type>Normal</Type>
<Latitude>33.730258</Latitude>
<Longitude>-84.564478</Longitude>
<Speed>0</Speed>
<Altitude>7000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="3">
<Name>NOTRE</Name>
<Type>Normal</Type>
<Latitude>33.730989</Latitude>
<Longitude>-84.749850</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="4">
<Name>WOTBA</Name>
<Type>Normal</Type>
<Latitude>33.730731</Latitude>
<Longitude>-84.847519</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="ILS09R">
<App_Waypoint ID="1">
<Name>TIZZY</Name>
<Type>Normal</Type>
<Latitude>33.631747</Latitude>
<Longitude>-84.627903</Longitude>
<Speed>0</Speed>
<Altitude>4000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>BURNY</Name>
<Type>Normal</Type>
<Latitude>33.632192</Latitude>
<Longitude>-84.542789</Longitude>
<Speed>0</Speed>
<Altitude>2700</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>RW09R</Name>
<Type>Runway</Type>
<Latitude>33.631822</Latitude>
<Longitude>-84.447967</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>94</Hdg_Crs_value>
<Sp_Turn>Right</Sp_Turn>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>ATL01</Name>
<Type>Normal</Type>
<Latitude>33.562566</Latitude>
<Longitude>-84.429525</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>SCARR</Name>
<Type>Normal</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>SCARR</Name>
<Type>Hold</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Rad</Hld_Rad_or_Inbd>
<Hld_Rad_value>180</Hld_Rad_value>
<Hld_Turn>Right</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="HESPI">
<AppTr_Waypoint ID="1">
<Name>BOJAA</Name>
<Type>Normal</Type>
<Latitude>33.545031</Latitude>
<Longitude>-84.307436</Longitude>
<Speed>210</Speed>
<Altitude>12000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="2">
<Name>FOGOG</Name>
<Type>Normal</Type>
<Latitude>33.545144</Latitude>
<Longitude>-84.546883</Longitude>
<Speed>0</Speed>
<Altitude>7000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="3">
<Name>SOTRE</Name>
<Type>Normal</Type>
<Latitude>33.545831</Latitude>
<Longitude>-84.749644</Longitude>
<Speed>0</Speed>
<Altitude>4000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="4">
<Name>HESPI</Name>
<Type>Normal</Type>
<Latitude>33.545972</Latitude>
<Longitude>-84.855000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="ILS26L">
<App_Waypoint ID="1">
<Name>KINKY</Name>
<Type>Normal</Type>
<Latitude>33.648864</Latitude>
<Longitude>-84.160419</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>PANOL</Name>
<Type>Normal</Type>
<Latitude>33.646636</Latitude>
<Longitude>-84.234614</Longitude>
<Speed>0</Speed>
<Altitude>3800</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>BR</Name>
<Type>Normal</Type>
<Latitude>33.645394</Latitude>
<Longitude>-84.311236</Longitude>
<Speed>0</Speed>
<Altitude>2600</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>RW26L</Name>
<Type>Runway</Type>
<Latitude>33.646797</Latitude>
<Longitude>-84.405511</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>(1400)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1400</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>273</Hdg_Crs_value>
<Sp_Turn>Right</Sp_Turn>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>ATL01</Name>
<Type>Normal</Type>
<Latitude>33.695578</Latitude>
<Longitude>-84.440627</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>TROYS</Name>
<Type>Normal</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="8">
<Name>TROYS</Name>
<Type>Hold</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Rad</Hld_Rad_or_Inbd>
<Hld_Rad_value>0</Hld_Rad_value>
<Hld_Turn>Right</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="IGEBE">
<AppTr_Waypoint ID="1">
<Name>NOFIV</Name>
<Type>Normal</Type>
<Latitude>33.730258</Latitude>
<Longitude>-84.564478</Longitude>
<Speed>210</Speed>
<Altitude>12000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="2">
<Name>FANEW</Name>
<Type>Normal</Type>
<Latitude>33.730794</Latitude>
<Longitude>-84.327614</Longitude>
<Speed>0</Speed>
<Altitude>7000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="3">
<Name>HAVAD</Name>
<Type>Normal</Type>
<Latitude>33.731214</Latitude>
<Longitude>-84.143967</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="4">
<Name>IGEBE</Name>
<Type>Normal</Type>
<Latitude>33.731242</Latitude>
<Longitude>-84.015556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="ILS26R">
<App_Waypoint ID="1">
<Name>FREAL</Name>
<Type>Normal</Type>
<Latitude>33.649275</Latitude>
<Longitude>-84.170042</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>BALLI</Name>
<Type>Normal</Type>
<Latitude>33.649400</Latitude>
<Longitude>-84.241194</Longitude>
<Speed>0</Speed>
<Altitude>3800</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>AJAAY</Name>
<Type>Normal</Type>
<Latitude>33.649483</Latitude>
<Longitude>-84.311186</Longitude>
<Speed>0</Speed>
<Altitude>2700</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>RW26R</Name>
<Type>Runway</Type>
<Latitude>33.649544</Latitude>
<Longitude>-84.409453</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>(1600)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1600</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>274</Hdg_Crs_value>
<Sp_Turn>Right</Sp_Turn>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>ATL01</Name>
<Type>Normal</Type>
<Latitude>33.695578</Latitude>
<Longitude>-84.440627</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>TROYS</Name>
<Type>Normal</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="8">
<Name>TROYS</Name>
<Type>Hold</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Rad</Hld_Rad_or_Inbd>
<Hld_Rad_value>0</Hld_Rad_value>
<Hld_Turn>Right</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="IGEBE">
<AppTr_Waypoint ID="1">
<Name>NOFIV</Name>
<Type>Normal</Type>
<Latitude>33.730258</Latitude>
<Longitude>-84.564478</Longitude>
<Speed>210</Speed>
<Altitude>12000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="2">
<Name>FANEW</Name>
<Type>Normal</Type>
<Latitude>33.730794</Latitude>
<Longitude>-84.327614</Longitude>
<Speed>0</Speed>
<Altitude>7000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="3">
<Name>HAVAD</Name>
<Type>Normal</Type>
<Latitude>33.731214</Latitude>
<Longitude>-84.143967</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="4">
<Name>IGEBE</Name>
<Type>Normal</Type>
<Latitude>33.731242</Latitude>
<Longitude>-84.015556</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="ILS27L">
<App_Waypoint ID="1">
<Name>ANVAL</Name>
<Type>Normal</Type>
<Latitude>33.631669</Latitude>
<Longitude>-84.238197</Longitude>
<Speed>0</Speed>
<Altitude>4000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>DEPOT</Name>
<Type>Normal</Type>
<Latitude>33.631761</Latitude>
<Longitude>-84.310303</Longitude>
<Speed>0</Speed>
<Altitude>2800</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>RW27L</Name>
<Type>Runway</Type>
<Latitude>33.631825</Latitude>
<Longitude>-84.418403</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>(1400)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1400</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>274</Hdg_Crs_value>
<Sp_Turn>Right</Sp_Turn>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>ATL01</Name>
<Type>Normal</Type>
<Latitude>33.562566</Latitude>
<Longitude>-84.429525</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>SCARR</Name>
<Type>Normal</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>SCARR</Name>
<Type>Hold</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Rad</Hld_Rad_or_Inbd>
<Hld_Rad_value>180</Hld_Rad_value>
<Hld_Turn>Right</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="SOFOR">
<AppTr_Waypoint ID="1">
<Name>FOGOG</Name>
<Type>Normal</Type>
<Latitude>33.545144</Latitude>
<Longitude>-84.546883</Longitude>
<Speed>210</Speed>
<Altitude>12000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="2">
<Name>BOJAA</Name>
<Type>Normal</Type>
<Latitude>33.545031</Latitude>
<Longitude>-84.307436</Longitude>
<Speed>0</Speed>
<Altitude>7000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="3">
<Name>HEDEG</Name>
<Type>Normal</Type>
<Latitude>33.545206</Latitude>
<Longitude>-84.107089</Longitude>
<Speed>0</Speed>
<Altitude>4000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="4">
<Name>SOFOR</Name>
<Type>Normal</Type>
<Latitude>33.545433</Latitude>
<Longitude>-84.003383</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="ILS27R">
<App_Waypoint ID="1">
<Name>HOKIE</Name>
<Type>Normal</Type>
<Latitude>33.634450</Latitude>
<Longitude>-84.230383</Longitude>
<Speed>0</Speed>
<Altitude>4000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>LIAMS</Name>
<Type>Normal</Type>
<Latitude>33.634589</Latitude>
<Longitude>-84.310219</Longitude>
<Speed>0</Speed>
<Altitude>2700</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>RW27R</Name>
<Type>Runway</Type>
<Latitude>33.634706</Latitude>
<Longitude>-84.408906</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>(1400)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1400</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>274</Hdg_Crs_value>
<Sp_Turn>Right</Sp_Turn>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>ATL01</Name>
<Type>Normal</Type>
<Latitude>33.562566</Latitude>
<Longitude>-84.429525</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>SCARR</Name>
<Type>Normal</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>SCARR</Name>
<Type>Hold</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Rad</Hld_Rad_or_Inbd>
<Hld_Rad_value>180</Hld_Rad_value>
<Hld_Turn>Right</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="SOFOR">
<AppTr_Waypoint ID="1">
<Name>FOGOG</Name>
<Type>Normal</Type>
<Latitude>33.545144</Latitude>
<Longitude>-84.546883</Longitude>
<Speed>210</Speed>
<Altitude>12000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="2">
<Name>BOJAA</Name>
<Type>Normal</Type>
<Latitude>33.545031</Latitude>
<Longitude>-84.307436</Longitude>
<Speed>0</Speed>
<Altitude>7000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="3">
<Name>HEDEG</Name>
<Type>Normal</Type>
<Latitude>33.545206</Latitude>
<Longitude>-84.107089</Longitude>
<Speed>0</Speed>
<Altitude>4000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="4">
<Name>SOFOR</Name>
<Type>Normal</Type>
<Latitude>33.545433</Latitude>
<Longitude>-84.003383</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="VOR27L">
<App_Waypoint ID="1">
<Name>AMATE</Name>
<Type>Normal</Type>
<Latitude>33.637469</Latitude>
<Longitude>-84.339339</Longitude>
<Speed>0</Speed>
<Altitude>2300</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>RW27L</Name>
<Type>Runway</Type>
<Latitude>33.631825</Latitude>
<Longitude>-84.418403</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>ATL01</Name>
<Type>Normal</Type>
<Latitude>33.562566</Latitude>
<Longitude>-84.429525</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>SCARR</Name>
<Type>Normal</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>SCARR</Name>
<Type>Hold</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Rad</Hld_Rad_or_Inbd>
<Hld_Rad_value>180</Hld_Rad_value>
<Hld_Turn>Right</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="PANOL">
<AppTr_Waypoint ID="1">
<Name>PANOL</Name>
<Type>Normal</Type>
<Latitude>33.646636</Latitude>
<Longitude>-84.234614</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="ILS09L">
<App_Waypoint ID="1">
<Name>ZABEL</Name>
<Type>Normal</Type>
<Latitude>33.634467</Latitude>
<Longitude>-84.634331</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>KIMMS</Name>
<Type>Normal</Type>
<Latitude>33.634614</Latitude>
<Longitude>-84.542928</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>RW09L</Name>
<Type>Runway</Type>
<Latitude>33.634708</Latitude>
<Longitude>-84.447967</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>(1500)</Name>
<Type>ConstHdgtoAlt</Type>
<Latitude>0.000000</Latitude>
<Longitude>0.000000</Longitude>
<Speed>0</Speed>
<Altitude>1500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
<Hdg_Crs>1</Hdg_Crs>
<Hdg_Crs_value>94</Hdg_Crs_value>
<Sp_Turn>Right</Sp_Turn>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>ATL01</Name>
<Type>Normal</Type>
<Latitude>33.562566</Latitude>
<Longitude>-84.429525</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>SCARR</Name>
<Type>Normal</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>SCARR</Name>
<Type>Hold</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>180</Hld_Rad_value>
<Hld_Turn>Right</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="HESPI">
<AppTr_Waypoint ID="1">
<Name>BOJAA</Name>
<Type>Normal</Type>
<Latitude>33.545031</Latitude>
<Longitude>-84.307436</Longitude>
<Speed>210</Speed>
<Altitude>12000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="2">
<Name>FOGOG</Name>
<Type>Normal</Type>
<Latitude>33.545144</Latitude>
<Longitude>-84.546883</Longitude>
<Speed>0</Speed>
<Altitude>7000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="3">
<Name>SOTRE</Name>
<Type>Normal</Type>
<Latitude>33.545831</Latitude>
<Longitude>-84.749644</Longitude>
<Speed>0</Speed>
<Altitude>4000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
<AppTr_Waypoint ID="4">
<Name>HESPI</Name>
<Type>Normal</Type>
<Latitude>33.545972</Latitude>
<Longitude>-84.855000</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="RNAV08L">
<App_Waypoint ID="1">
<Name>BOPGE</Name>
<Type>Normal</Type>
<Latitude>33.648922</Latitude>
<Longitude>-84.777475</Longitude>
<Speed>0</Speed>
<Altitude>4000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>SEMKE</Name>
<Type>Normal</Type>
<Latitude>33.649197</Latitude>
<Longitude>-84.677372</Longitude>
<Speed>0</Speed>
<Altitude>4000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>HOBUT</Name>
<Type>Normal</Type>
<Latitude>33.649442</Latitude>
<Longitude>-84.545567</Longitude>
<Speed>0</Speed>
<Altitude>2800</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>RW08L</Name>
<Type>Runway</Type>
<Latitude>33.649539</Latitude>
<Longitude>-84.439025</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>JOBAK</Name>
<Type>Normal</Type>
<Latitude>33.649542</Latitude>
<Longitude>-84.354972</Longitude>
<Speed>240</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>below</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>TROYS</Name>
<Type>Normal</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>TROYS</Name>
<Type>Hold</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>240</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>346</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="TEMPO">
<AppTr_Waypoint ID="1">
<Name>TEMPO</Name>
<Type>Normal</Type>
<Latitude>33.611303</Latitude>
<Longitude>-85.038636</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="RNAV08R">
<App_Waypoint ID="1">
<Name>TEGAE</Name>
<Type>Normal</Type>
<Latitude>33.646172</Latitude>
<Longitude>-84.777756</Longitude>
<Speed>0</Speed>
<Altitude>3600</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>ROTME</Name>
<Type>Normal</Type>
<Latitude>33.646525</Latitude>
<Longitude>-84.644417</Longitude>
<Speed>0</Speed>
<Altitude>3600</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>TALEE</Name>
<Type>Normal</Type>
<Latitude>33.646694</Latitude>
<Longitude>-84.544594</Longitude>
<Speed>0</Speed>
<Altitude>2800</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>RW08R</Name>
<Type>Runway</Type>
<Latitude>33.646792</Latitude>
<Longitude>-84.438361</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>BAMSE</Name>
<Type>Normal</Type>
<Latitude>33.646794</Latitude>
<Longitude>-84.354114</Longitude>
<Speed>240</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>below</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>TROYS</Name>
<Type>Normal</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>TROYS</Name>
<Type>Hold</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>240</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>346</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="TEMPO">
<AppTr_Waypoint ID="1">
<Name>TEMPO</Name>
<Type>Normal</Type>
<Latitude>33.611303</Latitude>
<Longitude>-85.038636</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>above</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="RNAV09L">
<App_Waypoint ID="1">
<Name>PONKE</Name>
<Type>Normal</Type>
<Latitude>33.634297</Latitude>
<Longitude>-84.747989</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>CAVKI</Name>
<Type>Normal</Type>
<Latitude>33.634514</Latitude>
<Longitude>-84.648281</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>BUGSE</Name>
<Type>Normal</Type>
<Latitude>33.634650</Latitude>
<Longitude>-84.548406</Longitude>
<Speed>0</Speed>
<Altitude>2700</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>RW09L</Name>
<Type>Runway</Type>
<Latitude>33.634708</Latitude>
<Longitude>-84.447967</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>APASE</Name>
<Type>Normal</Type>
<Latitude>33.634692</Latitude>
<Longitude>-84.369517</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>SCARR</Name>
<Type>Normal</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>SCARR</Name>
<Type>Hold</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>194</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="TEMPO">
<AppTr_Waypoint ID="1">
<Name>TEMPO</Name>
<Type>Normal</Type>
<Latitude>33.611303</Latitude>
<Longitude>-85.038636</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="RNAV09R">
<App_Waypoint ID="1">
<Name>RONAE</Name>
<Type>Normal</Type>
<Latitude>33.631319</Latitude>
<Longitude>-84.747778</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>SOSEE</Name>
<Type>Normal</Type>
<Latitude>33.631564</Latitude>
<Longitude>-84.647975</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>RX09R</Name>
<Type>Normal</Type>
<Latitude>33.630347</Latitude>
<Longitude>-84.550039</Longitude>
<Speed>0</Speed>
<Altitude>2700</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>RW09R</Name>
<Type>Runway</Type>
<Latitude>33.631822</Latitude>
<Longitude>-84.447967</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>BIDBE</Name>
<Type>Normal</Type>
<Latitude>33.631822</Latitude>
<Longitude>-84.369122</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>SCARR</Name>
<Type>Normal</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>SCARR</Name>
<Type>Hold</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>194</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="TEMPO">
<AppTr_Waypoint ID="1">
<Name>TEMPO</Name>
<Type>Normal</Type>
<Latitude>33.611303</Latitude>
<Longitude>-85.038636</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="RNAV26L">
<App_Waypoint ID="1">
<Name>BUPME</Name>
<Type>Normal</Type>
<Latitude>33.646483</Latitude>
<Longitude>-84.110036</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>TIGEE</Name>
<Type>Normal</Type>
<Latitude>33.646669</Latitude>
<Longitude>-84.209858</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>ADOGE</Name>
<Type>Normal</Type>
<Latitude>33.646772</Latitude>
<Longitude>-84.309725</Longitude>
<Speed>0</Speed>
<Altitude>2600</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>RW26L</Name>
<Type>Runway</Type>
<Latitude>33.646797</Latitude>
<Longitude>-84.405511</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>FAMIG</Name>
<Type>Normal</Type>
<Latitude>33.646756</Latitude>
<Longitude>-84.487561</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>TROYS</Name>
<Type>Normal</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>TROYS</Name>
<Type>Hold</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>13</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="CONNI">
<AppTr_Waypoint ID="1">
<Name>CONNI</Name>
<Type>Normal</Type>
<Latitude>33.654533</Latitude>
<Longitude>-83.816925</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="RNAV26R">
<App_Waypoint ID="1">
<Name>ANOGE</Name>
<Type>Normal</Type>
<Latitude>33.649217</Latitude>
<Longitude>-84.107583</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>CALES</Name>
<Type>Normal</Type>
<Latitude>33.649406</Latitude>
<Longitude>-84.207408</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>RUGBE</Name>
<Type>Normal</Type>
<Latitude>33.649514</Latitude>
<Longitude>-84.307250</Longitude>
<Speed>0</Speed>
<Altitude>2700</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>RW26R</Name>
<Type>Runway</Type>
<Latitude>33.649544</Latitude>
<Longitude>-84.409453</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>BADSE</Name>
<Type>Normal</Type>
<Latitude>33.649506</Latitude>
<Longitude>-84.486317</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>TROYS</Name>
<Type>Normal</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>TROYS</Name>
<Type>Hold</Type>
<Latitude>33.879528</Latitude>
<Longitude>-84.435072</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>13</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="CONNI">
<AppTr_Waypoint ID="1">
<Name>CONNI</Name>
<Type>Normal</Type>
<Latitude>33.654533</Latitude>
<Longitude>-83.816925</Longitude>
<Speed>0</Speed>
<Altitude>5000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="RNAV27L">
<App_Waypoint ID="1">
<Name>FAMES</Name>
<Type>Normal</Type>
<Latitude>33.631483</Latitude>
<Longitude>-84.110206</Longitude>
<Speed>0</Speed>
<Altitude>4000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>ASASE</Name>
<Type>Normal</Type>
<Latitude>33.631678</Latitude>
<Longitude>-84.210008</Longitude>
<Speed>0</Speed>
<Altitude>4000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>BUNSE</Name>
<Type>Normal</Type>
<Latitude>33.631792</Latitude>
<Longitude>-84.309811</Longitude>
<Speed>0</Speed>
<Altitude>2700</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>RW27L</Name>
<Type>Runway</Type>
<Latitude>33.631825</Latitude>
<Longitude>-84.418403</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>CALUP</Name>
<Type>Normal</Type>
<Latitude>33.631775</Latitude>
<Longitude>-84.510219</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>SCARR</Name>
<Type>Normal</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>SCARR</Name>
<Type>Hold</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>168</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="CONNI">
<AppTr_Waypoint ID="1">
<Name>CONNI</Name>
<Type>Normal</Type>
<Latitude>33.654533</Latitude>
<Longitude>-83.816925</Longitude>
<Speed>0</Speed>
<Altitude>4000</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
<Approach Name="RNAV27R">
<App_Waypoint ID="1">
<Name>FABUG</Name>
<Type>Normal</Type>
<Latitude>33.634244</Latitude>
<Longitude>-84.106292</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="2">
<Name>ANUME</Name>
<Type>Normal</Type>
<Latitude>33.634478</Latitude>
<Longitude>-84.206100</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="3">
<Name>CAMOL</Name>
<Type>Normal</Type>
<Latitude>33.634631</Latitude>
<Longitude>-84.306003</Longitude>
<Speed>0</Speed>
<Altitude>2700</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="4">
<Name>RW27R</Name>
<Type>Runway</Type>
<Latitude>33.634706</Latitude>
<Longitude>-84.408906</Longitude>
<Speed>0</Speed>
<Altitude>1026</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="5">
<Name>ROTLE</Name>
<Type>Normal</Type>
<Latitude>33.634700</Latitude>
<Longitude>-84.486158</Longitude>
<Speed>0</Speed>
<Altitude>0</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="6">
<Name>SCARR</Name>
<Type>Normal</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</App_Waypoint>
<App_Waypoint ID="7">
<Name>SCARR</Name>
<Type>Hold</Type>
<Latitude>33.378639</Latitude>
<Longitude>-84.435069</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>173</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>01.0</Hld_td_value>
</App_Waypoint>
<App_Transition Name="CONNI">
<AppTr_Waypoint ID="1">
<Name>CONNI</Name>
<Type>Normal</Type>
<Latitude>33.654533</Latitude>
<Longitude>-83.816925</Longitude>
<Speed>0</Speed>
<Altitude>3500</Altitude>
<AltitudeCons>0</AltitudeCons>
<AltitudeRestriction>at</AltitudeRestriction>
</AppTr_Waypoint>
</App_Transition>
</Approach>
</Airport>
</ProceduresDB>
</syntaxhighlight>

== References ==
{{Appendix}}

== Related content ==
=== Wiki articles ===
* [[Route manager]]
* [[Flightplan XML formats]]

=== Source code ===
* {{flightgear source|path=src/Navaids/LevelDXML.hxx}}
* {{flightgear source|path=src/Navaids/LevelDXML.cxx}}

Howto:Animate models

2021-06-10T20:02:39Z

Sfrsfr: /* Animation order */ Mention non-working timed animations due to wrong order. Link to a 'recent' development mailing list discussion

The real world is full of motion. To simulate this in [[FlightGear]], '''models must be animated'''.

FlightGear allows you to animate models in response to property changes: for example, the propellers can spin when the engine is on and the elevators can move up and down with your controller. There is no fixed limit on what parts can be animated: the only requirements are that the part is named in the 3D model file, and that there is a property in the main tree that you can use to get the positioning information.

This document provides basic information for all kind of animations. When animating your model, it is very helpful to find an aircraft with parts similar to yours and use it as an example. Cut and paste the code into your wrapper file and then edit to suit.

== Notes ==
=== File name of main model and animation XML file ===
{{main article|Aircraft-set.xml#Not used for loading multiplayer aircraft}}
The file name of the main model and animation XML file, or the .ac file if there is no XML file, (in essence the property <code>/sim/model/path</code>) will be the name of the aircraft that is transmitted when using [[multiplayer]] and will also be used for loading multiplayer aircraft.

There is also a mechanism to substitute a full aircraft model with a simpler AI aircraft model if one is available at the same file path (including for example <code>Models/Boeing-797-800.xml</code>), but in <code>[[$FG_ROOT]]/'''AI'''/Aircraft/</code> instead of <code>$FG_ROOT/Aircraft/</code>.

=== .ac files ===
{{Main article|AC files: Understanding and changing .ac code#Identifying an object}}

When referring to an .ac file in your xml animation, it is important that the <code><object-name></code> exactly matches the object named in the .ac file (this includes cases!).

'''Note for SketchUp users:''' The spatial reference X/Y/Z used in animation to locate an object or a point are different from the ones in AC3D ie X values are the same in both but Y in animation must be matched to AC3D's -Z (Z value but opposite sign) and Z value in animation must be matched to AC3D's Y value.

'''Note for SketchUp users:''' when exporting to AC3D in Sketchup, the .ac file will name the objects in your model to "blah" by default. You need to amend the relevant object names in your .ac file using text edit, so that the xml will work.

=== Animation order ===
Animations are executed by FlightGear in the order that they are read in the model's .xml file. Therefore, it is very important to pay attention to the order, especially when multiple animations are applied to the same object(s). Wrong ordering of animations might cause [[Howto:Animate models#Timed|timed]] animations (used to create flashing lights) to not work. For further details see this [https://sourceforge.net/p/flightgear/mailman/message/37090714/ thread] on the development mailing list. Updated [https://scenery.flightgear.org/app.php?c=Models&a=browse&shared=18 shared Effects models] will be available very soon.

== Tags used in most animations ==
=== Name ===
With a name animation, you can group multiple objects.

<source>
<animation>
<name>Collection1</name>
<object-name>Object1</object-name>
<object-name>Object2</object-name>
<object-name>Object3</object-name>
</animation>
</source>

The example above creates a "virtual object" with the name Collection1. In animation, we can animate this group of objects, by using:

<source>
<object-name>Collection1</object-name>
</source>

=== Object-name ===
These names are set in the 3D model. Each single object has a unique name; for easy identification it is advised to use descriptive names (LeftElevator, Rudder etc.). Animations are only applied to those objects that are mentioned in an object-name line (one object per line!). Animations lacking those, will be applied to the entire model.

=== Property ===
Each animation must be associated with exactly one property from the main FlightGear property tree (remember that the properties in the wrapper file are not part of the main tree), using <code><property></code> to provide the property path:

<source>
<animation>
<type>rotate</type>
<object-name>Rudder</object-name>
<property>controls/rudder</property>
</animation>
</source>

Note the omission of the leading slash '/' when referring to the property. This assures that when the model is used for AI or multiplayer traffic the animations will follow that of the AI controller instead of that of the user.

=== Axis ===
An axis part is required in every animation that involves a rotating or moving thing.

<source>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</source>

The axis are similar to the ones of the 3D model. There is a difference between rotation and translation:
* In rotation animations, the axis part defines around what axis the object rotates. Negative/positive values make the difference between counterclockwise and clockwise rotations.
* In translate animations, the part defines along what axis the object moves. If the x-axis is poiting backwards, an x-value of -1 will result in forward motion.

You could also define two points, between which FlightGear will calculate the correct axis. This makes the use of a [[#Center|<nowiki><center></nowiki>]] tag redundant! Such coordinates are extremely useful for animating control surfaces (rudder, elevators etc.).

<source>
<axis>
<x1-m> 4.9</x1-m>
<y1-m> 7.1</y1-m>
<z1-m>-1.0</z1-m>
<x2-m> 5.9</x2-m>
<y2-m>11.2</y2-m>
<z2-m>-0.5</z2-m>
</axis>
</source>

=== Center ===
Various animations ([[#Rotate|rotate]], [[#Spin|spin]], [[#Scale|scale]]) move around a center point.

<source>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
</source>

The axis are similar to the ones of the 3D model, so finding coordinates is easily done in 3D modeling software.

=== Using a geometry object for axis and centre (2017.2) ===

Added in V2017.2 is support to allow a geometry object (a line segment with two vertices) that is used to define both the centre and the axis for an animation. This will work with rotate, translate and the knob animations.

The axis line should be balanced, i.e. it should protrude equal amounts. The axis line should be normalized (i.e. 1m) as its length acts as a factor (affecting translate animations).

The syntax for this is
<source>
<axis>
<object-name>some-object</object-name>
</axis>
</source>

Once the object-name used for the axis has been processed the geometry object will be hidden. This also allows a visual check for any axis objects that are not yet assigned.

It is possible to reuse the same object definition multiple times within a single XML file.

[[File:Canopy-animation-axis-object.png|small|Illustration of where an axis object (2017.2) can be placed for a canopy]]

[[File:Gauges-knobs-animation-axis-object.png|small|Illustration of where an axis object (2017.2) can be placed for cockpit elements]]

== Additional tags that can be used in most animations ==
=== Conditions ===
Multiple animations can make use of a conditional. Check <tt>$FGDATA/Docs/README.conditions</tt> for some more details.

* '''equals:''' property value (or second property) is equal to value/(first)property.
* '''greater-than:''' property value (or second property) is larger than value/(first)property.
* '''greater-than-equals:''' property value (or second property) is greater than or equal to value/(first)property.
* '''less-than:''' property value (or second property) is smaller than value/(first)property.
* '''less-than-equals:''' property value (or second property) is smaller than or equal to value/(first)property.

The example below is true when n1 has a value greater than 25.
<source>
<condition>
<greater-than>
<property>engines/engine[1]/n1</property>
<value>25</value>
</greater-than>
</condition>
</source>

Then there are some special tags:

* '''and:'''
* '''not:'''
* '''or:'''

In the example below, the condition is true when either n1 is greater than 25% or equal to 0%.
<source>
<condition>
<or>
<greater-than>
<property>engines/engine[1]/n1</property>
<value>25</value>
</greater-than>
<equals>
<property>engines/engine[1]/n1</property>
<value>0</value>
</equals>
</or>
</condition>
</source>

An example of implementation into an animation looks as follows:

<source>
<animation>
<object-name>Object</object-name>
<type>rotate</type>
<property>suface-positions/left-aileron-pos-norm</property>
<factor>25</factor>
<condition>
<greater-than>
<property>suface-positions/left-aileron-pos-norm</property>
<value>10</value>
</greater-than>
</condition>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

=== Interpolation ===
For non-fixed factors, an interpolation "table" can be created.

<source>
<interpolation>
<entry>
<ind> 0.0</ind>
<dep> 0.0</dep>
</entry>
<entry>
<ind> 0.667</ind>
<dep> 0.0</dep>
</entry>
<entry>
<ind> 1.0</ind>
<dep> 0.5</dep>
</entry>
</interpolation>
</source>

The lines above represent the following table:

{|
!Input
!Output
|-
|0.0
|0.0
|-
|0.667
|0.0
|-
|1.0
|0.5
|}

You can add as many entries as you need. Interpolation tables are often used for gear animations (eg. to open doors during gear-movements and close them again once the gear is either retracted or fully extended).

=== Expressions ===
For some animations it is possible to define complex animations by using [[Expressions|Expressions]]. This even allows to drive the animation from multiple properties without the need for additional Nasal scripts. Here is an example for a translate animation depending on two properties and the cosine function:
<syntaxhighlight lang="xml">
<animation>
<type>translate</type>
<expression>
<product>
<property>/my/factor-property</property>
<cos>
<deg2rad>
<property>/my/angular-property</property>
</deg2rad>
</cos>
</product>
</expression>
[..]more elements[..]
</animation>
</syntaxhighlight>

Animations which can utilize [[Expressions|Expressions]] are:
* [[Howto:Animate_models#Translate|Translate]]
* [[Howto:Animate_models#Rotate|Rotate]]
* [[Howto:Animate_models#Scale|Scale]]
* [[Howto:Animate_models#Range|Range]]
* [[Howto:Animate_models#Blend|Blend]]

See more detailed info at [[Expressions|Expressions]]

== Lights ==
As of January 2021 FligthGear supports multiple light sources just like Project Rembrandt has always done.
[[Compositor#Lights|Adding lights to a model]]

== Object animations ==
=== Alpha-test ===
<source>
<animation>
<type>alpha-test</type>
<object-name>Object</object-name>
<alpha-factor>0.01</alpha-factor>
</animation>
</source>
This "animation" is a way to set an alpha test on a model branch. The effect is to avoid depth buffer writing of pixel that are not seen because they are transparent. This is particulary useful when modeling a metallic structure or a tree with a billboard. The threshold of transparency is set with the <alpha-factor> element. See also [[Pixel testing in effects]].

=== Blend ===
Blends an object with the surrounding. Comparable to a translucency animation. A value of 0 corresponds to no transparency, i.e. and ordinary solid object, and a value of 1 makes the object fully transparent, i.e., not visible at all.

<source>
<animation>
<type>blend</type>
<property>/velocities/airspeed-kt</property>
<factor>0.00025</factor>
<min>0.2</min>
<max>0.7</max>
</animation>
</source>

* '''property:'''
* '''factor:'''
* '''min:'''
* '''max:'''
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

Note that when using the Project Rembrandt renderer, all transparent and translucent objects must be registered to display properly. [[Project_Rembrandt#Registering_all_translucent_surfaces|More information here.]]

=== Billboard ===
This faces an object towards the viewer. Often used on 2D objects, like clouds, trees and lights.

<source>
<animation>
<type>billboard</type>
<object-name>Object</object-name>
<spherical type="bool">true</spherical>
</animation>
</source>

* '''spherical:'''

=== Dist-scale ===
Used to scale an object, based on the distance to the viewer. <code><nowiki><ind></nowiki></code> and <code><nowiki><dep></nowiki></code> (independent and dependent) are the distance in meters and the scale at that distance.

<source>
<animation>
<type>dist-scale</type>
<object-name>Object</object-name>
<interpolation>
<entry>
<ind>0</ind>
<dep>1</dep>
</entry>
<entry>
<ind>300</ind>
<dep>4</dep>
</entry>
<entry>
<ind>1500</ind>
<dep>8</dep>
</entry>
</interpolation>
</animation>
</source>

You can optionally add [[#Center|<center>]] coordinates, to scale the object around that point.

=== Flash ===

Used to scale an object based on the cosine of the angle between the axis provided in the animation and the view vector.

<source>
<animation>
<type>flash</type>
<object-name>Object</object-name>
<offset>0.0</offset>
<factor>1.0</factor>
<power>2</power>
<two-sides type="bool">false</two-sides>
<min>0.0</min>
<max>1.0</max>
<center>
<x-m>0.0</x-m>
<y-m>0.0</y-m>
<z-m>0.0</z-m>
</center>
<axis>
<x>0.0</x>
<y>-1</y>
<z>0.1</z>
</axis>
</animation>
</source>

* '''offset:'''
* '''factor:'''
* '''power:'''
* '''two-sides:''' if false, nothing is drawn if the cosine is negative.
* '''min:'''
* '''max:'''

scale = factor * pow( cosine, power ) + offset

scale is then clamped between min and max.

and this scale factor is applied to the object, from the center specified. It works best if scale is less than 1. Otherwise, there will be clipping issues.

=== Noshadow ===
This animation is used to make sure an object will cast no shadow.

<source>
<animation>
<type>noshadow</type>
<object-name>Object</object-name>
</animation>
</source>

=== Range ===
: ''See also [[Modeling - Getting Started#Level of Detail (LOD)]].''

To prevent objects -like instruments- being drawn when the aircraft is actually too far away for them to be seen anyway, a range animation is used.

<syntaxhighlight lang="xml">
<animation>
<type>range</type>
<min-m>0</min-m>
<max-m>30</max-m>
</animation>
</syntaxhighlight>

* '''min-m:''' the shortest distance (in meters) from the object center at which it is visible.
* '''max-m:''' the largest distance (in meters) from the object center at which it is visible.

You could also use the generic level of detail (LOD) properties, which can be set by the user through View > Adjust LOD rangers:
{| class="wikitable"
! Property
! Description
! Default value
|-
|<tt>/sim/rendering/static-lod/bare</tt>
| only a rough exterior model
| 30,000 m
|-
|<tt>/sim/rendering/static-lod/rough</tt>
| most should be visible
| 9,000 m
|-
|<tt>/sim/rendering/static-lod/detailed</tt>
| all details should be visible
| 1,500 m
|}

The animation code will look like this:
<syntaxhighlight lang="xml">
<animation>
<type>range</type>
<min-m>0</min-m>
<max-property>sim/rendering/static-lod/bare</max-property>
</animation>
</syntaxhighlight>

You can have both ranges (max and min) bound to a property, or just one of them.
* '''min-property:'''
* '''max-property:'''
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

=== Rotate ===
One of the most important and frequently used animations of all. It rotates an object to an absolute position in degrees, as provided by the property-value.

<source>
<animation>
<object-name>Object</object-name>
<type>rotate</type>
<property>surface-positions/left-aileron-pos-norm</property>
<factor>25</factor>
<offset-deg>25</offset-deg>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

* '''factor:''' is optional.
* '''offset-deg:''' is optional. Offset in degrees.
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

=== Scale ===
A scale animation scales (resizes) an object. This can be either property-value dependant (first example) or a fixed scale (second example).

<source>
<animation>
<type>scale</type>
<object-name>Object</object-name>
<property>sim/time/sun-angle-rad</property>
<x-min>1.0</x-min>
<y-min>1.0</y-min>
<z-min>1.0</z-min>
<x-factor>1.4</x-factor>
<y-factor>1.4</y-factor>
<z-factor>2.0</z-factor>
</animation>
</source>

* ?-min: the mimimum scale factor for each axis. If the property value would result in a smaller factor than this setting, the scale animation will hold.
* ?-factor: the scale factor for each axis (factor*property=scale factor).

<source>
<animation>
<type>scale</type>
<x-offset>0.5</x-offset>
<y-offset>0.5</y-offset>
<z-offset>0.5</z-offset>
</animation>
</source>

* x.offset: the scale factor.
* Add [[#Center|<center>]] coordinates, to scale the object around that point.
* '''You can optionally use an [[Howto:Animate_models#Expressions|expression]] in the <factor> or <offset> inputs.''' For more details see [[Expressions|Expressions]]

=== Select ===
This animation selects (or unselects) objects when certain conditions are true (or false). The example below shows the object when the n1 of engine[1] is higher than 25%.

<source>
<animation>
<object-name>Object</object-name>
<type>select</type>
<condition>
<greater-than>
<property>engines/engine[0]/n1</property>
<value>25</value>
</greater-than>
</condition>
</animation>
</source>

=== Shader ===
<source>
<animation>
<type>shader</type>
<shader>chrome</shader>
<texture>chrome2.png</texture>
<object-name>Object</object-name>
</animation>
</source>

* '''shader:'''
* '''texture:''' path to the texture used by the shader.

=== Spin ===
Very similar to [[#Rotate|rotate]], but the property provides a value in revolutions per minute (RPM) rather than an absolute position in degrees, and offset cannot be used.

<source>
<animation>
<object-name>Object</object-name>
<type>spin</type>
<property>engines/engine[0]/n1</property>
<factor>25</factor>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

* '''factor:''' is optional.

=== Timed ===
Swtiches between objects at specified intervals. This example switches between a lights-on model and a lights-off model. Lights on are shown 0.2 seconds, while lights off are displayed for 0.8 seconds.

<source>
<animation>
<type>timed</type>
<object-name>BacklightOn</object-name>
<object-name>BacklightOff</object-name>
<use-personality type="bool">true</use-personality>
<branch-duration-sec>0.8</branch-duration-sec>
<branch-duration-sec>0.2</branch-duration-sec>
</animation>
</source>

=== Tracking ===
The new (in 2.11) [[Howto:Animate gear scissors using the tracking animation|''locked-track animation'']] can do exactly the same thing as the [https://docs.blender.org/manual/en/latest/animation/constraints/tracking/locked_track.html Locked Track constraint] available in Blender. However it can also be used to simulate simple inverse kinematic systems consisting of two bones connected with a revolute joint (aka hinge). See [[Howto:Animate gear scissors using the tracking animation|detailed explanation]].

=== Translate ===
The same as [[#Textranslate|textranslate]], but this animation moves a whole object (so including fixed textures). The example below will move an object in the y-direction:

{| class="wikitable" border="0" cellspacing="0"
!Property value
!Output
|-
| -1
| -2.5
|-
| 0
| 2.5
|-
| 1
| 7.5
|}

<source>
<animation>
<type>translate</type>
<object-name>Object</object-name>
<property>controls/seat/pilot/position-norm</property>
<factor>5</factor>
<offset-m>2.5</offset-m>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

When using interpolation tables such as:
<source>
<interpolation>
<entry><ind>0.0</ind><dep> 0</dep></entry>
<entry><ind>0.666</ind><dep>0.18</dep></entry>
<entry><ind>1.0</ind><dep>0.27</dep></entry>
</interpolation>
</source>
The first figure (<ind> refers to the value of the property associated with the object and the second figure (in <dep>) refers to the amount that the object moves in metres. For example, in this case, the object moves 18cm when the value reads 0.66 and 27cm when the value is 1.

'''IF used WTIHOUT property''' : The object is placed at some (Value of Offset) meters away from its original position, along the virtual axis formed by said original position and the point with coordinates x/y/z defined in the <axis> tag.
Mathematically, assuming the Object to translate is (in the model space) placed at point A (x1, y1, z1) and you want to relocate it to point B (x2, y2, z2) then x2,y2,z2 are the values in the <axis> tag of the Translate animation and <offset> can be computed as SQRT((x2-x1)^2+(y2-y1)^2+(z2-z1)^2)

* '''factor:''' is optional.
* '''offset-m:''' is optional. Offset in meters.
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

== Material animation ==
An animation type that can be used in various ways. Of course you can combine the below mentiond systems into one (big) animation.

<source>
<animation>
<type>material</type>
<object-name>Object</object-name>
<property-base>sim/model/c172p/material</property-base>
<global type="bool">true</global> 
...
lines as mentioned below
...
</animation>
</source>

'''Optional:'''
* '''property-base:''' when using prop(erties), you might want to set a property-base. All props will be relative to this path.
* '''global (deprecated):''' by setting this to <tt>true</tt>, all objects using the same material as the defined object(s) (via <tt><object-name></tt>) will be affected by the animation. This is preferred to listing several objects in <object-name> tags. It's not only faster, but also doesn't break animations by forcing objects together. <span style="color:red; text-decoration: underline;">This tag is no longer supported</span>

'''Notes:'''
* Numbers are clamped to 0.0-1.0, except "shininess", which is clamped to 0-128.
* By appending <tt>-prop</tt> each of the material properties can read its value from another property.

=== Ambient ===
<source>
<ambient>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
</ambient>
</source>

=== Diffuse ===
<source>
<diffuse>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
</diffuse>
</source>

=== Emission ===
{{Main article|Howto: Illuminate faces}}
<source>
<emission>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
<factor-prop>controls/lighting/panel-norm</factor-prop>
</emission>
</source>

Emission colors are multiplied by the factor-prop value. 1 is maximum color intensity, while 0 is the minimum. Colors are calculated according to the [http://en.wikipedia.org/wiki/RGB_color_model RGB color model].

=== Shininess ===
Shininess is clamped to 0-128.
<source>
<shininess>105</shininess>
</source>

=== Specular ===
<source>
<specular>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
</specular>
</source>

=== Texture ===
Used for the [[Livery over MP]] system.

<source>
<property-base>sim/model/livery</property-base>
<texture-prop>engine</texture-prop>
<texture>KLM.png</texture>
</source>

=== Transparency ===
<source>
<transparency>
<alpha-prop>rotors/tail/rpm</alpha-prop>
<factor>-0.0015</factor>
<offset>1</offset>
</transparency>
</source>

=== Threshold ===
<source>
<threshold>0.001</threshold>
</source>

== Texture Animations ==

Applying different matrix transformations to the textures of an object.

=== Textranslate ===
A very important animation for cockpits! This animation moves textures over a surface.

<source>
<animation>
<type>textranslate</type>
<object-name>Object</object-name>
<property>autopilot/settings/target-speed-kt</property>
<bias>0.0001</bias>
<factor>0.001</factor>
<step>100</step>
<axis>
<x>0</x>
<y>1</y>
</axis>
</animation>
</source>

* '''bias:''' Adds an offset to the property before factor/step. A small value is needed to compensate for [http://en.wikipedia.org/wiki/Floating_point#Accuracy_problems floating point accuracy].
* '''factor:''' property * factor * texture width/height = the amount of pixels that the texture should be translated. If your texture is 256 pixels, an textranslate of 0.1 will result in the texture moving with 26 pixels, into the direction specified by the axis settings.
* '''step:''' the step size at which the texture is translated. If this is set to 0.1, the texture will only be translated at 0.1, 0.2, 0.3 etc.
* '''axis:''' the direction in which the texture is translated. Y is up/down, while X is left/right.

=== Texrotate ===

<source>
<animation>
<object-name>Object</object-name>
<type>texrotate</type>
<property>some/property/path</property>
<factor>25</factor>
<offset-deg>25</offset-deg>
<center>
<x>0.5</x>
<y>0.5</y>
<z>0</z>
</center>
<axis>
<x>0</x>
<y>0</y>
<z>1</z>
</axis>
</animation>
</source>

=== Textrapezoid ===

<source>
<animation>
<type>textrapezoid</type>
<object-name>HUD.l.canvas</object-name>
<property>/hud/trapezoid-correction</property>
<side>bottom</side>
</animation>
</source>

* '''side''': side of quad which should be scaled (''top'' (default)/''right''/''bottom''/''left'')

=== Texmultiple ===

Only one texture matrix can be applied to each object. With ''textmultiple'' multiple texture animations can be combined into a single matrix, applied to the specified object.

<source>
<animation>
<type>texmultiple</type>
<object-name>HUD.l.canvas</object-name>
<transform>
<subtype>textranslate</subtype>
<property>/hud/offset-x</property>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</transform>
<transform>
<subtype>textranslate</subtype>
<property>/hud/offset-y</property>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</transform>
<transform>
<subtype>textrapezoid</subtype>
<property>/hud/trapezoid-correction</property>
</transform>
</animation>
</source>

== Object interaction animations ==
=== Enable-hot ===
Scenery objects are automatically defined as solid by FlightGear, meaning that an aircraft can taxi on them and/or crash when touching. For certain objects (groundmarkings, beacon light-beams etc.) this might be an unwanted feature. The solidness can be disabled with the following animation:

<source>
<animation>
<object-name>Object</object-name>
<enable-hot type="bool">false</enable-hot>
</animation>
</source>

* '''enable-hot:''' can be either true or false. Remember that objects are automatically solid, so it should not be necessary to set this at all when wanting solidness.

=== Interactions ===
<source>
<animation>
<type>interaction</type>
<object-name>Object</object-name>
<interaction-type>carrier-wire</interaction-type>
</animation>
</source>

* '''interaction-type:''' can have the following values:
**'''carrier-catapult:'''
** '''carrier-wire:''' makes the object act as an arresting wire, as used on [[aircraft carrier]]s.

== Direct manipulation animations ==
=== Knob / slider (v. 2.11-) ===
{{Main article|Knob / slider animation}}

=== Pick ===
{{Main article|Howto: Make a clickable panel#Pick}}

=== Touch ===

The touch animation provides the normalized coordinates of a touch (or click) event on a 2d surface. The coordinates are passed in the argument and can be accessed using cmdarg() in Nasal.

* Touch animation is designed to work with a quad that is being used as a Canvas placement (display).
* The touch animation must not be combined with a pick animation on the same object.
* More info here: [[Touch Animation]]

==== touch example ====

<animation>
<type>touch</type>
<visible>true</visible>
<object-name>CanvasPlacement</object-name>
<action>
<touch>0</touch>
<repeatable>false</repeatable>
<binding>
<command>nasal</command>
<script>print("touch input (",cmdarg().getNode("x").getValue(),",",cmdarg().getNode("y").getValue())</script>
</binding>
</action>
</animation>

== Shadow Handling ==
There exist several possibilites for handling of shadows. <br />
See '''[[ALS_technical_notes|ALS Technical Notes]]''' and more specific '''[[ALS_technical_notes#ALS_fuselage_shadow_effect|Fuselage Shadow Effect with ALS]]''' for a relatively simple shadow handling.<br />
See '''[[Project Rembrandt]]''' which - amongst other functionality - implements a very realistic shadow mapping.
As of January 2021 Project Rembrandt was replaced by the '''[[Compositor]]''' renderer which combines both Project Rembrandt and ALS in a single rendering engine. This also means that the Fuselage Shadow Effect with ALS is now deprecated.

== References ==
{{Appendix|all|
* {{cite web |url=http://www.opensubscriber.com/message/flightgear-devel@flightgear.org/958955.html |title="material" animation (and the bo105 as an example) |first=Melchior |last=Franz |date=22 March 2005 |work=FlightGear-devel mailinglist }}
* {{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg01546.html |title=flash animation |first=Frederic |last=Bouvier |date=22 Feb 2006 |work=FlightGear-devel mailinglist }}
}}

== Related content ==
=== Wiki articles ===
* [[MP Fallback models]]
* [[Howto:Animate gear scissors]]
* [[Howto:Animate helicopters]]
* [[Howto:Creating 3D instruments]]

=== Forum topics ===
* {{forum link|t=37353|title=3d models, how to produce them in an understandable way}} (April 2020-) - Touches on the subject of not using LOD range animations in scenery models.
* {{forum link|t=36545|title=speedo Drum settings}} (November 2019) - Animating a mechanical multi-digit drum counter

[[Category:Aircraft enhancement|Animate models]]
[[Category:Howto|Animate models]]
[[Category:Modeling|Animate models]]
[[Category:Scenery enhancement|Animate models]]

Howto:Animate models

2021-06-03T11:48:45Z

Sfrsfr: /* Interactions */ no idea how i deleted that space

The real world is full of motion. To simulate this in [[FlightGear]], '''models must be animated'''.

FlightGear allows you to animate models in response to property changes: for example, the propellers can spin when the engine is on and the elevators can move up and down with your controller. There is no fixed limit on what parts can be animated: the only requirements are that the part is named in the 3D model file, and that there is a property in the main tree that you can use to get the positioning information.

This document provides basic information for all kind of animations. When animating your model, it is very helpful to find an aircraft with parts similar to yours and use it as an example. Cut and paste the code into your wrapper file and then edit to suit.

== Notes ==
=== File name of main model and animation XML file ===
{{main article|Aircraft-set.xml#Not used for loading multiplayer aircraft}}
The file name of the main model and animation XML file, or the .ac file if there is no XML file, (in essence the property <code>/sim/model/path</code>) will be the name of the aircraft that is transmitted when using [[multiplayer]] and will also be used for loading multiplayer aircraft.

There is also a mechanism to substitute a full aircraft model with a simpler AI aircraft model if one is available at the same file path (including for example <code>Models/Boeing-797-800.xml</code>), but in <code>[[$FG_ROOT]]/'''AI'''/Aircraft/</code> instead of <code>$FG_ROOT/Aircraft/</code>.

=== .ac files ===
{{Main article|AC files: Understanding and changing .ac code#Identifying an object}}

When referring to an .ac file in your xml animation, it is important that the <code><object-name></code> exactly matches the object named in the .ac file (this includes cases!).

'''Note for SketchUp users:''' The spatial reference X/Y/Z used in animation to locate an object or a point are different from the ones in AC3D ie X values are the same in both but Y in animation must be matched to AC3D's -Z (Z value but opposite sign) and Z value in animation must be matched to AC3D's Y value.

'''Note for SketchUp users:''' when exporting to AC3D in Sketchup, the .ac file will name the objects in your model to "blah" by default. You need to amend the relevant object names in your .ac file using text edit, so that the xml will work.

=== Animation order ===
Animations are executed by FlightGear in the order that they are read in the model's .xml file. Therefore, it is very important to pay attention to the order, especially when multiple animations are applied to the same object(s).

== Tags used in most animations ==
=== Name ===
With a name animation, you can group multiple objects.

<source>
<animation>
<name>Collection1</name>
<object-name>Object1</object-name>
<object-name>Object2</object-name>
<object-name>Object3</object-name>
</animation>
</source>

The example above creates a "virtual object" with the name Collection1. In animation, we can animate this group of objects, by using:

<source>
<object-name>Collection1</object-name>
</source>

=== Object-name ===
These names are set in the 3D model. Each single object has a unique name; for easy identification it is advised to use descriptive names (LeftElevator, Rudder etc.). Animations are only applied to those objects that are mentioned in an object-name line (one object per line!). Animations lacking those, will be applied to the entire model.

=== Property ===
Each animation must be associated with exactly one property from the main FlightGear property tree (remember that the properties in the wrapper file are not part of the main tree), using <code><property></code> to provide the property path:

<source>
<animation>
<type>rotate</type>
<object-name>Rudder</object-name>
<property>controls/rudder</property>
</animation>
</source>

Note the omission of the leading slash '/' when referring to the property. This assures that when the model is used for AI or multiplayer traffic the animations will follow that of the AI controller instead of that of the user.

=== Axis ===
An axis part is required in every animation that involves a rotating or moving thing.

<source>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</source>

The axis are similar to the ones of the 3D model. There is a difference between rotation and translation:
* In rotation animations, the axis part defines around what axis the object rotates. Negative/positive values make the difference between counterclockwise and clockwise rotations.
* In translate animations, the part defines along what axis the object moves. If the x-axis is poiting backwards, an x-value of -1 will result in forward motion.

You could also define two points, between which FlightGear will calculate the correct axis. This makes the use of a [[#Center|<nowiki><center></nowiki>]] tag redundant! Such coordinates are extremely useful for animating control surfaces (rudder, elevators etc.).

<source>
<axis>
<x1-m> 4.9</x1-m>
<y1-m> 7.1</y1-m>
<z1-m>-1.0</z1-m>
<x2-m> 5.9</x2-m>
<y2-m>11.2</y2-m>
<z2-m>-0.5</z2-m>
</axis>
</source>

=== Center ===
Various animations ([[#Rotate|rotate]], [[#Spin|spin]], [[#Scale|scale]]) move around a center point.

<source>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
</source>

The axis are similar to the ones of the 3D model, so finding coordinates is easily done in 3D modeling software.

=== Using a geometry object for axis and centre (2017.2) ===

Added in V2017.2 is support to allow a geometry object (a line segment with two vertices) that is used to define both the centre and the axis for an animation. This will work with rotate, translate and the knob animations.

The axis line should be balanced, i.e. it should protrude equal amounts. The axis line should be normalized (i.e. 1m) as its length acts as a factor (affecting translate animations).

The syntax for this is
<source>
<axis>
<object-name>some-object</object-name>
</axis>
</source>

Once the object-name used for the axis has been processed the geometry object will be hidden. This also allows a visual check for any axis objects that are not yet assigned.

It is possible to reuse the same object definition multiple times within a single XML file.

[[File:Canopy-animation-axis-object.png|small|Illustration of where an axis object (2017.2) can be placed for a canopy]]

[[File:Gauges-knobs-animation-axis-object.png|small|Illustration of where an axis object (2017.2) can be placed for cockpit elements]]

== Additional tags that can be used in most animations ==
=== Conditions ===
Multiple animations can make use of a conditional. Check <tt>$FGDATA/Docs/README.conditions</tt> for some more details.

* '''equals:''' property value (or second property) is equal to value/(first)property.
* '''greater-than:''' property value (or second property) is larger than value/(first)property.
* '''greater-than-equals:''' property value (or second property) is greater than or equal to value/(first)property.
* '''less-than:''' property value (or second property) is smaller than value/(first)property.
* '''less-than-equals:''' property value (or second property) is smaller than or equal to value/(first)property.

The example below is true when n1 has a value greater than 25.
<source>
<condition>
<greater-than>
<property>engines/engine[1]/n1</property>
<value>25</value>
</greater-than>
</condition>
</source>

Then there are some special tags:

* '''and:'''
* '''not:'''
* '''or:'''

In the example below, the condition is true when either n1 is greater than 25% or equal to 0%.
<source>
<condition>
<or>
<greater-than>
<property>engines/engine[1]/n1</property>
<value>25</value>
</greater-than>
<equals>
<property>engines/engine[1]/n1</property>
<value>0</value>
</equals>
</or>
</condition>
</source>

An example of implementation into an animation looks as follows:

<source>
<animation>
<object-name>Object</object-name>
<type>rotate</type>
<property>suface-positions/left-aileron-pos-norm</property>
<factor>25</factor>
<condition>
<greater-than>
<property>suface-positions/left-aileron-pos-norm</property>
<value>10</value>
</greater-than>
</condition>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

=== Interpolation ===
For non-fixed factors, an interpolation "table" can be created.

<source>
<interpolation>
<entry>
<ind> 0.0</ind>
<dep> 0.0</dep>
</entry>
<entry>
<ind> 0.667</ind>
<dep> 0.0</dep>
</entry>
<entry>
<ind> 1.0</ind>
<dep> 0.5</dep>
</entry>
</interpolation>
</source>

The lines above represent the following table:

{|
!Input
!Output
|-
|0.0
|0.0
|-
|0.667
|0.0
|-
|1.0
|0.5
|}

You can add as many entries as you need. Interpolation tables are often used for gear animations (eg. to open doors during gear-movements and close them again once the gear is either retracted or fully extended).

=== Expressions ===
For some animations it is possible to define complex animations by using [[Expressions|Expressions]]. This even allows to drive the animation from multiple properties without the need for additional Nasal scripts. Here is an example for a translate animation depending on two properties and the cosine function:
<syntaxhighlight lang="xml">
<animation>
<type>translate</type>
<expression>
<product>
<property>/my/factor-property</property>
<cos>
<deg2rad>
<property>/my/angular-property</property>
</deg2rad>
</cos>
</product>
</expression>
[..]more elements[..]
</animation>
</syntaxhighlight>

Animations which can utilize [[Expressions|Expressions]] are:
* [[Howto:Animate_models#Translate|Translate]]
* [[Howto:Animate_models#Rotate|Rotate]]
* [[Howto:Animate_models#Scale|Scale]]
* [[Howto:Animate_models#Range|Range]]
* [[Howto:Animate_models#Blend|Blend]]

See more detailed info at [[Expressions|Expressions]]

== Lights ==
As of January 2021 FligthGear supports multiple light sources just like Project Rembrandt has always done.
[[Compositor#Lights|Adding lights to a model]]

== Object animations ==
=== Alpha-test ===
<source>
<animation>
<type>alpha-test</type>
<object-name>Object</object-name>
<alpha-factor>0.01</alpha-factor>
</animation>
</source>
This "animation" is a way to set an alpha test on a model branch. The effect is to avoid depth buffer writing of pixel that are not seen because they are transparent. This is particulary useful when modeling a metallic structure or a tree with a billboard. The threshold of transparency is set with the <alpha-factor> element. See also [[Pixel testing in effects]].

=== Blend ===
Blends an object with the surrounding. Comparable to a translucency animation. A value of 0 corresponds to no transparency, i.e. and ordinary solid object, and a value of 1 makes the object fully transparent, i.e., not visible at all.

<source>
<animation>
<type>blend</type>
<property>/velocities/airspeed-kt</property>
<factor>0.00025</factor>
<min>0.2</min>
<max>0.7</max>
</animation>
</source>

* '''property:'''
* '''factor:'''
* '''min:'''
* '''max:'''
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

Note that when using the Project Rembrandt renderer, all transparent and translucent objects must be registered to display properly. [[Project_Rembrandt#Registering_all_translucent_surfaces|More information here.]]

=== Billboard ===
This faces an object towards the viewer. Often used on 2D objects, like clouds, trees and lights.

<source>
<animation>
<type>billboard</type>
<object-name>Object</object-name>
<spherical type="bool">true</spherical>
</animation>
</source>

* '''spherical:'''

=== Dist-scale ===
Used to scale an object, based on the distance to the viewer.

<source>
<animation>
<type>dist-scale</type>
<object-name>Object</object-name>
<interpolation>
<entry>
<ind>0</ind>
<dep>1</dep>
</entry>
<entry>
<ind>300</ind>
<dep>4</dep>
</entry>
<entry>
<ind>1500</ind>
<dep>8</dep>
</entry>
</interpolation>
</animation>
</source>

You can optionally add [[#Center|<center>]] coordinates, to scale the object around that point.

=== Flash ===

Used to scale an object based on the cosine of the angle between the axis provided in the animation and the view vector.

<source>
<animation>
<type>flash</type>
<object-name>Object</object-name>
<offset>0.0</offset>
<factor>1.0</factor>
<power>2</power>
<two-sides type="bool">false</two-sides>
<min>0.0</min>
<max>1.0</max>
<center>
<x-m>0.0</x-m>
<y-m>0.0</y-m>
<z-m>0.0</z-m>
</center>
<axis>
<x>0.0</x>
<y>-1</y>
<z>0.1</z>
</axis>
</animation>
</source>

* '''offset:'''
* '''factor:'''
* '''power:'''
* '''two-sides:''' if false, nothing is drawn if the cosine is negative.
* '''min:'''
* '''max:'''

scale = factor * pow( cosine, power ) + offset

scale is then clamped between min and max.

and this scale factor is applied to the object, from the center specified. It works best if scale is less than 1. Otherwise, there will be clipping issues.

=== Noshadow ===
This animation is used to make sure an object will cast no shadow.

<source>
<animation>
<type>noshadow</type>
<object-name>Object</object-name>
</animation>
</source>

=== Range ===
: ''See also [[Modeling - Getting Started#Level of Detail (LOD)]].''

To prevent objects -like instruments- being drawn when the aircraft is actually too far away for them to be seen anyway, a range animation is used.

<syntaxhighlight lang="xml">
<animation>
<type>range</type>
<min-m>0</min-m>
<max-m>30</max-m>
</animation>
</syntaxhighlight>

* '''min-m:''' the shortest distance (in meters) from the object center at which it is visible.
* '''max-m:''' the largest distance (in meters) from the object center at which it is visible.

You could also use the generic level of detail (LOD) properties, which can be set by the user through View > Adjust LOD rangers:
{| class="wikitable"
! Property
! Description
! Default value
|-
|<tt>/sim/rendering/static-lod/bare</tt>
| only a rough exterior model
| 30,000 m
|-
|<tt>/sim/rendering/static-lod/rough</tt>
| most should be visible
| 9,000 m
|-
|<tt>/sim/rendering/static-lod/detailed</tt>
| all details should be visible
| 1,500 m
|}

The animation code will look like this:
<syntaxhighlight lang="xml">
<animation>
<type>range</type>
<min-m>0</min-m>
<max-property>sim/rendering/static-lod/bare</max-property>
</animation>
</syntaxhighlight>

You can have both ranges (max and min) bound to a property, or just one of them.
* '''min-property:'''
* '''max-property:'''
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

=== Rotate ===
One of the most important and frequently used animations of all. It rotates an object to an absolute position in degrees, as provided by the property-value.

<source>
<animation>
<object-name>Object</object-name>
<type>rotate</type>
<property>surface-positions/left-aileron-pos-norm</property>
<factor>25</factor>
<offset-deg>25</offset-deg>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

* '''factor:''' is optional.
* '''offset-deg:''' is optional. Offset in degrees.
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

=== Scale ===
A scale animation scales (resizes) an object. This can be either property-value dependant (first example) or a fixed scale (second example).

<source>
<animation>
<type>scale</type>
<object-name>Object</object-name>
<property>sim/time/sun-angle-rad</property>
<x-min>1.0</x-min>
<y-min>1.0</y-min>
<z-min>1.0</z-min>
<x-factor>1.4</x-factor>
<y-factor>1.4</y-factor>
<z-factor>2.0</z-factor>
</animation>
</source>

* ?-min: the mimimum scale factor for each axis. If the property value would result in a smaller factor than this setting, the scale animation will hold.
* ?-factor: the scale factor for each axis (factor*property=scale factor).

<source>
<animation>
<type>scale</type>
<x-offset>0.5</x-offset>
<y-offset>0.5</y-offset>
<z-offset>0.5</z-offset>
</animation>
</source>

* x.offset: the scale factor.
* Add [[#Center|<center>]] coordinates, to scale the object around that point.
* '''You can optionally use an [[Howto:Animate_models#Expressions|expression]] in the <factor> or <offset> inputs.''' For more details see [[Expressions|Expressions]]

=== Select ===
This animation selects (or unselects) objects when certain conditions are true (or false). The example below shows the object when the n1 of engine[1] is higher than 25%.

<source>
<animation>
<object-name>Object</object-name>
<type>select</type>
<condition>
<greater-than>
<property>engines/engine[0]/n1</property>
<value>25</value>
</greater-than>
</condition>
</animation>
</source>

=== Shader ===
<source>
<animation>
<type>shader</type>
<shader>chrome</shader>
<texture>chrome2.png</texture>
<object-name>Object</object-name>
</animation>
</source>

* '''shader:'''
* '''texture:''' path to the texture used by the shader.

=== Spin ===
Very similar to [[#Rotate|rotate]], but the property provides a value in revolutions per minute (RPM) rather than an absolute position in degrees, and offset cannot be used.

<source>
<animation>
<object-name>Object</object-name>
<type>spin</type>
<property>engines/engine[0]/n1</property>
<factor>25</factor>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

* '''factor:''' is optional.

=== Timed ===
Swtiches between objects at specified intervals. This example switches between a lights-on model and a lights-off model. Lights on are shown 0.2 seconds, while lights off are displayed for 0.8 seconds.

<source>
<animation>
<type>timed</type>
<object-name>BacklightOn</object-name>
<object-name>BacklightOff</object-name>
<use-personality type="bool">true</use-personality>
<branch-duration-sec>0.8</branch-duration-sec>
<branch-duration-sec>0.2</branch-duration-sec>
</animation>
</source>

=== Tracking ===
The new (in 2.11) [[Howto:Animate gear scissors using the tracking animation|''locked-track animation'']] can do exactly the same thing as the [https://docs.blender.org/manual/en/latest/animation/constraints/tracking/locked_track.html Locked Track constraint] available in Blender. However it can also be used to simulate simple inverse kinematic systems consisting of two bones connected with a revolute joint (aka hinge). See [[Howto:Animate gear scissors using the tracking animation|detailed explanation]].

=== Translate ===
The same as [[#Textranslate|textranslate]], but this animation moves a whole object (so including fixed textures). The example below will move an object in the y-direction:

{| class="wikitable" border="0" cellspacing="0"
!Property value
!Output
|-
| -1
| -2.5
|-
| 0
| 2.5
|-
| 1
| 7.5
|}

<source>
<animation>
<type>translate</type>
<object-name>Object</object-name>
<property>controls/seat/pilot/position-norm</property>
<factor>5</factor>
<offset-m>2.5</offset-m>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

When using interpolation tables such as:
<source>
<interpolation>
<entry><ind>0.0</ind><dep> 0</dep></entry>
<entry><ind>0.666</ind><dep>0.18</dep></entry>
<entry><ind>1.0</ind><dep>0.27</dep></entry>
</interpolation>
</source>
The first figure (<ind> refers to the value of the property associated with the object and the second figure (in <dep>) refers to the amount that the object moves in metres. For example, in this case, the object moves 18cm when the value reads 0.66 and 27cm when the value is 1.

'''IF used WTIHOUT property''' : The object is placed at some (Value of Offset) meters away from its original position, along the virtual axis formed by said original position and the point with coordinates x/y/z defined in the <axis> tag.
Mathematically, assuming the Object to translate is (in the model space) placed at point A (x1, y1, z1) and you want to relocate it to point B (x2, y2, z2) then x2,y2,z2 are the values in the <axis> tag of the Translate animation and <offset> can be computed as SQRT((x2-x1)^2+(y2-y1)^2+(z2-z1)^2)

* '''factor:''' is optional.
* '''offset-m:''' is optional. Offset in meters.
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

== Material animation ==
An animation type that can be used in various ways. Of course you can combine the below mentiond systems into one (big) animation.

<source>
<animation>
<type>material</type>
<object-name>Object</object-name>
<property-base>sim/model/c172p/material</property-base>
<global type="bool">true</global> 
...
lines as mentioned below
...
</animation>
</source>

'''Optional:'''
* '''property-base:''' when using prop(erties), you might want to set a property-base. All props will be relative to this path.
* '''global (deprecated):''' by setting this to <tt>true</tt>, all objects using the same material as the defined object(s) (via <tt><object-name></tt>) will be affected by the animation. This is preferred to listing several objects in <object-name> tags. It's not only faster, but also doesn't break animations by forcing objects together. <span style="color:red; text-decoration: underline;">This tag is no longer supported</span>

'''Notes:'''
* Numbers are clamped to 0.0-1.0, except "shininess", which is clamped to 0-128.
* By appending <tt>-prop</tt> each of the material properties can read its value from another property.

=== Ambient ===
<source>
<ambient>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
</ambient>
</source>

=== Diffuse ===
<source>
<diffuse>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
</diffuse>
</source>

=== Emission ===
{{Main article|Howto: Illuminate faces}}
<source>
<emission>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
<factor-prop>controls/lighting/panel-norm</factor-prop>
</emission>
</source>

Emission colors are multiplied by the factor-prop value. 1 is maximum color intensity, while 0 is the minimum. Colors are calculated according to the [http://en.wikipedia.org/wiki/RGB_color_model RGB color model].

=== Shininess ===
Shininess is clamped to 0-128.
<source>
<shininess>105</shininess>
</source>

=== Specular ===
<source>
<specular>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
</specular>
</source>

=== Texture ===
Used for the [[Livery over MP]] system.

<source>
<property-base>sim/model/livery</property-base>
<texture-prop>engine</texture-prop>
<texture>KLM.png</texture>
</source>

=== Transparency ===
<source>
<transparency>
<alpha-prop>rotors/tail/rpm</alpha-prop>
<factor>-0.0015</factor>
<offset>1</offset>
</transparency>
</source>

=== Threshold ===
<source>
<threshold>0.001</threshold>
</source>

== Texture Animations ==

Applying different matrix transformations to the textures of an object.

=== Textranslate ===
A very important animation for cockpits! This animation moves textures over a surface.

<source>
<animation>
<type>textranslate</type>
<object-name>Object</object-name>
<property>autopilot/settings/target-speed-kt</property>
<bias>0.0001</bias>
<factor>0.001</factor>
<step>100</step>
<axis>
<x>0</x>
<y>1</y>
</axis>
</animation>
</source>

* '''bias:''' Adds an offset to the property before factor/step. A small value is needed to compensate for [http://en.wikipedia.org/wiki/Floating_point#Accuracy_problems floating point accuracy].
* '''factor:''' property * factor * texture width/height = the amount of pixels that the texture should be translated. If your texture is 256 pixels, an textranslate of 0.1 will result in the texture moving with 26 pixels, into the direction specified by the axis settings.
* '''step:''' the step size at which the texture is translated. If this is set to 0.1, the texture will only be translated at 0.1, 0.2, 0.3 etc.
* '''axis:''' the direction in which the texture is translated. Y is up/down, while X is left/right.

=== Texrotate ===

<source>
<animation>
<object-name>Object</object-name>
<type>texrotate</type>
<property>some/property/path</property>
<factor>25</factor>
<offset-deg>25</offset-deg>
<center>
<x>0.5</x>
<y>0.5</y>
<z>0</z>
</center>
<axis>
<x>0</x>
<y>0</y>
<z>1</z>
</axis>
</animation>
</source>

=== Textrapezoid ===

<source>
<animation>
<type>textrapezoid</type>
<object-name>HUD.l.canvas</object-name>
<property>/hud/trapezoid-correction</property>
<side>bottom</side>
</animation>
</source>

* '''side''': side of quad which should be scaled (''top'' (default)/''right''/''bottom''/''left'')

=== Texmultiple ===

Only one texture matrix can be applied to each object. With ''textmultiple'' multiple texture animations can be combined into a single matrix, applied to the specified object.

<source>
<animation>
<type>texmultiple</type>
<object-name>HUD.l.canvas</object-name>
<transform>
<subtype>textranslate</subtype>
<property>/hud/offset-x</property>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</transform>
<transform>
<subtype>textranslate</subtype>
<property>/hud/offset-y</property>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</transform>
<transform>
<subtype>textrapezoid</subtype>
<property>/hud/trapezoid-correction</property>
</transform>
</animation>
</source>

== Object interaction animations ==
=== Enable-hot ===
Scenery objects are automatically defined as solid by FlightGear, meaning that an aircraft can taxi on them and/or crash when touching. For certain objects (groundmarkings, beacon light-beams etc.) this might be an unwanted feature. The solidness can be disabled with the following animation:

<source>
<animation>
<object-name>Object</object-name>
<enable-hot type="bool">false</enable-hot>
</animation>
</source>

* '''enable-hot:''' can be either true or false. Remember that objects are automatically solid, so it should not be necessary to set this at all when wanting solidness.

=== Interactions ===
<source>
<animation>
<type>interaction</type>
<object-name>Object</object-name>
<interaction-type>carrier-wire</interaction-type>
</animation>
</source>

* '''interaction-type:''' can have the following values:
** '''carrier-catapult:'''
** '''carrier-wire:''' makes the object act as an arresting wire, as used on [[aircraft carrier]]s.

== Direct manipulation animations ==
=== Knob / slider (v. 2.11-) ===
{{Main article|Knob / slider animation}}

=== Pick ===
{{Main article|Howto: Make a clickable panel#Pick}}

=== Touch ===

The touch animation provides the normalized coordinates of a touch (or click) event on a 2d surface. The coordinates are passed in the argument and can be accessed using cmdarg() in Nasal.

* Touch animation is designed to work with a quad that is being used as a Canvas placement (display).
* The touch animation must not be combined with a pick animation on the same object.
* More info here: [[Touch Animation]]

==== touch example ====

<animation>
<type>touch</type>
<visible>true</visible>
<object-name>CanvasPlacement</object-name>
<action>
<touch>0</touch>
<repeatable>false</repeatable>
<binding>
<command>nasal</command>
<script>print("touch input (",cmdarg().getNode("x").getValue(),",",cmdarg().getNode("y").getValue())</script>
</binding>
</action>
</animation>

== Shadow Handling ==
There exist several possibilites for handling of shadows. <br />
See '''[[ALS_technical_notes|ALS Technical Notes]]''' and more specific '''[[ALS_technical_notes#ALS_fuselage_shadow_effect|Fuselage Shadow Effect with ALS]]''' for a relatively simple shadow handling.<br />
See '''[[Project Rembrandt]]''' which - amongst other functionality - implements a very realistic shadow mapping.
As of January 2021 Project Rembrandt was replaced by the '''[[Compositor]]''' renderer which combines both Project Rembrandt and ALS in a single rendering engine. This also means that the Fuselage Shadow Effect with ALS is now deprecated.

== References ==
{{Appendix|all|
* {{cite web |url=http://www.opensubscriber.com/message/flightgear-devel@flightgear.org/958955.html |title="material" animation (and the bo105 as an example) |first=Melchior |last=Franz |date=22 March 2005 |work=FlightGear-devel mailinglist }}
* {{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg01546.html |title=flash animation |first=Frederic |last=Bouvier |date=22 Feb 2006 |work=FlightGear-devel mailinglist }}
}}

== Related content ==
=== Wiki articles ===
* [[MP Fallback models]]
* [[Howto:Animate gear scissors]]
* [[Howto:Animate helicopters]]
* [[Howto:Creating 3D instruments]]

=== Forum topics ===
* {{forum link|t=37353|title=3d models, how to produce them in an understandable way}} (April 2020-) - Touches on the subject of not using LOD range animations in scenery models.
* {{forum link|t=36545|title=speedo Drum settings}} (November 2019) - Animating a mechanical multi-digit drum counter

[[Category:Aircraft enhancement|Animate models]]
[[Category:Howto|Animate models]]
[[Category:Modeling|Animate models]]
[[Category:Scenery enhancement|Animate models]]

Howto:Animate models

2021-06-03T10:05:46Z

Sfrsfr: Geometry object axis - added note about normaliziation

The real world is full of motion. To simulate this in [[FlightGear]], '''models must be animated'''.

FlightGear allows you to animate models in response to property changes: for example, the propellers can spin when the engine is on and the elevators can move up and down with your controller. There is no fixed limit on what parts can be animated: the only requirements are that the part is named in the 3D model file, and that there is a property in the main tree that you can use to get the positioning information.

This document provides basic information for all kind of animations. When animating your model, it is very helpful to find an aircraft with parts similar to yours and use it as an example. Cut and paste the code into your wrapper file and then edit to suit.

== Notes ==
=== File name of main model and animation XML file ===
{{main article|Aircraft-set.xml#Not used for loading multiplayer aircraft}}
The file name of the main model and animation XML file, or the .ac file if there is no XML file, (in essence the property <code>/sim/model/path</code>) will be the name of the aircraft that is transmitted when using [[multiplayer]] and will also be used for loading multiplayer aircraft.

There is also a mechanism to substitute a full aircraft model with a simpler AI aircraft model if one is available at the same file path (including for example <code>Models/Boeing-797-800.xml</code>), but in <code>[[$FG_ROOT]]/'''AI'''/Aircraft/</code> instead of <code>$FG_ROOT/Aircraft/</code>.

=== .ac files ===
{{Main article|AC files: Understanding and changing .ac code#Identifying an object}}

When referring to an .ac file in your xml animation, it is important that the <code><object-name></code> exactly matches the object named in the .ac file (this includes cases!).

'''Note for SketchUp users:''' The spatial reference X/Y/Z used in animation to locate an object or a point are different from the ones in AC3D ie X values are the same in both but Y in animation must be matched to AC3D's -Z (Z value but opposite sign) and Z value in animation must be matched to AC3D's Y value.

'''Note for SketchUp users:''' when exporting to AC3D in Sketchup, the .ac file will name the objects in your model to "blah" by default. You need to amend the relevant object names in your .ac file using text edit, so that the xml will work.

=== Animation order ===
Animations are executed by FlightGear in the order that they are read in the model's .xml file. Therefore, it is very important to pay attention to the order, especially when multiple animations are applied to the same object(s).

== Tags used in most animations ==
=== Name ===
With a name animation, you can group multiple objects.

<source>
<animation>
<name>Collection1</name>
<object-name>Object1</object-name>
<object-name>Object2</object-name>
<object-name>Object3</object-name>
</animation>
</source>

The example above creates a "virtual object" with the name Collection1. In animation, we can animate this group of objects, by using:

<source>
<object-name>Collection1</object-name>
</source>

=== Object-name ===
These names are set in the 3D model. Each single object has a unique name; for easy identification it is advised to use descriptive names (LeftElevator, Rudder etc.). Animations are only applied to those objects that are mentioned in an object-name line (one object per line!). Animations lacking those, will be applied to the entire model.

=== Property ===
Each animation must be associated with exactly one property from the main FlightGear property tree (remember that the properties in the wrapper file are not part of the main tree), using <code><property></code> to provide the property path:

<source>
<animation>
<type>rotate</type>
<object-name>Rudder</object-name>
<property>controls/rudder</property>
</animation>
</source>

Note the omission of the leading slash '/' when referring to the property. This assures that when the model is used for AI or multiplayer traffic the animations will follow that of the AI controller instead of that of the user.

=== Axis ===
An axis part is required in every animation that involves a rotating or moving thing.

<source>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</source>

The axis are similar to the ones of the 3D model. There is a difference between rotation and translation:
* In rotation animations, the axis part defines around what axis the object rotates. Negative/positive values make the difference between counterclockwise and clockwise rotations.
* In translate animations, the part defines along what axis the object moves. If the x-axis is poiting backwards, an x-value of -1 will result in forward motion.

You could also define two points, between which FlightGear will calculate the correct axis. This makes the use of a [[#Center|<nowiki><center></nowiki>]] tag redundant! Such coordinates are extremely useful for animating control surfaces (rudder, elevators etc.).

<source>
<axis>
<x1-m> 4.9</x1-m>
<y1-m> 7.1</y1-m>
<z1-m>-1.0</z1-m>
<x2-m> 5.9</x2-m>
<y2-m>11.2</y2-m>
<z2-m>-0.5</z2-m>
</axis>
</source>

=== Center ===
Various animations ([[#Rotate|rotate]], [[#Spin|spin]], [[#Scale|scale]]) move around a center point.

<source>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
</source>

The axis are similar to the ones of the 3D model, so finding coordinates is easily done in 3D modeling software.

=== Using a geometry object for axis and centre (2017.2) ===

Added in V2017.2 is support to allow a geometry object (a line segment with two vertices) that is used to define both the centre and the axis for an animation. This will work with rotate, translate and the knob animations.

The axis line should be balanced, i.e. it should protrude equal amounts. The axis line should be normalized (i.e. 1m) as its length acts as a factor (affecting translate animations).

The syntax for this is
<source>
<axis>
<object-name>some-object</object-name>
</axis>
</source>

Once the object-name used for the axis has been processed the geometry object will be hidden. This also allows a visual check for any axis objects that are not yet assigned.

It is possible to reuse the same object definition multiple times within a single XML file.

[[File:Canopy-animation-axis-object.png|small|Illustration of where an axis object (2017.2) can be placed for a canopy]]

[[File:Gauges-knobs-animation-axis-object.png|small|Illustration of where an axis object (2017.2) can be placed for cockpit elements]]

== Additional tags that can be used in most animations ==
=== Conditions ===
Multiple animations can make use of a conditional. Check <tt>$FGDATA/Docs/README.conditions</tt> for some more details.

* '''equals:''' property value (or second property) is equal to value/(first)property.
* '''greater-than:''' property value (or second property) is larger than value/(first)property.
* '''greater-than-equals:''' property value (or second property) is greater than or equal to value/(first)property.
* '''less-than:''' property value (or second property) is smaller than value/(first)property.
* '''less-than-equals:''' property value (or second property) is smaller than or equal to value/(first)property.

The example below is true when n1 has a value greater than 25.
<source>
<condition>
<greater-than>
<property>engines/engine[1]/n1</property>
<value>25</value>
</greater-than>
</condition>
</source>

Then there are some special tags:

* '''and:'''
* '''not:'''
* '''or:'''

In the example below, the condition is true when either n1 is greater than 25% or equal to 0%.
<source>
<condition>
<or>
<greater-than>
<property>engines/engine[1]/n1</property>
<value>25</value>
</greater-than>
<equals>
<property>engines/engine[1]/n1</property>
<value>0</value>
</equals>
</or>
</condition>
</source>

An example of implementation into an animation looks as follows:

<source>
<animation>
<object-name>Object</object-name>
<type>rotate</type>
<property>suface-positions/left-aileron-pos-norm</property>
<factor>25</factor>
<condition>
<greater-than>
<property>suface-positions/left-aileron-pos-norm</property>
<value>10</value>
</greater-than>
</condition>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

=== Interpolation ===
For non-fixed factors, an interpolation "table" can be created.

<source>
<interpolation>
<entry>
<ind> 0.0</ind>
<dep> 0.0</dep>
</entry>
<entry>
<ind> 0.667</ind>
<dep> 0.0</dep>
</entry>
<entry>
<ind> 1.0</ind>
<dep> 0.5</dep>
</entry>
</interpolation>
</source>

The lines above represent the following table:

{|
!Input
!Output
|-
|0.0
|0.0
|-
|0.667
|0.0
|-
|1.0
|0.5
|}

You can add as many entries as you need. Interpolation tables are often used for gear animations (eg. to open doors during gear-movements and close them again once the gear is either retracted or fully extended).

=== Expressions ===
For some animations it is possible to define complex animations by using [[Expressions|Expressions]]. This even allows to drive the animation from multiple properties without the need for additional Nasal scripts. Here is an example for a translate animation depending on two properties and the cosine function:
<syntaxhighlight lang="xml">
<animation>
<type>translate</type>
<expression>
<product>
<property>/my/factor-property</property>
<cos>
<deg2rad>
<property>/my/angular-property</property>
</deg2rad>
</cos>
</product>
</expression>
[..]more elements[..]
</animation>
</syntaxhighlight>

Animations which can utilize [[Expressions|Expressions]] are:
* [[Howto:Animate_models#Translate|Translate]]
* [[Howto:Animate_models#Rotate|Rotate]]
* [[Howto:Animate_models#Scale|Scale]]
* [[Howto:Animate_models#Range|Range]]
* [[Howto:Animate_models#Blend|Blend]]

See more detailed info at [[Expressions|Expressions]]

== Lights ==
As of January 2021 FligthGear supports multiple light sources just like Project Rembrandt has always done.
[[Compositor#Lights|Adding lights to a model]]

== Object animations ==
=== Alpha-test ===
<source>
<animation>
<type>alpha-test</type>
<object-name>Object</object-name>
<alpha-factor>0.01</alpha-factor>
</animation>
</source>
This "animation" is a way to set an alpha test on a model branch. The effect is to avoid depth buffer writing of pixel that are not seen because they are transparent. This is particulary useful when modeling a metallic structure or a tree with a billboard. The threshold of transparency is set with the <alpha-factor> element. See also [[Pixel testing in effects]].

=== Blend ===
Blends an object with the surrounding. Comparable to a translucency animation. A value of 0 corresponds to no transparency, i.e. and ordinary solid object, and a value of 1 makes the object fully transparent, i.e., not visible at all.

<source>
<animation>
<type>blend</type>
<property>/velocities/airspeed-kt</property>
<factor>0.00025</factor>
<min>0.2</min>
<max>0.7</max>
</animation>
</source>

* '''property:'''
* '''factor:'''
* '''min:'''
* '''max:'''
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

Note that when using the Project Rembrandt renderer, all transparent and translucent objects must be registered to display properly. [[Project_Rembrandt#Registering_all_translucent_surfaces|More information here.]]

=== Billboard ===
This faces an object towards the viewer. Often used on 2D objects, like clouds, trees and lights.

<source>
<animation>
<type>billboard</type>
<object-name>Object</object-name>
<spherical type="bool">true</spherical>
</animation>
</source>

* '''spherical:'''

=== Dist-scale ===
Used to scale an object, based on the distance to the viewer.

<source>
<animation>
<type>dist-scale</type>
<object-name>Object</object-name>
<interpolation>
<entry>
<ind>0</ind>
<dep>1</dep>
</entry>
<entry>
<ind>300</ind>
<dep>4</dep>
</entry>
<entry>
<ind>1500</ind>
<dep>8</dep>
</entry>
</interpolation>
</animation>
</source>

You can optionally add [[#Center|<center>]] coordinates, to scale the object around that point.

=== Flash ===

Used to scale an object based on the cosine of the angle between the axis provided in the animation and the view vector.

<source>
<animation>
<type>flash</type>
<object-name>Object</object-name>
<offset>0.0</offset>
<factor>1.0</factor>
<power>2</power>
<two-sides type="bool">false</two-sides>
<min>0.0</min>
<max>1.0</max>
<center>
<x-m>0.0</x-m>
<y-m>0.0</y-m>
<z-m>0.0</z-m>
</center>
<axis>
<x>0.0</x>
<y>-1</y>
<z>0.1</z>
</axis>
</animation>
</source>

* '''offset:'''
* '''factor:'''
* '''power:'''
* '''two-sides:''' if false, nothing is drawn if the cosine is negative.
* '''min:'''
* '''max:'''

scale = factor * pow( cosine, power ) + offset

scale is then clamped between min and max.

and this scale factor is applied to the object, from the center specified. It works best if scale is less than 1. Otherwise, there will be clipping issues.

=== Noshadow ===
This animation is used to make sure an object will cast no shadow.

<source>
<animation>
<type>noshadow</type>
<object-name>Object</object-name>
</animation>
</source>

=== Range ===
: ''See also [[Modeling - Getting Started#Level of Detail (LOD)]].''

To prevent objects -like instruments- being drawn when the aircraft is actually too far away for them to be seen anyway, a range animation is used.

<syntaxhighlight lang="xml">
<animation>
<type>range</type>
<min-m>0</min-m>
<max-m>30</max-m>
</animation>
</syntaxhighlight>

* '''min-m:''' the shortest distance (in meters) from the object center at which it is visible.
* '''max-m:''' the largest distance (in meters) from the object center at which it is visible.

You could also use the generic level of detail (LOD) properties, which can be set by the user through View > Adjust LOD rangers:
{| class="wikitable"
! Property
! Description
! Default value
|-
|<tt>/sim/rendering/static-lod/bare</tt>
| only a rough exterior model
| 30,000 m
|-
|<tt>/sim/rendering/static-lod/rough</tt>
| most should be visible
| 9,000 m
|-
|<tt>/sim/rendering/static-lod/detailed</tt>
| all details should be visible
| 1,500 m
|}

The animation code will look like this:
<syntaxhighlight lang="xml">
<animation>
<type>range</type>
<min-m>0</min-m>
<max-property>sim/rendering/static-lod/bare</max-property>
</animation>
</syntaxhighlight>

You can have both ranges (max and min) bound to a property, or just one of them.
* '''min-property:'''
* '''max-property:'''
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

=== Rotate ===
One of the most important and frequently used animations of all. It rotates an object to an absolute position in degrees, as provided by the property-value.

<source>
<animation>
<object-name>Object</object-name>
<type>rotate</type>
<property>surface-positions/left-aileron-pos-norm</property>
<factor>25</factor>
<offset-deg>25</offset-deg>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

* '''factor:''' is optional.
* '''offset-deg:''' is optional. Offset in degrees.
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

=== Scale ===
A scale animation scales (resizes) an object. This can be either property-value dependant (first example) or a fixed scale (second example).

<source>
<animation>
<type>scale</type>
<object-name>Object</object-name>
<property>sim/time/sun-angle-rad</property>
<x-min>1.0</x-min>
<y-min>1.0</y-min>
<z-min>1.0</z-min>
<x-factor>1.4</x-factor>
<y-factor>1.4</y-factor>
<z-factor>2.0</z-factor>
</animation>
</source>

* ?-min: the mimimum scale factor for each axis. If the property value would result in a smaller factor than this setting, the scale animation will hold.
* ?-factor: the scale factor for each axis (factor*property=scale factor).

<source>
<animation>
<type>scale</type>
<x-offset>0.5</x-offset>
<y-offset>0.5</y-offset>
<z-offset>0.5</z-offset>
</animation>
</source>

* x.offset: the scale factor.
* Add [[#Center|<center>]] coordinates, to scale the object around that point.
* '''You can optionally use an [[Howto:Animate_models#Expressions|expression]] in the <factor> or <offset> inputs.''' For more details see [[Expressions|Expressions]]

=== Select ===
This animation selects (or unselects) objects when certain conditions are true (or false). The example below shows the object when the n1 of engine[1] is higher than 25%.

<source>
<animation>
<object-name>Object</object-name>
<type>select</type>
<condition>
<greater-than>
<property>engines/engine[0]/n1</property>
<value>25</value>
</greater-than>
</condition>
</animation>
</source>

=== Shader ===
<source>
<animation>
<type>shader</type>
<shader>chrome</shader>
<texture>chrome2.png</texture>
<object-name>Object</object-name>
</animation>
</source>

* '''shader:'''
* '''texture:''' path to the texture used by the shader.

=== Spin ===
Very similar to [[#Rotate|rotate]], but the property provides a value in revolutions per minute (RPM) rather than an absolute position in degrees, and offset cannot be used.

<source>
<animation>
<object-name>Object</object-name>
<type>spin</type>
<property>engines/engine[0]/n1</property>
<factor>25</factor>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

* '''factor:''' is optional.

=== Timed ===
Swtiches between objects at specified intervals. This example switches between a lights-on model and a lights-off model. Lights on are shown 0.2 seconds, while lights off are displayed for 0.8 seconds.

<source>
<animation>
<type>timed</type>
<object-name>BacklightOn</object-name>
<object-name>BacklightOff</object-name>
<use-personality type="bool">true</use-personality>
<branch-duration-sec>0.8</branch-duration-sec>
<branch-duration-sec>0.2</branch-duration-sec>
</animation>
</source>

=== Tracking ===
The new (in 2.11) [[Howto:Animate gear scissors using the tracking animation|''locked-track animation'']] can do exactly the same thing as the [https://docs.blender.org/manual/en/latest/animation/constraints/tracking/locked_track.html Locked Track constraint] available in Blender. However it can also be used to simulate simple inverse kinematic systems consisting of two bones connected with a revolute joint (aka hinge). See [[Howto:Animate gear scissors using the tracking animation|detailed explanation]].

=== Translate ===
The same as [[#Textranslate|textranslate]], but this animation moves a whole object (so including fixed textures). The example below will move an object in the y-direction:

{| class="wikitable" border="0" cellspacing="0"
!Property value
!Output
|-
| -1
| -2.5
|-
| 0
| 2.5
|-
| 1
| 7.5
|}

<source>
<animation>
<type>translate</type>
<object-name>Object</object-name>
<property>controls/seat/pilot/position-norm</property>
<factor>5</factor>
<offset-m>2.5</offset-m>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

When using interpolation tables such as:
<source>
<interpolation>
<entry><ind>0.0</ind><dep> 0</dep></entry>
<entry><ind>0.666</ind><dep>0.18</dep></entry>
<entry><ind>1.0</ind><dep>0.27</dep></entry>
</interpolation>
</source>
The first figure (<ind> refers to the value of the property associated with the object and the second figure (in <dep>) refers to the amount that the object moves in metres. For example, in this case, the object moves 18cm when the value reads 0.66 and 27cm when the value is 1.

'''IF used WTIHOUT property''' : The object is placed at some (Value of Offset) meters away from its original position, along the virtual axis formed by said original position and the point with coordinates x/y/z defined in the <axis> tag.
Mathematically, assuming the Object to translate is (in the model space) placed at point A (x1, y1, z1) and you want to relocate it to point B (x2, y2, z2) then x2,y2,z2 are the values in the <axis> tag of the Translate animation and <offset> can be computed as SQRT((x2-x1)^2+(y2-y1)^2+(z2-z1)^2)

* '''factor:''' is optional.
* '''offset-m:''' is optional. Offset in meters.
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

== Material animation ==
An animation type that can be used in various ways. Of course you can combine the below mentiond systems into one (big) animation.

<source>
<animation>
<type>material</type>
<object-name>Object</object-name>
<property-base>sim/model/c172p/material</property-base>
<global type="bool">true</global> 
...
lines as mentioned below
...
</animation>
</source>

'''Optional:'''
* '''property-base:''' when using prop(erties), you might want to set a property-base. All props will be relative to this path.
* '''global (deprecated):''' by setting this to <tt>true</tt>, all objects using the same material as the defined object(s) (via <tt><object-name></tt>) will be affected by the animation. This is preferred to listing several objects in <object-name> tags. It's not only faster, but also doesn't break animations by forcing objects together. <span style="color:red; text-decoration: underline;">This tag is no longer supported</span>

'''Notes:'''
* Numbers are clamped to 0.0-1.0, except "shininess", which is clamped to 0-128.
* By appending <tt>-prop</tt> each of the material properties can read its value from another property.

=== Ambient ===
<source>
<ambient>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
</ambient>
</source>

=== Diffuse ===
<source>
<diffuse>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
</diffuse>
</source>

=== Emission ===
{{Main article|Howto: Illuminate faces}}
<source>
<emission>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
<factor-prop>controls/lighting/panel-norm</factor-prop>
</emission>
</source>

Emission colors are multiplied by the factor-prop value. 1 is maximum color intensity, while 0 is the minimum. Colors are calculated according to the [http://en.wikipedia.org/wiki/RGB_color_model RGB color model].

=== Shininess ===
Shininess is clamped to 0-128.
<source>
<shininess>105</shininess>
</source>

=== Specular ===
<source>
<specular>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
</specular>
</source>

=== Texture ===
Used for the [[Livery over MP]] system.

<source>
<property-base>sim/model/livery</property-base>
<texture-prop>engine</texture-prop>
<texture>KLM.png</texture>
</source>

=== Transparency ===
<source>
<transparency>
<alpha-prop>rotors/tail/rpm</alpha-prop>
<factor>-0.0015</factor>
<offset>1</offset>
</transparency>
</source>

=== Threshold ===
<source>
<threshold>0.001</threshold>
</source>

== Texture Animations ==

Applying different matrix transformations to the textures of an object.

=== Textranslate ===
A very important animation for cockpits! This animation moves textures over a surface.

<source>
<animation>
<type>textranslate</type>
<object-name>Object</object-name>
<property>autopilot/settings/target-speed-kt</property>
<bias>0.0001</bias>
<factor>0.001</factor>
<step>100</step>
<axis>
<x>0</x>
<y>1</y>
</axis>
</animation>
</source>

* '''bias:''' Adds an offset to the property before factor/step. A small value is needed to compensate for [http://en.wikipedia.org/wiki/Floating_point#Accuracy_problems floating point accuracy].
* '''factor:''' property * factor * texture width/height = the amount of pixels that the texture should be translated. If your texture is 256 pixels, an textranslate of 0.1 will result in the texture moving with 26 pixels, into the direction specified by the axis settings.
* '''step:''' the step size at which the texture is translated. If this is set to 0.1, the texture will only be translated at 0.1, 0.2, 0.3 etc.
* '''axis:''' the direction in which the texture is translated. Y is up/down, while X is left/right.

=== Texrotate ===

<source>
<animation>
<object-name>Object</object-name>
<type>texrotate</type>
<property>some/property/path</property>
<factor>25</factor>
<offset-deg>25</offset-deg>
<center>
<x>0.5</x>
<y>0.5</y>
<z>0</z>
</center>
<axis>
<x>0</x>
<y>0</y>
<z>1</z>
</axis>
</animation>
</source>

=== Textrapezoid ===

<source>
<animation>
<type>textrapezoid</type>
<object-name>HUD.l.canvas</object-name>
<property>/hud/trapezoid-correction</property>
<side>bottom</side>
</animation>
</source>

* '''side''': side of quad which should be scaled (''top'' (default)/''right''/''bottom''/''left'')

=== Texmultiple ===

Only one texture matrix can be applied to each object. With ''textmultiple'' multiple texture animations can be combined into a single matrix, applied to the specified object.

<source>
<animation>
<type>texmultiple</type>
<object-name>HUD.l.canvas</object-name>
<transform>
<subtype>textranslate</subtype>
<property>/hud/offset-x</property>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</transform>
<transform>
<subtype>textranslate</subtype>
<property>/hud/offset-y</property>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</transform>
<transform>
<subtype>textrapezoid</subtype>
<property>/hud/trapezoid-correction</property>
</transform>
</animation>
</source>

== Object interaction animations ==
=== Enable-hot ===
Scenery objects are automatically defined as solid by FlightGear, meaning that an aircraft can taxi on them and/or crash when touching. For certain objects (groundmarkings, beacon light-beams etc.) this might be an unwanted feature. The solidness can be disabled with the following animation:

<source>
<animation>
<object-name>Object</object-name>
<enable-hot type="bool">false</enable-hot>
</animation>
</source>

* '''enable-hot:''' can be either true or false. Remember that objects are automatically solid, so it should not be necessary to set this at all when wanting solidness.

=== Interactions ===
<source>
<animation>
<type>interaction</type>
<object-name>Object</object-name>
<interaction-type>carrier-wire</interaction-type>
</animation>
</source>

* '''interaction-type:''' can have the following values:
**'''carrier-catapult:'''
** '''carrier-wire:''' makes the object act as an arresting wire, as used on [[aircraft carrier]]s.

== Direct manipulation animations ==
=== Knob / slider (v. 2.11-) ===
{{Main article|Knob / slider animation}}

=== Pick ===
{{Main article|Howto: Make a clickable panel#Pick}}

=== Touch ===

The touch animation provides the normalized coordinates of a touch (or click) event on a 2d surface. The coordinates are passed in the argument and can be accessed using cmdarg() in Nasal.

* Touch animation is designed to work with a quad that is being used as a Canvas placement (display).
* The touch animation must not be combined with a pick animation on the same object.
* More info here: [[Touch Animation]]

==== touch example ====

<animation>
<type>touch</type>
<visible>true</visible>
<object-name>CanvasPlacement</object-name>
<action>
<touch>0</touch>
<repeatable>false</repeatable>
<binding>
<command>nasal</command>
<script>print("touch input (",cmdarg().getNode("x").getValue(),",",cmdarg().getNode("y").getValue())</script>
</binding>
</action>
</animation>

== Shadow Handling ==
There exist several possibilites for handling of shadows. <br />
See '''[[ALS_technical_notes|ALS Technical Notes]]''' and more specific '''[[ALS_technical_notes#ALS_fuselage_shadow_effect|Fuselage Shadow Effect with ALS]]''' for a relatively simple shadow handling.<br />
See '''[[Project Rembrandt]]''' which - amongst other functionality - implements a very realistic shadow mapping.
As of January 2021 Project Rembrandt was replaced by the '''[[Compositor]]''' renderer which combines both Project Rembrandt and ALS in a single rendering engine. This also means that the Fuselage Shadow Effect with ALS is now deprecated.

== References ==
{{Appendix|all|
* {{cite web |url=http://www.opensubscriber.com/message/flightgear-devel@flightgear.org/958955.html |title="material" animation (and the bo105 as an example) |first=Melchior |last=Franz |date=22 March 2005 |work=FlightGear-devel mailinglist }}
* {{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg01546.html |title=flash animation |first=Frederic |last=Bouvier |date=22 Feb 2006 |work=FlightGear-devel mailinglist }}
}}

== Related content ==
=== Wiki articles ===
* [[MP Fallback models]]
* [[Howto:Animate gear scissors]]
* [[Howto:Animate helicopters]]
* [[Howto:Creating 3D instruments]]

=== Forum topics ===
* {{forum link|t=37353|title=3d models, how to produce them in an understandable way}} (April 2020-) - Touches on the subject of not using LOD range animations in scenery models.
* {{forum link|t=36545|title=speedo Drum settings}} (November 2019) - Animating a mechanical multi-digit drum counter

[[Category:Aircraft enhancement|Animate models]]
[[Category:Howto|Animate models]]
[[Category:Modeling|Animate models]]
[[Category:Scenery enhancement|Animate models]]

Volunteer

2020-11-30T10:59:37Z

Sfrsfr: /* Creating Scenery Models */ Fixed broken link '3D models'

{{Volunteer Intro}}

== Media ==
=== Screenshots ===
Another easy way for getting started contributing is to create nice FlightGear screenshots. You can upload these to the wiki where they can then be used to illustrate articles and to highlight articles via the [[:Category:Picture of the week|picture of the week]] on the main page.

[[Howto: Make nice screenshots]] provides some tips on how to create stunning shots, while [[Help:Upload]] discusses how to upload screenshots to the wiki.

=== Videos ===
Many users like to capture their flights in FlightGear as a video, YouTube for example is an excellent way for sharing such videos with fellow FlightGear users. YouTube videos can also be directly embedded in forum postings and wiki articles.

=== Screencasts (video tutorials) ===
Creating FlightGear related video tutorials is another excellent way for getting started contributing.

== Documentation ==

{{forum|72|FlightGear Documentation}}

=== FAQ-Maintainers ===
The FlightGear project is looking for people who are willing to help maintain the FAQ which, given the constant development of the project, is chronically out of date. If you you would like to get involved, follow the {{forum link|text=forum}} to stay current on the latest news, problems, and of course on what questions are asked more frequently, and simply start editing the [[FAQ|wiki FAQ]].

=== Maintaining the wiki ===
You can easily [[Special:UserLogin|register an account]] and help [[Portal:Wiki|improve the wiki]], and provide your help in reviewing articles, fixing their look and readability, updating them and adding what you think is missing, for example many articles could be greatly improved just by adding a handful of relevant screenshots for illustration purposes. Proof reading of existing articles is also greatly appreciated.

Registering takes less than 10 seconds. After registration, you'll have to confirm your registration by clicking on the link sent to you by email.

=== Translating the wiki and FlightGear ===
You can also help localize the wiki by [[Help:Translate|translating]] important articles into different languages. Please see the [[translation requests]].

Also, FlightGear itself can be easily translated by updating the files in [[$FG_ROOT]]/Translations. For details please see [[Howto: Translate FlightGear|Translating FlightGear]].

=== Wiki article writers ===
Various aspects of FlightGear are currently not yet sufficiently documented, and available documentation is often not really suitable to be used by non-developers. This results in users being unaware of the wide range of features and possibilities that FlightGear supports already.

As an "article writer" you should be able to document your own experiences with FlightGear in a clear and concise style, so that others can easily follow your instructions in order to make use of the less known features of FlightGear. These articles don't need to be very comprehensive, they shall only provide users with easy to follow instructions on how to achieve something, and possibly some caveats and hints.

* [[:Category:Volunteer: Writing]]

=== Contributing to "The Manual" ===
The wiki is not the only documentation here, of course. FlightGear comes with a set of illustrated documentation, notably [[FlightGear Manual|"The Manual"]]. If you are a skilled writer and a little bit familiar with LaTex, your help would be really welcome. More on this at "The Manual" wiki page. You'll find the source code in the {{getstart source|text=Getstart repository}}.

=== Documentation Editors/Reviewers ===
{{Main article|Howto:Write a FlightGear Review}}
The documentation that comes with FlightGear base package is lacking, terse or simply inaccurate (outdated), due to the advances in FlightGear's code. You should check the current documentation and identify areas for improvement, by directly making corresponding suggestions for augmentations, or even writing new help documents altogether, while staying current with the mailing list.

Smaller corrections shall be sent by email to the developer mailing list, preferably in unified diff format (for patch to work). Alternatively, small text files can also be sent directly to the mailing list, more complex modifications should be only made available by uploading them to a webpage and linking to the corresponding files from your emails. Please consider trying [http://kdiff3.sourceforge.net/ KDiff3], a GUI frontend to the diff and patch utilities that works on several platforms (also Windows).

If you intend to redo a major part of the current documentation, first discuss this with the developers, to avoid documenting code that may also be under development or deprecation.

== Development ==
=== Creating interactive tutorials ===
FlightGear has a built-in [[Tutorials|tutorial]] system that is based on its scripting language [[Nasal]], this system is very flexible and can be used for creating interactive tutorials (or even missions) for use in FlightGear itself, in other words these tutorials run directly in the simulator.

Creating new tutorials, or updating and improving existing ones, is another great way for getting more familiar with FlightGear. For details please see [[Tutorials]].

=== Providing patches for aircraft's -set.xml status fields ===
One way you could easily contribute would be to submit patches to HEAD setting the "status" flag on each aircraft accurately. While it will require learning a bit about SCM, and XML, that would be a fine contribution. For a details on how the status should be arrived at see [[Aircraft status indication]].

=== Creating Scenery Models ===
The FlightGear project maintains a steadily growing repository of [http://scenemodels.flightgear.org 3D models] for adding some eye-candy to the scenery. The world has always enough room left for your [http://scenemodels.flightgear.org/contribute.php contribution]. Please take the time to investigate what is already there and enjoy populating your favourite area.

Note that you don't have to create any models yourself. You can simply [[Howto: Place 3D objects with the UFO|place existing models using the UFO]]. For example, placing objects in the scenery with the [[UFO]] and submitting them to the database is pretty straightforward and takes very little time. Even an hour spent doing this makes a difference.

If anyway you'd like to [[Modeling - Getting Started|test your modeling skills]], here some suggestions:
* We need people to go out and take good pictures of all the buildings at their local airports, build models, and create textures (that could be different people for each task).
* We need people to start modelling identifiable human-made landmarks like bridges, stadiums, and major buildings. Around the San Francisco Bay area, bridges are especially important. Once you have identified some buildings or objects you would like to have (Aircraft carriers, fuel bowsers, cars, towers, ...) you will need to check out the tools for creating and placing these objects.

It would be helpful if people would model the area they are interested in. Generally contributions are going to be from FlightGear users who find scenery lacking in some area and choose to improve it. You are encouraged to research your own area for airport, navaid and scenery information, to contribute the data or dive right in to airport and scenery design.

=== Making airports ===
Sometimes you'd like to populate your favourite airport with objects, but you find it has a wrong layout or that it doesn't exist at all! So, you'll want to [[Howto:Make an airport|make or improve that layout]], which can be done with [[WED]]. Remember that we're maintaining an open (GPL) airport database in common with X-Plane simulator.

Other than just fix the look, you might want to add interactive details like [[AI Traffic]] and maybe update navaids and comm frequencies. We need people to go over paper lists and airport diagrams for countries that don't publish air navigation data free online (i.e. almost everyone but the U.S.) and fill in the blanks in our navaid and airport databases (''note: especially for the last part, see the website of the current maintainer: [http://data.x-plane.com/ data.x-plane.com]''.)

To be sure the airport you're interested in is not already being worked on, check the [[Airports under construction]] article. Also, note that since we switched to a newer format for the airport database, there are many airports that need to be converted from the older (810) format to the newer (850). All the info is in [[Howto:Make an airport]].

=== Contributing to the scenery terrain ===
We need people to collect geodata to give us more accurate roads, rivers, etc., especially outside the U.S. and Europe. Note that since we're now allowed to use OpenStreetMap data for this, you might consider contributing to that project too. With time, more and more features will be imported from OSM, beginning with roads and rails, and going on with power lines and antennas and whatnot.

The first step into this is learning how to [[Using TerraGear|use TerraGear]]. Remember that all the data you plan to use must be GPL compatible. You might also consider editing some of that source data and contribute it to the Scenery Project that would make good use of it!

=== Core development ===
If you actually happen to be a C++ programmer and know Git, consider contributing to [[Howto:Start core development|core development]].

{{CppBind Ideas}}

== Other ==
=== Submitting bugs to the Bug Tracker ===
Bugs can be reported to [http://code.google.com/p/flightgear-bugs/ this tracker]. Reporting bugs accurately helps make bug fixing significantly easier for the developers. Another thing that is very helpful, is reviewing posted bug reports and see if you can reproduce/confirm them on your system.

=== Artwork Creators/Contributors ===
FlightGear itself would not be possible without the contribution of various types of artwork:
* Aircraft developers need photographs, images and sounds to realistically model a particular aircraft.
* The splash screen displayed when loading the simulator can be personalized, and you can [[Howto: Create custom splash screens|create one for your favourite aircraft]].
* Sound recordings of aircraft are also very valuable - particularly engine sounds for unusual aircraft.

In general, you can find requests and post your offers of this kind in the Developers forum, but you can also browse [[:Category:Aircraft by status|existing aircraft projects]] and see if there's anything you'd like to improve.

=== Pre-Release Testers ===
Prior to a release, release candidates are provided to the community. By directly providing feedback about your experiences with FlightGear's development code, you will become a crucial part of the development process and you will basically serve as quality control for FlightGear, your experiences will determine whether FlightGear's development code is ready for a next official release or not. See the [[Release plan]] to find out when release candidates will be distributed.

Note: If you are interested in actually doing development for FlightGear, make sure to check out the [[Portal:Developer|Developer section]].

=== Hosting a multiplayer server ===
If you have access to an Unix based server, another good opportunity for contributing would be to set up a multiplayer server for use with FlightGear, for details please check out [[Howto: Set up a multiplayer server]].

=== Tell us if FlightGear works with your hardware ===
You can help fellow FlightGear users by telling us if FlightGear works with your hardware. Please see [[FlightGear Hardware Recommendations]], [[Problematic Video Cards]] and [[Notebooks known to run FlightGear]].

=== Participate in the FlightGear Forums ===
If you haven't done so already, please consider registering at the {{forum link|text=FlightGear forum}}, this is a very simple thing to do, but it makes it very easy to obtain and provide help and other support within the FlightGear community.

Taking extra care in your posting to avoid requiring the attention of the moderators is in some ways also a contribution. Doing so helps self-police the forums so that the moderators can spend their time doing constructive development.

=== Check out the FlightGear Chat channel ===
{{Main article|FlightGear IRC channel}}
To talk to fellow FlightGear users in realtime, you may want to check out the IRC chat channel.
This is also an excellent way for getting and providing community help, or for getting the latest news about FlightGear.

=== Tell us about your own ideas and feature requests for improving FlightGear ===
If you think you have a good idea or feature request for improving FlightGear, the FlightGear forums and the IRC channel are also an excellent way for getting feedback.

Another new way for posting feature requests and making suggestions is provided at http://flightgear-bugs.googlecode.com

=== Help us write the FlightGear Newsletter ===
The FlightGear newsletter is a community driven newsletter that is created and edited using the wiki. All FlightGear users are invited to contribute to the newsletter. The only thing that is required is a wiki account, which is free and easy to register.

Please feel free to add news about your own FlightGear related projects, or projects started by others to the newsletter.

You can find the draft of next month's newsletter at: [[Next newsletter]]

Just tracking the forums, mailing lists or the IRC channel should provide you with plenty of opportunities for things that could be added to the newsletter. One simple thing for getting started - even without writing anything - is uploading screen shots showing recent FlightGear developments for use in the FlightGear newsletter.

=== Reviews ===
Another thing that can be easily done is reviewing FlightGear (or just certain parts of it, like for example scenery and/or aircraft) and submit your reviews to some of the flight simulation portals. Of course, you can also directly write your reviews using the FlightGear wiki, see: [[FlightGear Reviews]].

[[Category:Contribution requests]]
[[Category:Community]]

[[es:Tener a bien]]
[[fr:Volontaires]]

Software testing

2020-09-26T17:34:12Z

Sfrsfr: /* Building the test suite */ Cosmetics

{{Note|There’s already the test_suite in {{fg src file|path=test_suite}} using [[Cppunit effort|CppUnit]], thanks to some hard work by [[User:Bugman|Edward]]. We need more tests written for it, submissions welcome. (Pick an area of interest)<ref>https://sourceforge.net/p/flightgear/mailman/message/36972720/</ref>}}

{{See also|Cppunit effort}}

The FlightGear source code and data are tested by the FlightGear developers using a number of tools. This includes automated testing via unit tests in [[SimGear]] and a full test suite with multiple test categories in the [[FlightGear Git|flightgear repository]], as well as manual in-sim testing. Writing tests is one of the best ways to jump into FlightGear development.

One improving area is unit-testing: because of which, certain areas and features (eg, carrier start) now ‘can’t break’. As we add more such areas (eg Multi-player, AI, protocols and replay are all possible), we increase the baseline quality, and also have a clearer idea when we make incompatible changes. (The idea being we capture the ‘supported API’ in the tests: when an aircraft deviates from that, we can decide to add another test case, fix the aircraft, etc). Of course, there’s some pretty major areas where Automated Testing Is Hard (TM).<ref>https://sourceforge.net/p/flightgear/mailman/message/37078825/</ref>

== SimGear ==

The [[SimGear]] sources are checked via unit testing. This is implemented using the CMake CTest unit testing infrastructure. A number of tests are currently implemented using the BOOST unit testing infrastructure tied to the build system using CTest, however this should be avoided when writing tests as there is a shift towards eliminating BOOST by the FlightGear developers.

=== Building and running the SimGear tests ===
<syntaxhighlight lang="bash">
$ make
$ ctest
</syntaxhighlight>

== FlightGear ==

Testing of the [[FlightGear Git|flightgear sources]] is via a comprehensive test suite implemented using [https://www.freedesktop.org/wiki/Software/cppunit/ CppUnit], a port of the famous JUnit framework.

=== Building the test suite ===

To run the tests you will need to build FlightGear from source using cmake. See [[Building FlightGear]] for details.

Once you have your cmake build environment do the following:
# Change to your FlightGear build directory
# Enable building the tests by setting a cmake variable: <code>cmake -LBUILD_TESTING=ON .</code>
# Ensure the <code>[[$FG ROOT|$FG_ROOT]]</code> environment variable points to fgdata e.g. <code>$FG_INSTALL_DIR/share/fgdata</code>
# Build the test suite: <code>make test_suite</code>

This will also run the full test suite (see below), because you will typically want to write a test and then immediately compile and run it.

=== Running the test suite ===

To run the test suite, simply run <code>./test_suite/fgfs_test_suite</code>

This will run the full test suite and print a Synopsis of results similar to the following:

Synopsis
========

System/functional tests ....................................... [ OK ]
Unit tests .................................................... [ OK ]
Simgear unit tests ............................................ [ OK ]
FGData tests .................................................. [ OK ]
Synopsis ...................................................... [ OK ]

You can also run individual test cases. Run <code>./test_suite/fgfs_test_suite -h</code> to see the various options

=== Why write unit tests? ===

A well tested piece of software will have a much lower bug count/load. An extensive test suite with '''unit tests''', system/functional tests, GUI tests, installer tests, and other categories of tests can significantly help in this regard.

The benefits of not just chasing clear "wins" are great: An awesome learning experience for new developers; the ability to catch latent, unreported bugs; making it easier to refactor current code by creating a safety net; making it easier for current developers to accept new contributions (when accompanied with passing tests); helping other test writers by contributing to the common test suite infrastructure; and being able to easily check for memory leaks or other issues via Valgrind.<ref>https://sourceforge.net/p/flightgear/mailman/message/36977686/</ref>

If you are a new developer, just jump in and write any test! It does not need to catch a bug. Do whatever how ever you wish! Just dive in this shallow end and you'll see that the water is not cold.

Writing a test as a safety net. You write the test to pass, make your changes, then make sure that the test still passes. Then you push both the test and core changes.<ref>https://sourceforge.net/p/flightgear/mailman/message/36977465/</ref>

It'd be better jumping into a specific area of interest to you, and submitting merge-requests. That would naturally trigger some C++ feedback when reviewed but we aren’t looking for perfection here, more to increase the overall pool of knowledge of what best-practice looks like, even if a given commit is less than perfect.

I,e It’s more important to have 10 or 20 people actively contributing correct-and-reasonable code than three people contributing absolutely perfect, micro-optimised C++. <ref>https://sourceforge.net/p/flightgear/mailman/message/36951247/</ref>

=== Benefits of unit testing ===
There are lots of benefits to writing tests that pass.

Benefits include :

* Learning! New developers can learn a ton from writing a number of passing tests in the area they are interested in. This is one of the quickest ways to learn about a pre-existing and mature code base. You have zero worries about breaking things. This is diving in the shallow end.

* Latent bug uncovering. For every ten tests you write expecting them to pass, one will probably fail. Or at least uncover unexpected behavior that can be improved.

* Refactoring. If we had 10,000 passing tests (assuming universal test coverage), large scale refactoring of the entire code base would be quick and reliable. It would enable refactoring on a scale currently unimaginable. I cannot emphasize enough how much of a benefit this would be.

* Developer turnover. Again if we had 10,000 passing tests (assuming universal test coverage), it would encourage new developers. This is because the fear of breaking something is removed. It is a total safety net. It also would give existing developers peace of mind when a new developer is touching one of the dark parts of FlightGear that no current developer understands (there are plenty of those) .

* Test suite infrastructure. The more passing tests written, the better the test suite infrastructure will become. We can already do a lot. But the addition of more passing tests will help other test writers.

* Memory checking. Running a single test through Valgrind is amazing. Running FlightGear through Valgrind is close to impossible. Passing tests can be written to catch memory leaks!

* Low code quality and standards. This is related to the learning point. As long as a test compiles on all OSes without warning, it passes, and Valgrind gives you an ok, it is good enough. You dont need to be a C++ expert to dive into this shallow end of the pool.

=== Bootstrapping completely new tests ===
To start diving straight into the test suite code, firstly copy what has been done in this commit: {{repo link
| site = sf
| user = edauvergne
| repo = flightgear
| commit = 8474df
| view = commit
}}

Just modify all names for a JSBSim test (or any other test fixture you
want to code). You should then be able to compile and check that your
new testDummy() test passes as expected. You can then slowly build up
from this basic infrastructure as you learn the fgfs internals, c++,
and git skills required for implementing your test on your fork's new
development branch :)

=== Headless testing ===
{{Main article|FlightGear Headless}}

For an FDM+systems test, we should run FG without a renderer (which is what the test_suite does), to benchmark the pure C++ performance of whatever system it is we care about (FDM or whatever). But this is not really worth doing anyway, since a few hours playing with ‘perf’ on Linux / Instruments on macOS will show you that 80% of our CPU time is spent in OSG + the GL drivers, and hence Amdhal’s law will always get you.<ref>https://sourceforge.net/p/flightgear/mailman/message/36977666/</ref>

=== Graphics testing ===
{{See also|FlightGear Benchmark}}

The other thing is to setup some test-case scenes where you can quickly measure differences and compare via screenshots. The brain/eye/memory are very bad at this stuff, setup something you can load from the command line via a script to test old/new versions, if possible. <ref>https://sourceforge.net/p/flightgear/mailman/message/36959002/</ref>

For example, a test would would be a .[[fgfsrc]] that makes:
* c172p at some parking in a detailed airport;
* camera looking at it in specific direction with specific FOV;
* AW with specific METARs around (if not possible, BW with specific METAR);
* fixed rendering settings (several variants may be needed for renderers and threading modes) <ref>https://sourceforge.net/p/flightgear/mailman/message/36975122/</ref>

We can already load a [[Instant Replay|replay tape]] on startup, however, which is good for testing rendering (scenery, loading) performance, since the FDM is not involved, nor is the user-interface.

But essentially any and all of the methods proposed can be done here with small amounts of shell-script + Nasal hacking I think, and any of them would be welcome additions. For lower-level tests run by developers, the unit-test framework is great (i.e ‘does the API call produce the right results in the system’), but a smoke-test that regular users can run would be ideal.

A rendering performance would likely do:

* select some particular rendering settings (clouds, draw distance, etc)
* run a saved fgtape recording
* record the mean/min/max FPS during this and save it in some text file / copy to the clipboard

So yes, if anyone wants to work on the above, the code is all there, please jump in and start hacking - I don’t think it needs any more from the core code, but as ever, please just ask if it does.<ref>https://sourceforge.net/p/flightgear/mailman/message/36975213/</ref>

For example, describing a /rendering/ test (to establish FPS) - the advantage of a replay tape is the actual position (and therefore what is rendered) will be 100% consistent acorss different computers.

Keep in mind that the CPU use of the FDM+systems is typically < 10% of our total CPU use, even when running OSG single-threaded, so for a rendering performance test, whether the FD is run or not is probably noise compared to other things that do run (Nasal, Canvas for example)

Also, Multi-monitor setup is not tested so commonly unfortunately. <ref>https://sourceforge.net/p/flightgear/mailman/message/36904782/</ref>

== Fgdata ==
=== Nasal scripting (comments) ===
{{WIP}}

The now builtin CppUnit framework can obviously solve all the issues
identified in the old [[Nasal Unit Testing Framework]] wiki article and the discussions it points to
and provide the full framework required.<ref>https://sourceforge.net/p/flightgear/mailman/message/36990615/</ref>

have some very simple tests running now for the route-manager, which rely on Nasal. we're skipping a few of the bigger Nasal modules (local-weather, jetways) and have a few lingering issues in some other modules but the basic concept is working.

A very interesting further step, which you might wish to discuss with Edward, is writing test checks *in* Nasal, since this could be quite a fast way to test some area of the code. There’s several ways that could work, and I don’t know if Edward has always planned something around this, so I won’t preempt that conversation.
<ref>https://sourceforge.net/p/flightgear/mailman/message/36764781/</ref>

we have route-manager tests which validate route_manager.nas is working correctly, and we have Canavs tests ({{fg src file|path=test_suite/simgear_tests/canvas|}}) which poke the Nasal API. <ref>https://sourceforge.net/p/flightgear/mailman/message/36991200/</ref>

We need more FGData testing via the test suite.

Adding the CppUnit assertions to Nasal, is the task James has been suggesting he would do, so others can write tests in pure Nasal.

The other piece is some C++ code to scan a directory for files matching a pattern, eg test_XYZ.nas, and to run each of those automatically.

The idea for testing Nasal would be that you write a small CppUnit
interface in c++ in $FG_SRC/test_suite/*_tests/ (the FGData Nasal
testing would be in a fgdata_tests/ directory). This would register
each test which points to the script in
$FG_SRC/test_suite/shared_data/nasal/, and the setUp() and tearDown()
functions would use helper functions in the fgtest namespace to start
and stop Nasal. The Nasal scripts could then call the CppUnit
assertion macros wrapped up as Nasal functions for communicating
failures and errors to the test suite. <ref>https://sourceforge.net/p/flightgear/mailman/message/36991150/</ref>

Scanning for scripts is a great idea. Then developers (core and content) could write tests in pure Nasal.

However all scripts found and executed will be seen as a single test within the test suite. So maybe we should have a $FG_SRC/test_suite/nasal_staging/ directory for initial development of such auto-scanned scripts. But then we have someone shift them into $FG_SRC/test_suite/system_tests/, $FG_SRC/test_suite/unit_tests/, or $FG_SRC/test_suite/fgdata_tests/ later on? That would give better diagnostics and would avoid long-term clutter.<ref>https://sourceforge.net/p/flightgear/mailman/message/36991198/</ref>

* First we should probably hard code tests into the C++ framework. The CppUnit assertion macros will have to be wrapped up as Nasal functions for this.
* Then implement the scanning code as we need some CMake magic (probably using file(COPY, ...)).
* Finally work out if and how we need to improve the Nasal debugging output.

the code could go into a subdirectory in $FG_SRC/test_suite/fgdata_tests/, and the Nasal script in $FG_SRC/test_suite/shared_data/nasal/.

== References ==
{{Appendix}}

[[Category:Core development]]

Software testing

2020-09-26T12:30:42Z

Sfrsfr: /* Building the test suite */ Added note about $FG_ROOT

{{Note|There’s already the test_suite in {{fg src file|path=test_suite}} using [[Cppunit effort|CppUnit]], thanks to some hard work by [[User:Bugman|Edward]]. We need more tests written for it, submissions welcome. (Pick an area of interest)<ref>https://sourceforge.net/p/flightgear/mailman/message/36972720/</ref>}}

{{See also|Cppunit effort}}

The FlightGear source code and data are tested by the FlightGear developers using a number of tools. This includes automated testing via unit tests in [[SimGear]] and a full test suite with multiple test categories in the [[FlightGear Git|flightgear repository]], as well as manual in-sim testing. Writing tests is one of the best ways to jump into FlightGear development.

One improving area is unit-testing: because of which, certain areas and features (eg, carrier start) now ‘can’t break’. As we add more such areas (eg Multi-player, AI, protocols and replay are all possible), we increase the baseline quality, and also have a clearer idea when we make incompatible changes. (The idea being we capture the ‘supported API’ in the tests: when an aircraft deviates from that, we can decide to add another test case, fix the aircraft, etc). Of course, there’s some pretty major areas where Automated Testing Is Hard (TM).<ref>https://sourceforge.net/p/flightgear/mailman/message/37078825/</ref>

== SimGear ==

The [[SimGear]] sources are checked via unit testing. This is implemented using the CMake CTest unit testing infrastructure. A number of tests are currently implemented using the BOOST unit testing infrastructure tied to the build system using CTest, however this should be avoided when writing tests as there is a shift towards eliminating BOOST by the FlightGear developers.

=== Building and running the SimGear tests ===
<syntaxhighlight lang="bash">
$ make
$ ctest
</syntaxhighlight>

== FlightGear ==

Testing of the [[FlightGear Git|flightgear sources]] is via a comprehensive test suite implemented using [https://www.freedesktop.org/wiki/Software/cppunit/ CppUnit], a port of the famous JUnit framework.

=== Building the test suite ===

To run the tests you will need to build FlightGear from source using cmake. See [[Building FlightGear]] for details.

Once you have your cmake build environment do the following:
# Change to your FlightGear build directory
# Enable building the tests by setting a cmake variable: <code>cmake -LBUILD_TESTING=ON .</code>
# Ensure the [[$FG ROOT|$FG_ROOT]] environment variable points to fgdata e.g. $FG_INSTALL_DIR/share/fgdata.
# Build the test suite: <code>make test_suite</code>

This will also run the full test suite (see below), because you will typically want to write a test and then immediately compile and run it.

=== Running the test suite ===

To run the test suite, simply run <code>./test_suite/fgfs_test_suite</code>

This will run the full test suite and print a Synopsis of results similar to the following:

Synopsis
========

System/functional tests ....................................... [ OK ]
Unit tests .................................................... [ OK ]
Simgear unit tests ............................................ [ OK ]
FGData tests .................................................. [ OK ]
Synopsis ...................................................... [ OK ]

You can also run individual test cases. Run <code>./test_suite/fgfs_test_suite -h</code> to see the various options

=== Why write unit tests? ===

A well tested piece of software will have a much lower bug count/load. An extensive test suite with '''unit tests''', system/functional tests, GUI tests, installer tests, and other categories of tests can significantly help in this regard.

The benefits of not just chasing clear "wins" are great: An awesome learning experience for new developers; the ability to catch latent, unreported bugs; making it easier to refactor current code by creating a safety net; making it easier for current developers to accept new contributions (when accompanied with passing tests); helping other test writers by contributing to the common test suite infrastructure; and being able to easily check for memory leaks or other issues via Valgrind.<ref>https://sourceforge.net/p/flightgear/mailman/message/36977686/</ref>

If you are a new developer, just jump in and write any test! It does not need to catch a bug. Do whatever how ever you wish! Just dive in this shallow end and you'll see that the water is not cold.

Writing a test as a safety net. You write the test to pass, make your changes, then make sure that the test still passes. Then you push both the test and core changes.<ref>https://sourceforge.net/p/flightgear/mailman/message/36977465/</ref>

It'd be better jumping into a specific area of interest to you, and submitting merge-requests. That would naturally trigger some C++ feedback when reviewed but we aren’t looking for perfection here, more to increase the overall pool of knowledge of what best-practice looks like, even if a given commit is less than perfect.

I,e It’s more important to have 10 or 20 people actively contributing correct-and-reasonable code than three people contributing absolutely perfect, micro-optimised C++. <ref>https://sourceforge.net/p/flightgear/mailman/message/36951247/</ref>

=== Benefits of unit testing ===
There are lots of benefits to writing tests that pass.

Benefits include :

* Learning! New developers can learn a ton from writing a number of passing tests in the area they are interested in. This is one of the quickest ways to learn about a pre-existing and mature code base. You have zero worries about breaking things. This is diving in the shallow end.

* Latent bug uncovering. For every ten tests you write expecting them to pass, one will probably fail. Or at least uncover unexpected behavior that can be improved.

* Refactoring. If we had 10,000 passing tests (assuming universal test coverage), large scale refactoring of the entire code base would be quick and reliable. It would enable refactoring on a scale currently unimaginable. I cannot emphasize enough how much of a benefit this would be.

* Developer turnover. Again if we had 10,000 passing tests (assuming universal test coverage), it would encourage new developers. This is because the fear of breaking something is removed. It is a total safety net. It also would give existing developers peace of mind when a new developer is touching one of the dark parts of FlightGear that no current developer understands (there are plenty of those) .

* Test suite infrastructure. The more passing tests written, the better the test suite infrastructure will become. We can already do a lot. But the addition of more passing tests will help other test writers.

* Memory checking. Running a single test through Valgrind is amazing. Running FlightGear through Valgrind is close to impossible. Passing tests can be written to catch memory leaks!

* Low code quality and standards. This is related to the learning point. As long as a test compiles on all OSes without warning, it passes, and Valgrind gives you an ok, it is good enough. You dont need to be a C++ expert to dive into this shallow end of the pool.

=== Bootstrapping completely new tests ===
To start diving straight into the test suite code, firstly copy what has been done in this commit: {{repo link
| site = sf
| user = edauvergne
| repo = flightgear
| commit = 8474df
| view = commit
}}

Just modify all names for a JSBSim test (or any other test fixture you
want to code). You should then be able to compile and check that your
new testDummy() test passes as expected. You can then slowly build up
from this basic infrastructure as you learn the fgfs internals, c++,
and git skills required for implementing your test on your fork's new
development branch :)

=== Headless testing ===
{{Main article|FlightGear Headless}}

For an FDM+systems test, we should run FG without a renderer (which is what the test_suite does), to benchmark the pure C++ performance of whatever system it is we care about (FDM or whatever). But this is not really worth doing anyway, since a few hours playing with ‘perf’ on Linux / Instruments on macOS will show you that 80% of our CPU time is spent in OSG + the GL drivers, and hence Amdhal’s law will always get you.<ref>https://sourceforge.net/p/flightgear/mailman/message/36977666/</ref>

=== Graphics testing ===
{{See also|FlightGear Benchmark}}

The other thing is to setup some test-case scenes where you can quickly measure differences and compare via screenshots. The brain/eye/memory are very bad at this stuff, setup something you can load from the command line via a script to test old/new versions, if possible. <ref>https://sourceforge.net/p/flightgear/mailman/message/36959002/</ref>

For example, a test would would be a .[[fgfsrc]] that makes:
* c172p at some parking in a detailed airport;
* camera looking at it in specific direction with specific FOV;
* AW with specific METARs around (if not possible, BW with specific METAR);
* fixed rendering settings (several variants may be needed for renderers and threading modes) <ref>https://sourceforge.net/p/flightgear/mailman/message/36975122/</ref>

We can already load a [[Instant Replay|replay tape]] on startup, however, which is good for testing rendering (scenery, loading) performance, since the FDM is not involved, nor is the user-interface.

But essentially any and all of the methods proposed can be done here with small amounts of shell-script + Nasal hacking I think, and any of them would be welcome additions. For lower-level tests run by developers, the unit-test framework is great (i.e ‘does the API call produce the right results in the system’), but a smoke-test that regular users can run would be ideal.

A rendering performance would likely do:

* select some particular rendering settings (clouds, draw distance, etc)
* run a saved fgtape recording
* record the mean/min/max FPS during this and save it in some text file / copy to the clipboard

So yes, if anyone wants to work on the above, the code is all there, please jump in and start hacking - I don’t think it needs any more from the core code, but as ever, please just ask if it does.<ref>https://sourceforge.net/p/flightgear/mailman/message/36975213/</ref>

For example, describing a /rendering/ test (to establish FPS) - the advantage of a replay tape is the actual position (and therefore what is rendered) will be 100% consistent acorss different computers.

Keep in mind that the CPU use of the FDM+systems is typically < 10% of our total CPU use, even when running OSG single-threaded, so for a rendering performance test, whether the FD is run or not is probably noise compared to other things that do run (Nasal, Canvas for example)

Also, Multi-monitor setup is not tested so commonly unfortunately. <ref>https://sourceforge.net/p/flightgear/mailman/message/36904782/</ref>

== Fgdata ==
=== Nasal scripting (comments) ===
{{WIP}}

The now builtin CppUnit framework can obviously solve all the issues
identified in the old [[Nasal Unit Testing Framework]] wiki article and the discussions it points to
and provide the full framework required.<ref>https://sourceforge.net/p/flightgear/mailman/message/36990615/</ref>

have some very simple tests running now for the route-manager, which rely on Nasal. we're skipping a few of the bigger Nasal modules (local-weather, jetways) and have a few lingering issues in some other modules but the basic concept is working.

A very interesting further step, which you might wish to discuss with Edward, is writing test checks *in* Nasal, since this could be quite a fast way to test some area of the code. There’s several ways that could work, and I don’t know if Edward has always planned something around this, so I won’t preempt that conversation.
<ref>https://sourceforge.net/p/flightgear/mailman/message/36764781/</ref>

we have route-manager tests which validate route_manager.nas is working correctly, and we have Canavs tests ({{fg src file|path=test_suite/simgear_tests/canvas|}}) which poke the Nasal API. <ref>https://sourceforge.net/p/flightgear/mailman/message/36991200/</ref>

We need more FGData testing via the test suite.

Adding the CppUnit assertions to Nasal, is the task James has been suggesting he would do, so others can write tests in pure Nasal.

The other piece is some C++ code to scan a directory for files matching a pattern, eg test_XYZ.nas, and to run each of those automatically.

The idea for testing Nasal would be that you write a small CppUnit
interface in c++ in $FG_SRC/test_suite/*_tests/ (the FGData Nasal
testing would be in a fgdata_tests/ directory). This would register
each test which points to the script in
$FG_SRC/test_suite/shared_data/nasal/, and the setUp() and tearDown()
functions would use helper functions in the fgtest namespace to start
and stop Nasal. The Nasal scripts could then call the CppUnit
assertion macros wrapped up as Nasal functions for communicating
failures and errors to the test suite. <ref>https://sourceforge.net/p/flightgear/mailman/message/36991150/</ref>

Scanning for scripts is a great idea. Then developers (core and content) could write tests in pure Nasal.

However all scripts found and executed will be seen as a single test within the test suite. So maybe we should have a $FG_SRC/test_suite/nasal_staging/ directory for initial development of such auto-scanned scripts. But then we have someone shift them into $FG_SRC/test_suite/system_tests/, $FG_SRC/test_suite/unit_tests/, or $FG_SRC/test_suite/fgdata_tests/ later on? That would give better diagnostics and would avoid long-term clutter.<ref>https://sourceforge.net/p/flightgear/mailman/message/36991198/</ref>

* First we should probably hard code tests into the C++ framework. The CppUnit assertion macros will have to be wrapped up as Nasal functions for this.
* Then implement the scanning code as we need some CMake magic (probably using file(COPY, ...)).
* Finally work out if and how we need to improve the Nasal debugging output.

the code could go into a subdirectory in $FG_SRC/test_suite/fgdata_tests/, and the Nasal script in $FG_SRC/test_suite/shared_data/nasal/.

== References ==
{{Appendix}}

[[Category:Core development]]

AirportEditor

2020-09-05T07:41:05Z

Sfrsfr:

{{Infobox Software
| title = AirportEditor
| image =
| alt =
| developedby =
| initialrelease =
| latestrelease = 1.0.1 (2008)
| writtenin = Java
| os = OS Independent
| developmentstatus =
| license = [[GNU General Public License]].
| website = http://flightgear.greghawkes.com/tools/airporteditor.html
}}

('''FlightGear''')''' AirportEditor''' is a Java-based [[AI Traffic#Ground networks|AI ground network]] editor for [[FlightGear]]. Ground networks are vital for proper functioning [[Interactive AI|AI-traffic]], as they "tell" the aircraft what taxiroutes to follow.

AirportEditor requires Java version 6 (or later) to run.

== Related content ==
* [[TaxiDraw]], another ground network editor, but also airport layout editor.
* [[FGAirports]], another ground network editor, aiming to replace TaxiDraw.
* [[WorldEditor]], an airport layout editor.

== External link ==
* [http://flightgear.greghawkes.com/tools/airporteditor.html Official website]

[[Category:Scenery enhancement]]
[[Category:Software]]

Suggested software

2020-09-05T07:39:20Z

Sfrsfr:

==== Frontends ====
* [[FlightGear Launch Control]], FGrun is a graphical frontend to run FlightGear Flight Simulator.
* [http://code.google.com/p/fgcomgui FGComGUI] [http://forum.flightgear.org/viewtopic.php?f=6&t=5746]
* [[Airport Diagram Generator]] [http://forum.flightgear.org/viewtopic.php?f=6&t=5377]
* [[TerraGear GUI]]
* [[TerraMaster]] Java software allows you to manage scenery downloads without TerraSync

==== Using FlightGear ====
* [[FlightGear Admin Wizard|FGAdmin]]
* [[FGCOM]]
* [[MPmap]]

==== Mapping Software ====
* [[Atlas]] ([http://atlas.sourceforge.net Atlas]) aims to produce and display high quality charts of the world for users of FlightGear, an open source flight simulator. This is achieved through two main parts: The map creator (simply called Map) and the Atlas viewer.
* [[Kelpie Flight Planner]]
* [[Airport Diagram Generator]]
* Flightgear Mapping ([http://rubyforge.org/projects/fgmap fgmapping]): Provide a real-time map of flight position in Flightgear. It is based on tiles from Openstreetmap, downloads them in the background, provides navigation aids and runways, allows setting of waypoints and tracks the flight.

==== Scenery and Airport Editing ====
* [[TerraGear]] ([http://www.terragear.org TerraGear]) is a collection of open source tools and rendering libraries which can transform publically available GIS data in 3d representations (i.e. 3d models or 3d maps) of the earth for use in real time rendering projects. TerraGear can import 3d data sets such as DEM terrain grids, 2d polygon data sets such as coastlines, city outlines, lake outlines, and 2d raster data sets such as the 1km NAOO land use/land cover data. It also has tools for generating realistic airports, runways, and lighting based on available FAA data. <
** See [[Building Terragear]] for a walkthrough on obtaining a working copy of the TerraGear tools, and [[Using Terragear]] for an outline of the scenery building process.
* [[Taxidraw]] ([http://taxidraw.sourceforge.net/ Taxidraw])
* [[FGAirports]] a replacement for Taxidraw. Edit Airport groundnet files required for AI Traffic.
* [[AirportEditor]] ([http://www.greghawkes.com/flightgear/tools/airporteditor.html AirportEditor]) a [[Java]]-based airport editor for FlightGear [http://www.mail-archive.com/flightgear-users@lists.sourceforge.net/msg06118.html]
* [[WorldEditor]]

=== General ===
* 7-zip
* [[Blender]]
* [[GIMP]] ('''G'''NU '''I'''mage '''M'''anipulation '''P'''rogram, The Gimp)
* [[Open Office]]

== See also ==
* [[FlightGear related projects]]

[[Category:Lists]]
[[Category:Software]]

Howto:Place 3D objects with the UFO

2020-07-25T07:11:39Z

Sfrsfr: /* Placing objects */ Corrected keyboard shortcut. L, not Shift L

The [[UFO from the 'White Project' of the UNESCO|UFO]] aircraft is a superb tool for placing a new (or old) 3D object at any arbitrary location in the scenery with just a few clicks of the mouse. Placing objects in the scenery is a really easy way to contribute to the [[FlightGear]] project. It does not require any programming knowledge, and you can contribute something valuable in just a few minutes.

This article gives an overview of placing, editing and saving objects using the UFO. You can get a list of flying controls and editing commands by pressing the {{key press|?}} key while flying the UFO.

== Choosing your object ==
The first thing you need is a 3D model to place in the scenery. The [[FlightGear Scenery Database]] ([http://scenemodels.flightgear.org/ scenemodels.flightgear.org]) maintains a huge library of generic models, which will have been included in your FlightGear installation under the <tt>[[$FG_ROOT]]/Models/</tt> directory. You can skip to the next section when using a generic model.

=== Consider the file sizes ===
If you add many complex models or models with big textures to the scenery it ''will'' increase the memory usage and slow down FlightGear.
Here are two lists with shared models and shared model textures sorted by file size:
* [[Shared models sorted by file size]]
* [[Textures of shared models sorted by file size]]

=== Creating your own models ===
Alternatively, you can create your own models. You should save it in a subdirectory of your [[$FG_ROOT]] folder. Two options seem reasonable, although others are possible as well:
* Shared model, not unique to a single objects (for example a wind turbine): save it in a subdirectory of <tt>[[$FG_ROOT]]/Models/</tt>. That is the standard directory where the UFO will go when you press the space bar {{Key press|Space}}.
* Static model, unique object (like the Eiffel Tower): save it in the respective subdirectory of the Scenery folder, e.g. <tt>[[$FG_ROOT]]/Scenery/Objects/w130n30/w123n37</tt>. To browse objects anywhere on your computer, press {{key press|L}} when using the UFO.

When creating your own object, make sure it is the correct size. In [[Blender]], units are meters. Note that you should be careful about using Google Earth, due to restrictions in their license that might prevent submitting your work to the FlightGear database. See {{forum link|t=3356|text=here}} and {{forum link|t=3415|text=here}}.

== Selecting the UFO ==
[[File:Placing_objects_with_UFO_html_m49fbed81.jpg|400px]]

Now start FlightGear with the UFO as your aircraft and enable the console, which is needed later on. When launching FlightGear from command line, use <code>--aircraft=ufo --console</code>. In [[FGRun]], the "Show console" option on the last page should be checked.

== Placing objects ==
Once FlightGear has been started, fly with the UFO to roughly the place you want the model to be positioned.

[[File:Placing_objects_with_UFO_html_5fa8d7b1.jpg|400px]]

Let's say we want to position the catii-iii.xml object at the end of a taxiway. We stop the UFO just above this intersection and press the space key. A Select Model window will open up where the contents of the <tt>[[$FG_ROOT]]/Models/</tt> directory will be shown (or press {{key press|L}} and you can go to any desired directory). Select your preferred model from this list, then close the window. The selected model path/name will be displayed in green text at the bottom left of the FlightGear screen.

[[File:Placing_objects_with_UFO_html_m184fb381.jpg|400px]]

To place the object, simply left-click on the position that you want to place it. By default, it is placed completely horizontal and rotated to point north. It will probably not have the correct orientation and it might be partly covered by the surrounding terrain, but we can adjust that.

[[File:Placing_objects_with_UFO_html_12ee70a1.jpg|400px]]

=== Rotating objects ===
Fly closer to the ground with the UFO, so that you can see it better.

Now press {{key press|{{=}}}} (earlier versions than 3.0 uses {{key press|Tab}}) and use the resulting sliders to adjust the latitude/longitude/elevation/heading of the model. NB: "Pitch" and "roll" will not be saved, so using them might be fun, but won't help eventually.

[[File:Placing_objects_with_UFO_html_439816e9.jpg|400px]]

See the [[UFO from the 'White Project' of the UNESCO]] page for more information on the UFO command keys and exported file locations, or press {{key press|?}} while in FlightGear.

=== Deleting objects ===
There are three different ways to three different situations in which which you want to delete an object:
You want to delete the last object that you placed in this session:
: Press the [http://en.wikipedia.org/wiki/Backspace backspace button].
You want to delete an object that you placed in this session, but you have placed one or two models after it:
: That means that it is no longer active. Activate it by placing one more model '''on''' the object you want to delete, press the backspace button. Result: The model you want to delete starts blinking, which tells you that it is active.
You want to delete an object that is already saved in the corresponding .stg file and you don't know where it is:
: You don't know the filename: The model you want to delete is probably a shared model. You find it in the [http://scenemodels.flightgear.org/ scenery database]. Now you know the model's filename (e.g. [http://scenemodels.flightgear.org/modeledit.php?id=45 generic_skyscraper_01.ac] or [http://scenemodels.flightgear.org/modeledit.php?id=537 Office26x22.xml]).
: You still need to know where you find it. Place any model on that building and press {{key press|D}} to know in which file you find it (see [[#Exporting the result|Exporting the result]] below). If there are several objects of that type and you want to delete only one of them, find the one closest to the coordinates of your model placed on top.
: Open the .stg file, delete the whole model entry (see [[#Exporting the result|Exporting the result]] below). Done.

== Exporting the result ==
Now that the model is correctly positioned, press the {{key press|D}} key to dump the model position data to the terminal. A few lines will be printed on the console, providing the necessary orientation data.

[[File:Placing_objects_with_UFO_html_m4cf0cbf7.jpg]]

The most important lines are the last ones:
# e000n50/e008n50/3089154.stg
OBJECT_SHARED Models/Tabu/catii-iii.xml 8.57928135 50.03667992 105.9972 111.1

The first line identifies the location of the scenery file for the object. The OBJECT_SHARED line indicates the object's name, longitude, latitude, altitude, and orientation. This can be read by FlightGear itself and can be [http://scenemodels.flightgear.org/contribute.php submitted] to the FlightGear Scenery Object Database.

You can also save these coordinates into your own scenery file so that your changes will not be lost the next time you start FlightGear.

=== Saving the changes to your scenery ===
In the terminal window, you get three sections printed out by the UFO with very detailed information about what's going on. We need the lines at the end.

As noted above, the UFO helpfully exports the name of the scenery file where the object's coordinates have to be saved. In our example: e000n50/e008n50/3089154.stg

The default location for scenery objects is <tt>[[$FG_SCENERY]]/Objects/</tt>. Simply open the referenced .stg file, add the OBJECT_SHARED line to the bottom and save the file. Now you have your object's position saved, and it will appear inside the scenery every time you start FlightGear! There is one pitfall here. If TerraSync is enabled, which is the default in latest FlightGear versions, and you modified the stg file in the TerraSync folder, your modifications might be overridden by the syncing process. You might need to add the startup option --disable-terrasync for avoiding this and to keep your modifications.

In our example we would open in <tt>[[$FG_SCENERY]]/Objects/e000n50/e008n50/3089154.stg</tt> and add the following line:
OBJECT_SHARED Models/Tabu/catii-iii.xml 8.57928135 50.03667992 105.9972 111.1

For a short video demonstrating the .stg method, see the following video:
{{#ev:youtube|i2BSUOMyiIg|400|center}}

=== Saving to XML ===
Alternatively, if you press the {{key press|E}} key while developing scenery with UFO, FlightGear will generate an XML file with the dump of your current work in an "ufo-model-export.xml" file under [[$FG_HOME]].

=== Loading the XML file as part of FlightGear scenery ===
You can later reload this XML file with --config= command-line parameter:
Example for Linux: fgfs --config=$HOME/.fgfs/Export/ufo-model-export.xml

In Windows, this is done using the Advanced dialog, found on the last page of the [[FGRun]] GUI. Click Advanced and, under General, click the double-dot button, browse to the ufo-model-export.xml file and click OK.

== Sharing your updates with everyone! ==
Please, once you've improved the scenery around your place, consider sharing it with the community. This is done very easily using our [http://scenemodels.flightgear.org/submission scenery submission webforms]. More information and help on {{forum link|t=14671|text=the dedicated topic}} on the scenery forum.

[[Category:Howto]]
[[Category:Scenery enhancement]]
[[ar:Howto:Place 3D objects with the UFO]]
[[es:Colocar objetos con el UFO]]
[[fr:Placer des objets 3D avec UFO]]

Howto:Work with AC3D files in Blender

2020-07-25T05:12:32Z

Sfrsfr: /* Notes */ Added note about AC3D material settings

Many [[FlightGear]] [[aircraft]] modelers prefer [[Blender]] as their 3D-modelling editor. FlightGear primarily uses the [[AC3D]] file format (<code>.ac</code>) to model aircraft, [[scenery]] models, and many other things. For recent versions of Blender import/export support for the AC3D file format is implemented as an addon. This page gives a few more details about this addon.

{{TOC limit|3}}

== Blender versions 2.80 and later ==
=== Majic79 addon ===
Current maintainer: [[User:Necolatis]]

Tested with Blender version 2.63 to 2.78a

For more information you can follow the topic {{forum link|t=13442|title=Blender 2.6 AC3D Importer & Exporter}}.

: {{github source|user=NikolaiVChr|repo=Blender-AC3D|branch=2.80|text=Download Link (GitHub)}}. Probably: [[User:Necolatis]] due to lack of credits unsure.
: {{github source|proj=NikolaiVChr|repo=Blender-AC3D|text=Repository}} ({{github zip file|NikolaiVChr|Blender-AC3D|text=ZIP file download for Blender <= 2.79}}).

Notice that the above link is to Necolatis (Nikolai) latest version, as the Majic79 GitHub has not kept up with the updates and seems dead.

=== Notes ===
* Before you export a model with this addon, make sure that you set the UV map and texture inside the material, not just inside the UV editor. See the video tutorial [https://www.youtube.com/watch?v=URMjoFSm5pk here].
* Before you export make sure to exit ''Edit Mode'' or some of your last changes won't be exported.
* Inside Blender when you want to see the textures, be sure to set the shader to GLSL (or for 2.7+ just set view mode to materials). Alternatively set textured solid in solid view.
* To see textured surfaces as they will be shown in FlightGear, go into the material texture and set the blend type to ''Multiply'' instead of the default ''Mix'' (the importer will also do this automatically). An example plane that will look very different if this is not done is the FGAddon aircraft {{fgaddon source|path=Aircraft/ASK13|commit=1363|text=ASK-13}}, notice the wingtips.
* The final model might display color mismatches (Texture color vs Material color) when viewed in Flightgear. Hand editing the [[AC files: Basic changes to textures and colors#Materials|materials]] section of the exported AC3D file might fix this.
* If you wonder where to put the scripts you could open blender's user preferences ({{Key press|Ctrl|Alt|U}}, or ''File > User Preferences'') tick for example Import/Export and extent the information concerning an existing script. Usually this throws the path. For for example Ubuntu 14.04LTS/Blender 2.79b it is: <code>/usr/share/blender/scripts/addons/</code>.
* Be aware that Blender only has greyscale for emission and ambient colors. If you want to export/import a color for those, import/export options gives you capability to choose to use Blenders mirror color for that.
* The importer will not fail if it does not locate a texture, instead it will issue warnings. Pull down the top bar to see if there was any, they will be orange lines.
* The exporter will not fail if it tries to save a texture without data, instead it will issue warnings. Pull down the top bar to see if there was any, they will be orange lines. Notice that since AC3D only support 1 texture per object, if multiple textures are attached to an object in Blender the last of the textures that has any data, if any, will be the one that get exported, but it will still warn about the missing data in the others, so take care.
* Orientation: The default settings in the plugin correspond to the FlightGear coordinate system (-X forward and Z up, also see: [[Howto:3D_Aircraft_Models]]). The default settings are: Forward -Z and Up Y.

You can report bugs with the addon [https://github.com/NikolaiVChr/Blender-AC3D/issues here], but please include problematic <code>.ac</code>/<code>.blend</code> files and their textures.

=== Linux (kubuntu 19.10, DeBIAN 10 "buster") ===
: Use: <code>download.zip</code> (or really make sure to grep the right tree (see above!))

# Unpack <code>.zip</code> file.
# Read <code>README.MD</code>.
# Install for example into <code>/home/<User>/...</code>. Do '''not''' install into <code>/usr/...</code> since you will be lacking writing rights.
# Copy <code>io_scene_ac3d</code> into <code>blender-<version>-<OS architecture>/<version>/scripts/addons</code> (for example <code>blender-2.82a-linux64/2.82/scripts/addons</code>)
# Installation via Edit > Preferences > Addons > Install and select: <code>__init__.py</code>

== Blender versions 2.63 and later ==
For version 2.63 and later you have a choice of several scripts.

=== Mr. No addon ===
==== Notes ====
* When exporting with this addon, make sure you set the texture inside the UV editor.
* When using this script, it is very important that everything is textured. The addon will silently fail if this is not the case.
* This script does not work reliable when nested groups are being used in the imported AC3D model (for example {{github source|user=NikolaiVChr|repo=flightgear-saab-ja-37-viggen|tag=FG-v3.4|path=Aircraft/JA37/Models/Instruments/Altimeter2/altimeter-metric.ac|text=here}}).
* The importer cannot handle the token <code>subdiv</code>, its just ignored.
* The exporter does not always export the rotations/location matrix of objects correctly.

: [http://www.mediafire.com/?m4f9m95qj9e5qq0 Download link (MediaFire)]

=== FG2blender (PAF Team) ===
Authors: f-jjth, run

The PAF team (Patrouille de France), a French group of FlightGear enthusiasts have also made an AC3D Blender script. Their last commit dates back to 11 December 2013 and it feels like their FG2Blender project is abandoned. The PAF team is essentially active on their [http://equipe-flightgear.forumactif.com/ own French speaking forum]. There is no trace or documentation available, so the notes below are speculative and incomplete. It would be interesting to test these scripts and check if the work of the PAF team can be merged with the work of [[User:Necolatis]] as this is actually the only AC3D script that is still maintained.

==== Notes ====
* According to the source code, the script seems to be able to export animation.

{{sourceforge source|proj=pafteam|repo=fg2blender|text=Repository}} ([https://sourceforge.net/p/pafteam/fg2blender/ci/master/tarball Zip file download]{{dead link|2020-07}})

== Blender versions 2.5 to 2.62 ==
For these versions you can use one of these scripts by Majic79:

* {{github source|proj=majic79|repo=Blender-AC3D|branch=BL2.59|text=Version for Blender 2.59 (repository)}} ({{github zip file|majic79|Blender-AC3D|branch=BL2.59|text=ZIP file download}}).
* {{github source|proj=majic79|repo=Blender-AC3D|branch=BL2.60|text=Version for Blender 2.60 (repository)}} ({{github zip file|majic79|Blender-AC3D|branch=BL2.60|text=ZIP file download}}).
* {{github source|proj=majic79|repo=Blender-AC3D|branch=BL2.62|text=Version for Blender 2.62 (repository)}} ({{github zip file|majic79|Blender-AC3D|branch=BL2.62|text=ZIP file download}}).

== Blender versions 2.4 and older ==
For these versions, Blender supports both the import and export of AC3D files out of the box. Just go into user preferences and enable the addon scripts.

== External links ==
* {{cite web
| url = http://www.inivis.com/ac3d/man/ac3dfileformat.html
| title = The AC3D file format
| date = 27 March 2003
| publisher = Inivis Limited
| archiveurl = https://web.archive.org/web/20180814212703/http://www.inivis.com/ac3d/man/ac3dfileformat.html
| archivedate = 14 Aug 2018
| accessdate = 17 Jul 2020
}}

{{3d}}

[[Category:Modeling]]

Blender

2020-07-25T04:44:16Z

Sfrsfr: /* Also related to modeling and Blender */ Reordered links

'''Blender''' is a open source 3D content creation suite available for all major operating systems under the [[GNU General Public License]] and available for free. <sup>[http://www.blender.org/]</sup> Many [[FlightGear]] developers use Blender, and there are a lot of articles on the FlightGear Wiki about using it.

'''Note:''' An [[Blender_AC3D_import_and_export|importer/exporter]] for FlightGear's most common 3D format (AC3D, .ac) is only included in Blender version 2.49b or older. For later versions you have to install it manually. See the dedicated [[Blender_AC3D_import_and_export|Blender AC3D import and export]] wiki page for more information.

== Related content ==
=== Blender related articles ===
* [[Howto: Add smooth ("Ambient Occlusion") shadows in Blender]]
* [[Howto: Modeling Ground Signs with Blender]]
* Aircraft modeling tutorial (flightgear-specific)
** by Helijah: Breguet Br-761 "Deux ponts"
*** [http://helijah.free.fr/flightgear/Creation/Creation-fr.htm In French]
*** [http://helijah.free.fr/flightgear/Creation/Creation-en.htm In English]
* Aircraft modeling tutorial (non-flightgear-specific)
** by Kevin Jongen: [http://www.websitetoolbox.com/tool/post/felixdk/vpost?id=2283400 Nieuport 11] and [http://www.military-meshes.com/forums/showthread.php?t=2232 additional discussion]
** by Samo: [http://forums.cgsociety.org/showthread.php?f=91&t=252648&highlight=blender+aircraft Policarpov I-15 Chato]
** by Witold Jaworski: [http://airplanes3d.net/wm-000_e.xml E-book "Virtual Modeling" ] on P-40B. With over 3600 pictures and 1112 pages. Currently only in Polish (no English). But you can try machine translation plus the use of many pictures :-)
* Aircraft modeling video tutorial
** How to model Me163 Komet (Blender 2.64): [http://www.youtube.com/watch?feature=player_embedded&v=0et7lFsIf5E#! youtube]
** How to model an airliner (Blender 2.5): [http://www.youtube.com/watch?v=a5pva-Meu7E youtube]
** Blender 2.5 Tutorial- Introduction to Modeling in Blender: [http://www.youtube.com/watch?v=BGfJLsm54ho&feature=related youtube]
** Blender 2.59 Airplane Modeling Timelapse [http://www.youtube.com/watch?v=hC5pzvBbyQw&feature=relmfu youtube]
** Modeling an X-Wing in Blender 3D (Blender 2.4): [https://www.youtube.com/watch?v=BGfJLsm54ho&feature=related youtube]
** Blender 2.49b Reference Image Setup for Modeling workflow. [http://www.youtube.com/watch?v=SSedXO00H1c youtube] (Setting up the reference images as textured flat objects visible not only in orthographic views)

=== Also related to modeling and Blender ===
* [[Modeling - Getting Started]]
* [[Modeling - FAQ]]
* [[Model Import and Export]]
* [[Normals and Transparency Tutorial]]
* [[Howto: Illuminate faces|Illuminate faces]]
* [[Howto: Make a helicopter|Make a helicopter]]
* [[Modeling - SketchUp]]
* [[SketchUp to AC3D exporter]]
* [[GMax2AC]]

== External links ==
* [http://www.blender.org/ Official website]
* [http://wiki.blender.org/index.php/Main_Page Official wiki]
* [http://www.blender.org/download/get-blender/ Get Blender]

{{3d}}

[[Category:Modeling]]
[[Category:Software]]
[[Category:GPL software]]

Modeling - Getting Started

2020-07-17T19:18:04Z

Sfrsfr: Added reference to 'Blender AC3D import and export' wiki page

== Notice for Volunteers ==
{{main article|Volunteer#Scenery Model Creators}}
* We need people to go out and take good pictures of all the buildings at their local airports, build models, and create textures (that could be different people for each task).
* We need people to start modelling identifiable human-made landmarks like bridges, stadiums, and major buildings. Around the San Francisco Bay area, bridges are especially important. Once you have identified some buildings or objects you would like to have (Aircraft carriers, fuel bowsers, cars, towers, ...) you will need to check out the tools for creating and placing these objects.

== Getting Started ==

Generally one can start with a blueprint using their favorite imaging software like Gimp, Photoshop, or Paint shop pro then separate various views (front, back, etc...) into greyscale jpg files. Then import them as a background for easy modelling in your favorite 3D modelling software program.

=== 3D Software ===
To begin, you will need to create models in a 3d modeling appliction. Three popular ones are AC3D, Blender and SketchUp. FlightGear can display models in several formats, any format supported by [[PLIB]] is acceptable. AC3D is the most popular format for including scenery in Flightgear. Most or all of the default scenery bundled with a Flightgear release are in AC3D format.

If you do not have AC3D, Blender offers many import and export tools. See the Blender website for further information.

==== [[AC3D]] ====
Flightgear uses the ac3d model format for objects such as buildings. To create a model, you will need one of two modelling packages. Either go directly to [http://www.ac3d.org AC3D] itself, or use [http://www.blender.org Blender] and then convert via a Python script (see below). AC3D seems to be a much easier program to learn, while still being very powerful. The downside is that you have to buy a licence to get more than 14 days use.

* [http://wine.techlab.info/AC3D_Tutorials/ AC3D Modeling Tutorials]

==== [[Blender]] ====
[http://www.blender.org Blender] is more difficult to learn to use, since it is not quite as intuitive and is far more powerful. However it is GPL'd, and there are lots of tutorials to help with learning.

* [http://wiki.blender.org Blender Manual]
* [http://blenderartists.org/forum/ Excellent forum for discussing Blender issues]
* [[Blender AC3D import and export]]

Note: Before you start modelling its recommended to activate the 'Backface Culling' option (Viewport Shading -> Options). This will allow you to spot faces with inverted Normals. In FlightGear these faces will be invisible. To check your model for this issue switch Viewport Shading to Solid. Now you will be able to spot the affected faces. To correct them, mark all affected Faces. Then go to Mesh -> Normals and click 'Flip'.

==== SketchUp ====
{{Main article|Modeling - SketchUp}}

SketchUp (http://sketchup.google.com) is the easiest to use of these three programs. But the results are very nice and professional. I recommend SketchUp for users who are not really good at difficult computer programs.

==== [[Wings 3D]] ====
{{Main article|Modeling - Wings 3D}}

Wings 3D (http://www.wings3d.com/) is another 3D modeling program, and is free open source software.

=== Placing Objects on Scenery ===
There are several ways of doing this. The most direct way is to simply [[Adding shared models manually|add the required data by hand]].

[[File:Placing objects with UFO html 439816e9.jpg|thumb|270px|The model adjustment dialog of the [[UFO]]]]
The easiest way is to use the [[Placing 3D Objects with the UFO|UFO's object placement feature]] (in version 9.10 or higher). When operating the UFO, left-clicking the mouse anywhere on the ground will place an object, and pressing space-up or down will cycle through the models. Coordinates of placed models can then be dumped to the terminal or written to a configuration file.

[[Talk:Modeling_-_Getting_Started|Obsolete project?]] Another method is to use [[FlightGear Scenery Designer]] ([http://fgsd.sourceforge.net/ Project Site]). After setting the paths to your scenery data, simply load up the area where you want to place the object. Load your .ac format model, and right click on the desired spot to place your model there. Export the modifed scenery to save it, rerun Flightgear and your model should be there.

=== Finding, Creating, or Using Textures ===
Models in Flightgear use textures with PNG format.

Most image editors support editing PNG files, like [[THE GIMP]], Corel Paintshop Pro, Adobe Photoshop, etc.

The old SGI rgb format (.rgb extension) is no longer supported. (see http://scenemodels.flightgear.org/)

Once you have made your model building, you will want to apply some textures to it, so it looks as realistic as possible. This is possibly one of the hardest areas, as a good model with bad textures will still look bad. Since Flightgear and the scenery data are all released under the GPL, any textures that you use must also be able to be released under this license. This will probably prevent you from just using anything you come across on the net, unless it is already under the GPL. It is quite common for people to state that their pictures or textures are free. Since Flightgear can be sold for profit, and is released on Linux distributions that are sold, check that there are no clauses stating that the item can not be sold or used for commercial use.

=== Generation of textured light objects in Blender ===

{| style="margin-top:0.1em; margin-bottom:0.1em; margin-left:2em; padding:2px; font-size:95%; text-align:left; background: transparent;"
|-
| [[File:1rightarrow.png|15px]] ''See http://members.aon.at/mfranz/flightgear/blender-textured-lights.html for the main article about this subject.''
|}

== Improving models for best FlightGear performance ==
{{Merge|Modelling guidelines}}
[[File:Motor.jpg|thumb|270px|Using Multiple Models with varied detailing]]
[[File:Singlesided_blender.jpg|thumb|270px|To set faces to Singlesided (Blender), deselect the Doublesided button]]
=== Mesh ===
* In a single model, use a single mesh so far as possible. Note that this doesn't mean that every node must be linked to its object with an edge (e.g. a line of trees can be easily a single object.) Only have the separate objects if you need them for an animation or parts that use a transparent texture (any object using more then one texture is anyway spitted by the rendering engine.)
* Delete unseen faces such as faces inside the model, but remember that the [[Project Rembrandt|Rembrandt renderer]] needs closed meshes to cast shadows correctly, so you'll often want to keep the ones below.
* Remove "line faces", which are faces whose points are in the same line.
* Don't forget to remove double vertices (i.e. vertices sharing the same coordinates)
* See [[Howto:Decrease the number of faces]].

=== Single sided / double sided ===
* Set all the faces of the model to SingleSided. DoubleSided faces are very expensive to render properly. If a face needs to be displayed from every view angle use two faces with opposite normals rather than a Doublesided one (the overhead from the extra geometry is far lower than the overhead of doublesided faces)

=== Textures and Materials ===
{{FGCquote
|Modern graphics cards can handle very large textures and huge numbers of vertices with minimal frame rate impact. A typical scene in FlightGear (with clouds, buildings rivers, roads...) has millions of vertices which simply dwarfs a 17K aircraft making the aircraft model an insignificant factor. The general rule is use enough vertices and large enough textures to make things look right and no more. More recent aircraft efforts tend to have much higher vertex counts, much larger textures and a lot more detail then older work because of how capable modern hardware is. It is not unusual to see newer aircraft exceeding 100K vertices. For example the P-51D that will be released with 3.2 has an external model that is slightly over 100K vertices and this had a minimal frame rate impact on my (newer high end) hardware compared to the old 10K external model. <br/>
<br/>
If you can't see the difference between using a 512x512 instrument texture compared to a 256x256 texture then use the smaller texture. But if you can see the difference then use the larger texture. On modern hardware the difference in frame rate will be very small but it may impact those with older/slower/obsolete hardware in a noticeable way. All of the instruments in the P-51D are 512x512 for larger gauges or 256x256 for smaller gauges and at least to me they have a sharp appearance even when zoomed in fairly close. Many older aircraft use 128x128 textures for instruments but to me at least on the larger instruments on a very high resolution monitor these textures are a little bit fuzzy in appearance. The other thing I do is I create the textures at much higher resolution and then scale it to final size. This allows the scaling algorithm in the graphics package to apply anti aliasing during the scaling process which I think helps make the smaller textures look good since it reduces the appearance of jaggies.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=216211#p216211
|title=<nowiki>Re: key + animation</nowiki>
|author=<nowiki>hvengel</nowiki>
|date=<nowiki>Fri Aug 08</nowiki>
}}
}}
* Use Materials on Objects instead of textures where possible, but...
* ...avoid mixing textured and untextured geometry in the same model. Build the coloring into the texture map instead. This is to prevent that the object gets split, and anyway, the [[File Formats#*.ac files|AC format]] supports only one texture per object.
* Textures must be a power of two, or they will be resized at loading, and cause issues to some users.
* Avoid using big textures: 512x512 is mostly enough for most models.
* Use a single texture. However, if your model absolutely needs alpha texture and another part of the model is opaque, you should use two textures: one with alpha and the other without.
* Don't use alpha in texture when it is not needed: transparency is not easy to deal with, and often causes artifacts.

=== Effects ===
* Shader effects (like lightmaps, normalmaps...) and Rembrandt lights are not affordable by everyone's machine, so try to provide alternatives. However, remember also that FlightGear provides options to adjust such effects.

=== Level of Detail (LOD) ===
{{note|Note that range animations often used for LOD are very expensive (any time you move, every range animation must be evaluated), and give a real advantage only if they remove a very large amount of details (like 1000-2000 triangles), so it's not useful in many cases of for example scenery objects or cockpit details.}}
{{tip|Instead of using range animations for each little detail you could group many details together and do the range animation for them all, for example having one range animation for an entire cockpit instead of several dozens.}}
* If a model has to be detailed to a ''very high'' degree, use multiple objects with different levels of detailing, and switch between them based on LOD with a [[Howto:Animate models#Range|range animation]], or split the detailed parts to make them a couple more objects that add details incrementally.
* An alternative, less expensive way to support LOD is applying a [[Howto:Animate models#Select|select animation]], that can hide an object based on some property, for example hiding a cars side mirrors if "detailed" level is at less than 1500m (which is the default), indicating that the user has a less powerful machine. It is less flexible, but allows everyone to enjoy your models.

=== Other ===
* With modern graphics cards, the amount of objects can have a higher impact on performance than the amount of triangles/vertices.
* Textures, transparency, .xml included sub-models: The things that kill frame rate in FlightGear. Try to avoid them.
* Also avoid smooth shading when possible, but don't be afraid to use it for curved surfaces where it really has an impact on model quality.

== Related content ==
=== Wiki articles ===
==== Problems and Solutions ====
* [[3D Model Rotates Around Nose]]
* [[Howto: Configure views in FlightGear]]
* [[Howto: Decrease the number of faces|Decrease the number of faces]]

==== Resources ====
* [[Aircraft Information Resources‎]]
* [[Modeling Resources]]

{{3d}}

[[Category:Modeling]]

Howto talk:Work with AC3D files in Blender

2020-07-17T18:18:43Z

Sfrsfr:

Blender 2.83 LTS is declared to not be supported. What is the issue? I'm using Blender 2.90 successfully.

: Correct, i just retried AC3D import with 2.83.2 LTS and indeed it works. Must have been a mistake on my side when setting everything up.
: I've just corrected the page.

Howto:Work with AC3D files in Blender

2020-07-17T18:16:05Z

Sfrsfr: Removed incorrect statement about 2.83 LTS

Many [[FlightGear]] [[aircraft]] modelers prefer [[Blender]] as their 3D-modelling editor. FlightGear primarily uses the [[AC3D]] file format (<code>.ac</code>) to model aircraft, [[scenery]] models, and many other things. For recent versions of Blender import/export support for the AC3D file format is implemented as an addon. This page gives a few more details about this addon.

{{TOC limit|3}}

== Blender versions 2.80 and later ==
=== Majic79 addon ===
Current maintainer: [[User:Necolatis]]

Tested with Blender version 2.63 to 2.78a

For more information you can follow the topic {{forum link|t=13442|title=Blender 2.6 AC3D Importer & Exporter}}.

: {{github source|user=NikolaiVChr|repo=Blender-AC3D|branch=2.80|text=Download Link (GitHub)}}. Probably: [[User:Necolatis]] due to lack of credits unsure.
: {{github source|proj=NikolaiVChr|repo=Blender-AC3D|text=Repository}} ({{github zip file|NikolaiVChr|Blender-AC3D|text=ZIP file download for Blender <= 2.79}}).

Notice that the above link is to Necolatis (Nikolai) latest version, as the Majic79 GitHub has not kept up with the updates and seems dead.

=== Notes ===
* Before you export a model with this addon, make sure that you set the UV map and texture inside the material, not just inside the UV editor. See the video tutorial [https://www.youtube.com/watch?v=URMjoFSm5pk here].
* Before you export make sure to exit ''Edit Mode'' or some of your last changes won't be exported.
* Inside Blender when you want to see the textures, be sure to set the shader to GLSL (or for 2.7+ just set view mode to materials). Alternatively set textured solid in solid view.
* To see textured surfaces as they will be shown in FlightGear, go into the material texture and set the blend type to ''Multiply'' instead of the default ''Mix'' (the importer will also do this automatically). An example plane that will look very different if this is not done is the FGAddon aircraft {{fgaddon source|path=Aircraft/ASK13|commit=1363|text=ASK-13}}, notice the wingtips.
* If you wonder where to put the scripts you could open blender's user preferences ({{Key press|Ctrl|Alt|U}}, or ''File > User Preferences'') tick for example Import/Export and extent the information concerning an existing script. Usually this throws the path. For for example Ubuntu 14.04LTS/Blender 2.79b it is: <code>/usr/share/blender/scripts/addons/</code>.
* Be aware that Blender only has greyscale for emission and ambient colors. If you want to export/import a color for those, import/export options gives you capability to choose to use Blenders mirror color for that.
* The importer will not fail if it does not locate a texture, instead it will issue warnings. Pull down the top bar to see if there was any, they will be orange lines.
* The exporter will not fail if it tries to save a texture without data, instead it will issue warnings. Pull down the top bar to see if there was any, they will be orange lines. Notice that since AC3D only support 1 texture per object, if multiple textures are attached to an object in Blender the last of the textures that has any data, if any, will be the one that get exported, but it will still warn about the missing data in the others, so take care.
* Orientation: The default settings in the plugin correspond to the FlightGear coordinate system (-X forward and Z up, also see: [[Howto:3D_Aircraft_Models]]). The default settings are: Forward -Z and Up Y.

You can report bugs with the addon [https://github.com/NikolaiVChr/Blender-AC3D/issues here], but please include problematic <code>.ac</code>/<code>.blend</code> files and their textures.

=== Linux (kubuntu 19.10, DeBIAN 10 "buster") ===
: Use: <code>download.zip</code> (or really make sure to grep the right tree (see above!))

# Unpack <code>.zip</code> file.
# Read <code>README.MD</code>.
# Install for example into <code>/home/<User>/...</code>. Do '''not''' install into <code>/usr/...</code> since you will be lacking writing rights.
# Copy <code>io_scene_ac3d</code> into <code>blender-<version>-<OS architecture>/<version>/scripts/addons</code> (for example <code>blender-2.82a-linux64/2.82/scripts/addons</code>)
# Installation via Edit > Preferences > Addons > Install and select: <code>__init__.py</code>

== Blender versions 2.63 and later ==
For version 2.63 and later you have a choice of several scripts.

=== Mr. No addon ===
==== Notes ====
* When exporting with this addon, make sure you set the texture inside the UV editor.
* When using this script, it is very important that everything is textured. The addon will silently fail if this is not the case.
* This script does not work reliable when nested groups are being used in the imported AC3D model (for example {{github source|user=NikolaiVChr|repo=flightgear-saab-ja-37-viggen|tag=FG-v3.4|path=Aircraft/JA37/Models/Instruments/Altimeter2/altimeter-metric.ac|text=here}}).
* The importer cannot handle the token <code>subdiv</code>, its just ignored.
* The exporter does not always export the rotations/location matrix of objects correctly.

: [http://www.mediafire.com/?m4f9m95qj9e5qq0 Download link (MediaFire)]

=== FG2blender (PAF Team) ===
Authors: f-jjth, run

The PAF team (Patrouille de France), a French group of FlightGear enthusiasts have also made an AC3D Blender script. Their last commit dates back to 11 December 2013 and it feels like their FG2Blender project is abandoned. The PAF team is essentially active on their [http://equipe-flightgear.forumactif.com/ own French speaking forum]. There is no trace or documentation available, so the notes below are speculative and incomplete. It would be interesting to test these scripts and check if the work of the PAF team can be merged with the work of [[User:Necolatis]] as this is actually the only AC3D script that is still maintained.

==== Notes ====
* According to the source code, the script seems to be able to export animation.

{{sourceforge source|proj=pafteam|repo=fg2blender|text=Repository}} ([https://sourceforge.net/p/pafteam/fg2blender/ci/master/tarball Zip file download]{{dead link|2020-07}})

== Blender versions 2.5 to 2.62 ==
For these versions you can use one of these scripts by Majic79:

* {{github source|proj=majic79|repo=Blender-AC3D|branch=BL2.59|text=Version for Blender 2.59 (repository)}} ({{github zip file|majic79|Blender-AC3D|branch=BL2.59|text=ZIP file download}}).
* {{github source|proj=majic79|repo=Blender-AC3D|branch=BL2.60|text=Version for Blender 2.60 (repository)}} ({{github zip file|majic79|Blender-AC3D|branch=BL2.60|text=ZIP file download}}).
* {{github source|proj=majic79|repo=Blender-AC3D|branch=BL2.62|text=Version for Blender 2.62 (repository)}} ({{github zip file|majic79|Blender-AC3D|branch=BL2.62|text=ZIP file download}}).

== Blender versions 2.4 and older ==
For these versions, Blender supports both the import and export of AC3D files out of the box. Just go into user preferences and enable the addon scripts.

== External links ==
* {{cite web
| url = http://www.inivis.com/ac3d/man/ac3dfileformat.html
| title = The AC3D file format
| date = 27 March 2003
| publisher = Inivis Limited
| archiveurl = https://web.archive.org/web/20180814212703/http://www.inivis.com/ac3d/man/ac3dfileformat.html
| archivedate = 14 Aug 2018
| accessdate = 17 Jul 2020
}}

{{3d}}

[[Category:Modeling]]

Modeling - Getting Started

2020-07-17T11:55:44Z

Sfrsfr: Blender: added note about 'Backface Culling' / Inverted Normals

== Notice for Volunteers ==
{{main article|Volunteer#Scenery Model Creators}}
* We need people to go out and take good pictures of all the buildings at their local airports, build models, and create textures (that could be different people for each task).
* We need people to start modelling identifiable human-made landmarks like bridges, stadiums, and major buildings. Around the San Francisco Bay area, bridges are especially important. Once you have identified some buildings or objects you would like to have (Aircraft carriers, fuel bowsers, cars, towers, ...) you will need to check out the tools for creating and placing these objects.

== Getting Started ==

Generally one can start with a blueprint using their favorite imaging software like Gimp, Photoshop, or Paint shop pro then separate various views (front, back, etc...) into greyscale jpg files. Then import them as a background for easy modelling in your favorite 3D modelling software program.

=== 3D Software ===
To begin, you will need to create models in a 3d modeling appliction. Three popular ones are AC3D, Blender and SketchUp. FlightGear can display models in several formats, any format supported by [[PLIB]] is acceptable. AC3D is the most popular format for including scenery in Flightgear. Most or all of the default scenery bundled with a Flightgear release are in AC3D format.

If you do not have AC3D, Blender offers many import and export tools. See the Blender website for further information.

==== [[AC3D]] ====
Flightgear uses the ac3d model format for objects such as buildings. To create a model, you will need one of two modelling packages. Either go directly to [http://www.ac3d.org AC3D] itself, or use [http://www.blender.org Blender] and then convert via a Python script (see below). AC3D seems to be a much easier program to learn, while still being very powerful. The downside is that you have to buy a licence to get more than 14 days use.

* [http://wine.techlab.info/AC3D_Tutorials/ AC3D Modeling Tutorials]

==== [[Blender]] ====
[http://www.blender.org Blender] is more difficult to learn to use, since it is not quite as intuitive and is far more powerful. However it is GPL'd, and there are lots of tutorials to help with learning.

* [http://wiki.blender.org Blender Manual]
* [http://blenderartists.org/forum/ Excellent forum for discussing Blender issues]

Note: Before you start modelling its recommended to activate the 'Backface Culling' option (Viewport Shading -> Options). This will allow you to spot faces with inverted Normals. In FlightGear these faces will be invisible. To check your model for this issue switch Viewport Shading to Solid. Now you will be able to spot the affected faces. To correct them, mark all affected Faces. Then go to Mesh -> Normals and click 'Flip'.

==== SketchUp ====
{{Main article|Modeling - SketchUp}}

SketchUp (http://sketchup.google.com) is the easiest to use of these three programs. But the results are very nice and professional. I recommend SketchUp for users who are not really good at difficult computer programs.

==== [[Wings 3D]] ====
{{Main article|Modeling - Wings 3D}}

Wings 3D (http://www.wings3d.com/) is another 3D modeling program, and is free open source software.

=== Placing Objects on Scenery ===
There are several ways of doing this. The most direct way is to simply [[Adding shared models manually|add the required data by hand]].

[[File:Placing objects with UFO html 439816e9.jpg|thumb|270px|The model adjustment dialog of the [[UFO]]]]
The easiest way is to use the [[Placing 3D Objects with the UFO|UFO's object placement feature]] (in version 9.10 or higher). When operating the UFO, left-clicking the mouse anywhere on the ground will place an object, and pressing space-up or down will cycle through the models. Coordinates of placed models can then be dumped to the terminal or written to a configuration file.

[[Talk:Modeling_-_Getting_Started|Obsolete project?]] Another method is to use [[FlightGear Scenery Designer]] ([http://fgsd.sourceforge.net/ Project Site]). After setting the paths to your scenery data, simply load up the area where you want to place the object. Load your .ac format model, and right click on the desired spot to place your model there. Export the modifed scenery to save it, rerun Flightgear and your model should be there.

=== Finding, Creating, or Using Textures ===
Models in Flightgear use textures with PNG format.

Most image editors support editing PNG files, like [[THE GIMP]], Corel Paintshop Pro, Adobe Photoshop, etc.

The old SGI rgb format (.rgb extension) is no longer supported. (see http://scenemodels.flightgear.org/)

Once you have made your model building, you will want to apply some textures to it, so it looks as realistic as possible. This is possibly one of the hardest areas, as a good model with bad textures will still look bad. Since Flightgear and the scenery data are all released under the GPL, any textures that you use must also be able to be released under this license. This will probably prevent you from just using anything you come across on the net, unless it is already under the GPL. It is quite common for people to state that their pictures or textures are free. Since Flightgear can be sold for profit, and is released on Linux distributions that are sold, check that there are no clauses stating that the item can not be sold or used for commercial use.

=== Generation of textured light objects in Blender ===

{| style="margin-top:0.1em; margin-bottom:0.1em; margin-left:2em; padding:2px; font-size:95%; text-align:left; background: transparent;"
|-
| [[File:1rightarrow.png|15px]] ''See http://members.aon.at/mfranz/flightgear/blender-textured-lights.html for the main article about this subject.''
|}

== Improving models for best FlightGear performance ==
{{Merge|Modelling guidelines}}
[[File:Motor.jpg|thumb|270px|Using Multiple Models with varied detailing]]
[[File:Singlesided_blender.jpg|thumb|270px|To set faces to Singlesided (Blender), deselect the Doublesided button]]
=== Mesh ===
* In a single model, use a single mesh so far as possible. Note that this doesn't mean that every node must be linked to its object with an edge (e.g. a line of trees can be easily a single object.) Only have the separate objects if you need them for an animation or parts that use a transparent texture (any object using more then one texture is anyway spitted by the rendering engine.)
* Delete unseen faces such as faces inside the model, but remember that the [[Project Rembrandt|Rembrandt renderer]] needs closed meshes to cast shadows correctly, so you'll often want to keep the ones below.
* Remove "line faces", which are faces whose points are in the same line.
* Don't forget to remove double vertices (i.e. vertices sharing the same coordinates)
* See [[Howto:Decrease the number of faces]].

=== Single sided / double sided ===
* Set all the faces of the model to SingleSided. DoubleSided faces are very expensive to render properly. If a face needs to be displayed from every view angle use two faces with opposite normals rather than a Doublesided one (the overhead from the extra geometry is far lower than the overhead of doublesided faces)

=== Textures and Materials ===
{{FGCquote
|Modern graphics cards can handle very large textures and huge numbers of vertices with minimal frame rate impact. A typical scene in FlightGear (with clouds, buildings rivers, roads...) has millions of vertices which simply dwarfs a 17K aircraft making the aircraft model an insignificant factor. The general rule is use enough vertices and large enough textures to make things look right and no more. More recent aircraft efforts tend to have much higher vertex counts, much larger textures and a lot more detail then older work because of how capable modern hardware is. It is not unusual to see newer aircraft exceeding 100K vertices. For example the P-51D that will be released with 3.2 has an external model that is slightly over 100K vertices and this had a minimal frame rate impact on my (newer high end) hardware compared to the old 10K external model. <br/>
<br/>
If you can't see the difference between using a 512x512 instrument texture compared to a 256x256 texture then use the smaller texture. But if you can see the difference then use the larger texture. On modern hardware the difference in frame rate will be very small but it may impact those with older/slower/obsolete hardware in a noticeable way. All of the instruments in the P-51D are 512x512 for larger gauges or 256x256 for smaller gauges and at least to me they have a sharp appearance even when zoomed in fairly close. Many older aircraft use 128x128 textures for instruments but to me at least on the larger instruments on a very high resolution monitor these textures are a little bit fuzzy in appearance. The other thing I do is I create the textures at much higher resolution and then scale it to final size. This allows the scaling algorithm in the graphics package to apply anti aliasing during the scaling process which I think helps make the smaller textures look good since it reduces the appearance of jaggies.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=216211#p216211
|title=<nowiki>Re: key + animation</nowiki>
|author=<nowiki>hvengel</nowiki>
|date=<nowiki>Fri Aug 08</nowiki>
}}
}}
* Use Materials on Objects instead of textures where possible, but...
* ...avoid mixing textured and untextured geometry in the same model. Build the coloring into the texture map instead. This is to prevent that the object gets split, and anyway, the [[File Formats#*.ac files|AC format]] supports only one texture per object.
* Textures must be a power of two, or they will be resized at loading, and cause issues to some users.
* Avoid using big textures: 512x512 is mostly enough for most models.
* Use a single texture. However, if your model absolutely needs alpha texture and another part of the model is opaque, you should use two textures: one with alpha and the other without.
* Don't use alpha in texture when it is not needed: transparency is not easy to deal with, and often causes artifacts.

=== Effects ===
* Shader effects (like lightmaps, normalmaps...) and Rembrandt lights are not affordable by everyone's machine, so try to provide alternatives. However, remember also that FlightGear provides options to adjust such effects.

=== Level of Detail (LOD) ===
{{note|Note that range animations often used for LOD are very expensive (any time you move, every range animation must be evaluated), and give a real advantage only if they remove a very large amount of details (like 1000-2000 triangles), so it's not useful in many cases of for example scenery objects or cockpit details.}}
{{tip|Instead of using range animations for each little detail you could group many details together and do the range animation for them all, for example having one range animation for an entire cockpit instead of several dozens.}}
* If a model has to be detailed to a ''very high'' degree, use multiple objects with different levels of detailing, and switch between them based on LOD with a [[Howto:Animate models#Range|range animation]], or split the detailed parts to make them a couple more objects that add details incrementally.
* An alternative, less expensive way to support LOD is applying a [[Howto:Animate models#Select|select animation]], that can hide an object based on some property, for example hiding a cars side mirrors if "detailed" level is at less than 1500m (which is the default), indicating that the user has a less powerful machine. It is less flexible, but allows everyone to enjoy your models.

=== Other ===
* With modern graphics cards, the amount of objects can have a higher impact on performance than the amount of triangles/vertices.
* Textures, transparency, .xml included sub-models: The things that kill frame rate in FlightGear. Try to avoid them.
* Also avoid smooth shading when possible, but don't be afraid to use it for curved surfaces where it really has an impact on model quality.

== Related content ==
=== Wiki articles ===
==== Problems and Solutions ====
* [[3D Model Rotates Around Nose]]
* [[Howto: Configure views in FlightGear]]
* [[Howto: Decrease the number of faces|Decrease the number of faces]]

==== Resources ====
* [[Aircraft Information Resources‎]]
* [[Modeling Resources]]

{{3d}}

[[Category:Modeling]]

Howto:Work with AC3D files in Blender

2020-07-15T18:24:49Z

Sfrsfr: Reordered list of supported versions of Blender with the newest on top. Reworded the first paragraph, minor edits.

Many [[FlightGear]] [[aircraft]] modelers prefer [[Blender]] as their 3D-modelling editor. FlightGear primarily uses the [[AC3D]] file format (<code>.ac</code>) to model aircraft, [[scenery]] models, and many other things. For recent versions of Blender import/export support for the AC3D file format is implemented as an addon. This page gives a few more details about this addon.

== Blender version 2.83 LTS ==

Currently not supported, use version 2.80 or older instead.

== Blender versions 2.80 (probably up to 2.82a) ==

=== Majic79 addon ===

Current maintainer: [[User:Necolatis]]

Tested with Blender version 2.63 to 2.78a

You can follow the [http://forum.flightgear.org/viewtopic.php?f=18&t=13442 Forum thread] for more information.

: [https://github.com/NikolaiVChr/Blender-AC3D/tree/2.80 Download Link (GitHub)] ''probably: [[User:Necolatis]]'' due to lack of credits unsure.
: {{github source|proj=NikolaiVChr|repo=Blender-AC3D|text=Repository}} ({{github zip file|NikolaiVChr|Blender-AC3D|text=ZIP file download for Blender <= 2.79}}).

Notice that the above link is to Necolatis (Nikolai) latest version, as the Majic79 github hasn't kept up with the updates and seems dead.

'''Notes:'''
* Before you export a model with this addon, make sure that you set the UV map and texture inside the material, not just inside the UV editor. See the video tutorial [https://www.youtube.com/watch?v=URMjoFSm5pk here].
* Before you export make sure to exit Edit Mode or some of your last changes won't be exported.
* Inside Blender when you want to see the textures, be sure to set the shader to GLSL (or for 2.7+ just set view mode to materials). Alternatively set textured solid in solid view.
* To see textured surfaces as they will be shown in Flightgear, go into the material texture and set the blend type to "Multiply" instead of the default "Mix" (the importer will also do this automatically). An example plane that will look very different if this is not done is the FGAddon aircraft ASK-13, notice the wingtips.
* If you wonder where to put the scripts you could open blender's user preferences (''CTRL ALT U'', or ''File->User Preferences'') tick e.g. Import/Export and extent the informations concerning an existing script. Usually this throws the path. For Ubuntu 14.04LTS/Blender 2.79b e.g. it's: ''/usr/share/blender/scripts/addons/''.
* Be aware that Blender only has greyscale for emission and ambient colors. If you want to export/import a color for those, import/export options gives you capability to choose to use Blenders mirror color for that.
* The importer will not fail if it does not locate a texture, instead it will issue warnings. Pull down the top bar to see if there was any, they will be orange lines.
* The exporter will not fail if it tries to save a texture without data, instead it will issue warnings. Pull down the top bar to see if there was any, they will be orange lines. Notice that since AC3D only support 1 texture per object, if multiple textures are attached to an object in Blender the last of the textures that has any data, if any, will be the one that get exported, but it will still warn about the missing data in the others, so take care.
* Orientation: The default settings in the plugin correspond to the FlightGear coordinate system (-X forward and Z up, also see: [[Howto:3D_Aircraft_Models]]). The default settings are: Forward -Z and Up Y.

You can report bugs with the addon [https://github.com/NikolaiVChr/Blender-AC3D/issues here], but please include problematic .ac/.blend files and their textures.

=== Linux (kubuntu 19.10, DeBIAN 10 "buster") ===

: Use: ''download.zip'' (or really make sure to grep the right tree (see above!))
: unpack .zip
* read README.MD
* do NOT install into ''/usr/''... since you will be lacking writing rights (I installed below my ''/home/(USER)/...'')
* copy ''io_scene_ac3d'' into: ''blender-(VERSION)-(OS_ARCHITECTURE)/(VERSION)/scripts/addons'' (for me e.g. ''blender-2.82a-linux64/2.82/scripts/addons'')
* Installation via Edit->Preferences->Addons->Install select:''__init__.py''

== Blender versions 2.63 and later ==
For version 2.63 onwards you have a choice of several scripts.

=== Mr. No addon ===
'''Notes:'''
* When exporting with this addon, make sure you set the texture inside the UV editor.
* When using this script, it is very important that everything is textured. The addon will silently fail if this is not the case.
* This script does not work reliable when nested groups are being used in the imported AC3D model (example [https://github.com/NikolaiVChr/flightgear-saab-ja-37-viggen/blob/FG-v3.4/Aircraft/JA37/Models/Instruments/Altimeter2/altimeter-metric.ac here]).
* The importer cannot handle the token 'subdiv', its just ignored.
* The exporter does not always export the rotations/location matrix of objects correctly.

: [http://www.mediafire.com/?m4f9m95qj9e5qq0 Download link (MediaFire)]

=== FG2blender (PAF Team) ===

Authors: f-jjth, run

The PAF team (Patrouille de France), a French group of FlightGear enthusiasts have also made an AC3D Blender script. Their last commit dates back to 11 December 2013 and it feels like their FG2Blender project is abandoned. The PAF team is essentially active on their [http://equipe-flightgear.forumactif.com/ own French speaking forum]. There's no trace or documentation available, so the notes below are speculative and incomplete. It would be interesting to test these scripts and check if the work of the PAF team can be merged with the work of [[User:Necolatis]] as this is actually the only AC3D script that is still maintained.

'''Notes:'''

* According to the source code, the script seems to be able to export animation.

[https://sourceforge.net/p/pafteam/fg2blender/ci/master/tree/ Repository] ([https://sourceforge.net/p/pafteam/fg2blender/ci/master/tarball Zip file download])

== Blender versions 2.5 to 2.62 ==
For these versions you can use one of these scripts by Majic79:

* {{github source|proj=majic79|repo=Blender-AC3D|branch=BL2.59|text=Version for Blender 2.59 (repository)}} ({{github zip file|majic79|Blender-AC3D|branch=BL2.59|text=ZIP file download}}).
* {{github source|proj=majic79|repo=Blender-AC3D|branch=BL2.60|text=Version for Blender 2.60 (repository)}} ({{github zip file|majic79|Blender-AC3D|branch=BL2.60|text=ZIP file download}}).
* {{github source|proj=majic79|repo=Blender-AC3D|branch=BL2.62|text=Version for Blender 2.62 (repository)}} ({{github zip file|majic79|Blender-AC3D|branch=BL2.62|text=ZIP file download}}).

== Blender versions 2.4 and older ==
For these versions, Blender supports both the import and export of AC3D files out of the box. Just go into user preferences and enable the addon scripts.

== External links ==
[https://sites.google.com/view/ac3dfileformat/home AC3D file format]

{{3d}}

[[Category:Modeling]]