@@ -32,7 +32,7 @@ best tree_levels value to honor this precision. The value should be a
32
32
number followed by an optional distance unit. Valid distance units
33
33
include: `in`, `inch`, `yd`, `yard`, `mi`, `miles`, `km`, `kilometers`,
34
34
`m`,`meters`, `cm`,`centimeters`, `mm`, `millimeters`.
35
- | `meters `
35
+ | `50m `
36
36
37
37
|`tree_levels` |Maximum number of layers to be used by the PrefixTree.
38
38
This can be used to control the precision of shape representations and
@@ -42,7 +42,7 @@ certain level of understanding of the underlying implementation, users
42
42
may use the `precision` parameter instead. However, Elasticsearch only
43
43
uses the tree_levels parameter internally and this is what is returned
44
44
via the mapping API even if you use the precision parameter.
45
- | `50m`
45
+ | various
46
46
47
47
|`strategy` |The strategy parameter defines the approach for how to
48
48
represent shapes at indexing and search time. It also influences the
@@ -119,14 +119,14 @@ Geohashes are base32 encoded strings of the bits of the latitude and
119
119
longitude interleaved. So the longer the hash, the more precise it is.
120
120
Each character added to the geohash represents another tree level and
121
121
adds 5 bits of precision to the geohash. A geohash represents a
122
- rectangular area and has 32 sub rectangles. The maximum amount of levels
123
- in Elasticsearch is 24.
122
+ rectangular area and has 32 sub rectangles. The maximum number of levels
123
+ in Elasticsearch is 24; the default is 9 .
124
124
* QuadPrefixTree - Uses a
125
125
http://en.wikipedia.org/wiki/Quadtree[quadtree] for grid squares.
126
126
Similar to geohash, quad trees interleave the bits of the latitude and
127
127
longitude the resulting hash is a bit set. A tree level in a quad tree
128
128
represents 2 bits in this bit set, one for each coordinate. The maximum
129
- amount of levels for the quad trees in Elasticsearch is 29.
129
+ number of levels for the quad trees in Elasticsearch is 29; the default is 21 .
130
130
131
131
[[spatial-strategy]]
132
132
[float]
0 commit comments