We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Each point has a field called category that contains some valuable information, it would be nice to use this information in the scoring algorithm.
category
We could have a file weighted_categories.yml where we can define what weight each tag value corresponds to.
weighted_categories.yml
airport: 12 railway: 10 restaurant: 8 tourism: 11 poi:landmark: 10 ...
This should be a query time boosting easily do-able by just adding a script and using it in the API sorting logic.
Related to pelias/openstreetmap#33 and pelias/pelias#50
The text was updated successfully, but these errors were encountered:
sevko
Successfully merging a pull request may close this issue.
Each point has a field called
category
that contains some valuable information, it would be nice to use this information in the scoring algorithm.We could have a file
weighted_categories.yml
where we can define what weight each tag value corresponds to.This should be a query time boosting easily do-able by just adding a script and using it in the API sorting logic.
Related to pelias/openstreetmap#33 and pelias/pelias#50
The text was updated successfully, but these errors were encountered: