652
edits
OpenRadarGuide: Difference between revisions
Jump to navigation
Jump to search
→Runway Settings
m (→COM-Radios: add links) |
|||
| Line 336: | Line 336: | ||
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]] | [[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]] | ||
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]] | [[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]] | ||
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions | Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions. See e.g. the pictures on the right: | ||
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values | *From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values <small>''(see the picture "The Runway Manager Settings" below)''</small>. You open these settings by a right-mouse-click onto the runway-number ''(in the following describtion we clicked onto the "07R" in EDDF)'': | ||
**In the header line you see left the now chosen runway to be edited, and at the | **In the header line you see left the now chosen runway to be edited, and at the right a button "'''''Copy to All'''''". With this button you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 runways you can save a lot of time! With that copy only the numeric-values will be changed - all the selection-markers will remain as are in each unique setting table. ''<small>(e.g. the length-definitions will be copied for all - the markers "Landing" will remain unique!)</small>''. These settings will then be saved separately for each unique runway and airport in you private settings. | ||
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you | **With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you may | ||
::: | :::'''may not''' use runway 36 at all --> thus disable both lines: All data for that runway disappear | ||
::: | :::'''may only''' use runway 18, 07L, and 25R for "Landings" --> thus disable only "Landing": Just the "Land"-Option disappears | ||
:::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small> | :::<small>''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.</small> | ||
:*The "'''''Extended center line'''''" | :*The "'''''Extended center line'''''" are the blue lines you see in the picture "Typical runway/approach definitions" [[File:OpenRadar-Approach.png|thumb|right|250px|Typical runway/approach definitions]] at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"! | ||
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''. | :*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''. | ||
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in | :*"'''''Vectoring and base leg'''''" define that funnel that you also see in that picture ''"Typical runway/approach definitions"''. Also this will be shown only for the "Landing" runways. | ||
<br> | |||
Finally your picture will look similar to the right/above shown "The Runway Manager"! | |||
*In that one you see from left to right the following informations for each runway: | |||
:*The runway-name | :*The runway-name | ||
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L) | :*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L) | ||
:*A second check-box to display SID/STAR graphics for that runway <small>(if they are defined, check for them in .../OpenRadar/data/routes/''ICAO''/''ICAO''.xml)</small>. | |||
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar! | :*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar! | ||
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the Status Informations)</small> | :*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! <small>(Remember: You find the normal wind values in the METAR-data further up in the [[Status Informations]])</small> | ||
:*To the right follows | :*To the right follows | ||
::*in the upper line the exact runway heading (as needed for older type autopilots) | ::*in the upper line the exact runway heading (as needed for older type autopilots) | ||
::*in the lower line the length and width of the runway in feet! | ::*in the lower line the length and width of the runway in feet! | ||
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold. | :*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold. | ||
After you have defined all runways and activated your choice of active runways, you will exit the "Runway Manager" by moving the mouse-pointer out of it. Then the "Runway Manager" will reduce and show only the active runways. <small>(You may move the mouse very fast - then all runways remain visible)</small>. Click into that remaining "Runway Manager" to show again all runways. | |||
====='''Flight Strip Manager'''===== | ====='''Flight Strip Manager'''===== | ||