OpenRadarFeatureWishlist: Difference between revisions
Jump to navigation
Jump to search
(→FGCom Integration: request to alter clashing keyboard shortcut CTRL) |
|||
| Line 5: | Line 5: | ||
== General == | == General == | ||
* Callsign greater than 7 characters, cannot even have ICAO_TWR as callsign. Would like at least 10 | |||
* Inter ATC communication. Some method of talk/text just between ATC controllers would be nice, to coordinate handovers | |||
== RadarMap == | == RadarMap == | ||
Revision as of 21:48, 2 February 2013
This page collects the feature proposals for OpenRadar.
General
- Callsign greater than 7 characters, cannot even have ICAO_TWR as callsign. Would like at least 10
- Inter ATC communication. Some method of talk/text just between ATC controllers would be nice, to coordinate handovers
RadarMap
- add a navaid search
- add a situation based filter/highlighting for fixes (e.g. assign navaids to the landing mode of a specific runway, create possibility to hide all unassigned navaids)
- show more ground detail (data source?)
- rework data blocks a la VLC of vatsim
- separation rings
- alerts for collision and speed violations
RadarContact handling
FGCom Integration
- Remove CTRL as PTT button, clashes with CTRL-Left click for "neglect", suggest Right Shift
- Add "set PTT button" feature
ATC Coordination
- coordinate multiple instances of OpenRadar using a protocol a la VatSim