fix bug in testLat/LonQuantization

This commit is contained in:
nknize 2016-04-07 15:23:04 -05:00
parent b5ce2f67fd
commit d4bb6912fd
1 changed files with 2 additions and 2 deletions

View File

@ -56,7 +56,7 @@ public class TestGeoEncodingUtils extends LuceneTestCase {
assertEquals(encoded, encodeLatitude(decoded)); assertEquals(encoded, encodeLatitude(decoded));
assertEquals(encoded, encodeLatitudeCeil(decoded)); assertEquals(encoded, encodeLatitudeCeil(decoded));
// test within the range // test within the range
if (i != Integer.MAX_VALUE) { if (encoded != Integer.MAX_VALUE) {
// this is the next representable value // this is the next representable value
// all double values between [min .. max) should encode to the current integer // all double values between [min .. max) should encode to the current integer
// all double values between (min .. max] should encodeCeil to the next integer. // all double values between (min .. max] should encodeCeil to the next integer.
@ -105,7 +105,7 @@ public class TestGeoEncodingUtils extends LuceneTestCase {
assertEquals(encoded, encodeLongitude(decoded)); assertEquals(encoded, encodeLongitude(decoded));
assertEquals(encoded, encodeLongitudeCeil(decoded)); assertEquals(encoded, encodeLongitudeCeil(decoded));
// test within the range // test within the range
if (i != Integer.MAX_VALUE) { if (encoded != Integer.MAX_VALUE) {
// this is the next representable value // this is the next representable value
// all double values between [min .. max) should encode to the current integer // all double values between [min .. max) should encode to the current integer
// all double values between (min .. max] should encodeCeil to the next integer. // all double values between (min .. max] should encodeCeil to the next integer.