580
edits
Route manager: Difference between revisions
Jump to navigation
Jump to search
→Concepts
| Line 10: | Line 10: | ||
==Concepts== | ==Concepts== | ||
The route-manager maintains a flight-plan, consisting of departure, destination, alternate airport and cruise information, as well as a list of waypoints | The route-manager maintains a flight-plan, consisting of departure, destination, alternate airport and cruise information, as well as a list of waypoints. All information is currently optional, which is highly unrealistic, but convenient. | ||
Route manager waypoints are entered as a navaid ident, an explicit latitude/longitude pair, or as an offset (bearing and distance) from another navaid. Each waypoint may also have an altitude associated with it, for vertical navigation modes (VNAV). In the future, other data, especially speed restrictions, may also be associated with waypoints. | Route manager waypoints are entered as a navaid ident, an explicit latitude/longitude pair, or as an offset (bearing and distance) from another navaid. Each waypoint may also have an altitude associated with it, for vertical navigation modes (VNAV). In the future, other data, especially speed restrictions, may also be associated with waypoints. | ||
Example waypoint definitions: | |||
;KJFK | |||
: airport identifier | |||
;UW | |||
: navaid identifier (NDB, VOR or a fix/interaction) | |||
;TLA/210/35 | |||
: offset from a navaid - in this example, the 210-degree magnetic radial from TLA VOR, 35 nautical miles out | |||
;WOBAD@18000 | |||
: WOBAD fix, at eighteen thousand feet altitude | |||
;SPL/050/12.3@2000 | |||
: 12.3 nautical miles from SPL VOR on the 050 magnetic radial, at two thousand feet | |||
==Defining a Route== | ==Defining a Route== | ||