pelias / pelias/parser

Parsing Belgium street name

Open
#182 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
64
Forks
26
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
Autocomplete for Ter Waarde 91 or Ter Waarde 91, Ypres, Belgium or Ter Waarde 91, 8900 Ypres, Belgium always fails to return the proper result because pelias parser seems to want Waarde as a locality

       "santizer:text:pelias_parser": [[](https://pelias.github.io/compare/#)
          "0.60 ➜ locality='Waarde', postcode='8900', country='Belgium'",
          "0.57 ➜ postcode='8900', locality='Ypres', country='Belgium'"
        ]

Steps to Reproduce
https://pelias.github.io/compare/#/v1/autocomplete?text=Ter+Waarde+91%2C+Ypres%2C+Belgium&debug=1

trying to force address doesn't work either
https://pelias.github.io/compare/#/v1/autocomplete?layers=address&text=Ter+Waarde+91%2C+Ypres%2C+Belgium&debug=1

Expected behavior
Find this result
https://pelias.github.io/compare/#/v1/search?text=Ter+Waarde+91%2C+Ypres%2C+Belgium&debug=1
https://pelias.github.io/compare/#/v1/place?ids=openaddresses%3Aaddress%3Abe%2Fvlg%2Fbosa-region-flanders-nl%3A91ab227c88a0dfad&debug=1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Pelias compare autocomplete requests for “Ter Waarde 91, Ypres, Belgium”, including the address-only variant, and compare their parser classifications with the linked search and place results. The issue is done when autocomplete returns the expected OpenAddresses result instead of treating “Waarde” as the locality; no source file or test is named, so the relevant parser entry point and regression test must be located.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.