Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support bounding box aggregation on geo_shape/geo_point data types. #5634

Closed
yeroc opened this issue Mar 31, 2014 · 0 comments
Closed

Support bounding box aggregation on geo_shape/geo_point data types. #5634

yeroc opened this issue Mar 31, 2014 · 0 comments

Comments

@yeroc
Copy link

yeroc commented Mar 31, 2014

For applications that index spatial data it would be very useful to be able to request an aggregation that would return the bounding box (extent) of the matching hits. A typical use case would be to zoom a map to area containing matching hits.

colings86 added a commit that referenced this issue Jun 3, 2014
The GeoBounds Aggregation is a new single bucket aggregation which outputs the coordinates of a bounding box containing all the points from all the documents passed to the aggregation as well as the doc count. Geobound Aggregation also use a wrap_logitude parameter which specifies whether the resulting bounding box is permitted to overlap the international date line.  This option defaults to true.

This aggregation introduces the idea of MetricsAggregation which do not return double values and cannot be used for sorting.  The existing MetricsAggregation has been renamed to NumericMetricsAggregation and is a subclass of MetricsAggregation.  MetricsAggregations do not store doc counts and do not support child aggregations.

Closes #5634
@clintongormley clintongormley changed the title Aggregations: Support bounding box aggregation on geo_shape/geo_point data types. Support bounding box aggregation on geo_shape/geo_point data types. Jun 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants