Flight Plan Route description Parsing

[anonymous555]

When entering a flight plan route description from text, a few missing items.

Issue 1: Airway Airway intersections

When entering a flight plan route description from text, little nav map is unable to find the intersection of two airways. For example when this is entered:

KLAX SLI V25 V208 OCN KNKX

I get the above error:

No waypoint after airway V25. Ignoring flight plan segment.
No waypoint before airway V208. Ignoring flight plan segment.

Note that skyvector is able to figure this one out and display it. https://skyvector.com/

This example came directly from

https://www.fly.faa.gov/rmt/nfdc_preferred_routes_database.jsp

There are many other similar examples in that database's csv file.

**Issue 2: Import angles from a VOR **

This is given here for example

LAX SEAL_BEACH-DP SLI SLI148 V25 V208 OCN OKB

Note the SLI148 is an angle from SLI

This example came directly from

https://www.fly.faa.gov/rmt/nfdc_preferred_routes_database.jsp

There are many other similar examples in that database's csv file.

[anonymous555]

Great tool, littlenavmap is amazing!!!

[anonymous555]

Also, this results in an error

KPSP V388 PDZ KSBD

No waypoint before airway V388. Ignoring flight plan segment.
Found airway V388 instead of waypoint as first entry in en-route list. Ignoring.

[anonymous555]

May be related to

#824

[albar965]

The start and end waypoint is required and airway intersections are not supported for now.
Maybe I can add this in a future version but the complexity of route description parsing is increasing too much.