Opened 6 years ago

Closed 6 years ago

#4726 closed defect (fixed)

strange extra results of street with wrong postal code

Reported by: skyper Owned by: geocoding@…
Priority: minor Milestone:
Component: nominatim Version:
Keywords: post code Cc:

Description

Searching http://nominatim.openstreetmap.org/search.php?q=mercystra%C3%9Fe&viewbox= returns in first place one valid result: http://nominatim.openstreetmap.org/details.php?place_id=42638941

This is not the best choice, as I expected to get the whole street and not just a part (situation see below) but OK.

In third place I get: http://nominatim.openstreetmap.org/details.php?place_id=82189640 with a wrong postal code. Do not know where this comes from but seen this code on several search for streets around this area. Please do not show this post code as it is an individual post code for the administration and not valid for any street.

situation

  • the street has a valid associatedStreet relation with post code (79100). This should be the first hit and only valid post code.
  • the postal code is tagged in the whole city either with the admin boundary relation or if needed as an own boundary relation boundary=postal_code.

Please do not use the postal_code of nodes with place=* as this might be totally wrong. Thanks

Change History (1)

comment:1 Changed 6 years ago by Sarah Hoffmann

Resolution: fixed
Status: newclosed

Postcodes on admin boundaries now work. For post codes on associatedStreet relations see #4878.

Note: See TracTickets for help on using tickets.