580
edits
Route manager: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 3: | Line 3: | ||
==Introduction== | ==Introduction== | ||
The route-manager models part of the functionality found in real-world GPS and FMS devices, but is usable in any aircraft. Some panel instruments may provide access to the route manager via their own UI, but the route-manager is always available through a generic dialog box. The route-manager is also | (in the following sections, familiarity with basic IFR concepts, autopilot usage and radio navigation is assumed) | ||
The route-manager models part of the functionality found in real-world GPS and FMS devices, but is usable in any aircraft. Some panel instruments may provide access to the route manager via their own UI, but the route-manager is always available through a generic dialog box. The route-manager is also how a flight plan is made available to FlightGear - in the future this will hopefully permit better ATC and multi-player interactions, since ATC logic or controllers will be able to observe the filed plan associated with a pilot. | |||
==Concepts== | ==Concepts== | ||
The route-manager tracks flight-plan, consisting of departure, destination, alternate 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. | The route-manager tracks 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). | ||