7
edits
Stand Alone ATC Control Development: Difference between revisions
Jump to navigation
Jump to search
Stand Alone ATC Control Development (view source)
Revision as of 07:54, 3 December 2010
, 3 December 2010→The ideal ATC client
mNo edit summary |
|||
| Line 218: | Line 218: | ||
*Taxiways | *Taxiways | ||
*Extended runway centerlines | *Extended runway centerlines | ||
*Higher and lower air routes | |||
*Geographic elements: water, coastlines | *Geographic elements: water, coastlines | ||
*Range rings | *Range rings | ||
| Line 230: | Line 231: | ||
All this in a non-distracting way for the controller. | All this in a non-distracting way for the controller. | ||
All those elements should be read from the FlightGear Scenery, so that pilots and controllers share the same data. | All those elements should be read from the FlightGear Scenery (except range rings), so that pilots and controllers share the same data. That will pose the need to add some elements to the FG scenery. | ||
'''Voice:''' FGCom as external application is OK. | '''Voice:''' FGCom as external application is OK. | ||