292
edits
OpenRadar Change Log: Difference between revisions
Jump to navigation
Jump to search
Next changes
No edit summary |
(Next changes) |
||
| Line 1: | Line 1: | ||
[[OpenRadar| Back to mainpage]] | [[OpenRadar| Back to mainpage]] | ||
'''next update''' | |||
* Assignment of a runway via double click on runway (select contact, double click runway) => Runway appears in data block | |||
* Improvement to METAR parsing | |||
* fix for auto assigned squawk codes xxx8 and xxx9, that do not exist | |||
* chat aliases (see forum), | |||
:*Examples: | |||
::* .tr 010 => Turn right heading 010 | |||
::* .sqa => Squawk 2004 (next free squawk code) | |||
::* .hs 15 => Hold short runway 15 | |||
:* Arguments to aliases are used internally to update the flightplan (some important) and can be reused in other messages | |||
* I am working on (on a slower pace, not contained in next update) | |||
:* Flightplan exchange server | |||
::* Prototype for a common backend for FlightGear (I need someone to add it to FG), ATC apps like OR and Website like lennys FP landing page | |||
::* First stage: Implement and test with OR without full persistence to a database | |||
::* Second stage: Implement database interface | |||
::* Thirst stage: Permanent availability by running on a public server | |||
:* 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-05-30''' | '''OpenRadar 2013-05-30''' | ||
| Line 10: | Line 36: | ||
:* correction to highlight coloring and documentation | :* correction to highlight coloring and documentation | ||
:* navaid elements can appear multiple times in a route, each with its own color. | :* navaid elements can appear multiple times in a route, each with its own color. | ||
* fgcom support is now indicated on the flight strips too | * fgcom support is now indicated on the flight strips too | ||
* '''disabled:''' Chat messages became too long to be received by flightgear | * '''disabled:''' Chat messages became too long to be received by flightgear | ||