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

Incorrect postal code: Herrsching am Ammersee, Germany #835

Open
JulianFl opened this issue Sep 27, 2024 · 3 comments
Open

Incorrect postal code: Herrsching am Ammersee, Germany #835

JulianFl opened this issue Sep 27, 2024 · 3 comments

Comments

@JulianFl
Copy link

JulianFl commented Sep 27, 2024

I have a problem with an incorrect postal code:

Country: Germany
Location: Herrsching am Ammersee
Latitude: 48.00276153295002
Longitude: 11.17008090019226

Nominatim returns the correct postal code (82211) while Photon returns the incorrect postal code (82237).
In this issue the basis in Nominatim was already wrong. In my case it is true for Nominatim and wrong for Photon.

@lonvia
Copy link
Collaborator

lonvia commented Nov 27, 2024

You do what kind of search? Searching for Herrsching am Ammersee returns the right postal code.

@JulianFl
Copy link
Author

JulianFl commented Nov 27, 2024

For example this one:
Bahnhofstraße Herrsching

@lonvia
Copy link
Collaborator

lonvia commented Nov 27, 2024

Looks like Nominatim and Photon have different assumptions what the computed postcode is and how to handle postcode boundaries.

Nominatim ignores the computed postcode for this way and just uses the postcode from the boundary relation: https://nominatim.openstreetmap.org/ui/details.html?osmtype=W&osmid=222883869

Photon ignores the relation and just uses the computed postcode.

I need to figure out who is doing it right.

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