This document presents the sector file definition of the IVAO ATC client.
Definition: Most GPS devices provide geographic coordinates in the Degrees, Minutes and Seconds (DMS) format, or more commonly the Decimal Degrees (DD) format.
You can use the following formats:
∗ DMS with 14 characters: use geographic coordinates, pad with zeros, Latitude and Longitude separated by semicolon ( ; ), and finish the row with a semicolon ( ; )
∗ Example = N038.10.04.627;E024.33.34.904;∗ DMS without separation with 11 characters: use geographic coordinates, Latitude and Longitude separated by semicolon ( ; ), and finish the row with a semicolon ( ; )
∗ Example = N0381004627;E0243334904;∗ Decimal: with maximum 13 characters. North and East are positive but South and West are negative and require a minus (-) to prefix the coordinate, Latitude and Longitude separated by semicolon ( ; ), and finish the row with a semicolon ( ; )
∗ Example = 38.02235785;24.12223578;∗ Reference point: use a FIX, VOR or NDB identifier as reference for its Latitude and Longitude, separated by semicolon ( ; ), and finish the row with a semicolon ( ; )
∗ Example = NAME;NAME;
Following formatting will give unpredictable, usually truncated results. Please do not use them.
-abbreviated DMS coordinates with delimiter such as S040, N038.10 or E024.33.34
-abbreviated DMS coordinates without delimiter such as S040, N03810, or E0243334
In addition to the above format, you may use a mix of the different formats like:
A mix between DMS and Reference (ID) format is ALLOWED.
N038.10.04.627;AMB;
AMB;E024.33.34.904;
A mix between Decimal and Reference (ID) format is ALLOWED.
38.02235785;AMB;
AMB;24.12223578;
A mix of DMS and Decimal format, in one line, is NOT ALLOWED, and it will return an error.
N038.10.04.627;24.12223578;
38.02235785;E024.33.34.904;
Colors can be defined in two ways via hex code or RGB codes. Preferably use hex code colors for better future proof compatibility.
From Version 1.4.1.x onwards ALPHABLEND was added; thus, allowing to modify the opacity of polygons.
Therefore, colors can also be defined as AARRGGBB
, where AA
is the opacity value, and RRGGBB
still is HEX code colors. Colors on Aurora GEO drawings are 32 bits.
Keep in mind that colors defined as
RRGGBB
before version 1.4.1.x will also work on later versions and the opacity value will be set to %100 (FF
)
AARRGGBB
code definition example:
#08466717
Opacity modified polygons will ONLY work if the user has ACTIVATED the Smooth Drawing option (PVD OTHER Smooth Drawing).
Therefore, colors can also be defined as AARRGGBB
, where AA
is the transparency value, and RRGGBB
still is HEX code colors.
Hex code definition example:
#18b76c
RGB code definition example:
24,183,108
We highly recommend you to build Sector Definition with separated files, in order to ensure a proper management and organization of the data.
The first step is to create a folder inside the “include” sub-folder, located inside the main “SectorFile” folder. The name of this new folder must be related to the sector file. The final route shall be something like “/Aurora/SectorFiles/include/new-folder”
Then, you must declare this new folder, at LINE 6 of [INFO] section (see INFO).
For these files to be used as part of the Sector Definition, you need to “declare” it, inside the corresponding section. For this, you start the line with “F;” followed by the file name.
For example:
[ARTCC]
F;ICAO.xxx
F;ICAO.yyy
IMPORTANT NOTE: Below is a list of AUTOMATICALLY loaded files. This means that, if you create a separate file named “ICAO.sid”, where ICAO match an ICAO declared in the .apt file under [AIRPORTS] section, the file will be loaded in Sector Definition, without the need to declare it under the [SID] section.
∗ ICAO.gts = Gates or Parking Stands
∗ ICAO.txi = Taxi Labels
∗ ICAO.sid = SID’s
∗ ICAO.str = STAR’s
∗ ICAO.vfi = VFR Fixes
∗ ICAO.vrt = VFR Routes
∗ ICAO.mva = MRVA Areas
∗ ICAO.tfl = Polyline
Rule : No other characters or spaces shall be inserted after the file declaration. Never add a semicolon ";" to finish any row after a file name.
There is a two line format usable which does not contain sector file data:
∗ Empty lines
∗ Comment lines : comments can be inserted by creating a new line starting with a two slash "//" prefix before the text.
Empty lines can be freely used to make the sector file more readable and more clear. You can freely use them as these lines will not be processed by the Client as data.
Only empty rows, or rows starting with two (2) slashes "//" are allowed.
Comments starting with "//" inserted at the end of data line are not recommended since they may be interpreted as data in some sections.
Aurora\SectorFiles\
directory of the user.How to reference other files?
Simply prefix any reference to a file with F;
and the relative path to the file location.
[INFO]
Centerpoint Longtitude
Centerpoint Latitude
Vertical Ratio (latitude)
Horizontal Ratio (longtitude)
Magnetic Variation
Folder;Folder
QDM Variation
[COLORSCHEME]
F;xxxxx.clr
[PROFILE]
F;file;
//ONLY file definition. multiple files are accepted. The structure is the as used on profiles.
// [PROFILE] data will be set when opening sector and atc position profiles will open when using the connection settings selection.
//DO NOT USE THIS TO SHARE ATC POSITIONS. This preferences will override the user settings.
//Remove all lines that will have effect on screens and other prefs. Aurora will then use the users settings.
[DEFINE]
//Label;Color hex code;
Label;#6d6d6d;
[AIRPORT]
F;airports.ap
//or
//ICAO;Elevation;Transition Altitude;Lattiude (DMS);Longitude (DMS);Airport Name;
LTAB;2686;10000;N039.56.05.000;E032.44.26.000;Guvercinlik AB;
[ELEVATION]
F;sector.elev
//or
// Label;Lattiude (DMS);Longitude (DMS);Elevation in ft;Text;
[SYMBOLS]
F;sector_symbols.sym
//No definition needed, just assign the file where your symbol information is.
[RUNWAY]
F;runway.rw
//or
LTAB;06;24;2682;2691;060;240;N039.55.50.940;E032.43.46.050;N039.56.19.100;E032.45.02.790;
ICAO;RW1;RW2;ELEVATION1;ELEVATION2;TRACK1;TRACK2;LAT1;LON1;LAT2;LON2;
[FIXES]
F;fixes.fix
F;Navaids\fixes.fix
//or
ABLON;N038.10.10.000;E023.44.08.000;
ID;LAT;LON;
[NDB]
F;ndb.ndb
F;Navaids\ndb.ndb
//or
ALP;351.000;N040.51.21.000;E025.56.27.100;
ID;FREQ;LAT;LON;
[VOR]
F;vor.vor
F;Navaids\vor.vor
//or
ALX;113.800;N040.51.14.200;E025.57.24.200;
ID;FREQ;LAT;LON;
[HIGH AIRWAY]
F;highairway.awh
F;Airways\highairway.awh
//or
TYPE;ID;LAT:LON;
//TYPES : L = LABEL, T = TRACK
L;A10;N035.55.30.000;E025.20.56.000;
L;B1;N036.44.51.000;E024.31.10.000;
L;B1;N035.55.30.000;E025.20.56.000;
T;A10;N036.44.51.000;E024.31.10.000;
T;A10;N035.55.30.000;E025.20.56.000;
[LOW AIRWAY]
F;lowiarway.awl
F;Airways\lowairway.awl
//or
TYPE;ID;LAT:LON;
//TYPES : L = LABEL, T = TRACK
L;A10;N035.55.30.000;E025.20.56.000;
L;B1;N036.44.51.000;E024.31.10.000;
L;B1;N035.55.30.000;E025.20.56.000;
T;A10;N036.44.51.000;E024.31.10.000;
T;A10;N035.55.30.000;E025.20.56.000;
[ARTCC] or [AIRSPACE]
F;artcc.artcc
F;airspace.airspace
F;Airspace\artcc.artcc
F;Airspace\airspace.airspace
//or
L;ATHINAI_AC;N037.37.00.001;E023.40.30.000;20;
T;N037.37.00.001;E023.40.30.000;
T;N037.51.00.000;E024.18.00.000;
T;N037.58.59.999;E024.52.00.001;
T;IMR;IMR;
T;ID;LAT;LON;
L;ID;LAT;LON;FONTSIZE;
//TYPES : L = LABEL, T = TRACK
[ARTCC HIGH] or [AIRSPACE HIGH]
F;artcch.artcc
F;airspaceh.airspace
F;Airspace\artcch.artcc
F;Airspace\airspaceh.airspace
//or
L;ATHINAI_AC;N037.37.00.001;E023.40.30.000;20;
T;N037.37.00.001;E023.40.30.000;
T;N037.51.00.000;E024.18.00.000;
T;N037.58.59.999;E024.52.00.001;
T;ABACO;ABACO;
T;ID;LAT;LON;
L;ID;LAT;LON;FONTSIZE;
//TYPES : L = LABELT = TRACK
[ARTCC LOW] or [AIRSPACE LOW]
F;artccl.artcc
F;airspacel.airspace
F;Airspace\artccl.artcc
F;Airspace\airspacel.airspace
//or
L;ATHINAI_AC;N037.37.00.001;E023.40.30.000;20;
T;N037.37.00.001;E023.40.30.000;
T;N037.51.00.000;E024.18.00.000;
T;N037.58.59.999;E024.52.00.001;
T;ABACO;ABACO;
T;ID;LAT;LON;
L;ID;LAT;LON;FONTSIZE;
//TYPES : L = LABELT = TRACK
[GEO]
F;prohibited.prohibited
F;restricted.restricted
F;danger.danger
//There's no need to define icao.geo files since they will be loaded automatically if the icao is defined under the [AIRPORTS] section
//or
N036.45.27.014;E031.46.41.995;N036.45.24.980;E031.46.25.021;COAST;
N036.45.24.980;E031.46.25.021;N036.45.23.990;E031.46.12.990;COAST;
LAT1;LON1;LAT2;LON2;COLOR ID;
//STANDART COLOR ID'S : COAST,RUNWAY,TAXIWAY,PARKING,TAXI_CENTER,DANGER,RESTRICT,PROHIBIT,BUILDING,APRON,STOPLINE,PIER
[FILLCOLOR]
//There are 2 types of polygons:
//1. Static = always shown and can be used with icao.tfl or xxx.tfl file.
//2. Dynamic = only shown if ATC is online and should be a .fcl file.
//There's no need to define icao.tfl aurora will detect it automatically, only .fcl and xxx.tfl files must be defined.
F;EDDF_APP.fcl //polygon activates if ATC is online
F;EDDF_TMA.tfl //TMA boundary polygon always active
//ID;FILLCOLOR;STROKE WIDTH;STROKE COLOR;FILLCOLOR CLEAR;(Fillcolor Clear = Optional value 1 = with opacity)
// AREA : LAT;LON;
LGAV_APP LGAV_DEP;#00120000;1;#00120000;1;
N038.09.56.002;E022.43.58.001;
N038.09.56.002;E024.10.58.001;
N038.12.56.002;E024.15.58.000;
N038.36.56.002;E024.22.58.001;
N038.25.45.001;E024.32.19.000;
N038.09.56.002;E024.44.57.998;
N037.59.56.000;E024.51.58.000;
N037.36.56.002;E025.01.58.001;
N037.15.20.002;E025.01.58.001;
N036.59.56.000;E024.03.58.000;
N037.16.55.999;E022.31.58.001;
N037.33.56.002;E022.31.58.001;
//COMMENTS
STATIC;#00404040;1;#00120000;
N037.55.17.581;E023.55.07.096;
N037.56.56.164;E023.56.40.442;
N037.56.55.308;E023.56.41.895;
N037.55.16.719;E023.55.08.545;
[ATC]
F;atc.atc
//or
LTAB_TWR;120.200;
//Position;Freq;Transfer list;Profile to load;ATIS Structure;Block CPDLC (Use 1 to block, 0 for allowing);
LGAV_APP;132.975;LGMD LGGG LGAV LGTT LGEL LGSO LGMG LGMK_APP -LGMD_E_CTR -LGGG_E_CTR;lgav_app.cpr;
//Transfer List:
// - Seperate station ICAO code or full station login seperated by space.
// - To exclude prefix the station with a minus: "-ICAO"
// - Exclude definitions always have to be define last
Second step will be to create the files mentioned in the .isc file, all of them are explained below.
If you would like your sectorfile to look organized and be easy to update, you can use multiple folders and files.
Example:∗ You should only have 1 folder inside the "Include" folder, inside this folder, you can have multiple folders.
∗ Imagine your main folder name in "SubMap" inside this folder, you could have: Airspace, Airway, Other, MVA, Fillcolor... folders.
∗ Each folder would need to be defined in the 6th field on [INFO] seperated by ";" if you want automatically loaded files.
∗ If not, you don't need to add them. Only mention the files in the necessary places, check the example .isc above.
The header of the sector file shall describe the following information lines in order to configure and display your sector file well:
∗ Latitude
∗ Longitude
∗ Vertical ratio
∗ Horizonal ratio
∗ Magnetic Variation
∗ Folder name / Sub-Folder name
∗ QDM VariationThe [INFO] beacon shall be inserted alone in a line followed by all the 7 lines in order.
Line number | Description | Format | Attribute |
---|---|---|---|
Line 1 | Center point Latitude | N/Sddd.mm.ss.sss | REQUIRED |
Line 2 | Center point Longitude | E/Wddd.mm.ss.sss | REQUIRED |
Line 3 | Vertical RATIO (latitude) | 00 | REQUIRED |
Line 4 | Horizontal RATIO (longitude) | 00 | REQUIRED |
Line 5 | Magnetic Variation (magvar) | 0.0 or -0.0 | REQUIRED |
Line 6 | Include folder name (SectorFiles/Include/XXXX) In addition, you can specify sub-folders to organize data, separated by a semicolon ";" |
XXXX;XXXX\SID;XXXX\STAR | OPTIONAL |
Line 7 | QDM Variation | 0.0 or -0.0 | OPTIONAL |
NOTE:
- Magnetic Variation (magvar) will use the East Positive (no sign) or West Negative (add -) format.
- Horizontal Ratio (longitude) = vertical Ratio x cos(center point latitude)
- Center point latitude and longitude only accept the regular N/Sddd.mm.ss.sss and E/Wddd.mm.ss.sss formats
- QDM Variation: In case it is needed, using QDM variation can help to display the magnetic heading on the QDM, while using true headings in the sectorfile (To achieve this, Magnetic Variation should be set to 0 and QDM Variation should be set with the Magnetic Variation previusly mentioned)
Example:
[INFO]
S033.23.39.000
W070.47.37.000
60
51
-1.8
SKED;SKED\Airports;SKED\SID;SKED\STAR
The DEFINE section lists all the available colour definitions:
The [DEFINE] beacon shall be inserted alone in a line before all the data.
Each row shall represent one colour label.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
Colour label | String | Grass | REQUIRED |
Colour number | RGB format | %48:98:0 | REQUIRED |
Note: The colour number can use any accepted format as described above in the colour definition chapter.
Example:
[DEFINE]
GRASS;%48:98:0;
ASPHALT;#FF4455f0;
The following colours strings (case-insensitive) are predefined in the colorscheme options for GEO sections and do not need to be defined:
∗ APRON = Apron and Parking area (APPRON is still accepted but could be dismissed in the future)
∗ BUILDING = Buildings
∗ COAST = Coast lines
∗ DANGER = Danger (D) areas
∗ PIER = Piers
∗ PROHIBIT = Prohibited (P) areas
∗ RESTRICT = Restricted (R) areas
∗ RUNWAY = Runway elements and lines
∗ STOPBAR = Taxiway stop bars (STOPLINE is still accepted but could be dismissed in the future)
∗ TAXI_CENTER = Taxiway center lines
∗ TAXIWAY = Taxiway edge lines
To learn about Sector.atis
files check staff tools for the Job at the following page where you will find the ATIS creator tool, alongside a video tutorial.
The ATC section lists all the available colour definitions:
The [ATC] beacon shall be inserted alone in a line before all the data.
Each row shall represent ATC station.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
ATC Position | IVAO position (ICAO_SFX) ICAO code + underscore char '_' + 3 letter IVAO position suffix |
LGAV_APP | REQUIRED |
ATC Position frequency | Frequency Number 3 digits + decimal separator '.' + 3 digits |
132.975 | REQUIRED |
Transfert List | List of ICAO or IVAO position First Include list (LSGG LGAV) Second Exclude list with '-' sign before the positon (-LGMD_E_CTR -LGGG_E_CTR) |
LGGG LGAV -LGMD_E_CTR -LGGG_E_CTR |
OPTIONAL |
Profile | Associated profile file for this ATC position. ".cpr" file. These preferences will overwrite user settings. | PREFS\LGAL.cpr | OPTIONAL |
Associates ATIS Structure | Associated profile file for this ATC position. ".atis" file. | ATIS\LG.atis | OPTIONAL |
Block CPDLC | Use this field to block the use of CPDLC in a designed ATC position. Use value 1 to block CPDLC |
PREFS\LGAL.cpr | OPTIONAL |
It is recommended to remove unneccesarry lines from the .cpr file, as these settings will overwrite user settings, only include the needed parts in the file.
Transfer List Rules:
∗ All positions must be separated by space.
∗ The first part is the INCLUDE
∗ The second part is the EXCLUDE use '-' before the callsign.
∗ DO NOT use an INCLUDE definition after EXCLUDE definitions! It will not work
Example:
\[ATC\]
LGAV\_APP;132.975;LGMD LGGG LGAV LGTT LGEL LGSO LGMG LGMK\_APP -LGMD\_E\_CTR -LGGG\_E\_CTR;ATIS\LG.atis;1;
NOTE: You have to define this file under [ATC] in your .isc file. If you have a file named ICAO.atc, where the ICAO matches an airport declared in the [AIRPORTS] section, it will NOT be automatically loaded in the SectorFile.
The AIRPORT section lists all the available airfields including small ones up to large ones.
The [AIRPORT] beacon shall be inserted alone in a line before all the data.
Each row shall describe only one ICAO airfield. Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
Identifier | 4 letter ICAO code | KJFK | REQUIRED |
Airfield elevation | number in feet | 310 | REQUIRED |
Transition Altitude | number in feet | 5000 | REQUIRED |
Latitude | DMS format | N000.00.00.000 | REQUIRED |
Longitude | DMS format | E000.00.00.000 | REQUIRED |
Airfield name | string maximum 50 characters | New York | REQUIRED |
Hide tag | 1=Hide 2=Show | 1 | OPTIONAL |
Type of installation | 0=Airport,1=Helipad, 2=Military, 3=Private, 4=Uncontrolled | 2 | OPTIONAL |
Note: Transition Altitude and Elevation field may be left empty, or completed with a zero ( 0 ).
Example:
[AIRPORT]
SCEL;1555;10000;S033.23.39.990;W070.47.37.690;AP Arturo Merino Benitez;1;0;
SCSN;246;0;S033.39.24.000;W071.36.57.000;AD Santo Domingo;1; 2;
The AIRPORT section can be included in a separate file:
[AIRPORT]
F;SCEZ.apt
The elevation information is used with the ELEV button inside Aurora. This function will draw a filled squared around the coordinate with a elevation value, which can be useful to represent topografic profiles alongside the colorscheme customization.
Field | Format | Example | Attribute |
---|---|---|---|
Description | Plain Text used to identify the Elevation area in aurora | BOGOTA ELEVATION | REQUIRED |
Elevation Point Coordiante Latitude | DMS Format or Decimal Format | N000.00.00.000 | REQUIRED |
Elevation Point Coordiante Longitude | DMS Format or Decimal Format | N000.00.00.000 | REQUIRED |
Elevation in ft | Feet elevation of the LAT LON coordinate. It accepts decimals with a . separator. |
3067.5 | REQUIRED |
Text | Plain Text | 9350ft | OPTIONAL |
The Description field is used when you SHIFT + Click the ELEV button to show or hide individual elevation areas.
Example:
[ELEVATION]
BOG;5.067339923;-74.099951425;3434;
BOG;4.512913805;-74.041678587;3429;3429 AGL;
BOG;4.443471897;-74.192407246;3426;
The RUNWAY section can be included in a separate file:
[ELEVATION]
F;BOG.elev
Custom symbols can be defined using this feature. To learn more about the matrix software that lets you create new symbols please check ATC Ops Tools.
Symbols can only be added by defining the path or defining the file where symbols are.
Example:
[SYMBOLS]
F;ECUADOR.sym
The RUNWAY section lists all the available runways for all airfields including small ones up to large ones.
The [RUNWAY] beacon shall be inserted alone in a line before all the data.
Each row shall describe one unique RUNWAY.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
Airport Identifier | 4 letter ICAO code | SBUL | REQUIRED |
Primary Runway Number | Runway number between 01 and 18 with L/C/R suffix when applicable |
07R | REQUIRED |
Opposite Runway Number | Runway number between 19 and 36 with L/C/R suffix when applicable |
25L | REQUIRED |
Primary Runway Elevation | number in feet | 310 | REQUIRED |
Opposite Runway Elevation | number in feet | 295 | REQUIRED |
Primary Runway Course | Magnetic orientation in degrees | 071 | REQUIRED |
Opposite Runway Course | Magnetic orientation in degrees | 251 | REQUIRED |
Primary Runway edge Latitude | DMS Format | N000.00.00.000 | REQUIRED |
Primary Runway edge Longitude | DMS Format | E000.00.00.000 | REQUIRED |
Opposite Runway edge Latitude | DMS Format | N000.00.00.000 | REQUIRED |
Opposite Runway edge Longitude | DMS Format | E000.00.00.000 | REQUIRED |
Example:
[RUNWAY]
SCEL;17L;35R;1555;1555;175;355;S033.22.33.890;W070.47.12.150;S033.24.17.600;W070.47.06.570;
SCSN;05;23;246;246;053;233;S033.39.16.811;W071.36.43.636;S033.39.31.259;W071.37.09.447;
The RUNWAY section can be included in a separate file:
[RUNWAY]
F;SCEZ.rwy
The TAXIWAY section lists all the available taxiway identifiers to be displayed.
The [TAXIWAY] beacon shall be inserted alone in a line before all the data.
Each row shall describe only one TAXIWAY identified.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
Taxiway Identifier | short String | L2 | REQUIRED |
Airport Identifier | 4 letter ICAO code | LFRS | REQUIRED |
Taxiway Identifier Latitude | DMS Format | N000.00.00.000 | REQUIRED |
Taxiway Identifier Longitude | DMS Format | E000.00.00.000 | REQUIRED |
Example:
\[TAXIWAY\]
A;SCEL;S033.23.77.000;W070.47.76.000;
D;SCEL;S033.23.75.000;W070.47.56.000;
NOTE: If you have a file named ICAO.txi, where the ICAO matches an airport declared in the [AIRPORTS] section, it will be automatically loaded in the SectorFile.
The GATES section lists all the available gate identifiers to be displayed.
The [GATES] beacon shall be inserted alone in a line before all the data.
Each row shall describe only one GATE identified.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
Gate Identifier | String maximum 20 characters | A43 | REQUIRED |
Airport Identifier | 4 letter ICAO code | EDLL | REQUIRED |
Gate Identifier Latitude | DMS Format | N000.00.00.000 | REQUIRED |
Gate Identifier Longitude | DMS Format | E000.00.00.000 | REQUIRED |
Gate Type | One Letter Type: L = Light, M = Medium, H = Heavy, S = Super, G = General Aviation |
H | OPTIONAL |
Example:
[GATES]
16;SCEL;S033.23.77.000;W070.47.76.000;H;
22;SCEL;S033.23.75.000;W070.47.56.000;
NOTE: If you have a file named ICAO.gts, where the ICAO matches an airport declared in the[AIRPORTS] section, it will be automatically loaded in the SectorFile.
The FIXES section lists all the available FIXES to be displayed.
The [FIXES] beacon shall be inserted alone in a line before all the data.
Each row shall describe only one FIX identified.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
Fix Identifier | String maximum 5 characters | FISTO | REQUIRED |
Fix Latitude | DMS Format | N000.00.00.000 | REQUIRED |
Fix Longitude | DMS Format | E000.00.00.000 | REQUIRED |
Fix Type | number type: 0 = Enroute, 1 = Terminal, 2 = Both, 3= Hidden |
2 | REQUIRED |
Fix is boundary | Number: 0 = OFF, 1 = ON |
0 | REQUIRED |
Example:
[FIXES]
ALDER;S027.05.48.000;W071.09.02.000;0;0;
LODAM;S029.45.27.000;W071.21.01.000;2;0;
GILSA;S030.30.59.000;W067.37.53.000;1;1;
The FIXES section can be included in a separate file:
[FIXES]
F;SCEZ.fix
The NDB section lists all the available NDB navaids to be displayed.
The [NDB] beacon shall be inserted alone in a line before all data.
Each row shall describe only one NDB navaid.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
NDB Identifier | String maximum 5 characters | GOL | REQUIRED |
NDB Frequency | Frequency value in kHz (interpreted as a text field, max length=8) | 369.0 | REQUIRED |
NDB Latitude | DMS Format | N000.00.00.000 | REQUIRED |
NDB Longitude | DMS Format | E000.00.00.000 | REQUIRED |
NDB Visibility | 0 (Show) or 1 (Hide) | 1 | OPTIONAL |
Example:
[NDB]
CLD;227.000;S027.04.37.000;W070.49.07.000;
TOY;260.000;S030.15.47.000;W071.28.47.000;
The NDB section can be included in a separate file:
[NDB]
F;SCEZ.ndb
The VOR section lists all the available VOR navaids to be displayed.
The [VOR] beacon shall be inserted alone in a line before all the data.
Each row shall describe only one VOR navaid.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
VOR Identifier | String maximum 3 characters | NTS | REQUIRED |
VOR Frequency | Frequency value in kHz (interpreted as a text field, max length=8) | 115.50 | REQUIRED |
VOR Latitude | DMS Format | N000.00.00.000 | REQUIRED |
VOR Longitude | DMS Format | E000.00.00.000 | REQUIRED |
VOR Visibility | 0 (Show) or 1 (Hide) | 1 | OPTIONAL |
VOR Type | 0 = VOR, 1 = VORDME, 2 = VORTACAN, 3 = TACAN, 4 = DME | 1 | OPTIONAL |
TACAN Channel Info | Plain Text indicating TACAN's Channel information | CH 56X | OPTIONAL |
Example:
[VOR]
DAT;117.100;S027.16.46.000;W070.46.39.000;1;1;
SER;116.500;S029.54.56.000;W071.11.49.000;;3;CH 56X;
TOY;115.500;S030.16.35.000;W071.28.25.000;
The VOR section can be included in a separate file:
[VOR]
F;SCEZ.vor
The LOW AIRWAY section lists all the available low altitude AIRWAYS .
The [LOW AIRWAY] beacon shall be inserted alone in a line before all the data.
Each AIRWAY definition shall be a list of intersection constituting this airway associated with its own airway identifier.
Each row shall describe only one high altitude AIRWAY intersection.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
Airway Type | One character L for Label, T for Track |
T | REQUIRED |
Airway identifier | String | A33 | REQUIRED |
Airway Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
Airway Longitude | DMS Format or reference fix/navaid | E000.00.00.000 or LAROK | REQUIRED |
Note: You can set multiple labels for the same airway.
The use of reference FIX, NDB or VOR (replacing DMS format) is highly recommended in order to ease the readability and the maintenance of the airways data.
Example:
[LOW AIRWAY]
L;V200;REPUK;REPUK;
L;V200;DOVRI;DOVRI;
L;V200;UPUKU;UPUKU;
T;V200;ARI;ARI;
T;V200;REPUK;REPUK;
T;V200;IQQ;IQQ;
T;V200;BRADA;BRADA;
T;V200;FAG;FAG;
T;V200;DOVRI;DOVRI;
T;V200;PUNSO;PUNSO;
T;V200;DOVKA;DOVKA;
T;V200;DAT;DAT;
T;V200;UPUKU;UPUKU;
The LOW AIRWAYS section can be included in a separate file:
[LOW AIRWAY]
F;SCEZ.lairway
The HIGH AIRWAY section lists all the available high altitude AIRWAYS .
The [HIGH AIRWAY] beacon shall be inserted alone in a line before all the data.
Each AIRWAY definition shall be a list of intersection constituting this airway associated with its own airway identifier.
Each row shall describe only one high altitude AIRWAY intersection.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
Airway Type | One character L for Label, T for Track |
T | REQUIRED |
Airway identifier | String | UY433 | REQUIRED |
Airway Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
Airway Longitude | DMS Format or reference fix/navaid | E000.00.00.000 or LAROK | REQUIRED |
Note: You can set multiple labels for the same airway.
The use of reference FIX, NDB or VOR (replacing DMS format) is highly recommended in order to ease the readability and the maintenance of the airways data.
Example:
[HIGH AIRWAY]
L;UV 200;REPUK;REPUK;
L;UV 200;BRADA;BRADA;
L;UV 200;PUNSO;PUNSO;
L;UV 200;UPUKU;UPUKU;
T;UV 200;ARI;ARI;
T;UV 200;REPUK;REPUK;
T;UV 200;IQQ;IQQ;
T;UV 200;BRADA;BRADA;
T;UV 200;FAG;FAG;
T;UV 200;DOVRI;DOVRI;
T;UV 200;PUNSO;PUNSO;
T;UV 200;DAT;DAT;
T;UV 200;UPUKU;UPUKU;
The HIGH AIRWAY section can be included in a separate file:
[HIGH AIRWAY]
F;SCEZ.hairway
The AIRSPACE section lists the available air traffic controller AIRSPACE .
AIRSPACE definition can be split in 3 areas in order to separate different types of airspace (CTA, TMA, CTR, ACC, FIR, UTA...):
∗ [AIRSPACE] area ( or [ARTCC]) this section
∗ [AIRSPACE LOW] area ( or [ARTCC LOW]) for lower airspace definition (see next chapter)
∗ [AIRSPACE HIGH] area ( or [ARTCC HIGH]) for higher airspace definition (see next chapter)
The [AIRSPACE] beacon shall be inserted alone in a line before all the data.
One AIRSPACE definition is consisting to declare a list of boundary points in sequence (clockwise or anticlockwise);
Each row shall describe only one border point of AIRSPACE described in function of the identifier given.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
Type | One character L for Label, T for Track |
T | REQUIRED |
AIRSPACE identifier | String | SCFZ_OCC | REQUIRED |
AIRSPACE Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
AIRSPACE Longitude | DMS Format or reference fix/navaid | E000.00.00.000 or LAROK | REQUIRED |
Font Size | Number Font size for label |
15 | OPTIONAL |
The use of reference FIX, NDB or VOR (replacing DMS format) is highly recommended in order to ease the readability and the maintenance of the airways data.
IMPORTANT: Each ARTCC shall be named differently.
Example:
[AIRSPACE] // - ANTOFA OCC
T;ANTOFA\_OCC;S018.21.00.000;W090.00.00.000;
T;ANTOFA\_OCC;S018.21.00.000;W073.44.00.000;
T;ANTOFA\_OCC;S025.03.52.000;W072.30.06.000;
T;ANTOFA\_OCC;S028.30.00.000;W071.46.00.000;
T;ANTOFA\_OCC;S028.30.00.000;W090.00.00.000;
T;ANTOFA\_OCC;S018.21.00.000;W090.00.00.000;
//
// - EDGG\_S\_CTR
T;EDGG\_S\_CTR;N048.46.28.668;E008.01.52.464;
T;EDGG\_S\_CTR;N048.39.24.000;E007.52.36.000;
T;EDGG\_S\_CTR;N048.38.46.000;E007.50.06.000;
T;EDGG\_S\_CTR;N048.35.10.000;E007.48.00.000;
T;EDGG\_S\_CTR;N048.30.42.000;E007.47.58.000;
T;EDGG\_S\_CTR;N048.29.52.000;E007.47.00.000;
The AIRSPACE section can be included in a separate file:
[AIRSPACE]
F;SCEZ.airspace
F;SCEZ.artcc
The AIRSPACE section lists the available air traffic controller AIRSPACE .
AIRSPACE definition can be split in 3 areas in order to separate different types of airspace (CTA, TMA, CTR, ACC, FIR, UTA...):
∗ [AIRSPACE] area ( or [ARTCC] ) this section (see previous chapter)
∗ [AIRSPACE LOW] area ( or [ARTCC LOW] ) for lower airspace definition (see next chapter)
∗ [AIRSPACE HIGH] area ( or [ARTCC HIGH] ) for higher airspace definition (this section)
The [AIRSPACE HIGH] beacon shall be inserted alone in a line before all the datas.
One HIGH AIRSPACE definition is consisting to declare a list of boundary points in sequence (clockwise or anticlockwise);
Each row shall describe only one border point of HIGH AIRSPACE described in function of the identifier given.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
Type | One character L for Label, T for Track |
T | REQUIRED |
HIGH AIRSPACE identifier | String | ARI_TMA | REQUIRED |
HIGH AIRSPACE Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
HIGH AIRSPACE Longitude | DMS Format or reference fix/navaid | E000.00.00.000 or LAROK | REQUIRED |
Font Size | Number Font size for label |
15 | OPTIONAL |
The use of reference FIX, NDB or VOR (replacing DMS format) is highly recommended in order to ease the readability and the maintenance of the airways data.
IMPORTANT: Each HIGH AIRSPACE shall be named differently.
Example:
[AIRPSACE HIGH]
// - ARI TMA
T;ARI\_TMA;S017.58.44.000;W069.46.46.000;
T;ARI\_TMA;S017.59.56.631;W069.45.44.330;
T;ARI\_TMA;S018.06.51.560;W069.41.50.638;
T;ARI\_TMA;S018.14.21.783;W069.39.26.731;
The ARTCC HIGH section can be included in a separate file:
[AIRSPACE HIGH]
F;SCAR.hairspece
F;SCAR.hartcc
The AIRSPACE section lists the available air traffic controller AIRSPACE .
AIRSPACE definition can be split in 3 areas in order to separate different types of airspace (CTA, TMA, CTR, ACC, FIR, UTA...):
∗ [AIRSPACE] area ( or [ARTCC]) (see previous chapter)
∗ [AIRSPACE LOW] area ( or [ARTCC LOW]) for lower airspace definition (this section)
∗ [AIRSPACE HIGH] area ( or [ARTCC HIGH]) for higher airspace definition (see previous chapter)
The [AIRSPACE LOW] beacon shall be inserted alone in a line before all the data.
One LOW AIRSPACE definition is consisting to declare a list of boundary points in sequence (clockwise or anticlockwise);
Each row shall describe only one border point of LOW AIRSPACE described in function of the identifier given.Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
Type | One character L for Label, T for Track |
T | REQUIRED |
LOW AIRSPACE identifier | String | SCAR_ATZ | REQUIRED |
LOW AIRSPACE Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
LOW AIRSPACE Longitude | DMS Format or reference fix/navaid | E000.00.00.000 or LAROK | REQUIRED |
Font Size | Number Font size for label |
15 | OPTIONAL |
The use of reference FIX, NDB or VOR (replacing DMS format) is highly recommended in order to ease the readability and the maintenance of the airways data.
IMPORTANT: Each LOW AIRSPACE shall be named differently.
Example:
[AIRSPACE LOW]
// SCAR ATZ
T;SCAR\_ATZ;S018.21.53.527;W070.25.28.996;
T;SCAR\_ATZ;S018.22.49.805;W070.25.11.010;
T;SCAR\_ATZ;S018.23.41.671;W070.24.41.802;
T;SCAR\_ATZ;S018.24.27.132;W070.24.02.495;
The AIRSPACE section can be included in a separate file:
[AIRSPACE LOW]
F;SCAR.lairspace
F;SCAR.lartcc
NOTE: If you have a file named ICAO.sid, where the ICAO matches an airport declared in the [AIRPORTS] section, it will be automatically loaded in the SectorFile.
The SID section lists the available standard departure procedures (SID).
The [SID] beacon shall be inserted alone in a line before all the data. SID definition is defined with 2 lines of information inserted in the sector file in sequence:
- SID Label line
- SID track (reference point)
One SID definition is consisting to declare:
- a SID label line followed by
- a list of SID track points in order
Each row shall describe only one SID label or one SID point.
Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
LABEL line definition:
Field | Format | Example | Attribute |
---|---|---|---|
Airport Identifier | 4 letter ICAO code | SCEL | REQUIRED |
Runway(s) | Runway number with the L,R,C suffix addition if required If more than one, separate each one with ":" sign |
17L:17R | REQUIRED |
SID Identifier | String | DONT3B | REQUIRED |
SID Label Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
SID Label Longitude | DMS Format or reference fix/navaid | E000.00.00.000 or LAROK | REQUIRED |
Type | Value number representing the type: 0/empty=SID 1=Transition 2=Holding 3=IAP 4=FAP 5=GO Around |
1 | OPTIONAL |
Transition | NAVAID name If more than one, seperate each one with an empty space |
WOODY | OPTIONAL |
TRACK line definition:
Field | Format | Example | Attribute |
---|---|---|---|
SID Track Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
SID Track Longitude | DMS Format or reference fix/navaid | E000.00.00.000 or LAROK | REQUIRED |
SID Track Information | String | 3000ft | OPTIONAL |
Example:
[SID]
SCEL;17L:17R;DONT3B;AMB;AMB;0;WOODY;
AMB;AMB;
SEKSU;SEKSU;
EL370;EL370;
DONTI;DONTI;
To start a new path you need to append <br>
at the end of the 1st point where the line starts.
Example:
[SID]
SCEL;17L:17R;DONT3B;AMB;AMB;0;WOODY;
AMB;AMB;
SEKSU;SEKSU;
EL370;EL370;
DONTI;DONTI;
ABC;ABC;<br>;
MONTI;MONTI;
DAFUS;DAFUS;
The STAR section lists the available standard arrival procedures (STAR).
STAR definition is defined with 2 lines of information inserted in the sector file in sequence:
- STAR Label line
- STAR track (reference point):
The [AIRSPACE] beacon shall be inserted alone in a line before all the data.
One STAR definition is consisting to declare:
- a STAR label line followed by
- a list of STAR track points in order
Each row shall describe only one STAR label or one STAR point.
Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
LABEL line definition:
Field | Format | Example | Attribute |
---|---|---|---|
Airport Identifier | 4 letter ICAO code | SCEL | REQUIRED |
Runway(s) | Runway number with the L,R,C suffix addition if required If more than one, separate each one with ":" sign |
17L:17R | REQUIRED |
STAR ID | String | UMKA4C | REQUIRED |
STAR Label Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
STAR Label Longitude | DMS Format or reference fix/navaid | E000.00.00.000 or LAROK | REQUIRED |
Type | Value number representing the type: 0/empty=STAR 1=Transition 2=Holding 3=IAP 4=FAP 5=GO Around |
1 | OPTIONAL |
Transition | NAVAID name If more than one, seperate each one with an empty space |
WOODY | OPTIONAL |
TRACK line definition:
Field | Format | Example | Attribute |
---|---|---|---|
STAR Track Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
STAR Track Longitude | DMS Format or reference fix/navaid | E000.00.00.000 or LAROK | REQUIRED |
STAR Track Information | String | 7500ft | OPTIONAL |
Example:
[STAR]
SCEL;17L:17R;UMKA4C;UMKAL;UMKAL;1;WOODY;
UMKAL;UMKAL;
LOSAN;LOSAN;
SAFEL;SAFEL;
UGOLA;UGOLA;
To start a new path you need to append <br>
at the end of the 1st point where the line starts.
[STAR]
SCEL;17L:17R;UMKA4C;UMKAL;UMKAL;1;WOODY;
UMKAL;UMKAL;
LOSAN;LOSAN;
SAFEL;SAFEL;
UGOLA;UGOLA;
UMKAL;UMKAL;<br>;
TADOP;TADOP;
MEKSI;MEKSI;
NOTE: If you have a file named ICAO.str, where the ICAO matches an airport declared in the [AIRPORTS] section, it will be automatically loaded in the SectorFile.
The VFR fix section lists all the available VFR fixes to be displayed.
The [VFRFIX] beacon shall be inserted alone in a line before all the data.
Each row shall describe only one VFR fix.
Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
VFR Fix Name | String | HOLARGOS | REQUIRED |
VFR Fix Altitude | String or number in feets Specific like 2500, or Range as 2500-4000 |
2500-4000 | REQUIRED |
VFR Fix Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
VFR Fix Longitude | DMS Format or reference fix/navaid | E000.00.00.000 or LAROK | REQUIRED |
VFR Fix Type | 0 = VFR mandatory, 1 = VFR, 2 = VFR HELI, 3 = VFR AREA | 1 | OPTIONAL |
The
0 = VFR mandatory
refres to mandatory VFR reporting points
The use of reference FIX, NDB or VOR (replacing DMS format) is highly recommended in order to ease the readability and the maintenance of the airways data.
Example:
\[VFRFIX\]
HOLARGOS;2500-4000;N037.59.80.000;E023.48.10.000;
A.KEA;MAX 2500;N037.59.80.000;E023.48.10.000;
NOTE: If you have a file named ICAO.vfi, where the ICAO matches an airport declared in the [AIRPORTS] section, it will be automatically loaded in the SectorFile.
The VFRFIX section can be included in a separate file:
\[VFRFIX\]
F;SCEZ.vfi
The VFR route section lists all the available VFR routes to be displayed.
The [VFRROUTE] beacon shall be inserted alone in a line before all the data.
Each row shall describe only one VFR intersection of the selected VFR route by its own identifier .
Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
Route Identifier | Number (serial) | 1 | REQUIRED |
Route Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
Route Longitude | DMS Format or reference fix/navaid | E000.00.00.000 or LAROK | REQUIRED |
Example:
[VFRROUTE]
1;LOFOS;LOFOS;
1;PERATI;PERATI;
2;PERATI;PERATI;
2;MANDILOU;MANDILOU;
NOTE: If you have a file named ICAO.vrt, where the ICAO matches an airport declared in the [AIRPORTS] section, it will be automatically loaded in the SectorFile.
The MVA section lists all the available minimum vector altitudes and sectors to be displayed.
The [MVA] beacon shall be inserted alone in a line before all the data.
Each row shall describe only one border point of MVA sectors described in function of the identifier given.
Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
Field | Format | Example | Attribute |
---|---|---|---|
MVA Type | One character L for Label, T for Track |
T | REQUIRED |
MVA identifier | String | LG MVA | REQUIRED |
MVA Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
MVA Longitude | DMS Format or reference fix/navaid | E000.00.00.000 or LAROK | REQUIRED |
MVA Description | Description shown in screen (L only) | 7500ft | OPTIONAL |
MVA Font | Font size for description (L only) | 15 | OPTIONAL |
Note: You can set multiple labels for the same mva.
The use of reference FIX, NDB or VOR (replacing DMS format) is highly recommended in order to ease the readability and the maintenance of the airways data.
Example:
[MVA]
L;LG MVA;N038.50.00.000;E022.02.24.000;7500ft;15;
T;LG MVA;N038.50.03.000;E022.03.24.000;
T;LG MVA;N038.49.23.632;E022.04.22.123;
T;LG MVA;N038.48.44.257;E022.05.20.228;
NOTE: If you have a file named ICAO.mva, where the ICAO matches an airport declared in the [AIRPORTS] section, it will be automatically loaded in the SectorFile.
The GEO section lists all the available geographical and fixed information to be displayed in terms of lines and areas.
The [GEO] beacon shall be inserted alone in a line before all the data.
Each row shall describe only one border point of GEO sectors or area described in function of the identifier given.
Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
RULE: Each GEO area shall be constructed with the following structure:
Field | Format | Example | Attribute |
---|---|---|---|
GEO Starting Latitude | DMS Format or reference fix/navaid | N045.00.00.000 or KOKOS | REQUIRED |
GEO Starting Longitude | DMS Format or reference fix/navaid | E001.00.00.000 or KOKOS | REQUIRED |
GEO Ending Latitude | DMS Format or reference fix/navaid | N046.00.00.000 or REQIN | REQUIRED |
GEO Ending Longitude | DMS Format or reference fix/navaid | E003.00.00.000 or REQIN | REQUIRED |
GEO Color | RGB color format | #00404040 | OPTIONAL |
RULE: Any new blank or commented line in this section will initiate a new path without linking it to the previous point.
GEO examples can be (and not limited to these data) :
Example:
[GEO]
// COAST LINE
S048.00.36.101;W074.39.07.700;S047.59.28.702;W074.34.48.202;COAST;
S047.59.28.702;W074.34.48.202;S047.56.58.499;W074.32.03.199;COAST;
S047.56.58.499;W074.32.03.199;S047.58.49.598;W074.27.27.101;COAST;
//
// DANGER ZONES
//
// SC-D01
S030.48.28.000;W071.14.10.000;S030.48.29.153;W071.13.56.369;danger;
S030.48.29.153;W071.13.56.369;S030.48.32.567;W071.13.43.262;danger;
S030.48.32.567;W071.13.43.262;S030.48.38.112;W071.13.31.182;danger;
The GEO section can be included in a separate file to improve sectorfile order and performance:
[GEO]
F;SCEZ.danger
F;SCEZ.restrict
F;SCEZ.prohibit
F;SCEZ.geo
Also, they can be included as
ICAO.xxx
and there will be no need to declare them under the [GEO] part.ICAO.rwy (Runway)
ICAO.txo (Taxi Outer)
ICAO.txc (Taxi Inner)
ICAO.stp (Stop Areas)
ICAO.apr (Apron)
ICAO.pier (Airport Piers)
ICAO.bld (Buildings)
The FILLCOLOR section lists all the available coloured areas named polygons in the sector file.
The [FILLCOLOR] beacon shall be inserted alone in a line before all the data. Each polygon shall have:
Each row shall describe only one border point of GEO sectors or area described in function of the identifier given.
Each row shall contain the following fields inserted by order, separated and finished with a semicolon ( ; ):
RULE: These polygon areas can be static or dynamic:
Definition: the Polygon declaration shall be located in the first row of each polygon declaration:
Field | Format | Example | Attribute |
---|---|---|---|
Polygon Type | Predefined String 'Static' or IVAO ATC position list (ICAO_POS) for dynamic ] |
Static (or) LGAV_APP LGAV_DEP |
REQUIRED |
Fill Color | RGB format | #00404040 | REQUIRED |
Stroke Width | Predefined Number | 1 | REQUIRED |
Stroke Color | RGB format | #00404040 | REQUIRED |
Fill Color Clear | Number 0 = default 1 = with opacity |
1 | OPTIONAL |
Filter | String: COAST, RUNWAY, GATES, PIER, TAXIWAY, APRON, BUILDING |
TAXIWAY | OPTIONAL |
Definition: the polygon area point lines shall be located after the polygon declaration on a new line:
Field | Format | Example | Attribute |
---|---|---|---|
Latitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
Longitude | DMS Format or reference fix/navaid | N000.00.00.000 or LAROK | REQUIRED |
Example:
[FILLCOLOR]
// runway 03L-21R LGAV STATIC;#00404040;1;#00120000;
N037.55.17.581;E023.55.07.096;
N037.56.56.164;E023.56.40.442;
N037.56.55.308;E023.56.41.895;
// TMA LGAV
LGAV_APP LGAV_DEP;#00120000;1;#00120000;1;
N038.09.56.002;E022.43.58.001;
N038.09.56.002;E024.10.58.001;
N038.12.56.002;E024.15.58.000;
NOTE: If you have a file named ICAO.tfl, where the ICAO matches an airport declared in the [AIRPORTS] section, it will be automatically loaded in the SectorFile.
Some data of the FILLCOLOR section can be included in some separate file by using custom extention outside "tfl" one:
[FILLCOLOR]
F;SCEZ.myext
When updating a sector file, there are two ways to make the old and unnecessary files invisible.
1. Removing the definition of the related file from .isc file.
2. Making Aurora completely delete the unwanted files with the update.
While first option is enough for most of the files, having redundant files may create issues with some of the file types.
To delete files with the update, you must create a file named delete.upd
delete.upd should be placed to root of the update.zip along with the .isc file. So the .zip should contain, delete.upd, sectorname.isc, and Include folder.
You must define the files to be deleted inside delete.upd. Example delete.upd file:
TR\LTFM.tfl
TR\Other\tratc.atc
Keep in mind that the deletion operation will be done after the unzipping, thus do not delete the files which will be overwritten.