117
edits
No edit summary |
(Removed a little white lie) |
||
Line 341: | Line 341: | ||
==== Refining the network: Mark points on the runway as such ==== | ==== Refining the network: Mark points on the runway as such ==== | ||
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: | 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). | ||
It should be noted that there is no reason why TaxiDraw should not be able to mark the runway points as such automatically. After all, the geometry information of both runways and AI nodes is available. Although this automatic feature is planned, the taxidraw developers have as of yet not found the opportunity to implement this feature. Until that time, on runway marking has to be done by hand. | It should be noted that there is no reason why TaxiDraw should not be able to mark the runway points as such automatically. After all, the geometry information of both runways and AI nodes is available. Although this automatic feature is planned, the taxidraw developers have as of yet not found the opportunity to implement this feature. Until that time, on runway marking has to be done by hand. | ||
==== Refining the network: Set Holding points ==== | ==== Refining the network: Set Holding points ==== |
edits