[DOCS-2890] Contradictory advice about storing coordinates Created: 10/Mar/14 Updated: 25/Mar/14 Resolved: 25/Mar/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| 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 | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 47 weeks, 1 day ago | ||||
| Description |
|
This page: http://docs.mongodb.org/manual/applications/geospatial-indexes/ ... begins with the sound advice to use a 2dsphere index with GeoJSON coordinates, and a 2d index with legacy coordinates. It then says to use a 2dsphere index with GeoJSON *or* legacy coordinates. This is all technically accurate, but only the sages understand why. Let's make clear that 2dsphere indexes offer backwards compatibility with legacy coordinates as a convenience, but it's not really the right way to do things. As it stands now, the page appears to contradict itself. |
| Comments |
| Comment by Githook User [ 25/Mar/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 25/Mar/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |