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

Reduce search query multi_match's neighbourhood boost #1438

Closed
wants to merge 1 commit into from

Conversation

orangejulius
Copy link
Member

After the venue popularity changes in pelias/openstreetmap#531, many venue results are improved.

However, our test for finding the Statue of Liberty, which corresponds to one of our oldest venue popularity related issues, was still showing the statue as the second result, after the ferry terminal on Liberty Island.

I traced this down to scoring boosts given to the ferry terminal because it's part of the Liberty Island neighbourhood, whereas the statue itself is not (for some reason).

In general, I don't think neighbourhoods should make this much of a difference in queries, so this PR reduces the boost given to those matches in search queries.

This doesn't break any other tests, and while we generally don't like to adjust settings for one particular test, I think this change is worth considering.

@orangejulius orangejulius requested review from missinglink and Joxit May 25, 2020 18:49
Copy link
Member

@Joxit Joxit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 😄

@orangejulius
Copy link
Member Author

I looked into this more, and for the Statue of Liberty in the Pelias build I was using at least, the Statue itself is in the WOF neighbourhood Southern Tip, which is similar, but not identical to the Liberty Island neighbourhood. Maybe we should look at having the "Southern Tip" neighbourhood removed, instead of merging this PR.

@orangejulius
Copy link
Member Author

The relevant neighbourhood here has been removed from WOF data after being deemed invalid.

I don't think we need this PR in general, so I'm closing it.

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

Successfully merging this pull request may close these issues.

2 participants