Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#5140 closed defect (fixed)

Cannot find postcode from postal_code relation

Reported by: defonion Owned by: geocoding@…
Priority: major Milestone:
Component: nominatim Version:
Keywords: postal code Cc:


The query for the postalcode "04457" ( results in two adresses: "Mölkau, Zweinaundorf, Leipzig, Sachsen, 04457, Deutschland, European Union" and "Lincoln, Piscataquis, Maine, 04457, United States of America" but the result in germany actually has the postalcode 04316. Furthermore querys for streets in this german region deliver wrong postcodes for the addresses. For example the query ( "Paul-Klöpsch-Straße, Holzhausen, Zweinaundorf, Leipzig, Sachsen, 04288, Deutschland, Europäische Union" but the postal code should be 04316.

Change History (5)

comment:1 Changed 6 years ago by Sarah Hoffmann

Resolution: invalid
Status: newclosed

Outdated postcodes are a known issue. Postcodes have not been updated since the last reimport 1.5 years ago.

The postcode display for the roads needs to be fixed in the OSM data. Looks like there is no postal code area with postcode 04316.

comment:2 Changed 6 years ago by defonion

But there is an relation with the id 1301664 which has the information of the postal code 04316 surrounding this area. Is this not enough? What would be the way to tag it to be recognized by nominatim?

comment:3 Changed 6 years ago by Sarah Hoffmann

Resolution: invalid
Status: closedreopened
Summary: Search for postalcode 04457 delivers non existing resultCannot find postcode from postal_code relation

Thanks for the relation id. A postal_code area should indeed be enough. Nominatim did import the relation, see here, but it can neither be found nor used in addresses. I've reopened the bug.

It looks like the main issue is that the name only appears in the postcode column, it should be copied as a ref into the name column.

comment:4 Changed 6 years ago by Sarah Hoffmann

Resolution: fixed
Status: reopenedclosed

ref in the name column got lost on updates.

Fixed in c2417dd/nominatim

Note 1: I've manually reimported the relation 1301664 to check that the fix works but other relations with the same problem have not been changed. They will automatically getsorted out once the data is touched in OSM the next time.

Note 2: this does not fix the well-known issue with postcode centroids (e.g. not being updated. They still may cause glitches.

comment:5 Changed 6 years ago by defonion

Thanks a lot!

Note: See TracTickets for help on using tickets.