Differences

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

Link to this comparison view

Next revision 		Previous revision
ivac2:firdef_ssr_xml [2017/07/25 22:41]
filip.jonckers created 		ivac2:firdef_ssr_xml [2017/07/25 23:25] (current)
filip.jonckers
Line 5: Line 5:
 The ''​ssr.xml''​ file is located in the ''​fir/''​ directory The ''​ssr.xml''​ file is located in the ''​fir/''​ directory
  
-^Root Element|blocks||+^Root Element|ssr|| 
 +| ^Element|codeblocks|| 
 +| | ^Element|block| 
 +| ^Element|allocation|| 
 +| | ^Element|modesasp| 
 +| | ^Element|ssr| 
 + 
 + 
 +The structure of the elements are as follows: 
 + 
 ^Element|block|| ^Element|block||
 ^Attribute^Format^Remarks^ ^Attribute^Format^Remarks^
-|id|string|Unique ID of code range| +|id|string|Unique ID of this code block - must be unique for this FIR !| 
-|first|integer|First code available in range| +|first|integer|First code available in this block| 
-|last|integer|Last code available in range|+|last|integer|Last code available in this block| 
 +|prtm|integer|PRotection TiMe - time in minutes that a code is protected (not allocated) | 
 + 
 + 
 +The <​modesasp>​ elements shall only be used when mode A code 1000 can be assigned to specific city pairs. 
 +Note that only specific departure and destination airports and routes are eligible for a A1000 ssr code.   The usage of A1000 requires complete mode S surveillance coverage from ground to air to ground at arrival (gate to gate Mode S coverage). ​ This is also called Mode S declared airspace. ​  Only major airports with the required surveillance equipment (multilateration,​ mode S radar coverage, etc..) use A1000. 
 +If not present,​A1000 is not used.  A1000 does not use a ssr code block. 
 + 
 +^Element|modesasp|| 
 +^Attribute^Format^Remarks^ 
 +|adep|string|departure airport icao code (starts with)| 
 +|ades|string|arrival airport icao code (starts with)| 
 + 
 + 
 +===SSR code allocation rules=== 
  
-^Root Element|assignment|| 
 ^Element|ssr|| ^Element|ssr||
 ^Attribute^Format^Remarks^ ^Attribute^Format^Remarks^
-|block|string|ID of code range defined in <blocks>| +|block|string|ID of code block defined in <codeblocks>, a code block can be used in multiple allocation rules| 
-|fr|V / I / IV|Flight Rules (I = IFR, V= VFR)| +|fr|V / I / IV|Flight Rules (I = IFR, V= VFR) - default IV |
-|ty|string|Type of flight (SGM etc)| +
-|atc|string|Controlling unit which assigns the code|+
 |adep|string|Departure aerodrome (1, 2, 3, 4 characters of ICAO code = EB or EBBR)| |adep|string|Departure aerodrome (1, 2, 3, 4 characters of ICAO code = EB or EBBR)|
 |ades|string|Arrival aerodrome (1, 2, 3, 4 characters of ICAO code = EB or EBBR)| |ades|string|Arrival aerodrome (1, 2, 3, 4 characters of ICAO code = EB or EBBR)|
-|sid|string|Assigned departure route| +|sid|string|Assigned ​SID standard instrument ​departure route (starts with) | 
-|minrfl|integer|Lowest requested flight level| +|minrfl|integer|Lowest requested flight level - default zero| 
-|maxrfl|integer|Highest requested flight level|+|maxrfl|integer|Highest requested flight level - default 999| 
 + 
 +All attributes are optional except for the block attribute. ​ The order is of importance! ​ The first block found is used first, if the code block has no free ssr codes then the next found ssr block is used etc... 
 + 
 +SSR codes are allocated randomly from each block. ​ SSR Codes are available after the protection time defined for each block. (last radar detection time + PRTM in minutes) 
 +So it is quite important that at the end you have a catch-all code block rule - this could be the transit code block rule. 
 + 
 +tip: use the first part (point name) of the SID name to allocate to multiple SIDs which use the same point name.
  
-''​Note that this file has not been finalised, format changes may occur''​