OpenRadarFeatureWishlist: Difference between revisions

Jump to navigation Jump to search

OpenRadarFeatureWishlist (view source)

Revision as of 08:23, 9 May 2013

3,450 bytes removed ,  9 May 2013
Cleanup of old and done points
(→‎General: Dubai (OMDB) error loading tower position)
(Cleanup of old and done points)
Line 11: Line 11:
* Make it not working at FG's [[KSFO|default airport]] (to guard against heart attacks on trying-to-be-KSFO-police people).  
* 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...
: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 (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.
Line 23: Line 21:
* 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.
* (implemented as bi-directional checkbox in rw settings dialog) 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.
::mc: Yes, e.g. airports in "rural areas", especially when there are temples, military conflicts (prohibited, danger and restricted areas).
* 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, 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.
Line 43: Line 38:
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.
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)
* (MP data?) Red colored flags for emergency codes such as 7500 (hijack), 7600 (radio failure) and 7700 (general emergency MAYDAY, PAN PAN)
* (done: Set in contact dialog, displayed as little headset) Voice, Text ability of Pilot (FGCom)


== METAR ==
== METAR ==
* (corrected) Winds below 100 degrees with preceeding 0/00, so that wind directions are read in 3 numbers. (E.g. wind 9@3 is read as "wind zero-zero-niner at tree")
* METAR of nearby airports
* METAR of nearby airports
* (available via tooltip text of wind, pressure line) Full METAR code
* (available via tooltip text of wind, pressure line) Full METAR code


== Messages ==
== Messages ==
:ww: Up to now, we are still close to the implementation of ATC-ML, although there are some minor differences. I understand the need to change the following and will make it, but maintenance effort will increase.
* (done) Angles in the ATIS message should also be padded with 0 (see comment on the Winds below 100 deg in previous section)
* (done): The angle of the ILS is confusing as written: <code>active rwy(s) 06 ILS 108.50-62</code>, I'd rather see that: <code>active rwy(s) 06 ILS 108.50 (062)</code>
* (done) FGCOM message should list all frequencies the ATC listens too. Ex: FGCOM 118.700 TWR, 123.87 APP, 117.750 GND
* (done) QNH should be given in inHg and hPa. Ex: QNH 30.12/1020, except if there is a way to tell OpenRadar which unit the ATC wants to give (which is even better).
* (exists: try ESC! )A shortcut should be available to cancel and clear the whole message line


== Radar Map ==
== Radar Map ==
Line 62: Line 49:
* 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
* 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
* (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
* (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].)
* 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].)
Line 68: Line 55:


== Route Editing ==
== Route Editing ==
* (done: syntax <code><addPoint code="AGOLO" point="50.200000,9.676111"/></code> ) 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 <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?)
* (done: example: <code>begin="KOAK-RW29"</code>) The ability to reference runway start and end as nav points
* (done: both formats: N47°57'51'',E7°54'58'' and N47°57.2',E7°54.10') ability to specify geographic coordinates in degrees, minutes, seconds and not only in decimal degrees


== Radar Contact handling ==
== Radar Contact handling ==
== FGCom Integration ==
== 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
* Add "set PTT button" feature


Line 82: Line 64:
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.  
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.
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.
* 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 ==
== ATC Coordination ==
Wagnerw
292

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/59993"

Navigation menu