back | start | next |
Cumulus uses the following sets of maps:
The maps can be installed at two different places:
Please Note! The map files have to be stored in different subdirectories under the root map path.
You must create these subdirectories alone under the map root.
If the maps are installed outside of the known locations, e.g. on a SD card at your Internet Tablet, you must setup the path to the new map root directory in the Map Settings configuration page (Setup->General Setup->Map Setting). Use the Maps button to navigate to the appropriate root directory under which the expected maps subdirectories are to find. Is nothing is setup the maps are searched only under the default location. But this directory is unsuitably for the Nokia Internet Tablet due to no access via an USB connection and the limited space at the home file system.
Do only load the airfields and do install the airspace maps for the area you need. This will make Cumulus faster and saves runtime memory. The Ground and Terrain Maps maps are not concerned of that. If you experience memory problems running Cumulus, you can choose not to install certain map sets. You could for instance skip the terrain maps. This will disable the display of terrain features (the isolines) but it will also save memory and reduce map loading and drawing time. It is advisable at least to use the Ground maps because you will end up with a blue background otherwise, which is not very helpful in navigation.
The maps you install are not projected. This is done on loading. Because this is a computationally complex operation, the resulting maps are stored again with a .kfc or .txc extension. For many maps, these files are a bit smaller than the original files. The next time Cumulus needs to load the file, it first tries to load this compiled file to improve speed. In the Map Settings page you can modify the behaviour of Cumulus for map projection and map compilation.
OpenAir SUA map files
Cumulus supports the commonly available OpenAir SUA file format for airspaces. Just put the map files in the subdirectory airspaces and make sure they have the .txt extension written in lower letters.
In addition to the OpenAir files themselves, you can add a file to configure the mapping of airspace types from the OpenAir file to the types Cumulus uses. Cumulus knows the following types:
Example: Sourcefile=openair.txt, Mappingfile=openair_mappings.conf
The mapping file must be placed in the same directory as the OpenAir file is contained. The used syntax in the file is simple. Empty lines and lines starting with # or * are ignored and can be used for comments. 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 file you wish to map and the value is the corresponding Cumulus type you wish to assign. The default mappings are:
You only need to define the values you actually want to change in the file. These instructions will overwrite the default mappings.
Example: CTR=ControlD
This statement changes the assignment ControlC to ControlD.
Consider that the mappings are case sensitive!
Usage of Welt2000 airfield and outlanding data
Cumulus uses for airfields and outlandings the Welt2000 data base. These data were created by Michael Meier, called Milomei, as one big file here.
Just install this file in the subdirectory airfields and make sure that it carries the name welt2000.txt. Because a welt2000.txt file covers the whole world, the amount of data to be read in must be limited in a useful kind. Cumulus provides for that two ways:
One disadvantage of Welt2000 is that it knows only three types of airfield elements (Airfield, Glider Field, Ultra Light Field) but cumulus a lot more. This lack can be overcome by an additional provided mapping. You can map short names or ICAO identifiers of the Welt2000 file entries into other cumulus map elements by using a simple syntax to be defined in a configuration file. The configuration file has to carry the name welt2000.conf and must be located in the same directory where the source file welt2000.txt is to find. The file provides the following syntax:
Short example of a welt2000.conf file:
# Example of a welt2000.conf file, starting with a comment
line
$ This is also a comment line
#
# Now follows a country filter definition rule
# Only the coutries Germany, Poland and Czechia will be extracted from
the welt2000.txt source
FILTER countries=de,pl,cz
#
# Now follows an ICAO identifier mapping rule
# The german airport Berlin-Schönefeld is mapped at an
international airport element
MAP_ICAO EDDB=IntAirport
#
# Now follows a short name mapping rule
# The german military airport Holzdorf is mapped at a military airport
element
MAP_SHORT_NAME HOLZD1=MilAirport
Please note the following! If a new welt2000.txt file has been installed the first run of cumulus after that needs a longer time (ca. 10-20 seconds) to extract the desired data from it. Cumulus generates a compressed file of the extracted data reuseable by further runs of it. This file carry the name welt2000.txc and will be reused, so long the original source, the configuration file, the map projection or the home position are not changed. This behavior minimize the read in time after a restart.
If you make necessary corrections on the data of the Welt2000 file, please report all your changes to the guys, who do maintain the source. Their email address is to find in the header part of the Welt2000 file or at this page. We all should help to keep up to date the Welt2000 source and thanks the guys who do this work.
back | start | next |