The 2d index has a min/max range - however the exact maximum of this range hashes back to the minimum value. This results in incorrect query results when exactly on the boundary.

Unchanged in 2.6, seems to have slipped into 2.4 since the geo_borders.js test is poor.