OpenRadarFeatureWishlist

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

• Wider radar range for CTR controllers
• Squawk / Transponder codes
• Private message feature
• Intercom FGCom frequency call GND to GND to call other ATC's

Aircraft/Pilot Flag

• 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/ALT2992) aboce 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)

Radar Map

• show more ground detail (data source?)
• separation rings (1000ft in vertical and 500ft in horizontal distance)
• 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

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

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

• 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
• Hand-off feature

• See to which frequency the Pilot is connected to (com1 & com2)
• "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)
• Assigning squawk code to the flightstrip

• See & edit the flightplan