restrict number of results for reverse queries

When given a coordinate off the coast of a large town, the entire
town may end up in the potential results during the reverse query.
Postgres then needs to sort tens of thousands of results before it
can determine the clostest one. Given that the results at such a
large search radius are bound to be imprecise anyway, restrict
the number of results postgres should consider to 1000.
This commit is contained in:
Sarah Hoffmann
2017-10-25 22:34:29 +02:00
parent f78d094483
commit adbbb1ce02
2 changed files with 17 additions and 3 deletions

View File

@@ -45,3 +45,9 @@ Feature: Reverse geocoding
Then result addresses contain
| house_number | road |
| 5 | Clasingstraße |
Scenario: Location off the coast
When sending jsonv2 reverse coordinates 54.046489113,8.5546870529
Then results contain
| display_name |
| Freie und Hansestadt Hamburg, Deutschland |