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
What steps will reproduce the problem?
1. Use async branch to search a large database, using large max distance.
What is the expected output? What do you see instead?
max_results results are returned, but they are not clustered around the search
location. They may be offset towards one compass quadrant (NE, SE, SW, NW)
What version of the product are you using? On what operating system?
Async branch, patched for issues 13, 16, 23, 33.
Please provide any additional information below.
This behaviour is caused by over optimisation. max_results are found and
returned before searching adjacents geocells of equal resolution for closer
results.
Eliminate this behaviour by changing geomodel.py from:
if len(results) >= max_results:
if DEBUG:
logging.debug(('GeoModel Proximity Query: '
'Wanted %d results, ending search') %
(max_results,))
break
to:
if len(results) >= max_results and len(cur_geocells) == 4:
if DEBUG:
logging.debug(('GeoModel Proximity Query: '
'Wanted %d results, ending search') %
(max_results,))
break
Original issue reported on code.google.com by [email protected] on 5 Nov 2012 at 12:45
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 5 Nov 2012 at 12:45The text was updated successfully, but these errors were encountered: