Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to not use the WhosonFirstClassifier for AddressParser #173

Open
mansoor-sajjad opened this issue Jan 10, 2023 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@mansoor-sajjad
Copy link
Contributor

pelias-parser has classifier called WhosonFirstClassifier to classify the token in the given address string as locality, region and country.

In our usecase, a lot of Norwegian street names are classified as a localities and regions.

For example:

Eikeland is classified as locality even if land is the valid street type in address Nordre Eikeland 50
Haga is classified as locality and bru is classified as region in address Haga bru 76

This results in pelias-api filtering out the address layer.

Solution

Solution may be to optionally not use the WhosonfirstClassifier.

Can we make optional using the configuration, like it is done for the admin unit lookup from Whos on First for data importers like pelias-csv-importer using the following configuration.

"imports": {
 "adminLookup": {
   "enabled": false
 },
},

We can add the configuration option in the pelias-config, which pelias-api can send further into pelias-parser using options parameter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant