Airspace data in YAIXM format.
The data is split into five files:
-
airspace.yaml - Airspace data from the UK Aeronautical Information Package
-
loa.yaml - BGA Letters of Agreement (see https://members.gliding.co.uk/library/loas)
-
obstacle.yaml - Obstacle data from the data file listed in section ENR 5.4 of the UK AIP.
-
rat.yaml - RA(T) data from mauve AICs
-
service.yaml - Radio frequencies
YAIXM is a simplified version of the FAA/EUROCONTOL Aeronautical Information Exchange Model (AIXM) using YAML.
AIXM was chosen as the underlying model because it provides a ready made mapping of the AIP to computer readable data. The AIP itself is (or, possibly, will be) built on AIXM data, though unfortunately this data isn't publicly available.
YAML is a data serialisation format specifically designed to be human readable and writable. This is important - YAIXM data is entered manually from the AIP.
YAIXM data can be parsed directly (YAML libraries are available for all common computer languages) or converted to JSON before parsing.
YAML doesn't have a schema language. However YAIXM data can be mapped directly to/from JSON, so JSON Schema can be used instead. The JSON schema for YAIXM can be found on GitHub.
I'm Alan Sparrow
YAIXM is on GitHub.
Please get in touch, via GitHub or otherwise. If you've got something to contribute it would be very welcome.
type | localtype | description |
---|---|---|
ATZ | Air traffic zone | |
CTA | Control area | |
CTR | Control zone | |
D | Danger area | |
D_OTHER | DZ | Drop zone |
D_OTHER | LASER | Laser site |
D_OTHER | GLIDER | Wave box, or LOA area (with LOA rule) |
D_OTHER | HIRTA | HIRTA |
D_OTHER | GVS | Gas venting station |
OTHER | GLIDER | Gliding site |
OTHER | ILS | Instrument landing system |
OTHER | MATZ | Military ATZ |
OTHER | NOATZ | Training airfield |
OTHER | RMZ | Radio mandatory zone |
OTHER | TMZ | Transponder mandatory zone |
OTHER | UL | Ultralight airfield |
P | Prohibited area | |
R | Restricted area | |
TMA | Terminal manouvering area |