86
edits
AI Traffic: Difference between revisions
Jump to navigation
Jump to search
Points on Runway and Backtracking routes
mNo edit summary |
(Points on Runway and Backtracking routes) |
||
| Line 364: | Line 364: | ||
With the startup locations in place, select one of them. The next step will be to connect this parking area to each runway end. After selecting the parking, click on the "insert bidirectionally connected network nodes" (the two green dots icon), and start drawing. Place nodes at strategic locations, such as intersections, corners, and arcs. finally, place one node at the centerline of one of the runways. Once this is finished, one gate is connected to one end of one runway. The next job is to extend the network by connecting more gates and more runways. | With the startup locations in place, select one of them. The next step will be to connect this parking area to each runway end. After selecting the parking, click on the "insert bidirectionally connected network nodes" (the two green dots icon), and start drawing. Place nodes at strategic locations, such as intersections, corners, and arcs. finally, place one node at the centerline of one of the runways. Once this is finished, one gate is connected to one end of one runway. The next job is to extend the network by connecting more gates and more runways. | ||
Traffic Manager 'calculates/understands' each runway centreline as the line between the two threshold points stored in the matching airport ICAO file in Terrasync/Airports/[I]/[C]/[A]/[ICAO].threshold.xml. Whenever placing a route end node on a runway, you should ensure the node sits on or close to this line. Traffic manager will then use the vector between the two threshold to trigger the AI aircraft take off sequence (deciding that the aircraft has reached the centreline and can start speeding up) as well as setting its take off heading. This is most important in case of displaced thresholds. | |||
''Backtracking'' | |||
Certain airports do not have taxiways along the runway and aircrafts will 'backtrack' on the runway itself to reach the threshold (and pivot on a turnaround area to align for take off). In this scenario, you must place nodes and segments to form a route on the runway to guide the AI aircrafts all the way from their access point to the threshold, including on the turnaround area | |||
[[File:Using the runway to backtrack to the threshold.jpg|thumb|AI Groudnet configuration for backtracking in absence of parallel taxiway]] | |||
Create a second branch from the existing route, which goes to another runway. To do so, press [ctrl-a] to deselect all objects. Then, select the point where you want to branch off from. Select this point using a left mouse click, while holding down the shift key. Since TaxiDraw is still in node connect mode, simply left-clicking would have resulted in placing a new node. With this node selected, continue drawing. Repeat this procedure until all runways are connected. | Create a second branch from the existing route, which goes to another runway. To do so, press [ctrl-a] to deselect all objects. Then, select the point where you want to branch off from. Select this point using a left mouse click, while holding down the shift key. Since TaxiDraw is still in node connect mode, simply left-clicking would have resulted in placing a new node. With this node selected, continue drawing. Repeat this procedure until all runways are connected. | ||
| Line 374: | Line 381: | ||
With the basic infrastructure in place, the next step is to fine-tune the network. The first step in this process is to mark the network nodes that are located on a runway. This is important for a number of reasons: TaxiDraw needs these OnRunway points for it's network verification tool. Secondly, the use of the type of runway marking will be used in future versions of FlightGear for runway entrance / exit calculations, in addition to a host of other possible uses in routing (such as blocking a certain node then a crossing runway is in use, etc, etc). | With the basic infrastructure in place, the next step is to fine-tune the network. The first step in this process is to mark the network nodes that are located on a runway. This is important for a number of reasons: TaxiDraw needs these OnRunway points for it's network verification tool. Secondly, the use of the type of runway marking will be used in future versions of FlightGear for runway entrance / exit calculations, in addition to a host of other possible uses in routing (such as blocking a certain node then a crossing runway is in use, etc, etc). | ||
Taxidraws's verification tool will automatically detect and report discrepancies (Node not marked 'on runway' where it should and vice versa) for as long as the runway(s) elements are included in the project file. | |||
==== Refining the network: Set Holding points ==== | ==== Refining the network: Set Holding points ==== | ||