-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lang=en vs. lang=default #746
Comments
The two queries have already different result lists when used without the location bias. We currently structure the query such that the location bias more or less only results in reordering of the search results without location bias, so that the closer result is never really considered.
This needs some deeper structural changes to the ES query to get fixed. Possibly an early result boost for location bias and bbox. |
Even with exact query, name is not found in lang=default results:
but matched in lang=en
|
Explicitly set 'en' when using a language not specifically supported by GraphHopper instead of relying on leaving out the parameter, as this has some issues. See: komoot/photon#746
Explicitly set 'en' when using a language not specifically supported by GraphHopper instead of relying on leaving out the parameter, as this has some issues. See: komoot/photon#746
Explicitly set 'en' when using a language not specifically supported by GraphHopper instead of relying on leaving out the parameter, as this has some issues. See: komoot/photon#746
See the following requests:
https://photon.komoot.io/api/?q=primeke&lang=default&lat=59.863704493020094&lon=17.639317368224624
https://photon.komoot.io/api/?q=primeke&lang=en&lat=59.863704493020094&lon=17.639317368224624
Both OSM nodes have only a "name" tag and no "name:en", so that I wouldn't expect a difference.
The text was updated successfully, but these errors were encountered: