Repository navigation
limit parameter changes result #1104
Answered
by
lonvia
romanpickl
asked this question in
Q&A
|
Hi, It seems as if the limit parameter has a big impact on the result quality in this case: https://photon.komoot.io/api/?q=Kaiserswerther%20Stra%C3%9Fe%20404,%2040474%20D%C3%BCsseldorf&limit=10 https://photon.komoot.io/api/?q=Kaiserswerther%20Stra%C3%9Fe%20404,%2040474%20D%C3%BCsseldorf&limit=50 is this expected? Thanks a lot, |
Answered by
lonvia
Aug 6, 2026
Replies: 1 comment
|
Yes, that is a known issue and very difficult to fix. Or rather: we could hide it from the user by always working with the maximum allowed limit. Only that doesn't fix the underlying issue that for some queries the correct answer is not in the first N returned with the initial internal filter query. |
0 replies
Answer selected by
romanpickl
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes, that is a known issue and very difficult to fix. Or rather: we could hide it from the user by always working with the maximum allowed limit. Only that doesn't fix the underlying issue that for some queries the correct answer is not in the first N returned with the initial internal filter query.