You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running a self hosted installation of Pelias for some internal applications and i've observed some strange behavior.
Whenever i search for a street only using its abbreviated form (e.g. Woogstr. instead of Woogstraße), Pelias is unable to find it.
However, when i use the full street name, it suddenly appears. Here is an example:
I've previously opened an issue for a similar bug (#1594), but this seems to be a different issue. However, i'm not sure if this is actually is a bug in the code or just a problem with the imported data, because the street is clearly there! I'm using the latest version of Pelias and the polylines were imported following the instructions at pelias/polylines using an up-to-date OSM extreact.
Any help is very much appreciated!
The text was updated successfully, but these errors were encountered:
Hey,
I'm running a self hosted installation of Pelias for some internal applications and i've observed some strange behavior.
Whenever i search for a street only using its abbreviated form (e.g. Woogstr. instead of Woogstraße), Pelias is unable to find it.
However, when i use the full street name, it suddenly appears. Here is an example:
Woogstr. Frankfurt
Woogstraße Frankfurt
For comparison, when i search for the same street using dev.api.geocode.earth, it finds it no problem!
https://pelias.github.io/compare/#/v1/search?text=Woogstr.+Frankfurt
I've previously opened an issue for a similar bug (#1594), but this seems to be a different issue. However, i'm not sure if this is actually is a bug in the code or just a problem with the imported data, because the street is clearly there! I'm using the latest version of Pelias and the polylines were imported following the instructions at pelias/polylines using an up-to-date OSM extreact.
Any help is very much appreciated!
The text was updated successfully, but these errors were encountered: