7
edits
Stand Alone ATC Control Development: Difference between revisions
Jump to navigation
Jump to search
m
Stand Alone ATC Control Development (view source)
Revision as of 04:45, 3 December 2010
, 3 December 2010no edit summary
(Add flight plan support to ideal ATC client) |
mNo edit summary |
||
| Line 236: | Line 236: | ||
'''Chat messages''' to/from other pilots and controllers. | '''Chat messages''' to/from other pilots and controllers. | ||
'''Flight plans''' will be the trickiest part. Not only should the ATC client have the ability to understand things like the route (to draw it on screen if needed; though this is quite optional at the beginning), but it will pose on Flightgear itself the need to support flight plans, with a standard form to be filled in by pilots prior to the flight; additionally, the MP protocol will have to implement it so that "flight plan packets" can be sent (by pilots) and received (by controllers). Additionally, as seen in other environments (optional at the beginning also), the controller should have the authority of correcting that FP, which would be sent back to the pilot with the modifications. This can apply either to aircrafts under the | '''Flight plans''' will be the trickiest part. Not only should the ATC client have the ability to understand things like the route (to draw it on screen if needed; though this is quite optional at the beginning), but it will pose on Flightgear itself the need to support flight plans, with a standard form to be filled in by pilots prior to the flight; additionally, the MP protocol will have to implement it so that "flight plan packets" can be sent (by pilots) and received (by controllers). Additionally, as seen in other environments (optional at the beginning also), the controller should have the authority of correcting that FP, which would be sent back to the pilot with the modifications. This can apply either to aircrafts under the control of the particular ATC, or to all the aircrafts in scope. | ||
I don't think the radar client should connect as a fake pilot. In my opinion, the MP protocol should be extended so that controllers could login as such. | I don't think the radar client should connect as a fake pilot. In my opinion, the MP protocol should be extended so that controllers could login as such. | ||
| Line 251: | Line 251: | ||
There is another application in IVAO, called IvAe, which consists of a "Google Earthish" interface that shows all the pilots and controllers connected to the network, and you can retrieve much of their info (flight plans for pilots, ATIS for controllers, etc.). In this case, Atlas would be a good starting point for that. | There is another application in IVAO, called IvAe, which consists of a "Google Earthish" interface that shows all the pilots and controllers connected to the network, and you can retrieve much of their info (flight plans for pilots, ATIS for controllers, etc.). In this case, Atlas would be a good starting point for that. | ||
=Related= | =Related= | ||