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

limit does not seem to work properly for location bias #300

Closed
karussell opened this issue Jan 21, 2018 · 4 comments
Closed

limit does not seem to work properly for location bias #300

karussell opened this issue Jan 21, 2018 · 4 comments
Labels

Comments

@karussell
Copy link
Collaborator

karussell commented Jan 21, 2018

There seems to be something strange with the limit. If I use limit=10 I sometimes get 7 hits, but using limit=7 I only get 4? This seems to occur only for the location bias

@karussell karussell added the bug label Jan 21, 2018
@karussell karussell changed the title Increasing limit does not seem to work properly for location bias limit does not seem to work properly for location bias Jan 21, 2018
@hbruch
Copy link
Collaborator

hbruch commented Jan 21, 2018

This could be caused by a post-query street deduplication, which filters multiple objects of type highway with same name and postal_code.

@karussell
Copy link
Collaborator Author

karussell commented Jan 21, 2018

Ah, cool, didn't know this. If this is the case maybe we then use a heuristic like *1.5 or *2 before simplification to improve the situation a bit? And do you know where this happens?

@hbruch
Copy link
Collaborator

hbruch commented Jan 22, 2018

Such a heuristic (applied for limits >1) could improve this a bit, yes.
The StreetDupesRemover is only used in forward geocoding.

@karussell
Copy link
Collaborator Author

See #301

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

No branches or pull requests

2 participants