Howto:Implementing a simple GCA system: Difference between revisions

Howto:Implementing a simple GCA system (view source)

211 bytes added , 13 September 2017

20,741

edits

@@ Line 28: / Line 28: @@
 == Status ==
-So far, we haven't actually coded up any heuristics at all: We merely ended up implementing the previously mentioned helper class to monitor/track an aircraft using a timer object, and call a single  buildInstruction() routine that internally deals with two geo.Coord() objects, one representing the destination (i.e. runway) and the other the permanently updated position of the aircraft that is being tracked.
+You can download it from [https://drive.google.com/file/d/0BzojFuPdeyMWGpCV3VLS0QxUVU/view?usp=sharing here].
+Please read the Readme file included into the zip.
+Note this is to be installed as Submodule. Later I'll make the addon.
+But prior to that please provide feedback about its 'architecture' and behavior.
+Thanks in advance for your cooperation.<ref>{{cite web
+  |url    =  https://forum.flightgear.org/viewtopic.php?p=318458#p318458
+  |title  =  <nowiki> Spoken GCA </nowiki>
+  |author =  <nowiki> rleibner </nowiki>
+  |date   =  Sep 7th, 2017
+  |added  =  Sep 7th, 2017
+  |script_version = 0.40
+  }}</ref>
 We also looked up screen shots of actual ATC software to see what kind of parameters can commonly be configured for a GCA, which is why we put together a Canvas based UI dialog to more easily configure the GCA in FlightGear, including the corresponding offsets.