ATC sectors extending

Following rules only apply to specific regions / FIRs / ARTCC and allow for ATC duplicating when certain rules are followed.

Australia

Data is fetched from Sectors.xml: https://raw.githubusercontent.com/vatSys/australia-dataset/master/Sectors.xml
Rules are only applied to _CTR, _APP and _DEP
Controller's ATIS should include both: Frequency of duplicated sector and Name of duplicated sector (s). For example, EXT ASW 131.800 or EXT ASW 131.8

In such case, controller is duplicated as-is, excluding callsign and frequency - those are changed to target sector.

Data is hard coded - extending is allowed for specified callsigns. Controller ATIS should include text of sections below for mapping to work.

Example: Area A in ZOA/NCT ATIS will duplicate controller with SJC_APP callsign.

In that case, controller is duplicated as-is, excluding callsign - this is being changed to target sector.

Allowed for NCT, SFO, OAK, SJC, SMF, RNO, MRY, MOD, BAY (APP, DEP, CTR or TMU).

Allows opening or closing of ZMA's TRACONs based off various callsign/polygon definitions

Data is hard coded - allows opening or closing of ZMA's Ocean Area based off various callsign/polygon definitions
If controller ATIS includes Ocean Area, ZMO_##_CTR (KZMA-OCN polygon) is opened in addition to the current MIA_##_CTR (KZMA polygon) position
If controller ATIS includes No Ocean Area, MIA_##_CTR (KZMA) is signed off and replaced with ZMA_##_CTR (KZMA-N polygon)

In such case, controller is duplicated as-is, excluding callsign - this is being changed to target sector.

Contact us in Discord if you are duplicating your sectors internally, have this system documented, and want to make it work on VATSIM Radar.