API Documentation


At the moment, we provide two API's with two different formats: The Native JSON API provides the maximum detail of data. This also includes the original definition of shapes, which may not only consist of polygons, but also arcs (e.g. CTR Sion). Usually, geo-standards don't provide this possibility. So we defined our own (JSON-based) format, which we use internally and also provide as a Web API.

If you want to use a more standard-based API, we also provide data in GeoJSON format. Arcs are converted to polygons in this case. Further metadata and altitudes are provided in the properties object.


The V* (current V1) API's are stable and we won't break the endpoints and data structures. We might add new features/fields, but will not delete or rename any.

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.

Further options


Airspaces are automatically uploaded to the XContest airspace database. So you might also fetch the data from there. This is especially useful if you already have an XContest interface. Links will be published here, as soon as they are available.

What about OpenAir format?

With OpenAir, we could not provide the full dataset. For example, OpenAir only supports one type of altitude. But we want to provide altitudes in meters as well as in feet. So you get to choose which altitudes you want to use (check the API docs for more details). Furthermore, various navigation devices interpret the OpenAir format a bit differently and sometimes don't support all features or values (airspace types for example). That's why we don't provide OpenAir files. But we hope that manufacturers will convert the airspace data provided here or through XContest for optimal use with their devices.



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.