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.

Sign up for GitHub

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

Jump to bottom

Housenumber tuning #197

Closed
karussell opened this issue Oct 6, 2015 · 2 comments
Closed

Housenumber tuning #197

karussell opened this issue Oct 6, 2015 · 2 comments
Milestone
0.3.0

Comments

@karussell
Copy link
Collaborator

Another user reported problem is a street and housenumer with a character e.g. see here with '10e' vs. here where '10 e' leads to removal of 'e' and to incorrect results

Related: #187

As the (German) user noted we should investigate other 'mixed content' housenumbers like described in the wiki
@hbruch
Copy link
Collaborator

hbruch commented Jan 5, 2018

Related: #221

See also geocoders/geocoder-tester#28 for housenumber testcases.

@hbruch hbruch added this to the 0.3.0 milestone Mar 13, 2018
@hbruch
Copy link
Collaborator

hbruch commented Mar 13, 2018

I suggest to close, as above mentioned issue is fixed via #288.

Both queries, Bornkamp 10e Lübeck and Bornkamp 10 e Lübeck return expected match.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.3.0
Development

No branches or pull requests
2 participants
@karussell @hbruch