-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
quadtree_grid aggregation #24587
Comments
@nknize any thoughts? |
FixitFriday: removing the discuss label and assigning to Nick. This soulds like a useful feature but we need to validate whether we can execute such an aggregation efficiently. |
Pinging @elastic/es-search-aggs |
Agreed this would be useful for heatmap drawing on the front-end, so +1 from me. Seems like a somewhat similar request to #16895 (comment) |
Hi @yavuzmester, We have created a new Does this enable your use-case? You still only are returned a representation of the bucket, and need to use client-side logic to translate each bucket into a visual tile on a map. |
@yavuzmester you might also be interested in #39810 |
I'm going to close this, since I think the |
We are drawing heatmaps with quadtrees. For each 256px tile, we dive 8 levels in the quadtree and find the pixel value that way.
In elasticsearch we can have a location field with the following mapping:
location: {
type: geo_shape,
tree: quadtree,
tree_levels: 25,
points_only: true
}
But there is only geohash_grid aggregation. What about quadtree_grid aggregation where in the response keys are paths like [0,2,1,3,0,1].
The text was updated successfully, but these errors were encountered: