Replies: 1 comment 7 replies
-
In general 'km 840' is not supported and not data mapped in OpenStreetMap so it's always better to remove it from the query. https://nominatim.openstreetmap.org uses the The tokenizer got completely rewritten and osm-search/Nominatim#2588 improves the house-number matching (not clear if that explains the difference for this query though as KM 840 is not a house number). You can try the new tokenizer with the I should note at the same time https://nominatim.openstreetmap.org is also behind, e.g. reindexing OSM data, so it can happen results on your local fresh installed instance are better in some regions of the world. |
Beta Was this translation helpful? Give feedback.
-
Hello!
For some addresses, the matching process between our local instance and the OSM-hosted instance seems to differ.
Simple example:
https://nominatim.openstreetmap.org/ui/search.html?street=VIA+NAZIONALE+DELLE+PUGLIE+KM+840&city=CASORIA&country=IT
The OSM-hosted instance returns several results, the first of which is osm_id = W908701685.
When I run a search on our instance with the exact same GET parameters, I get no results. However, running the details request locally confirms that this Node DOES exist in our DB:
GET /details?osmtype=W&osmid=908701685
.Our local instance starts returning results when we wither remove the house number
840
from thestreet
parameter, or when we remove the tokenKM
.What could be causing this inconsistency between the two instances?
Thanks for your help :) Awesome project, by the way 👏
Details:
Beta Was this translation helpful? Give feedback.
All reactions