Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

nominatim returns bad data #5

Open
echarlie opened this issue Jan 16, 2018 · 2 comments
Open

nominatim returns bad data #5

echarlie opened this issue Jan 16, 2018 · 2 comments

Comments

@echarlie
Copy link
Member

problem seen in mutantmonkey/phenny#78
e.g.: .tfwf KROA (Roanoke Airport) returns weather in ENSB (Norway)
.tfwf 24061 (Blacksburg) returns weather in LIME (Italy)

Someone should look into why nominatim has been giving us such poor location data recently.

@echarlie
Copy link
Member Author

I did some quick looking. It seems that the priority values attached to the Nominatim lookup rank those alternatives higher; perhaps the solution here is to do some more parsing; always prefer class: aeroway would be a starting point.

@mutantmonkey
Copy link
Contributor

Yeah, I agree that more parsing may be the best solution.

See also mutantmonkey/phenny#81

@mutantmonkey mutantmonkey transferred this issue from mutantmonkey/phenny Oct 22, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants