-
Notifications
You must be signed in to change notification settings - Fork 69
Data Format
Data is stored in JSON files. Generally, you should aim for one vACC/vARTCC per dataset. In some cases (e.g. vACCs with multiple, unconnected FIRs), it may be more appropriate to split data across multiple files. There are three standard formats:
This is the original file format. All data is stored in a single JSON file, named <icao>.json, where <icao> is the relevant ICAO country code (or FIR ID where multiple files exist).
This format is most appropriate for vACCs/vARTCCs with a single sector ownership hierarchy. I.e. Sector A always owns Sector X and Airport Y if there is no local ATC online, regardless of the traffic situation.
This format provides support for dynamic assignment of ATC sectors to controllers. All data is stored in a single directory, named <icao>, where <icao> is the relevant ICAO country code (or FIR ID where multiple files exist).
Airspace and Position data are stored permanently in two JSON files. Additionally, the ownership sub-directory contains one or more JSON files which assign sectors and airports to positions.
If all controllers in a data set (including defined Positions and controllers auto-matched to Airports) log off, the site automatically resets to using the default.json ownership file. N.B. All controllers must disconnect to trigger this, including DEL/RMP/GND.
This format is most appropriate for vACCs/vARTCCs with a multiple sector ownership hierarchies. I.e. Sector A or Sector B could own Sector X and Airport Y if there is no local ATC online, depending on the traffic situation.
There are two Dynamic ownership file formats, Ownership and Editor. A data set can contain a mix of both file formats.
This format provides support for all features of the Static file format. However, sector ownership cannot be adjusted using the Editor.
Controllers can select from the list of ownership JSON files provided by local staff or temporarily upload their own.
This format provides support for some features of the Static file format. However, sector ownership can be adjusted using the Editor.
Controllers can select from the list of ownership JSON files provided by local staff or temporarily upload their own.
Sectors and Airports can be assigned to controllers using the Editor page. However, ownership hierarchies are not supported. Each sector and airport can only be assigned to a single controller, and will display as uncontrolled if that controller is offline.