FG1000: Difference between revisions
Line 3: | Line 3: | ||
== Motivation == | == Motivation == | ||
{{Main article|Canvas_News#Moving_map.2FRNAV_discussion}} | {{Main article|Canvas_News#Moving_map.2FRNAV_discussion}} | ||
The enormous variety in current glass flight decks means we really need to think of a new way of defining glass cockpit layouts.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/15602744/ | |||
|title = <nowiki> Re: [Flightgear-devel] Glass cockpit and external gauges. </nowiki> | |||
|author = <nowiki> Robin van Steenbergen </nowiki> | |||
|date = Oct 2nd, 2007 | |||
|added = Oct 2nd, 2007 | |||
|script_version = 0.40 | |||
}}</ref> | |||
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. <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35924395/ | |||
|title = <nowiki> [Flightgear-devel] RFD: FlightGear and the changing state of air | |||
navigation </nowiki> | |||
|author = <nowiki> David Megginson </nowiki> | |||
|date = Jul 3rd, 2017 | |||
|added = Jul 3rd, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
== Background == | == Background == | ||
{{Main article|Complex Canvas Avionics}} | {{Main article|Complex Canvas Avionics}} |
Revision as of 09:37, 15 October 2017
This article is a stub. You can help the wiki by expanding it. |
Motivation
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
See Complex Canvas Avionics for the main article about this subject. |
Status
See Canvas_News#G1000_.26_MapStructure_improvements for the main article about this subject. |
Related
References
|