272
edits
Navdata cache: Difference between revisions
m
fix $FG_HOME hyperlink
(Reordering some sections; More details on some known issues and how to solve them; Non-camel case headings) |
Hamzaalloush (talk | contribs) m (fix $FG_HOME hyperlink) |
||
| Line 3: | Line 3: | ||
[[File:Fghome.png|400px|right|Screen shot showing structure of [[$FG_HOME]] ]] | [[File:Fghome.png|400px|right|Screen shot showing structure of [[$FG_HOME]] ]] | ||
The '''navdata cache''', '''navdb''', (sometimes also '''navcache''') is automatically built by FlightGear during startup by parsing/processing the gzipped <code>nav.dat</code> file and building a spatial SQLite-based database in $FG_HOME so that more efficient queries can be run at run-time, but, in particular when starting up/[[Reset & re-init|re-initializing FlightGear]]. | The '''navdata cache''', '''navdb''', (sometimes also '''navcache''') is automatically built by FlightGear during startup by parsing/processing the gzipped <code>nav.dat</code> file and building a spatial SQLite-based database in [[$FG_HOME]] so that more efficient queries can be run at run-time, but, in particular when starting up/[[Reset & re-init|re-initializing FlightGear]]. | ||
Memory consumption is also lower, since we don't keep airports / fixes / taxiways / runways in memory until they're needed. | Memory consumption is also lower, since we don't keep airports / fixes / taxiways / runways in memory until they're needed. | ||