Locations spanning over the 180th meridian

[Timmitry]

Some locations, e.g. the island of Taveuni, span across the 180th meridian. This means that their longitude, going east, approaches 180° and then jumps to -180°.

When searching for Taveuni, the nominatim API returns two results. The first result has a bounding box from -180° to 180°, which would span all longitudes, and is thus wrong. The second result is more useful, and has a bounding box from -180.2925899 to -179.6525899, which we could easily handle.

However, the wrong result always shows first. This also happens for other queries, e.g. "Russia".

[sbungartz]

This has been "fixed" by #6 since we support MultiPolygon and no single GeoJSON Polygon crosses the 180th meridian.
However, the bounding box is still covering a lot of land that is not within the Polygon, so especially for tiny places like Taveuni the Monte-Carlo approach of picking points inside the bounding box until one is inside the polygon takes quite a lot of time.
We can keep this issue open to think of more efficient approaches.