[DOCS-6292] Multi-location documents for 2dsphere indexes Created: 29/Sep/15 Updated: 11/Jan/17 Resolved: 12/Oct/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Andrew Ryder (Inactive) | Assignee: | Andrew Aldridge |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 8 years, 16 weeks, 3 days ago | ||||
| Description |
|
Regarding our wonderful doc on multi-location documents for 2D indexes: There is no equivalent document explaining how to do this in 2dsphere indexes. A 2dsphere index achieves the same effect via the use of "MultiPoint" GeoJSON objects, which is a sufficiently different mechanism as to not be immediately obvious for people who are upgrading from a 2D index. It might be nice to call this out on the above document. |
| Comments |
| Comment by Githook User [ 25/Oct/15 ] |
|
Author: {u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 16/Oct/15 ] |
|
Author: {u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Andrew Aldridge [ 12/Oct/15 ] |
|
Thanks for the report! |