Documents near or on the boundaries of a geoNear search are susceptible to being excluded because the distance calculations in geoNear can produce inaccurate results due to floating point error (i.e. 54.001 - 54 > 0.001). Currently, this is accounted for in flat queries for by slightly expanding the last search interval and filtering with the TwoDPtInAnnulusExpression, but it is unclear if this handles all cases. Also, it may not be correct to return the documents if the distance calculation returns a value over the maxDistance.