Opened 6 years ago

Closed 4 years ago

#4772 closed defect (fixed)

Bridge with ref found instead of address point

Reported by: ppawel@… Owned by: geocoding@…
Priority: minor Milestone:
Component: nominatim Version:
Keywords: Cc: ESYSCODER

Description

http://nominatim.openstreetmap.org/search.php?q=16%2C+herdera%2C+olsztyn&viewbox=-112.5%2C46.08%2C112.5%2C-46.08

"16, herdera, olsztyn" finds a bridge with ref=16 "herdera 16, olsztyn" finds the proper address

Change History (4)

comment:1 Changed 6 years ago by ESYSCODER

Cc: ESYSCODER added

comment:2 Changed 6 years ago by SQ9NIT

"4, Kętrzyńskiego, Olsztyn" founds railway platform with ref=4

http://nominatim.openstreetmap.org/search.php?q=4%2C+Kętrzyńskiego%2C+olsztyn

"Kętrzyńskiego 4, Olsztyn" founds the proper address.

comment:3 Changed 6 years ago by Sarah Hoffmann

You expect that a partial match for your search term (the street name) is ranked higher than a perfect match. This is a bit tricky to do without breaking search for other countries. You can work around this issue by adding short_name tags with the commonly used abbreviated name to the streets.

The second result works because Nominatim expects the name of an object at the beginning or the end of the query. Thus the 16 or 4 won't be matched against the ref tag.

comment:4 Changed 4 years ago by Sarah Hoffmann

Resolution: fixed
Status: newclosed

This seems to have been fixed with proper reversing of the search query (https://github.com/twain47/Nominatim/commit/e16fcf879d9155602aec3780779ca65c964d0626). At least the two examples work well. Please reopen, if you find other examples where this goes wrong.

Note: See TracTickets for help on using tickets.