OpenRadarFeatureWishlist: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(Cleanup of old and done points)
 
(11 intermediate revisions by 4 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...
* 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.
* (MP data?) Squawk / Transponder codes
:ww: Are not part of the MP protocol => are not transfered to OpenRadar.
* (MP data?) Private message feature
:ww: Is not part of the MP protocol.
* Intercom FGCom frequency call GND to GND to call other ATC's
:ww: Some ATCs are using mumble right now, for this purpose. I keep it in mind. But I don't want to exclude the ATC-models out of the game.
* Controlling multiple airports (CTR controller)
* 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.
: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, but FGCOM is a separate application, linked to OR via a simple network protocol. Difficult... Especially as we support many different operating systems and setups.
: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!! ;)
::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?)
* 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.
:ww: technically possible, but tooltips disturb usability very much. Please open a thread in forum and discuss is with the users!
* OpenRadar fails for LSZN (Hausen am Albis) with error "SEVERE: Error: could not parse tower position in file sectors.properties for airport LSZN"
* Traffic counter
:LSZN TWR is +47° 14' 16.86" N +8° 30' 51.51" E, LSZN runway +47° 14' 19" N, +8° 30' 56" E
* Allow IAPs to be shown separate to SIDS / STARS
* Same error for OMDB (Dubai):
:de.knewcleus.openradar.gui.setup.AirportData checkTowerPosition
:SEVERE: Error: could not parse tower position in file sectors.properties for airport OMDB


== Aircraft/Pilot Flag ==
== Aircraft/Pilot Flag ==
* See assigned flightlevel (according to flightplan)
* See assigned flightlevel (according to flightplan)
* (MP data?) Squawk/Transponder Code
* (MP data?) "True" altitude according to local air pressure below transition level and flightlevel according to standard pressure (QNH 1013/2992) above transition level
ww: I have no access to the airpressure at the spot, where the plane is. All I get is the TRUE position of the airplane in world coordinate system. If the MP protocol would deliver both, the true altitude and the FL- pressure dependent altitude, this would be no problem.
* (MP data?) 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 => right click on the METAR lines and define them.
* (available via tooltip text of wind, pressure line) Full METAR code


== Messages ==
== 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
* (done) 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
* (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].)
:ww: I use the latest apt.dat file from xplane already (format 10.00) if something is missing, you can add the navaids for OR display in the standard route files. The problem for the pilots persist until the FG database is updated/corrected, but even in xplane file, there are some fixes missing)


== Route Editing ==
== Route Editing ==
* 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?)
* Loop - allow standard / non-standard loop - e.g. https://i.imgur.com/1IA0TFB.png


== Radar Contact handling ==
== FGCom Integration ==
== FGCom Integration ==
* Add "set PTT button" feature
* Add "set PTT shortcut key" feature
 
* Change volume of fgcom channel
=== Missing/not working frequencies ===
ww: I have changed from the frequencies delivered by the xplane files to the phonebook of fgcom. Both did mismatch. Now they are equal and (if you don't use an older Fgcom phonebook) you should be able to connect to all displayed frequencies.
BUT: this does not mean, that all frequencies are there. The frequencies should be maintained by the FGCOM team, as I am only a client. I will update the phonebook when I notice it has been updated.


== 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 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.
: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
:* (mp data) See to which frequency the Pilot is connected to (com1 & com2)
:* (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)
::ww: the frequency transmitted by FG via MP is not correct, is already implemented in background)
:* "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)
:* (mp data) Assigning squawk code to the flightstrip
::ww:Squawk codes are not transmitted via MP protocol.
* See & edit the flightplan
::ww: Suggest central registration for this.


== Missing/incomplete FG MP protocol data ==
== Missing/incomplete FG MP protocol data ==
* '''Squawk code'''
* '''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)
* '''local, airpressure dependent, altitude''', additional to the true altitude (as displayed in the airplane to show the FL above transition alt)
* the '''tuned-in COM frequencies''', there is one for COM1, but it is not implemented, it delivers no data
[[Category:OpenRadar|FeatureWishlist]]
* MP Chat Unicode support
* MP Chat Unicode support
* MP Chat private message support
* MP Chat private message support
* ?ATC extensions? (extensions for ATC MP partners)
==TTS Support==
:* STRING: list of contacts that are controlled by the ATC
By [[User:Legoboyvdlp|Legoboyvdlp]] ([[User talk:Legoboyvdlp|talk]]) 10:32, 20 April 2015 (EDT)
:* STRING: xml messages, like handovers, flightplan transfer
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]]

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?

Retrieved from "https://wiki.flightgear.org/w/index.php?title=OpenRadarFeatureWishlist&oldid=116762"