52. Loading Airspaces
Airspaces are loaded from the Navigraph database, simulator database, a user defined directory or online flying services.
You can select airspaces to show in the main menu
Scenery Library -> Airspace Libraries.
52.1. FSX, Prepar3D and MSFS Airspaces
Little Navmap reads all airspaces from the scenery library of FSX, P3D and MSFS. These airspaces
are added in the airspace source
52.2. Airspace Formats
Little Navmap can read three airspace formats from a user defined directory.
See Airspace Libraries for more information on airspace sources.
Little Navmap can read OpenAir airspaces (OpenAir airspace format) from X-Plane or an user defined directory.
Note that the publicly available airspace files can contain errors which may prevent the loading of an airspace file. These hard errors are reported after loading the scenery library. Other errors only affecting single airspaces or the geometry are reported in the log file only.
Additional airspace files can be downloaded from the OpenAirspace Directory, Soaring Services, openAIP or Luftraumdaten Deutschland, for example.
Airspace files must have a
.txt extension and are loaded from the
following directories by Little Navmap:
The files can be encoded in any
UTF format but must have
a BOM to be
recognized properly. Otherwise Windows ANSI coding (
used. Special characters like umlauts or accents are not displayed
correctly in names if the encoding is not correct. All other
functionality is unaffected.
You can convert the files using any advanced editor like Notepad++ for example.
Airspaces will appear as duplicates in the map if an airspace file is found in more than one of these directories or sources.
Airspace types recognized in OpenAir format:
A: Class A
B: Class B
C: Class C
D: Class D
E: Class E
F: Class F
G: Class G
GP: Glider prohibited
W: Wave Window
RMZRadio Mandatory Zone / Class G
TMZ: Transponder Mandatory Zone / Mode C
Internal airspace types:
Little Navmap passes an airspace type through to its scenery library database if it is not one of the recognied types above. This means you can additionally use these types which are only recognized by Little Navmap:
CA: Class A
CB: Class B
CC: Class C
CD: Class D
CE: Class E
CF: Class F
CG: Class G
NP: National park
GCA: Control area
GP: Glider prohibited
Further formats for online airspaces are GEOJSON which can be downloaded for VATSIM boundaries at the VATSpy Data Project.
The extension is
52.2.3. IVAO JSON
IVAO boundaries in JSON format can be downloaded at Little Navmap Downloads - Airspace Boundaries.
The extension is
52.3. X-Plane Airspaces
X-Plane 11 and 12 come with a single airspace file that can be found in
Little Navmap reads X-Plane airspaces from the following locations:
These airspaces are added to airspace source
52.4. User Airspaces
These airspaces are added in the airspace source
User. You can load
them by selecting
Scenery Library -> Load User Airspaces.
Airspaces read with this function will be added to the airspace source
User and are stored in a database independent of flight simulator
52.5. Online Airspaces
Online centers are displayed as circular airspaces in Little Navmap per default and provide the same functionality as the other airspaces (tooltips, information and more). They are loaded with the online data when connected and are only stored in a temporary database which is deleted on exit.
Little Navmap can use real center boundaries instead of the circular
airspaces. First you have to enable one or both options in Map Display Online under
Online Center Boundary Lookup in User Airspaces. These are enabled
There are two options:
Create an OpenAir airspace file which contains a single boundary for a center. Give the file the same name as the callsign for the center, i.e. name the file
EDDB_TWR.txtfor the center with the callsign
Create an OpenAir airspace containing the boundaries for all the centers you need. Give the file any name but name the boundaries according to the callsign of the centers. You need a line in the file containing
AN= airspace name) to use the boundary for a center with the callsign
Now place the file or files into you user airspace directory and reload the user airspaces. See above User Airspaces how to do this.
Once done the center should show the correct boundary.