Airspaces

Airspaces can be inspected, modified, imported or added on this page. They are visualized on the map of the logging page.

Unless a text filter has been specified all airspaces inside the database are listed. To manually add a new airspace touch the + symbol in the navigation bar. To delete one or more airspaces touch Edit. To inspect or modify data of an existing airspace touch the airspace's information symbol.

On the details view of an airspace the airspace's specification as well as other information can be found. Besides for informational purposes some of the data also fulfills other purposes. The airspace class for example also determines the color with which the airspace is shown on a map. In case of airspace classes 'A' to 'E' and 'R' the airspace is drawn in pink, 'P' and 'Q' in red, 'W' in green and classes 'F' and 'G' are drawn in light blue.

Before the height of an airspace can be entered the height's unit has to be specified. Afterwards an additional cell for the height value itself appears.

The airspace's area itself can either be a circle or its border can be specified by individual points that are connected with the next element by straight lines or by arc segments.

The easiest way to enter airspaces is to import airspace from files of the so called OpenAir format. These files can be downloaded from various places on the internet and then copied into the document folder of SkyLogger. These files show up after having touched in the navigation bar. When selecting one or more files their data is read and copied into the database.

Although the OpenAir format is the only popular format for specifying airspaces, the format is not well defined. This can lead to inconsistent data. SkyLogger will stop importing the data - an error message will be displayed - and no data from that particular file is being imported. The user has to modify the file before starting another attempt to import the file. If a file has been parsed successfully, all airspaces are added to the database.

Remark: SkyLogger only supports ASCII or UTF-8 encoded text files! If other encodings are used, the names of airspaces having characters outside the English character set will be incorrectly spelled.