20,741
edits
Stand Alone ATC Control Development: Difference between revisions
Jump to navigation
Jump to search
Stand Alone ATC Control Development (view source)
Revision as of 11:10, 22 September 2010
, 22 September 2010"AutoATC" is not GUI related
("AutoATC" is not GUI related) |
|||
| Line 1: | Line 1: | ||
Last updated: Sept. 2010 | Last updated: Sept. 2010 | ||
Status: Discussion | Status: Discussion | ||
This wiki is created upon the fired up debate and forum talks to create a centralized idea-bank, so the development proposals/goals can clearly be identified. All users are welcomed to contribute to this entry with their real or virtual world experience and simulator environment requirements for a stand alone [[ATC]] client for [[FlightGear]] [[Howto: Multiplayer|Multiplayer Network]]. | This wiki is created upon the fired up debate and forum talks to create a centralized idea-bank, so the development proposals/goals can clearly be identified. All users are welcomed to contribute to this entry with their real or virtual world experience and simulator environment requirements for a stand alone [[ATC]] '''GUI''' client for [[FlightGear]] [[Howto: Multiplayer|Multiplayer Network]] (TRACON and ARTCC). | ||
=Minimum set of required features= | =Minimum set of required features= | ||
| Line 9: | Line 10: | ||
* display a radar-like screen | * display a radar-like screen | ||
* display data tags (altitude, callsign, course, sqwk code etc) | * display data tags (altitude, callsign, course, sqwk code etc) | ||
= Features provided by the 'ATC aircraft' = | |||
=Other features and ideas = | =Other features and ideas = | ||
* [[FGCom]] integration | * [[FGCom]] integration | ||
= Standard features commonly provided by VATSIM and IVAO clients = | |||
= End user feature requests = | |||
=Customizing [[Atlas]] for use as an ATC client = | |||
In the scope of the ATC discussion, we have also talked about extending [[Atlas]] to use it as the foundation for a standalone ATC client, concentrating on a maximum degree of code reuse. | |||
It seems, that most of the existing atlas features could be used for ATC purposes, too. While only very few new features would be needed that would require changes to the C++ source code. This would make it possible to generalize the atlas code some more, so that using Atlas for ATC purposes would merely be a different "mode". | |||
For the time being, the most important new feature for atlas would be multiplayer support. | |||
Most of the other changes would be about making atlas features either more configurable (i.e. moving hard coded defaults out of the C++ source code into configuration files, plain text or XML based), or about provididing an option to completely disable other features. | |||
== Required enhancements == | |||
* multiplayer support | |||
* possibility to customize appearance for typical ATC use | |||
== Open questions == | |||
* should atlas connect to fgms as a server (relay?) or a client (observer), or should it just poll fgms for updates? | |||
* how about reusing data that is already sent to FlightGear (that would require a running FlightGear instance) | |||
== Roadmap == | |||
=== Milestone 1 === | |||
* radar-like appearance | |||
=== Milestone 2 === | |||
* multiplayer support (processing XDR messages from fgms) | |||
= Standalone (non GUI) automated ATC = | |||
==Beginning of an idea Auto-ATC== | ==Beginning of an idea Auto-ATC== | ||
A project has been started some years ago, named [http://seb.marque.free.fr/fichiers/scripts/perl/auto-atc/ AutoATC]. Indeed it is in a really alpha 0.0.0.1 version, not usable at all. | A project has been started some years ago, named [http://seb.marque.free.fr/fichiers/scripts/perl/auto-atc/ AutoATC]. Indeed it is in a really alpha 0.0.0.1 version, not usable at all. | ||
| Line 30: | Line 61: | ||
Why the project has stopped? Because I was unable to send a correctly formatted UDP packet: the position message is different from C++... this was until I discover [http://www.swig.org/ swig] ([http://pigeond.net/git/?p=flightgear/fgmap.git;a=blob;f=sg_perl/README which is used on FGMap]). Swig can be the solution to allow a revival of autoATC, which is next on my TODO list. | Why the project has stopped? Because I was unable to send a correctly formatted UDP packet: the position message is different from C++... this was until I discover [http://www.swig.org/ swig] ([http://pigeond.net/git/?p=flightgear/fgmap.git;a=blob;f=sg_perl/README which is used on FGMap]). Swig can be the solution to allow a revival of autoATC, which is next on my TODO list. | ||
=Related= | |||
== Wiki == | |||
* [[OpenRadar]] | |||
== Talks == | |||
* http://sourceforge.net/tracker/?func=detail&aid=1416662&group_id=9456&atid=359456 | |||
* http://sourceforge.net/tracker/?func=detail&aid=1827096&group_id=161928&atid=821811 | |||
== | == Software:Open source == | ||
(list taken from atlas/fgms sourceforge trackers) | |||
* http://sourceforge.net/projects/nogozone/ (an EuroControl project) | |||
* http://sourceforge.net/projects/atc-xsolus/ | |||
* http://sourceforge.net/projects/atsf/ | |||
* http://sourceforge.net/projects/atc2/ | |||
* http://sourceforge.net/projects/racetrack/ | |||
* http://sourceforge.net/projects/jatcsimdata/ | |||
* http://sourceforge.net/projects/jatc/ | |||
* http://sourceforge.net/projects/swiss-atc/ | |||
== Software:Freeware == | |||
== Software:Proprietary == | |||
== Freeware == | |||
== Proprietary == | |||