This shows you the differences between two versions of the page.
|
ivac2:firdef_sectors_xml [2015/03/13 07:55] filip.jonckers |
ivac2:firdef_sectors_xml [2017/04/08 14:27] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== IvAc 2 sector system ====== | ||
| - | The sector system in IvAc 2 will implement the following major changes: | ||
| - | |||
| - | * 3D definition of each sector, for traffic detection and WebEye display. | ||
| - | * The ability to combine and split sectors without reconnecting or changing frequency | ||
| - | * The ability to activate and deactivate sectors individually | ||
| - | |||
| - | ===== Sector definition ===== | ||
| - | |||
| - | 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. | ||
| - | |||
| - | {{ :ivac2:ivac-2-sectors.png?nolink |}} | ||
| - | |||
| - | A **sector** is an indivisible block of airspace which may be activated. Each sector is composed of the following: | ||
| - | |||
| - | * Sector ID | ||
| - | * Sector Name | ||
| - | * Radio Callsign | ||
| - | * Frequency | ||
| - | * Type (DEL, GND, TWR, APP, ACC, FSS) | ||
| - | |||
| - | <code XML> | ||
| - | <sector id="Y" name="Yellow sector" callsign="Somewhere Radar" freq="125.550" type="acc"> | ||
| - | <volume id="Y_Sect_1" /> | ||
| - | <volume id="Y_Sect_2" /> | ||
| - | </sector> | ||
| - | </code> | ||
| - | |||
| - | The sector is defined by one of more volumes of airspace. | ||
| - | |||
| - | A **volume** is a polygon with a upper and lower level that defines the airspace of a particular sector. A sector with 2 different upper/lower levels such as Y sector would have two volumes. | ||
| - | |||
| - | Volumes of separate sectors may overlap and the smallest volume will be considered. Reference to the diagram above, in Y sector there is no need to cut out the APP airspace. | ||
| - | |||
| - | Note that DEL & GND sectors don't have volumes as they are linked to the aerodrome reference point & transfer conditions are different than between airborne sectors. | ||
| - | |||
| - | <code XML> | ||
| - | <volume id="Y_sect_1" bottom="000" top="999"> | ||
| - | <point lat="N0494918000" lon="E0041835000" /> | ||
| - | <point lat="N0494918000" lon="E0041835000" /> | ||
| - | <point lat="N0494918000" lon="E0041835000" /> | ||
| - | </volume> | ||
| - | </code> | ||
| - | |||
| - | ===== Scribbles and unknowns ===== | ||
| - | |||
| - | |||
| - | Preset = Map configuration | ||
| - | |||
| - | * Map(s) | ||
| - | * Centerpoint | ||
| - | * Zoom_Level | ||
| - | * Theme | ||
| - | |||
| - | Position = User connection to IVAO | ||
| - | |||
| - | * FSD Connection | ||
| - | * Voice Channel | ||
| - | * Preset | ||
| - | * Sector(s) | ||
| - | |||
| - | Sector = What pilots / controllers see | ||
| - | |||
| - | * ID | ||
| - | * Frequency | ||
| - | * LOA | ||
| - | * Volume(s) | ||
| - | * Adjacent sector(s) | ||
| - | * Sub sector(s) | ||
| - | |||
| - | Volume = Internal | ||
| - | |||
| - | * ID | ||
| - | * Upper level | ||
| - | * Lower level | ||
| - | * Lat / Lon Points | ||