-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:
*Location*: http://docs.mongodb.org/manual/core/2d/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31
*Referrer*: http://docs.mongodb.org/manual/core/geospatial-indexes/
*Screen Resolution*: 1440 x 900
*repo*: docs
*source*: core/2d
*Location*: http://docs.mongodb.org/manual/core/2d/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31 *Referrer*: http://docs.mongodb.org/manual/core/geospatial-indexes/ *Screen Resolution*: 1440 x 900 *repo*: docs *source*: core/2d
Hi,
The 2.4 docs indicate that 2d indexes should be in the order: longitude, latitude.
I'm almost positive that this is the wrong order for 2d indexes. I believe the new order is long/lat for 2dsphere indexes, but that the 2d index order must be lat/long.
Can you confirm?