API Documentation



Provides all airspaces. Returns a GeoJSON FeatureCollection. Each airspace is a Feature inside the collection and represented by a Polygon. Metadata is described in the properties object.

Test it!


    "type": "FeatureCollection",
    "features": [
            "type": "Feature",
            "properties": { ... },
            "geometry": {
                "type": "Polygon",
                "coordinates": [ ... ]

Airspace metadata / properties object

The following airspace metadata is available in the properties object:

"properties": { 
    "Name": "TMA Emmen 3 HX",
    "ASClass": "D",
    "ASType": "TMA",
    "HX": true,
    "DABS": false,
    "Dropzone": false,
    "InactiveByAgreement": false,
    "Callsign": "Emmen TWR",
    "Frequency": "120.425",
    "AdditionalInfos": "Sample text...",
    "Validity": [ ... ],
    "Upper": { ... },
    "Lower": { ... }
Name of the airspace
Airspace class A-G (optional). Usually only provided for relevant airspaces (Class C and D). Class A and B don't exist in Switzerland. Class E-G are usually not designated, since they are not relevant for navigational purpose.
Airspace type:
CTA: according to ICAO/glider chart
AWY: Airway, according to ICAO/glider chart
CTR: according to ICAO/glider chart
TMA: according to ICAO/glider chart
FIZ: according to ICAO/glider chart
RMZ: Radio Mandatory Zone, according to ICAO/glider chart or local agreements
Q: Danger Area (LS-D) according to ICAO/glider chart
R: Restricted Area (LS-R) according to ICAO/glider chart
W: Glider Sector according to ICAO/glider chart
Airfield: according to VLK or local agreements
Heliport: according to VLK or local agreements
Whether the airspace is HX activated (can be activated any time)
Whether the airspace is activated by DABS
Whether the airspace/airfield contains a Para/Dropzone.
Whether the airspace (mostly used for small airfields / heliports) is replaced by some local agreements. In this case, the airspace is just depicted for situational awareness and the boundaries of the local agreement (usually smaller) counts.
[optional] Callsign to be used when communicating on the airspace frequency
[optional] Associated frequency of the airspace, e.g. to get a clearence
[optional] Description / additional infos for the airspace if available
[optional] In what date range(s) the airspace is valid/active. E.g. if an airspace is newly added or removed or if it's only valid on certain dates during the year. See Validity object. If the airspace is always valid, the property is omitted.
Upper and Lower altitudes

Airspace Altitudes

With each airspace (segment), an upper and lower altitude boundary is provided. Since published metric (glider chart) and imperial (ICAO) altitudes are not mathematical meter/feet conversions, we'll provide both numbers in separate fields. If only one of them is availabe, we will provide the original value and will not calculate the other.

"Upper": {
    "Metric": {
        "Alt": { "Type": "m STD", "Altitude": 3950 }
    "Imperial": {
        "Alt": { "Type": "FL", "Altitude": 130 }
"Lower": {
    "Metric": {
        "Alt": { "Type": "m QNH", "Altitude": 1850 },
        "Alt2": { "Type": "m AGL", "Altitude": 300 }
    "Imperial": {
        "Alt": { "Type": "ft QNH", "Altitude": 6000 },
        "Alt2": { "Type": "ft AGL", "Altitude": 1000 }
Primary altitude, always given
[optional] Secondary altitude, if an airspace boundary is defined by two altitudes like "1850m AMSL or 300m AGL".
Unit of the altitude and wheter it refers to local pressure (QNH) or standard atmosphere. Possible values are:
m QNH: Meters above mean sea level in local pressure (QNH)
m STD: Meters above mean sea level in standard atmosphere
m AGL: Meters above ground ("GND" will be encoded as 0 m AGL)
ft QNH: Feet above mean sea level in local pressure (QNH)
ft STD: Feet above mean sea level in standard atmosphere (usually, these altitudes should be given as FL)
ft AGL: Feet above ground ("GND" will be encoded as 0 ft AGL)
FL: Flight level, always in standard atmosphere
NOTAM: Altitude is only defined by NOTAM. Altitude value will be 0.
The altitude value

Airspace Validity

Array of from/to dates, when an airspace is valid/active. The following example shows an airspace that is active until March 24th, from May 1st until May 31st, and then again from October 1st onwards.

    { "ValidFrom": null, "ValidTo": "2021-03-24" },
    { "ValidFrom": "2021-05-01", "ValidTo": "2021-05-31" },
    { "ValidFrom": "2021-10-01", "ValidTo": null },


For the latest features and tests, we provide the BETA API. Please be aware that endpoints or data structures might change at any time. So this is not meant for production use.

See also


If you have any questions about the API, feel free to ask:
Dominik Mauchle.
Also, if you are using the API and want to be informed about updates, let me know.