This is an old revision of the document!
revision: April 2015
This file contains the configuration for the FIR and sets the public release date.
The config.fir
file is located in the fir/
directory.
Element | Attribute | Format | Comment |
---|---|---|---|
fir | FIR definition | ||
id | string | FIR identification - must be unique ICAO 4 letter designator | |
name | string | FIR name | |
country | string | country ISO code (2 letter code) | |
date | integer | date defined as YYYYMMDD, AIRAC cycle date at which this FIRDEF will be released | |
revision | integer | revision number (00-99), allows for intraday or intra AIRAC cycle updates |
Note: As the revision date is read before the revision number, unless multiple revisions are required on the same day the revision number should always be 1
The origin point is the coordinate of the centerpoint of all the maps. Internally all latitude and longitude coordinates are transferred to a cartesian X/Y format in nautical mile. If you use X/Y values instead of lat/lon in a map definition, this is the origin point for these X/Y coordinates.
The <origin> element requires 1 <point> element.
Parent | Element | Attribute | Format | Comment |
---|---|---|---|---|
origin | origin element, only one instance allowed, contains one point element | |||
point | lat | WGS84 | origin point latitude | |
lon | WGS84 | origin point longitude |
This element describes the way tracks are correlated with a specific flight plan.
The classic method uses a discrete Mode A code (a.s.a. Squawk Code) to link a track to a flight plan.
Non discrete codes are Mode A codes ending with two zeroes (1000 7000 2000 1200 …) and cannot be used to correlate a flight plan.
Modern systems use the Aircraft Identification (BDS20) received from the onboard Mode S transponder. Currently only certain ANSP's 1) (Air Navigation Service Providers) use Mode S correlation enabling them to assign the non-discrete Mode A code 1000 to certain tracks which are fully Mode S transponder equipped. This also requires full Mode S radar coverage.
Element | Attribute | Format | Comment |
---|---|---|---|
trackcorrelation | Track Correlation method to use | ||
method | string | ||
A | use discrete Mode A code only | ||
S | use Mode S Aircraft Identification if transponder is Mode S, else use Mode A code |
Default preset to load if not specified in atc.xml
Element | Attribute | Format | Comment |
---|---|---|---|
preset | default | string | name of default preset |
Default SDD theme to load if not specified in atc.xml
Element | Attribute | Format | Comment |
---|---|---|---|
theme | default | string | name of default theme |
Set if RVSM is used in this FIR.
Element | Attribute | Format | Comment |
---|---|---|---|
rvsm | enabled | string | true or false |
Set the default range used for observer or staff connections
Element | Attribute | Format | Comment |
---|---|---|---|
range | default | string | 1 - 2500 |
Example of a config.fir file:
<fir id="EBBU" name="Brussels FIR" country="BE" date="20150402" revision="01"> <!-- system center point - will be used as X=0 Y=0 in Cartesian system --> <origin> <point lat="N05053491100" lon="E00429086400"/> </origin> <!-- track correlation method to use --> <trackcorrelation method="S" /> <!-- RVSM airspace --> <rvsm enabled="true" /> <!-- default preset --> <preset default="default" /> <!-- default theme --> <theme default="canac2" /> <!-- default label --> <label default="canac2" /> <!-- default range (OBS) --> <label default="250" /> </fir>