From 616c833e17a5f1b0d53b1a877d89d7af36ebeed2 Mon Sep 17 00:00:00 2001 From: Nathan Perry Date: Mon, 9 Jan 2017 14:46:55 -0500 Subject: [PATCH] phrasing smaller geohash string not smaller geographic area --- .../aggregations/bucket/geohashgrid-aggregation.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/aggregations/bucket/geohashgrid-aggregation.asciidoc b/docs/reference/aggregations/bucket/geohashgrid-aggregation.asciidoc index 17ca509e3c5df..3d053d1ef4ac4 100644 --- a/docs/reference/aggregations/bucket/geohashgrid-aggregation.asciidoc +++ b/docs/reference/aggregations/bucket/geohashgrid-aggregation.asciidoc @@ -10,7 +10,7 @@ The resulting grid can be sparse and only contains cells that have matching data Geohashes used in this aggregation can have a choice of precision between 1 and 12. WARNING: The highest-precision geohash of length 12 produces cells that cover less than a square metre of land and so high-precision requests can be very costly in terms of RAM and result sizes. -Please see the example below on how to first filter the aggregation to a smaller geographic area before requesting high-levels of detail. +Please see the example below on how to first filter the aggregation to a larger geographic area before requesting high-levels of detail. The specified field must be of type `geo_point` (which can only be set explicitly in the mappings) and it can also hold an array of `geo_point` fields, in which case all points will be taken into account during aggregation.