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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: lonvia [Added to the original trac issue at 10.39pm, Tuesday, 13th November 2012]
The linked_place_id is the culprit here. The search for places does not take it into account but gets the limit. The subsequent lookup in the placex table does look at linked_place_id and reduce the already limited results further.
The easiest fix I can see is to internally work with a limit that is twice the requested limit. That should cover the worst case scenario but also doubles the work load in the worst case. Any other ideas?
Reporter: karussell
[Submitted to the original trac issue database at 8.08pm, Sunday, 11th November 2012]
Example URLs:
http://nominatim.openstreetmap.org/search?format=json&q=hamburg&limit=2
=> correct result
http://nominatim.openstreetmap.org/search?format=json&q=hamburg&limit=1
=> no result
The text was updated successfully, but these errors were encountered: