292
edits
OpenRadar Change Log: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(cat: OpenRadar; Headings; Template:TOC limit; etc.) |
No edit summary |
||
| Line 1: | Line 1: | ||
[[OpenRadar| Back to mainpage]] | [[OpenRadar| Back to mainpage]] | ||
* I am working on (on a slower pace, not contained in next update) | * I am working on (on a slower pace, not contained in next update) | ||
:* Flightplan exchange server | :* Flightplan exchange server | ||
| Line 16: | Line 15: | ||
::* Auto release from control, if contact leaves the range of the controlling ATC. | ::* Auto release from control, if contact leaves the range of the controlling ATC. | ||
::* All other ATCs see the current flightplan of contacts that are controlled by someone else. | ::* All other ATCs see the current flightplan of contacts that are controlled by someone else. | ||
{{TOC limit|2}} | {{TOC limit|2}} | ||
== OpenRadar updates | == Next update == | ||
(no changes yet) | |||
== Published updates == | |||
=== OpenRadar updates March 2014 === | |||
:* Flightplan integration into OR | |||
::* Destination airport is displayed in data block | |||
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport | |||
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data | |||
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase. | |||
::* Auto release from control, if contact leaves the range of the controlling ATC. | |||
::* All other ATCs see the current flightplan of contacts that are controlled by someone else. | |||
=== OpenRadar 2013-10-12 === | === OpenRadar 2013-10-12 === | ||