`StructuredFallbackQuery` scoring of `venue` queries.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
When specifying the venue param for /v1/search/structured (ie. when searching for a POI), additional information, such as the postcode and street fields are not considered for scoring.
This results in POI results being returned in insertion order rather than better matches being shown first.
Examples:
The second result matches the postalcode 6011, yet is displayed second:
Adding the address information of the second result returns only address layer results:
Manually specifying layers=venue shows the same results as the original query (incorrectly ordered):
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the venue query through the /v1/search/structured entry point, using the postcode and street examples from the issue. Then inspect layout/StructuredFallbackQuery.js around line 166 to trace which fields contribute to scoring. Done means venue results use the additional address information so better postcode and street matches rank ahead of insertion order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100