Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ivac2:firdef_sectors_xml [2015/06/08 12:45]
splendor.bouman removed
ivac2:firdef_sectors_xml [2017/04/08 14:27] (current)
Line 1: Line 1:
-====== ​IvAc 2 sector system ​======+====== ​Sectors.xml ​======
  
-The sector system in IvAc 2 will implement the following major changes:+Sectors are indivisible ATC units of airspace which are defined using one or a number of [[ivac2:firdef_sectors_volumes|volumes]]. Sectors form the base for all coordination and AFTM calculations.
  
-  * 3D definition of each sector, for traffic detection and WebEye display.  +The ''​sectors.xml''​ file is located in the ''​fir/​sectors''​ directory
-  * The ability to combine and split sectors ​without reconnecting or changing frequency +
-  * The ability to activate and deactivate ​sectors ​individually+
  
-===== Sector definition =====+^Element|sector|| 
 +^Attribute^Format^Remarks^ 
 +|id|string|sector id - used when referring to the sector| 
 +|fir|string|FIR in which the sector occurs (avoids duplicates)| 
 +|name| string |sector name| 
 +|callsign| string |Radio callsign of the sector| 
 +|freq|frequency|Radio frequency of the sector| 
 +|type|string|Type of sector (DEL, GND, TWR, APP, DEP, ACC, FSS)|
  
-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 <​sector>​ element must contain at least one volume if the type of unit is:
  
-{{ :​ivac2:​ivac-2-sectors.png?​nolink |}}+  * TWR 
 +  * APP 
 +  * DEP 
 +  * ACC 
 +  * FSS
  
-A **sector** is an indivisible block of airspace which may be activated. Each sector is composed of the following:​ +===== Example =====
- +
-  * Sector ID +
-  * FIR +
-  * Sector Name +
-  * Radio Callsign +
-  * Frequency +
-  * Type (DEL, GND, TWR, APP, ACC, FSS)+
  
 <code XML> <code XML>
Line 28: Line 30:
 </​sector>​ </​sector>​
 </​code>​ </​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"​ fir="​ABXX"​ bottom="​000"​ top="​999">​ 
-  <point lat="​N0494918000"​ lon="​E0041835000"​ /> 
-  <point lat="​N0494918000"​ lon="​E0041835000"​ /> 
-  <point lat="​N0494918000"​ lon="​E0041835000"​ /> 
-</​volume>​ 
-</​code>​ 
- 
-===== Structure ===== 
- 
- 
-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 
- 
  
 ---- ----
  
 [[ivac2:​firdef|Back]] [[ivac2:​firdef|Back]]