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

Wrong Postal Code Asignment #5235

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

Wrong Postal Code Asignment #5235

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

Comments

@openstreetmap-trac
Copy link

Reporter: Juan Carlos Rico Gil
[Submitted to the original trac issue database at 12.12pm, Thursday, 2nd October 2014]

The query "30150,Murcia" in OpenStreetMap Nominatim gives a wrong answer, situating it in "Guadalupe de Maciascoque" instead of "La Alberca de las Torres", some kilometers to south east.
This is due to the fact that id=98284169 (30150, Type:place:postcode, Center Point: 37.9968697, -1.1802832) has as parent id=313397672 (Guadalupe de Maciascoque, Type:place:suburb) and as such, affects to it and to a set of other ids of which id=313397672 is also Parent, propagating the wrong postal code also to these ids.
It appears that interrogating the OSM database through JOSM (under ubuntu 14.??) reveals that the Postal Code Node id=98284169 has been deleted!
It seems that this is not the case in OpenStreetMap Nominatim, where it still cause this problem

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 4.23pm, Friday, 10th October 2014]

The database has been reimported now but the situation has not improved much because there is still a stray object with postcode 30150: http://www.openstreetmap.org/node/299660257, so altogether it's a data problem.

Note that at the moment Nominatim doesn't properly update postcodes, so changes in OSM will not really be reflected in the search engine. We are working on that. Closing as duplicate for the moment here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant