[DOCS-1677] $geoNear queries and legacy points Created: 05/Jul/13 Updated: 08/Jul/13 Resolved: 08/Jul/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 32 weeks, 2 days ago |
| Description |
|
http://docs.mongodb.org/manual/reference/operator/nearSphere/ : "In a 2dsphere index, a grid coordinate is interpreted as a GeoJSON point." This is unclear. It seems to imply that a $geoNear query with a grid coordinate like [1, 2] will act the same as a $geoNear query with a GeoJSON point--that is, it will calculate $maxDistance in *meters*. This is false: $geoNear acts like other geospatial operators, interpreting $maxDistance in radians for grid coordinates and in meters for GeoJSON coordinates. While we're here, can we standardize on either "grid coordinates" or "legacy coordinate pairs" as the term for non-GeoJSON points? |
| Comments |
| Comment by auto [ 08/Jul/13 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |