venue name parsing
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 64
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
related to https://github.com/pelias/api/pull/1380
we're currently not doing a great job of parsing venue names where the place classification comes at the end of the input:
node bin/cli.js Café Pelias
(0.40) ➜ [ { place: 'Café' } ]
node bin/cli.js Café Pelias Geocoder
(0.22) ➜ [ { place: 'Café' } ]
node bin/cli.js Pelias Café
(0.90) ➜ [ { place: 'Pelias Café' } ]
node bin/cli.js Pelias Geocoder Café
(0.80) ➜ [ { place: 'Pelias Geocoder Café' } ]
examples: https://brandongaille.com/list-45-catchy-coffee-shop-house-names/
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 with the examples in bin/cli.js and trace the parser path used for venue names. Run the four Café Pelias and Pelias Café commands to compare classification results. Done means venue names whose place classification appears at the end are parsed with the full name, matching the existing leading-classification behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100