Skip to content
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

Wayponts in routes (routing.json) does not accept airways. #20

Open
lalbri opened this issue Aug 21, 2022 · 2 comments
Open

Wayponts in routes (routing.json) does not accept airways. #20

lalbri opened this issue Aug 21, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@lalbri
Copy link

lalbri commented Aug 21, 2022

Wayponts in routes (routing.json) accepts only waypoints not airways.
A tipical route LIMC-LSGG is "AOSTA L615 BANKO".
It is not configurable like route in regular controlling nor during events.
ES shows orange INV, in effect.
Es.:
{
"name": "AOSTA",
"routes": [{
"icao": "LSGG",
"maxlvl": 200,
"minlvl": 200,
"waypoints": ["L615", "BANKO"]
}
]
},

Any clues?

Tnx

@lalbri lalbri added the enhancement New feature or request label Aug 21, 2022
@FreshDave29
Copy link
Collaborator

L615 isn't a valid waypoint (obviously), and ES is parsing all points that are on this airway into the route.

Only current workaround is to use AOSTA BANKO as "valid" routing.

@lalbri
Copy link
Author

lalbri commented Nov 26, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants