pelias / pelias/parser

Autocomplete fails for Polish addresses depending on word order

Open
#194 5 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

Bug description

I've encountered an issue with Polish addresses where autocomplete results depend on the order of words in the query. This does not seem to be an issue for addresses in the US.

Steps to reproduce
  • Search with query: "wiejska 1 warsaw" (street, city) → returns results
  • Search with query: "warsaw wiejska 1" (city, street) → does not return results
Github references

No response

Environment

No response

Log output

Data references

No response

Project or organization

No response

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 by reproducing the two Polish queries in the parser's autocomplete flow and compare their classification or matching results. Trace where word order affects address parsing, then add a regression test showing that both query forms return equivalent results. Done means the reversed-order query returns the expected Polish address without changing the existing US behavior.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.