You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Got it. Tnx
Inviato da Yahoo Mail su Android
Il sab, 26 nov, 2022 alle 17:05, ***@***.***> ha scritto:
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.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
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
The text was updated successfully, but these errors were encountered: