Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
None
-
*Location*: http://docs.mongodb.org/manual/reference/operator/aggregation/geoNear/#pipe._S_geoNear
*User-Agent*: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/reference/operator/aggregation-pipeline/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: reference/operator/aggregation/geoNear
*Location*: http://docs.mongodb.org/manual/reference/operator/aggregation/geoNear/#pipe._S_geoNear *User-Agent*: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/reference/operator/aggregation-pipeline/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: reference/operator/aggregation/geoNear
Description
There is conflicting information on this page regarding the geoNear command and manual/reference/command/geoNear with regards to maxDistance. This page states that distance should be given in radians while the other page states that radians should only be used for legacy coordinate pairs.
Granted that one is a aggregation command and the other is not, but I have been using $geoNear in an aggregation pipeline with GeoJSON objects and have experienced that maxDistance in this instance requires meters and not radians as the text on this page explicitly states.