Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Wrong Post Code taken in address (even with associatedStreet, ...) #4986

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

Wrong Post Code taken in address (even with associatedStreet, ...) #4986

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Assignees
@openstreetmap-trac
Labels
Component: nominatim Priority: minor Resolution: duplicate Type: defect

Comments

@openstreetmap-trac
Copy link

Reporter: eMerzh
[Submitted to the original trac issue database at 9.53pm, Monday, 16th September 2013]

Hi,

let's take this way :

http://www.openstreetmap.org/browse/way/179455113

It's tagged with the AssociatedStreet relation here :
Ici prsente http://www.openstreetmap.org/browse/relation/2963829

The addr:postcode of the relation is correct : '1090' and the one of the city too :
http://www.openstreetmap.org/browse/node/66513277 and http://www.openstreetmap.org/browse/relation/58258

but when i look in nominatim, i got the wrong postcode (1081) as showed here
http://nominatim.openstreetmap.org/search.php?q=Avenue+Giele+11%2C+jette&viewbox=4.32%2C50.87%2C4.34%2C50.86

i think i can't do better tagging to help nominatim...?! or should we put the postal code on every address?

Thanks
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 9.30pm, Sunday, 15th December 2013]

This case seems to have been solved with a postal_code boundary relation in the meantime.

Problem of associated_street postcode is a duplicate of #4878.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@openstreetmap-trac openstreetmap-trac

Labels
Component: nominatim Priority: minor Resolution: duplicate Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac