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 50Haga 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.
pelias-parser
has classifier calledWhosonFirstClassifier
to classify the token in the given address string aslocality
,region
andcountry
.In our usecase, a lot of Norwegian street names are classified as a localities and regions.
For example:
Eikeland
is classified as locality even ifland
is the valid street type in addressNordre Eikeland 50
Haga
is classified as locality andbru
is classified as region in addressHaga 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.
We can add the configuration option in the
pelias-config
, whichpelias-api
can send further intopelias-parser
usingoptions
parameter.