|This article is a stub. You can help the wiki by|
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.
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. 
See Complex Canvas Avionics for the main article about this subject.
See Canvas_News#G1000_.26_MapStructure_improvements for the main article about this subject.
Stuart committed some changes to update the Select Airport dialog to use Canvas MapStructure Layers to display airport information, rather than the now deprecated map layers. The change should be largely transparent to end users - the only significant change is that your can display navigation symbols. This is all part of a long-term effort to provide the building blocks for a Garmin G1000 - these layers could be used for the airport display on the MFD, and could easily be combined with the APS layer to show a moving aircraft.