diff --git a/source/core/2d.txt b/source/core/2d.txt index 4ddcc66bda8..860c0bc030f 100644 --- a/source/core/2d.txt +++ b/source/core/2d.txt @@ -16,7 +16,7 @@ Use a ``2d`` index if: Do not use a ``2d`` index if your location data includes GeoJSON objects. To index on both legacy coordinate pairs *and* GeoJSON objects, use a -:doc:`2dsphere index `. +:doc:`2dsphere ` index. The ``2d`` index supports calculations on a flat, Euclidean plane. The ``2d`` index also supports *distance-only* calculations on a sphere, but @@ -30,7 +30,8 @@ criteria selects a large number of documents, the additional criteria only filters the result set. The additional criteria *does not* result in a more targeted query. -MongoDB allows one ``2d`` index per collection. +MongoDB allows one ``2d`` index per collection. MongoDB also allows one +:doc:`2dsphere ` index per collection. .. important:: You cannot use a ``2d`` index as a shard key when sharding a collection. However, you can create and maintain a diff --git a/source/core/2dsphere.txt b/source/core/2dsphere.txt index af1e5a02be9..8ec1db0f9e1 100644 --- a/source/core/2dsphere.txt +++ b/source/core/2dsphere.txt @@ -22,6 +22,9 @@ documents. You can arrange the fields in any order. The default datum for an earth-like sphere in MongoDB 2.4 is :term:`WGS84`. Coordinate-axis order is **longitude, latitude**. +MongoDB allows one ``2dsphere`` index per collection. MongoDB also +allows one :doc:`2d ` index per collection. + .. important:: You cannot use a ``2dsphere`` index as a shard key when sharding a collection. However, you can create and maintain a geospatial index on a sharded collection by using a different field