atc.xml

A position is an individual controller connected to IVAO. Theoretically a position will be able to activate a number of sectors simultaneously which will be individually visible online.

The atc.xml file is located in the fir directory

XML structure

Fields may be added in future

Elementatc
ValueFormatDescription
id string ATC position id
long string long position ID. Used in lists etc. to identify other ATC positions. Should be unique.
short string short position ID. Used in label to identify current/next sector
freq frequency Frequency of the position (for legacy support)
avbl true/false ATC position available for login (boolean: true/false)
callsign string radio callsign of the ATC position
name string Display name used in the launcher, (defaults to callsign if not present)
label string label definition to be used for this specific ATC position (default=“default”)
theme string SDD theme for this specific ATC position (default=“default”)
preset string map preset to load when position is loaded
atis string DEPARTURE (for departure ATIS), ARRIVAL (for arrival ATIS), BOTH (default value, combined departure and arrival ATIS), MINIMAL (no actual ATIS, callsign and voice server only (for ACC sectors etc.)
lat The latitude of the radar position/radio antenna location
lon The longitude of the radar position/radio antenna location
range int The radar/radio range of the position (in NM)
magvar int The magnetic variation specific to this ATC position. If specified, it will over-ride any value provided in the confg.fir file. This setting is deprecated in favour of applying magvar in a preset definition.

The avbl attribute indicates if the ATC position is available for login in this FIR. Positions which are not available (false) are used to define position identifications for foreign/neighbouring ATC positions.

Positions which control airspace (everything except GND/DEL) need to be assigned one or more sectors, in the open <atc> tag.

Elementsector
ValueFormatDescription
id string sector ID
active true/false whether or not this sector is visible as active
fir string the FIR ID in the sectors definition

Example

<atc
id="EKDK_A_CTR" long="EKDKA" short="A" freq="121.375"
lat="N0550000" lon="E0110000" range="150" avbl="true"
callsign="Copenhagen Control" label="acc" theme="coopans" preset="dka"
name="Copenhagen Sector A" atis="MINIMAL"
>
 
  <sector id="DKA" active="true" fir="EKDK" />
 
</atc>
 
<atc id="EKKA_TWR" long="EKKATWR" short="KT" freq="119.575"
lat="N0561750850" lon="E0090728660" range="100" avbl="true"
label="app" theme="coopans" callsign="Karup Tower" preset="ekka" name="Karup TWR"
>
 
  <sector id="KT" active="true" fir="EKDK" />
 
</atc>
<atc id="EKCH_GND" long="APNARR" short="APNA" freq="121.625"
lat="N0553704500" lon="E0123921500" range="15" avbl="true"
label="app" theme="coopans" callsign="Kastrup Apron" preset="ekch_apn"
name="Kastrup Apron (main/arrival)"
>
 
  <sector id="APNA" active="true" fir="EKDK" />
 
</atc>
<atc id="ESMM_CTR"    long="ESMM"    short="MM" avbl="false" callsign="Sweden Control"/>
<atc id="ESMM_K_CTR"  long="ESMM-K"  short="MM" avbl="false" callsign="Sweden Control"/>
<atc id="ESMM_L_CTR"  long="ESMM-L"  short="MM" avbl="false" callsign="Sweden Control"/>

Back