Skip to content
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

Open
karussell opened this issue Aug 22, 2023 · 1 comment
Open

lang=en vs. lang=default #746

karussell opened this issue Aug 22, 2023 · 1 comment

Comments

@karussell
Copy link
Collaborator

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.

@lonvia
Copy link
Collaborator

lonvia commented Feb 9, 2024

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.

lang=default gives so much more of a boost to 'Primekens Kopf' in 'Permecke' (both somewhat similar to 'q=primeke' that the other possible matches are discarded.

This needs some deeper structural changes to the ES query to get fixed. Possibly an early result boost for location bias and bbox.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants