580
edits
Route manager: Difference between revisions
Jump to navigation
Jump to search
→Concepts
mNo edit summary |
|||
| Line 8: | Line 8: | ||
==Concepts== | ==Concepts== | ||
The route-manager | The route-manager maintains a flight-plan, consisting of departure, destination, alternate airport and cruise information, as well as a list of waypoints (technically, route segments, or legs). A flight plan must have a departure airport and destination airport specified; all other 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). | 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. | ||
==Defining a Route== | ==Defining a Route== | ||