Log files of Little Navmap are stored in the directories:
The program keeps three log files and rotates these on each startup if the file size of 10 MB is exceeded. So you may find up to three logs:
Send the log file
abarthel-little_navmap.log if you like to report an error.
Please compress the log file using ZIP when sending per email.
All configuration files for my programs are stored in these directories:
Linux and macOS:
little_navmap.ini: INI style configuration file. Text file.
little_navmap.history: The map position history. Binary file.
little_navmap.track: The user aircraft trail. Binary file.
little_navmap_profile.track: User aircraft trail for the elevation profile. Binary file.
Three more configuration files are created for customization of colors and styles:
little_navmap_fusionstyle.ini: INI style configuration file for customizing the GUI colors of the style
little_navmap_nightstyle.ini: As above but for the style
little_navmap_mapstyle.ini: INI style configuration file. Text file. Used for customization of the map display.
See Customization for more information.
Note that Little Navmap might reset these files when updated, but only after creating backup files. This is usually mentioned in the change log.
The disk cache that is used to store all the downloaded online map tile images can be found here:
- Linux and macOS:
You can delete the cache manually to save space if Little Navmap is not running.
Databases are stored in the directories:
- Linux and macOS:
Do not modify, move, rename or delete databases while Little Navmap is running.
Do not let the Navigraph FMS Database Manager update databases while Little Navmap is running. Little Navmap might crash, the update might fail or remain incomplete.
The number of files depends on which simulators you have installed and which scenery libraries you've loaded.
The files are:
little_navmap_.sqlite: An empty dummy database.
little_navmap_fsx.sqlite: Flight Simulator X
little_navmap_fsxse.sqlite: Flight Simulator - Steam Edition
little_navmap_p3dv2.sqlite: Prepar3D v2
little_navmap_p3dv3.sqlite: Prepar3D v3
little_navmap_p3dv4.sqlite: Prepar3D v4
little_navmap_xp11.sqlite: X-Plane 11
little_navmap_navigraph.sqlite: Navigraph navdatabase. Can be either the included database or an update installed by the Navigraph _FMS Data Manager.
little_navmap_userdata.sqlite contains the user-defined waypoints.
Little Navmap creates a backup copy on startup and keeps up to four backup files:
little_navmap_userdata_backup.sqlite.3. You can copy these files back to the original database
little_navmap_userdata.sqlite if you did something wrong.
little_navmap_userairspace.sqlite contains the user-defined airspaces read by using Load User Airspaces.
It is backed up in the same way as the userdata.
little_navmap_logbook.sqlite is used to store logbook entries.
Little Navmap creates backup copies on startup and keeps up to four backup files as for the user-defined waypoints as described above.
Other Database Files
Additional files like
are used by temporary processes like the database compilation or online network data. These can be ignored.
Annotated Flight Plan File Format
Little Navmap uses the FSX/P3D XML flight plan format. The XML standard allows to add comments in a file which are ignored by the simulators and by most add-on programs.
The added comment is an XML comment starting with
<!-- LNMDATA and ending with
-->. Inside the comment is a simple key/value list separated by
Little Navmap stores metadata like version and date in the file which helps when reporting errors or for future extensions.
The most important data is alternate airports and procedure information which allows the program to restore SIDs, STARs, approaches and transitions in an error tolerant way when loading flight plans.
Use Export as Clean PLN if a program is not capable of reading the annotated files.
"1.0" encoding="UTF-8" xml version=<SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <!-- LNMDATA _lnm=Erstellt mit Little Navmap Version 2.2.1.beta (Revision 257538e) am 2018 11 05T20:20:11| aircraftperffile=C:\Users\alex\Documents\Little Navmap\Boeing 737-200 JT8D-15A.lnmperf| aircraftperfname=Boeing 737-200| aircraftperftype=B732| approach=LITSI| approacharinc=D34| approachdistance=11.9| approachrw=34| approachsize=9| approachsuffix=| approachtype=VORDME| cycle=1811| navdata=NAVIGRAPH| sidappr=MARE5W| sidapprdistance=28.2| sidapprrw=22| sidapprsize=5| simdata=XP11| star=ASTU2D| stardistance=128.4| starrw=34| starsize=5| transition=ZAK| transitiondistance=17.5| transitionsize=3| transitiontype=F --> <FlightPlan.FlightPlan> ... </FlightPlan.FlightPlan> </SimBase.Document>
Aircraft Performance File Format
lnmperf files are simple text files and use the Windows-
INI style that has groups in square brackets and
key=value lines. See here for more information about this type of configuration files.
Speed units are always knots and feet per minute. Fuel units are gallons or lbs depending on the value of
ContingencyFuelPercent is percent which will be added to trip fuel.
Description has to be enclosed in double quotes.
\n are interpreted as line feeds.
Note that comments starting with
; will be replaced when saving the file in Little Navmap. You can add a dummy key like
Comment1=my remarks to circumvent this. Unknown keys are not replaced when saving.
[Options] AircraftType=B732 Description="Engine type JT8D-15A\n\nClimb: 92% N1, 280/0.7\nCruise: 0.74\nDescent: 0.74,300\n\nhttps://example.com/dokuwiki/doku.php?id=boeing_737-200_reference" FormatVersion=1.0.0 FuelAsVolume=false JetFuel=true Metadata=Created by Little Navmap Version 2.2.0.beta (revision 16944ce) on 2018 11 02T20:23:52 Name=Boeing 737-200 ProgramVersion=2.2.0.beta [Perf] ClimbFuelFlowLbsGalPerHour=10000 ClimbSpeedKtsTAS=350 ClimbVertSpeedFtPerMin=1500 ContingencyFuelPercent=0 CruiseFuelFlowLbsGalPerHour=4800 CruiseSpeedKtsTAS=430 DescentFuelFlowLbsGalPerHour=400 DescentSpeedKtsTAS=420 DescentVertSpeedFtPerMin=2500 ExtraFuelLbsGal=0 ReserveFuelLbsGal=6000 TaxiFuelLbsGal=500