Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

FG1000

From FlightGear wiki
Revision as of 04:37, 15 October 2017 by Hooray (Talk | contribs) (Motivation)

Jump to: navigation, search
This article is a stub. You can help the wiki by expanding it.

Motivation

1rightarrow.png See Canvas_News#Moving_map.2FRNAV_discussion for the main article about this subject.

The enormous variety in current glass flight decks means we really need to think of a new way of defining glass cockpit layouts.[1]


The airspace system is in the process of changing drastically [...] this isn't just a matter of throwing up a canvas showing some GPS waypoints and a magenta line. Modern navigators are astoundingly-complex devices — probably an order of magnitude more lines of code than FlightGear itself — and even their basic flight planning algorithms and databases (e.g. fly-by waypoints vs fly-over waypoints, open vs closed approach procedures, transitions into RNAV approaches, etc.) are far beyond the scope of anything we've tried, and we'd also need an up-to-date database far more complex than the ones we have now. Once you get to the extra features, like FIS-B weather or TIS-B traffic info over ADS-B, or TAWS (terrain alerting), we're probably in way over our heads trying to emulate even the simplest general-aviation IFR GPS.

Depending on how we deal with this challenge, the question is whether that means that the usefulness of FlightGear will also gradually taper off. [2]

Background

1rightarrow.png See Complex Canvas Avionics for the main article about this subject.

Status

1rightarrow.png See Canvas_News#G1000_.26_MapStructure_improvements for the main article about this subject.

Related

References