v0.20 - Nodes on Runway not Checked

Portree-Kid / flightgear-airports

GNU General Public License v3.0

6 stars 1 forks source link

v0.20 - Nodes on Runway not Checked #59

Closed BecOzIcan closed 4 years ago

BecOzIcan commented 4 years ago

Discrepancy between TD and FGA. TD detects multiple nodes on runway not marked as such in files created in FGA and submitted

wkitty42 commented 4 years ago

is this saying that all nodes in a runway have to be marked as such? not just the final node on the runway?

BecOzIcan commented 4 years ago

Yes all nodes on runway should be marked as such. Departing aircrafts will queue at the last "not on runway" node on hte route (ie just outside the runway from the rule above) until cleared to take off

wkitty42 commented 4 years ago

ooooooohhhhh... ok, so my trick of having only one on the runway to grab landing craft with is in error... alright...

Portree-Kid commented 4 years ago

Works now, but may lead to problems. Scotland has lots of taxi down runway type of airports. AI doesn't handle them well "yet".

BecOzIcan commented 4 years ago

You mean backtracking? Like use the runway as taxiway all the way to the threshold and swing around? I just did a paragraph on them in the wiki last week with tips and trick from Brett. Awesome news for the Turf Test (love the name, keeping it)

Portree-Kid commented 4 years ago

Yes. Maybe Runway is not the correct check? More like Threshold path?

BecOzIcan commented 4 years ago

Yes. The best test would be node on the line between each pair of THR but we would need some tolerance around that, can you calculate a "Theoretical Runway Box" for node on runway test purposes : Length = distance between THR pair Width = 15 meters (our smallest aircraft radius x2) Position and Heading : Centered between THR

The European Aviation Safety Agency suggest 18 is the minimum real width. Ref Doc Link in the Wiki Radii page

Portree-Kid commented 4 years ago

Fixed in 0.0.21