OpenRadarFeatureWishlist: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
 
(29 intermediate revisions by 5 users not shown)
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 controll with similar callsigns? (E.g. LSZH_APP_EAST,LSZH_APP_WEST)
::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
:(ww: yes, but as much as I know they use mumble right now... I am looking for a smart way to do this)
* Make it not working at FG's [[KSFO|default airport]] (to guard against heart attacks on trying-to-be-KSFO-police people).
:ww: We are living in a free world of free software. Its like forbidding aircrafts at an airport. I have seen pilots missing all decency and mad ATC guys. We cannot lock them out without creating a closed environment... No, that is not the way it should be done... If someone wants to disturb he still can use aircrafts or the different ATC-models out there...
* (done: SHIFT+F12) The ability to reload the airport without having to restart the whole application. This is while I am developing Routes, it's a pain to constantly have to restart the entire thing.
:(ww: yes, pretty useful, I think about it. Reloading the routes would be enough I think...)
* Wider radar range for CTR controllers (FGCom radio & visibility range)
* Wider radar range for CTR controllers (FGCom radio & visibility range)
* Squawk / Transponder codes
: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.
* Private message feature
* Intercom FGCom frequency call GND to GND to call other ATC's
* Controlling multiple airports (CTR controller)
* Controlling multiple airports (CTR controller)
* Enable "contradictory" runway setting. (E.g. The common setting in [http://www.cats.com.kh/siem-reap-airport.php VDSR], - in real life, - [http://www.cats.com.kh/atis.php is rwy 23 for departure and 05 for landing], which seems contradictory but is the commonly used configuration.)
:ww: To be able switch some features from airport to airport (METAR, runways, FGCOM, StdRoutes) I need to rework some parts of the application (relocation of OR multiplayer client to new airport, loading of different METAR, runways, routes etc). It would work like an hopping from airport to airport. Something for future releases, I think.
* ATIS recording feature
* ATIS recording feature
:ww: Recording and then replay over the ATIS frequency? This might be possible.
::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?)
:ww: technically possible, but tooltips disturb usability very much. Please open a thread in forum and discuss is with the users!
* Traffic counter
* Allow IAPs to be shown separate to SIDS / STARS


== Aircraft/Pilot Flag ==
== Aircraft/Pilot Flag ==
* See assigned flightlevel (according to flightplan)
* See assigned flightlevel (according to flightplan)
* Squawk/Transponder Code
* "True" altitude according to local air pressure below transition level and flightlevel according to standard pressure (QNH 1013/2992) above transition level
* Red colored flags for emergency codes such as 7500 (hijack), 7600 (radio failure) and 7700 (general emergency MAYDAY, PAN PAN)
* Voice, Text ability of Pilot (FGCom)


== METAR ==
== METAR ==
* Winds below 100 degrees with preceeding 0/00, so that wind directions are read in 3 numbers. (E.g. wind 9@3 is read as "wind zero-zero-niner at tree")
* METAR of nearby airports => right click on the METAR lines and define them.
* METAR of nearby airports
 
* Full METAR code
== Messages ==


== Radar Map ==
== Radar Map ==
* show more ground detail (data source?)
* 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
* an alarm for when new aircraft enter the area so that when you are busy doing something else while waiting for someone to come into your area you will be notified
* additional deselect button below the map
* Show Restricted, Prohibited and Danger Areas
* (via Standard routes, have no other data source) Show Restricted, Prohibited and Danger Areas


== Route Editing ==
== Route Editing ==
* (done: syntax <code><addPoint code="AGOLO" point="50.200000,9.676111"/></code> ) Ability to specific locally specific points. Rather than hacking the Apt.dat.tgz file, adding to say nav.xml within folder. Additionally these points should be in the form of existing points notification and searched first before globals
* Speed limitation point tag for Elements, similar to the arrows. Requires text for speed. (ww: the attribute <code>text=""</code> is not enough?)
* Speed limitation point tag for Elements, similar to the arrows. Requires text for speed. (ww: the attribute <code>text=""</code> is not enough?)
* (done: example: <code>begin="KOAK-RW29"</code>) The ability to reference runway start and end as nav points
* Loop - allow standard / non-standard loop - e.g. https://i.imgur.com/1IA0TFB.png


== Radar Contact handling ==
== FGCom Integration ==
== FGCom Integration ==
* (Done) Remove CTRL as PTT button, clashes with CTRL-Left click for "neglect", suggest Right Shift (ww: but the right hand is occupied with the mouse. maybe we move the neglected key to the right SHIFT. SH: If using FGcom, most of the time there would be no need to use anything but single key presses, so therefore any button would be fine. Remember LShift is the primary key for PTT2. Fn keys?)
* Add "set PTT shortcut key" feature
:ww: removed CTRL+CLICK, there is a textbutton above the flightstrips now, to toggle neglect
* Change volume of fgcom channel
* Add "set PTT button" feature
 
=== Missing/not working frequencies ===
* 118.10 seems not to work at LSZH TWR. - Maybe there is a collision with the frequency of another airport?
* LSZH_DEL missing Delivery frequency 121.920
* LSZH_GND missing APRON frequencies 121.850
* LSZH_APP missing Approach frequencies 118.0, 120.750, 119.7
* LSZH_DEP missing Departure frequency 125.950


== 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...)
* see what frequencies othe ATC's are using
* (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.
* Hand-off feature
* Hand-off feature
:* See to which frequency the Pilot is connected to (com1 & com2)
:* (mp data) See to which frequency the Pilot is connected to (com1 & com2)
:* "owning" and aircraft according to the flight strip
::ww: the frequency transmitted by FG via MP is not correct, is already implemented in background)
:* 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)
:* Assigning squawk code to the flightstrip
 
* See & edit the flightplan
== 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
* MP Chat Unicode support
* MP Chat private message support
==TTS Support==
By [[User:Legoboyvdlp|Legoboyvdlp]] ([[User talk:Legoboyvdlp|talk]]) 10:32, 20 April 2015 (EDT)
Hi. I would like to see in the future TextToSpeech support with the ordinary chatbox, over FGCOM.
*ATIS- one would say Welcome... TTS in use... Please use (arpt frequency) for ALL services incl. ATIS. A pilot would tune in, and one would listen to their "Hello XXXX ATC" and then one would press a button to auto calculate what the ATIS is IRL or define your own by typing or a dialog box
One would use the . Commands and it would "talk" over FGCOM
possible?


[[Category:OpenRadar|FeatureWishlist]]
[[Category:OpenRadar|FeatureWishlist]]

Latest revision as of 11:23, 5 December 2018

Back to mainpage

This page collects the feature proposals for OpenRadar.

General

  • (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)
Well this should be fixed. What if multiple controllers control with similar callsigns? (E.g. LSZH_APP_EAST,LSZH_APP_WEST)
  • 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.
  • Controlling multiple airports (CTR controller)
ww: To be able switch some features from airport to airport (METAR, runways, FGCOM, StdRoutes) I need to rework some parts of the application (relocation of OR multiplayer client to new airport, loading of different METAR, runways, routes etc). It would work like an hopping from airport to airport. Something for future releases, I think.
  • ATIS recording feature
ww: Recording and then replay over the ATIS frequency? This might be possible.
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?)
ww: technically possible, but tooltips disturb usability very much. Please open a thread in forum and discuss is with the users!
  • Traffic counter
  • Allow IAPs to be shown separate to SIDS / STARS

Aircraft/Pilot Flag

  • See assigned flightlevel (according to flightplan)

METAR

  • METAR of nearby airports => right click on the METAR lines and define them.

Messages

Radar Map

  • separation rings (1000ft in vertical and 500ft in horizontal distance)
  • alerts for collision and speed violations
  • additional deselect button below the map
  • (via Standard routes, have no other data source) Show Restricted, Prohibited and Danger Areas

Route Editing

  • Speed limitation point tag for Elements, similar to the arrows. Requires text for speed. (ww: the attribute text="" is not enough?)
  • Loop - allow standard / non-standard loop - e.g. https://i.imgur.com/1IA0TFB.png

FGCom Integration

  • Add "set PTT shortcut key" feature
  • Change volume of fgcom channel

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...)
  • (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.
  • Hand-off feature
  • (mp data) See to which frequency the Pilot is connected to (com1 & com2)
ww: the frequency transmitted by FG via MP is not correct, is already implemented in background)
  • 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)

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
  • MP Chat Unicode support
  • MP Chat private message support

TTS Support

By Legoboyvdlp (talk) 10:32, 20 April 2015 (EDT) Hi. I would like to see in the future TextToSpeech support with the ordinary chatbox, over FGCOM.

  • ATIS- one would say Welcome... TTS in use... Please use (arpt frequency) for ALL services incl. ATIS. A pilot would tune in, and one would listen to their "Hello XXXX ATC" and then one would press a button to auto calculate what the ATIS is IRL or define your own by typing or a dialog box

One would use the . Commands and it would "talk" over FGCOM possible?