You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: lonvia [Added to the original trac issue at 3.52pm, Friday, 17th April 2015]
That result is not really wrong but a result of generous fuzzy matching and the ordering is correct.
There was an issue with Nominatim being to generous with including surrounding postcode points when a postcode area was available but that has been fixed in osm-search/Nominatim@5d87136
I've forced an reindex on your example address now and you'll see that the second result is gone. Addresses of other roads will gradually follow as the data gets changed in OSM.
Reporter: flohoff
[Submitted to the original trac issue database at 7.24am, Sunday, 12th April 2015]
Hi,
the address:
56727 Mayen, Bergstrae 12
returns 2 results.
Correct:
http://nominatim.openstreetmap.org/details.php?place_id=2581169749
Broken
http://nominatim.openstreetmap.org/details.php?place_id=2571390463
I guess result 2 is taken into account is because of the "Landkreis Mayen-Koblenz" which matches the Mayen.
Result 1 is a much better match though. Its an exact match on the town and an exact match on the postcode.
The text was updated successfully, but these errors were encountered: