292
edits
No edit summary |
(Adapted to status after todays update) |
||
Line 9: | Line 9: | ||
* 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) | ||
* 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. | ||
* ( | * (DONE) 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 25: | Line 23: | ||
::mc: Yes. compare with VRC (VatSim Virtual Radar Client), which has a recording option and EuroScope which does generate if from recorded fragments. - Text to speech (Espeak/Festival) integration would be the "tripple-A" feature!1!! ;) | ::mc: Yes. compare with VRC (VatSim Virtual Radar Client), which has a recording option and EuroScope which does generate if from recorded fragments. - Text to speech (Espeak/Festival) integration would be the "tripple-A" feature!1!! ;) | ||
* 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?) | ||
:ww: technically possible, but tooltips disturb usability very much. Please open a thread in forum and discuss is with the users! | |||
* 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) | ||
* ( | * (DONE) Squawk/Transponder Code | ||
* ( | * (DONE (transmitter support) "True" altitude according to local air pressure below transition level and flightlevel according to standard pressure (QNH 1013/2992) above transition level | ||
* ( | * (DONE) Red colored flags for emergency codes such as 7500 (hijack), 7600 (radio failure) and 7700 (general emergency MAYDAY, PAN PAN) | ||
== METAR == | == METAR == | ||
* METAR of nearby airports | * METAR of nearby airports | ||
== Messages == | == Messages == | ||
== Radar Map == | == Radar Map == | ||
* 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 | ||
Line 53: | Line 50: | ||
== FGCom Integration == | == FGCom Integration == | ||
* Add "set PTT button" feature | * Add "set PTT button" feature | ||
== ATC Coordination == | == ATC Coordination == | ||
* coordinate multiple instances of OpenRadar using a protocol a la VatSim (ww: this will work only for OpenRadar instances, not to ATC-ML, ATC-TOWER etc...) | * coordinate multiple instances of OpenRadar using a protocol a la VatSim (ww: this will work only for OpenRadar instances, not to ATC-ML, ATC-TOWER etc...) | ||
* (mp data) see what frequencies | * (mp data) see what frequencies other ATC's are using | ||
:ww: I transmit the first frequency via FGCOM protocol, but do not display it yet, because the FG frequencies are set to a fix value. | :ww: I transmit the first frequency via FGCOM protocol, but do not display it yet, because the FG frequencies are set to a fix value. | ||
* Hand-off feature | * Hand-off feature | ||
Line 67: | Line 60: | ||
:* "owning" and aircraft according to the flight strip | :* "owning" and aircraft according to the flight strip | ||
:* See on the map what regions are "controlled" by who (dark grey if an area is controlled, so the ATC knows to whom he can do the handoff) | :* See on the map what regions are "controlled" by who (dark grey if an area is controlled, so the ATC knows to whom he can do the handoff) | ||
* See & edit the flightplan | * See & edit the flightplan | ||
::ww: Suggest central registration for this. | ::ww: Suggest central registration for this. | ||
== Missing/incomplete FG MP protocol data == | == Missing/incomplete FG MP protocol data == | ||
* '''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 | * '''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 | ||
* MP Chat Unicode support | * MP Chat Unicode support |
edits