Opened 7 years ago

Closed 7 years ago

#4855 closed defect (fixed)

reverse geocaode provides wrong zip-code (postcode) and city

Reported by: 5erBande Owned by: geocoding@…
Priority: minor Milestone:
Component: nominatim Version:
Keywords: reverse geocoding zip zoom Cc:



Result with Zoom level 16

The above request returns the <postcode>51491</postcode>, which belongs to the city Overath nearby. The other adressparts are correct (<city>Lohmar</city> <county>Rhein-Sieg-Kreis</county>).

Both, the lat/lon and the next street Dahlhauser Straße (osm_type=way osm_id=36991809) are within the boundary of the relation of the city Lohmar (osm_id=173123), which includes the right postcode (postal_code = 53797). I have checked the boundary OSM-relation of Lohmar and did not found an error.

Result with Zoom level 12

The search function uses the <suburb>Steinenbrück</suburb> (osm_type=node osm_id="401294963), which is tagged is_in=Overath. In this case postcode and city matches, but both is wrong.

Change History (1)

comment:1 Changed 7 years ago by Sarah Hoffmann

Resolution: fixed
Status: newclosed

Fixed in 10f3a4d/nominatim. Postcode tag on objects from the address are now merged into the display result.

Note: See TracTickets for help on using tickets.