OpenRadarFeatureWishlist

From FlightGear wiki
Revision as of 21:19, 16 March 2013 by Wagnerw (talk | contribs)
Jump to navigation Jump to search

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)
  • 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 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...)

RadarMap

  • show more ground detail (data source?)
  • separation rings
  • 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

Route Editing

  • (done: syntax <addPoint code="AGOLO" point="50.200000,9.676111"/> ) 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 text="" is not enough?)
  • (done: example: begin="KOAK-RW29") The ability to reference runway start and end as nav points

RadarContact handling

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?)
ww: removed CTRL+CLICK, there is a textbutton above the flightstrips now, to toggle neglect
  • Add "set PTT button" feature

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...)