[DOCS-3901] Comment on: "manual/reference/operator/aggregation/geoNear.txt" Created: 13/Aug/14  Updated: 03/Nov/17  Resolved: 19/Aug/14

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: Docs Collector User (Inactive) Assignee: Unassigned
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

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


Participants:
Days since reply: 9 years, 26 weeks, 1 day ago

 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.



 Comments   
Comment by Kay Kim (Inactive) [ 19/Aug/14 ]

Fixed during work for DOCS-3112

Generated at Thu Feb 08 07:46:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.