You are not logged in. Please login or register.
JARDesign Group Board → Custom ATC routes for XP Airports → Wrong practice of ATC-taxiroutes drawing
Ok, lets talk what wrong and how make better with gate/stand drawing and ATC-texiroutes drawing. Please use this info when you work with WED or with GateEditor.
What wrong? Runway connect with hold short point with several lines.
How better? Connect Hold short with Runway with One line.
What wrong? Taxiway leads to nowhere.
Or like this:
How better? Just delete it!
What wrong? Runway connect with hold short point with several lines.
How better? Connect Hold short with Runway with One line. If this is not possible - take the rule: Next point after hold-short should be Runway.
What wrong? A lot of "extra" lines.
How better? Delete "extra lines".
What wrong? A lot of "extra" lines.
How better? Delete "extra lines".
What wrong? Wingspan/path Conflict with static aircrafts, with traffic aircraft, with apron road, etc.
How better? - decrease aircraft category!
What wrong? Stand may be use for C-D-E category, but use only for E.
How better - mark it for C,D,E
That Wrong: Aircraft symbol in the WED NOT oriented exactly with heading of the plane just taxied to parking
How better:
What wrong? Draw "Taxi-in / Taxi-out" without break at taxiline and without Oneway marked.
How better: add break and add Oneway makrers.
What wrong: multicrossline drawing
How better?
What wrong: draw multilines what can be replace by one line. No brake, no Oneway for Taxi-in/Taxi-out stand
How better:
JARDesign Group Board → Custom ATC routes for XP Airports → Wrong practice of ATC-taxiroutes drawing
Powered by PunBB, supported by Informer Technologies, Inc.