[DOCS-8123] $geoNear distanceMultiplier Created: 17/Jun/16 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Jake Angerman | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
There are discrepancies on the units used for various fields for $geoNear. The description for the distanceMultiplier field for $geoNear says
Also, the description for minDistance says,
however a 2dsphere index will convert legacy coordinate pairs to GeoJSON Point. So I can have a field like this:
whose 2dsphere index will convert it into
such that I can specify minDistance in meters even though the documentation says it should be in radians. The near field sheds some light:
So the main factor appears to be the index used (2dsphere vs 2d) instead of whether the point is GeoJSON or legacy coordinate pair. Comment on: "reference/operator/aggregation/geoNear.txt" |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |