parser
parser copied to clipboard
pelias
natural language classification engine for geocoding
currently, quotes are considered boundary characters with the same semantic meaning as a comma or tab. I think it would be better to consider quoted sections as 'literal', so that...
Looking over the code today I noticed that the query 'Am Falkplatz' (and friends) are relying on a `StopWordClassification` for matching. This seems brittle, this PR replaces it with the...
branched from `stopword-classification`, requires https://github.com/pelias/parser/pull/179 be merged first. This PR is an attempt at solving https://github.com/pelias/parser/issues/178 with minimal changes. However, it seems to solve a longstanding issue which was more...
Add support for/test cases covering `bis/ter` housenumber suffixes for French addresses. ``` 1 bis Av. Amélie, 92320 Châtillon, France ``` ```js { "subject": "1 bis Av.", "housenumber": "1", "street": "bis...
--- #### Here's the reason for this change :rocket: Versions 2.4.0 and 2.5.0 respectively introduced some issues, making certain kinds of input either unparseable or unsuitable for geocoding. Demo links:...
**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...
The following address currently returns zero solutions: ``` P. O. Hviezdoslava 2262/24, Topoľčany, NI, Slovakia ``` It's a complicated parse because: - The street [P. O. Hviezdoslava](https://en.wikipedia.org/wiki/Pavol_Orsz%C3%A1gh_Hviezdoslav) is a proper...
### Bug description As discussed in https://github.com/pelias/parser/pull/195#pullrequestreview-3238761585 is seems the following classification is safe to remove in `classifier/scheme/street.js:120`: ```bash not: ['IntersectionClassification'] ``` ### Steps to reproduce as discussed in https://github.com/pelias/parser/pull/195...
### 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...
**Describe the bug** I've noticed that the parser has issues in some cases with addresses that it should be able to parse. Unfortunately I have a really hard time grokking...