-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Actually USE the suffixes of procedures #33
Comments
Depends on #193. |
@erikquinn @indianbhaji given the following procedure (from "BUZAD": {
"icao": "BUZAD",
"name": "Buzad",
"suffix": {"09L":"3K", "09R":"4J"},
"rwy": {
"09L": [],
"09R": []
},
"body": [["_LONR072D10", "A30+"], "BUZAD", "WOBUN", "DTY", "HON"],
"draw": [["_LONR072D10", "BUZAD"]]
}, if a command was issued Am I understanding this correctly? |
@n8rzz Yes |
With reference to #422 I am just adding the problem that ocurred on EDDL, as discussed on slack: At EDDL (but not limited to it) the correct assignment to a runway is managed using approach transitions from the STAR's Initial Approach Fixes (=start of the approach transition) to the Final Approach Fix (=end of the approach transition). But as we don't code those approach transitions but only the STARs we need a solution for the "one suffix for multiple runways"-issue. |
Given a procedure
ANKER
, users should be able to enterSID ANKER1Q
and/orSTAR ANKER1Q
, depending on the type of procedure. Such was the intent of thesuffix
property, but it was never really fully hooked up, and airport creators have worked around it by creating individual proceduresPIK27X
,PIK27D
,PIK23X
,PIK23D
,PIK21X
,PIK21D
, etc. Completing the functionality of the suffixes would eliminate the need for them to do this.Originally reported in zlsa/atc#655.
The text was updated successfully, but these errors were encountered: