Sector File Definition[PDF]

Introduction

This document presents the sector file definition of the IVAO ATC client.


Generic Data Format Definition

Definition: Most GPS devices provide geographic coordinates in the Degrees, Minutes and Seconds (DMS) format, or more commonly the Decimal Degrees (DD) format.

Coordinates 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;


Note:

Abbreviated DMS coordinates with separation such as S040, N038.10 or E024.33.34 will give unpredictable, usually truncated results. Please do not use them.

Abbreviated DMS coordinates without separation such as S040, N03810, or E0243334 will give unpredictable, usually truncated results. Please do not use them.

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;

Colours Format

The colour format shall use the RGB definition.

Definition RGB: The RGB colour model is an additive colour model in which red(R), green(G), and blue(B) lights are added together in various ways to reproduce a broad array of colours. The name of the model comes from the initials of the three additive primary colors, Red, Green and Blue.
You should use one of the following RGB hexadecimal colour formats:
  • #00RRGGBB
  • $00RRGGBB
  • #RRGGBB
  • $RRGGBB


RULE: In hexadecimal format RR, GG and BB shall be coded from the value "00" (minimum) to "FF" (maximum).
(in hexadecimal format, each digit can take the following value by order : 0,1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F.)
If you do not want any RGB hexadecimal colour format, you should use the following RGB decimal colour format:
  • %rrr:ggg:bbb
RULE: In decimal format rrr, ggg and bbb shall be coded from the value "000" (minimum) to "255" (maximum).
Colours table.jpg

Separated files

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 [AIRPORTS] section, the file will be loaded in Sector Definition, without the need to declare it under the [SID] section.
  • XXXX.atc = ATC Information
  • 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.

Allowed lines with no data

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.

Rule:

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.


Section Format Definition

Sector files have several areas. Each area has a specific purpose.


INFO Information - [INFO]

The header of the sector file shall describe the following information lines in order to configure and display your sector file well:
  1. Latitude
  2. Longitude
  3. Vertical ratio
  4. Horizonal ratio
  5. Magnetic Variation
  6. Folder name / Sub-Folder name


The [INFO] beacon shall be inserted alone in a line followed by all the 6 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



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

Example:

[INFO]
S033.23.39.000
W070.47.37.000
60
51
-1.8
SCEZ;SCEZ\airports;SCEZ\SID;SCEZ\STAR


DEFINE information - [DEFINE]

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;#4455f0;

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

ATC information - [ATC]

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


Example:

[ATC]

LGAV_APP;132.975;

NOTE: If you have a file named ICAO.atc, where the ICAO matches an airport declared in the [AIRPORTS] section, it will be automatically loaded in the SectorFile.


AIRPORT information - [AIRPORT]

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


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;
SCSN;246;0;S033.39.24.000;W071.36.57.000;AD Santo Domingo;

The AIRPORT section can be included in a separate file:

[AIRPORT]

F;SCEZ.apt


RUNWAY information - [RUNWAY]

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;
SCEL;17R;35L;1555;1555;175;355;S033.22.19.020;W070.48.13.380;S033.24.22.250;W070.48.06.770;

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



TAXIWAY information - [TAXIWAY]

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.

GATES information - [GATES]

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.

FIXES information - [FIXES]

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


NDB information - [NDB]

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


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


VOR information - [VOR]

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


Example:

[VOR]
DAT;117.100;S027.16.46.000;W070.46.39.000;
SER;116.500;S029.54.56.000;W071.11.49.000;
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


LOW AIRWAY information - [LOW AIRWAY]

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


HIGH AIRWAY information - [HIGH AIRWAY]

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



AIRSPACE information - [AIRSPACE] or [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
  • [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.aispace
F;SCEZ.artcc



HIGH AIRSPACE information - [AIRSPACE HIGH] or [ARTCC HIGH]

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



LOW AIRSPACE information - [AIRSPACE LOW] or [ARTCC LOW]

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



SID information - [SID]

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


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


RULE: Any new blank line in this section will initiate a new path without linking it to the previous point.

Example:

[SID]
SCEL;17L:17R;DONT3B;AMB;AMB;
AMB;AMB;
SEKSU;SEKSU;
EL370;EL370;
DONTI;DONTI;

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.




STAR information - [STAR]

The STAR section lists the available standard arrival procedures (STAR).

The [AIRSPACE] beacon shall be inserted alone in a line before all the data.
STAR definition is defined with 2 lines of information inserted in the sector file in sequence:

  • STAR Label line
  • STAR track (reference point)


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


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


RULE: Any new blank line in this section will initiate a new path without linking it to the previous point.

Example:

[STAR]
SCEL;17L:17R;UMKA4C;UMKAL;UMKAL;
UMKAL;UMKAL;
LOSAN;LOSAN;
SAFEL;SAFEL;
UGOLA;UGOLA;

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.

VFR FIX information - [VFRFIX]

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


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



VFR ROUTE information - [VFRROUTE]

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.

MVA information - [MVA]

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.

GEO information - [GEO]

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:
  • A mandatory comment line which can contain optionally any string which describes the geo area (highly recommended).
  • A list of geographical coordinates listed one by one in sequence on each row
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) :
  • Rivers, lakes, coasts, ...
  • Mountains, high level landmarks
  • Buildings, towers, terminals, ...
  • Danger, restricted and prohibited zones ...

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:

[GEO]

F;SCEZ.danger
F;SCEZ.restrict
F;SCEZ.prohibit
F;SCEZ.geo



POLYLINE information - [FILLCOLOR]

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:

  • one commented line for polygon definition or separation (OPTIONAL)
  • one polygon declaration line for polygon properties (MANDATORY)
  • list of polygon area point lines for polygon definition (MANDATORY)

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:
  • The polygons defined in static, with inserting 'Static' string in the property, are always displayed whatever the other ATC presence.
  • The polygon defined in dynamic, with inserting a list of concerned IVAO ATC positions (ICAO_POS) in the property, are displayed in function of the presence of these ATC.

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


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



See also

  • None

Reference

  • None

Author

  • VID 193103 - Creation
  • VID 425236 - Update
  • VID 150259 - Wiki integration

DATE OF SUBMISSION

  • 16:11, 4 February 2020

COPYRIGHT

  • This documentation is copyrighted as part of the intellectual property of the International Virtual Aviation Organisation.

DISCLAIMER

  • The content of this documentation is intended for aviation simulation only and must not be used for real aviation operations.