292
edits
OpenRadarFeatureWishlist: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 39: | Line 39: | ||
== METAR == | == METAR == | ||
* 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") | * (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 | ||
* Full METAR code | * (available via tooltip text of wind, pressure line) Full METAR code | ||
== Radar Map == | == Radar Map == | ||
| Line 48: | Line 48: | ||
* 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 | * 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 | ||
* 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].) | ||
:ww: I use the latest apt.dat file from xplane already (format 10.00) if something is missing, you can add the navaids for OR display in the standard route files. The problem for the pilots persist until the FG database is updated/corrected, but even in xplane file, there are some fixes missing) | |||
== Route Editing == | == Route Editing == | ||
| Line 63: | Line 64: | ||
=== Missing/not working frequencies === | === Missing/not working 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. | |||
* 118.10 seems not to work at LSZH TWR. - Maybe there is a collision with the frequency of another airport? | * 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_DEL missing Delivery frequency 121.920 | ||
| Line 71: | Line 75: | ||
== ATC Coordination == | == 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...) | * 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 | * (mp data) see what frequencies othe ATC's are using | ||
:ww: I transmit the first frequency via FGCOM protocol, but do not display it yet, because the FG frequencies are set to a fix value. | |||
* Hand-off feature | * Hand-off feature | ||
:* See to which frequency the Pilot is connected to (com1 & com2) | :* (mp data) See to which frequency the Pilot is connected to (com1 & com2) | ||
::ww: the frequency transmitted by FG via MP is not correct, is already implemented in background) | ::ww: the frequency transmitted by FG via MP is not correct, is already implemented in background) | ||
:* "owning" and aircraft according to the flight strip | :* "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) | :* 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 | :* (mp data) Assigning squawk code to the flightstrip | ||
::ww:Squawk codes are not transmitted via MP protocol. | ::ww:Squawk codes are not transmitted via MP protocol. | ||
* See & edit the flightplan | * See & edit the flightplan | ||
::ww: Suggest central registration for this. | ::ww: Suggest central registration for this. | ||
== Missing/incomplete FG MP protocol data == | |||
* '''Squawk code''' | |||
* '''Active''', tuned in '''frequency''' (COM1/COM2) | |||
* '''local, airpressure dependent, altitude''', additional to the true altitude (as displayed in the airplane to show the FL above transition alt) | |||
* the '''tuned-in COM frequencies''', there is one for COM1, but it is not implemented, it delivers no data | |||
[[Category:OpenRadar|FeatureWishlist]] | [[Category:OpenRadar|FeatureWishlist]] | ||
* MP Chat Unicode support | |||
* MP Chat private message support | |||
* ?ATC extensions? (extensions for ATC MP partners) | |||
:* STRING: list of contacts that are controlled by the ATC | |||
:* STRING: xml messages, like handovers, flightplan transfer | |||