Geohash Grid Aggregation - Option to Return Latitude/Longitude Bounding Box

[doc987]

The geohash_grid bucket aggregation (https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-geohashgrid-aggregation.html) returns the geohash as the "key" property. It would be nice if there was an option to get equivalent latitude and longitude bounding box (GeoJSON bounding box is [west,south,east,north] https://tools.ietf.org/html/rfc7946#section-5) either in addition, or as a replacement for the hash.

Note that the bounding box mentioned here is the the same box as the geohash, which is not necessarily the same as computing the minimum bounding box of the data in that Geohash using the geo_bounds aggregation.

[elasticmachine]

Pinging @elastic/es-analytics-geo

[imotov]

@doc987 could you describe the use case for this bounding box?

[Destroy666x]

Mostly a QoL change - getting it instantly rather than having to use another library to decode the geohash. And why would you get it? To use it for Google Maps Javascript API, for example, it has functions to pan to or fit bounding box while hash doesn't matter.

[imotov]

I see, so basically use outside of Elasticsearch DSL (which already supports using geohashes, returned by aggs for for filtering).

[doc987]

Agree.

[imotov]

We talked about that and decided that adding coordinates will provide a lot of additional overhead in case of large number of buckets, while giving very little benefits since the bounding box can be easily calculated on the client side. However, we should improve the documentation though with some examples on how to calculate the bounding box from the geohash.