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.
Reporter: kiddo [Submitted to the original trac issue database at 10.52pm, Wednesday, 7th May 2008]
Searching "la prairie" takes forever, searching "prairie" is a matter of seconds.
I was told that any search that involves a common word like "la" will be slow as there are a lot of places with that in their name to consider.
Shouldn't osm just discard it like google does, especially since it's short? Or if this can't be worked around this way, maybe add additional search fields to specify the country+region? that should surely make performance (and result relevance) better?
In any case, the search performance when including short words like "la" is horrible, and there is no way to tell namefinder to stop the search and refine it.
The text was updated successfully, but these errors were encountered:
Reporter: kiddo
[Submitted to the original trac issue database at 10.52pm, Wednesday, 7th May 2008]
Searching "la prairie" takes forever, searching "prairie" is a matter of seconds.
I was told that any search that involves a common word like "la" will be slow as there are a lot of places with that in their name to consider.
Shouldn't osm just discard it like google does, especially since it's short? Or if this can't be worked around this way, maybe add additional search fields to specify the country+region? that should surely make performance (and result relevance) better?
In any case, the search performance when including short words like "la" is horrible, and there is no way to tell namefinder to stop the search and refine it.
The text was updated successfully, but these errors were encountered: