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

Autimatically include higher-ordered / higher-ranking communities or townships when searching for an address #19835

Open
wehkah opened this issue May 11, 2024 · 1 comment
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning

Comments

@wehkah
Copy link

wehkah commented May 11, 2024

Describe the idea (required)

Now and then, searching an address in Osmand provides no result, because OpenStreetMap assigned the address to a wrong part of a city, the wrong district, etc. (No offence meant, mistakes happen!)

Would it be possible to automatically switch to the next higher ordered community if a search does not find the desired address?

Tell us about the expected behaviour (required)

The expected behaviour would look like this: I enter an address, which is assigned to a faulty district of the higher ordered city, but Osmand will find the street / the address nonetheless, e.g. bases on the zip code ("Postleitzahl" in Germany), or based on distance.

Tell us about alternatives you've considered (required)

There are two alternatives: I can use Google Maps to find the desired address, or I can use the phone and ask for manual routing instructions, which feels sooooo like in the 1980s again... :(

Context (optional)

No response

@vshcherb vshcherb added the Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning label May 13, 2024
@vshcherb
Copy link
Member

Yes, probably we can combine other data sources to have better result

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning
Projects
None yet
Development

No branches or pull requests

2 participants