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

Plan NDB appears to be selected instead of VOR when both have same ID #52

Closed
apps4av opened this issue Mar 4, 2014 · 0 comments
Closed
Assignees

Comments

@apps4av
Copy link
Owner

apps4av commented Mar 4, 2014

Entering a route as follows: KPWK JVL ODI KFCM. Avare correctly identifies JVL as a navaid waypoint, but it is using the JVL NDB (located at the field) instead of the JVL VOR (about 5 nm SW of the field).

Similar problem occurs when using the "Find" function and searching for JVL. The airport, the VOR, and the NDB come up, but even if the VOR is selected the NDB winds up being the selected waypoint. This is confirmed by pulling up the "Find" function again, which shows the most recent search results - the JVL NDB is at the top of the list.

I'm sure there are other locations in the system where an airport, VOR, and NDB share the same identifier and the NDB is off-field - maybe this is a problem in other places as well.

This is on 5.4.1 on a Nexus 4 with 4.4.2 Kitkat.

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

No branches or pull requests

2 participants