[DOCS-2009] Comment on: "manual/reference/operator/near.txt" Created: 28/Sep/13 Updated: 03/Nov/17 Resolved: 03/Oct/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dan Harasty | Assignee: | Kay Kim (Inactive) |
| 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/near/ |
||
| Participants: | |
| Days since reply: | 10 years, 19 weeks, 6 days ago |
| 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." |
| Comments |
| Comment by Kay Kim (Inactive) [ 03/Oct/13 ] |
|
Hi Dan – the unit of measurements for $maxDistance is "paired" with the coordinates. And for legacy coordinates, the uom is radians. So, am closing this issue for now, with a mind toward some future edits to the geospatial indexes/operators pages to improve clarity. Thanks again. Regards, Kay |