292
edits
OpenRadarFeatureWishlist: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 6: | Line 6: | ||
* (by design) Callsign greater than 7 characters, cannot even have ICAO_TWR as callsign. Would like at least 10 | * (by design) Callsign greater than 7 characters, cannot even have ICAO_TWR as callsign. Would like at least 10 | ||
:(comment ww: The flightgear MP protocol supports only 7 chars (max. 7 chars plus trailing zero equals 8 bytes, see [[Multiplayer protocol]]) | :(comment ww: The flightgear MP protocol supports only 7 chars (max. 7 chars plus trailing zero equals 8 bytes, see [[Multiplayer protocol]]) | ||
::Well this should be fixed. What if multiple controllers | ::Well this should be fixed. What if multiple controllers control with similar callsigns? (E.g. LSZH_APP_EAST,LSZH_APP_WEST) | ||
* Inter ATC communication. Some method of talk/text just between ATC controllers would be nice, to coordinate handovers | * Inter ATC communication. Some method of talk/text just between ATC controllers would be nice, to coordinate handovers | ||
:(ww: yes, but as much as I know they use mumble right now... I am looking for a smart way to do this) | :(ww: yes, but as much as I know they use mumble right now... I am looking for a smart way to do this) | ||
| Line 13: | Line 13: | ||
* Wider radar range for CTR controllers (FGCom radio & visibility range) | * Wider radar range for CTR controllers (FGCom radio & visibility range) | ||
:ww:I need to validate, but to my current knowledge, FGCOM is restricted on server side and the contact visibility by the MP server. I thought already about a special mode for CTR, that registers OR as MP server (proxy). Then it would get all contacts worldwide. For FGCOM we could add these special frequencies to the list of frequencies that are available everywhere at the FGCOM server. | :ww:I need to validate, but to my current knowledge, FGCOM is restricted on server side and the contact visibility by the MP server. I thought already about a special mode for CTR, that registers OR as MP server (proxy). Then it would get all contacts worldwide. For FGCOM we could add these special frequencies to the list of frequencies that are available everywhere at the FGCOM server. | ||
* ( | * (IN WORK) Squawk / Transponder codes | ||
:ww: Are not part of the MP protocol => are not transfered to OpenRadar. | :ww: Are not part of the MP protocol => are not transfered to OpenRadar. | ||
* (MP data?) Private message feature | * (MP data?) Private message feature | ||
| Line 26: | Line 26: | ||
* Give the fullname of a VOR when going over it with the cursor (MLN = Melun, LGL = L'Aigle) as ATC and pilot use also VOR names in real life. (Do the same for Airports and NDB?) | * Give the fullname of a VOR when going over it with the cursor (MLN = Melun, LGL = L'Aigle) as ATC and pilot use also VOR names in real life. (Do the same for Airports and NDB?) | ||
* Direction finder: as we don't have flightplans yet, it would be useful to be able to find the direction from say XXXX to EDDF when sitting as ATC at XXXX so to find the best SID at XXXX. Maybe the search box at the bottom of the radar window could be able to find any apt/navaid point and indicate its distance and heading from the current airport one controls. | * Direction finder: as we don't have flightplans yet, it would be useful to be able to find the direction from say XXXX to EDDF when sitting as ATC at XXXX so to find the best SID at XXXX. Maybe the search box at the bottom of the radar window could be able to find any apt/navaid point and indicate its distance and heading from the current airport one controls. | ||
== Aircraft/Pilot Flag == | == Aircraft/Pilot Flag == | ||
* See assigned flightlevel (according to flightplan) | * See assigned flightlevel (according to flightplan) | ||
* ( | * (IN WORK) Squawk/Transponder Code | ||
* ( | * (IN WORK (transmitter support) "True" altitude according to local air pressure below transition level and flightlevel according to standard pressure (QNH 1013/2992) above transition level | ||
* (IN WORK) (MP data?) Red colored flags for emergency codes such as 7500 (hijack), 7600 (radio failure) and 7700 (general emergency MAYDAY, PAN PAN) | |||
* (MP data?) Red colored flags for emergency codes such as 7500 (hijack), 7600 (radio failure) and 7700 (general emergency MAYDAY, PAN PAN) | |||
== METAR == | == METAR == | ||
| Line 49: | Line 43: | ||
* separation rings (1000ft in vertical and 500ft in horizontal distance) | * separation rings (1000ft in vertical and 500ft in horizontal distance) | ||
* alerts for collision and speed violations | * alerts for collision and speed violations | ||
* (via Standard routes, have no other data source) Show Restricted, Prohibited and Danger Areas | * (via Standard routes, have no other data source) Show Restricted, Prohibited and Danger Areas | ||
* Accurate and up-to-date navigation data. (Some SID/STAR are not being displayed, because the navigation data is incomplete and inaccurate. - [[Talk:Airport data (apt.dat) update|See this thread]] and/or [http://github.com/mcantsin/x-plane-navdata/wiki this proposal].) | * Accurate and up-to-date navigation data. (Some SID/STAR are not being displayed, because the navigation data is incomplete and inaccurate. - [[Talk:Airport data (apt.dat) update|See this thread]] and/or [http://github.com/mcantsin/x-plane-navdata/wiki this proposal].) | ||
| Line 80: | Line 73: | ||
== Missing/incomplete FG MP protocol data == | == Missing/incomplete FG MP protocol data == | ||
* '''Squawk code''' | * (IN WORK)'''Squawk code''' | ||
* | * (IN WORK)'''local, airpressure dependent, altitude''', additional to the true altitude (as displayed in the airplane to show the FL above transition alt) | ||
* '''Active''', tuned in '''frequency''' (COM1/COM2): the '''tuned-in COM frequencies''', there is one for COM1, but it is not implemented, it delivers no data | |||
* the '''tuned-in COM frequencies''', there is one for COM1, but it is not implemented, it delivers no data | |||
* MP Chat Unicode support | * MP Chat Unicode support | ||
* MP Chat private message support | * MP Chat private message support | ||
: | [[Category:OpenRadar|FeatureWishlist]] | ||