LUCENE-7125: remove additional confusion (we already quantize once, don't do it again).

This commit is contained in:
Robert Muir 2016-03-21 22:47:31 -04:00
parent d74572ac9c
commit 69da13ff6f
1 changed files with 3 additions and 17 deletions

View File

@ -53,28 +53,14 @@ public class TestLatLonPointQueries extends BaseGeoPointTestCase {
@Override
protected Boolean rectContainsPoint(GeoRect rect, double pointLat, double pointLon) {
assert Double.isNaN(pointLat) == false;
int rectLatMinEnc = LatLonPoint.encodeLatitude(rect.minLat);
int rectLatMaxEnc = LatLonPoint.encodeLatitude(rect.maxLat);
int rectLonMinEnc = LatLonPoint.encodeLongitude(rect.minLon);
int rectLonMaxEnc = LatLonPoint.encodeLongitude(rect.maxLon);
int pointLatEnc = LatLonPoint.encodeLatitude(pointLat);
int pointLonEnc = LatLonPoint.encodeLongitude(pointLon);
if (rect.minLon < rect.maxLon) {
return pointLatEnc >= rectLatMinEnc &&
pointLatEnc <= rectLatMaxEnc &&
pointLonEnc >= rectLonMinEnc &&
pointLonEnc <= rectLonMaxEnc;
return GeoRelationUtils.pointInRectPrecise(pointLon, pointLat, rect.minLon, rect.minLat, rect.maxLon, rect.maxLat);
} else {
// Rect crosses dateline:
return pointLatEnc >= rectLatMinEnc &&
pointLatEnc <= rectLatMaxEnc &&
(pointLonEnc >= rectLonMinEnc ||
pointLonEnc <= rectLonMaxEnc);
return GeoRelationUtils.pointInRectPrecise(pointLon, pointLat, -180.0, rect.minLat, rect.maxLon, rect.maxLat)
|| GeoRelationUtils.pointInRectPrecise(pointLon, pointLat, rect.minLon, rect.minLat, 180.0, rect.maxLat);
}
}