Opened 5 years ago

Closed 5 years ago

#5237 closed defect (duplicate)

Wrong Postal Code Asignment

Reported by: Juan Carlos Rico Gil Owned by: geocoding@…
Priority: minor Milestone:
Component: nominatim Version:
Keywords: Cc:


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

Change History (1)

comment:1 Changed 5 years ago by Sarah Hoffmann

Resolution: duplicate
Status: newclosed

The database has been reimported now but the situation has not improved much because there is still a stray object with postcode 30150:, 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.

Note: See TracTickets for help on using tickets.