-
Notifications
You must be signed in to change notification settings - Fork 293
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
Comments
You do what kind of search? Searching for Herrsching am Ammersee returns the right postal code. |
For example this one: |
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. |
Note to self, the correct order for determining the postcode is:
|
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.
The text was updated successfully, but these errors were encountered: