back start next

Maps - Airspace

Cumulus supports two different source formats:

as database for airspaces.

OpenAir

OpenAir files must be downloaded manually from the Internet and installed in Cumulus. Addesses where you can find OpenAir airspace files are:

openAIP

openAIP airspace files can be found on the openAIP website, where this project is hosted. The download and installation of openAIP airspace files is supported by Cumulus. See here for further help.

Installation Directory

Just put your airspace files in the directory .../maps/airspaces and make sure, that OpenAir files have the .txt extension while openAIP files uses the .aip extension. The extension spelling is not case sensitive for .txt files.

Because you can have a lot of airspace files in the airspace directory, maybe one for every country, it is useful to define, which files should be loaded only to save run-time memory. That can be done in the configuration setup for Airspaces. Press the Load button on that page and select the airspace files in the displayed list to be loaded.

Mapping Services

Certain OpenAir/openAIP airspace elements are not unique mapable to Cumulus airspace elements. Therefore Cumulus provides additional mapping services. The mapping files must be placed in the same directory as the airspace files are installed. Their rules overwrite the default Cumulus mapping rules.

Global Mapping File

The global mapping file is applied first to all read airspace file. The name of the file is airspace_mappings.conf.

Special Mapping Files

Special mapping files can be applied only once to a related airspace file. Such a file consists of the basename of the airspace file without the extension .txt or .aip, extended by the string _mappings.conf.

Example: SourceFile=openair.txt, MappingFile=openair_mappings.conf

Cumulus knows the following airspace types:

The syntax used in the mapping file is very simple. Lines starting with # or * are ignored and can be used for comments. Empty lines are also ignored. The rest of the lines should contain entries in the form key = value, one entry per line. The key is the airspace type in the OpenAir/openAIP file you wish to map, and the value is the corresponding Cumulus type you wish to assign.

Default mapping for OpenAir

Default mapping for openAIP

Note! You only need to define the values you actually want to change in the read airspace file. These instructions will overwrite the default mappings.

Example: CTR=AirC

This statement changes the default assignment for Control Zone to Airspace C.

Remember that the mapping definitions are case-sensitive! Otherwise the mapping rules will fail.

back start next