Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
None
-
*Location*: http://docs.mongodb.org/manual/reference/operator/near/
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.76 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/reference/operator/geoIntersects/
*Screen Resolution*: 1600 x 900
*repo*: docs
*source*: reference/operator/near
*Location*: http://docs.mongodb.org/manual/reference/operator/near/ *User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.76 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/reference/operator/geoIntersects/ *Screen Resolution*: 1600 x 900 *repo*: docs *source*: reference/operator/near
Description
The text states:
"If you query for legacy coordinate pairs, specify $maxDistance in radians."
But I think – from my tests – the correct statement would be:
"If you query for legacy coordinate pairs, specify $maxDistance in whatever unit you are using for your coordinates. For example, if your units are UTM "easting/northing", then the unit is implicitly meters. If you are using latitude and longitude, the unit is degrees – but note using degrees this way is naive, and conversion to linear distance is problematic."