OpenRadarFeatureWishlist: Difference between revisions

Jump to navigation Jump to search
(→‎Radar Map: accurate navigation data)
Line 14: Line 14:
:(ww: yes, pretty useful, I think about it. Reloading the routes would be enough I think...)
:(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.
* Squawk / Transponder codes  
:ww: Are not part of the MP protocol => are not transfered to OpenRadar.
* Private message feature
* Private message feature
:ww: Is not part of the MP protocol.
* Intercom FGCom frequency call GND to GND to call other ATC's
* 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.
* 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.
* 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.)
* 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: interesting. How many airports have this setting? I think about a special checkbox in runway settingsdialog.
* 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.


== Aircraft/Pilot Flag ==
== Aircraft/Pilot Flag ==
292

edits

Navigation menu