[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/
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


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 –
thank you so much for taking the time to comment (as well as running your tests) for the $near. I've verified with our engineer, the legacy coordinates are radians. He concurred with your statement that (paraphrasing) –

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

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