The existing Grid aggregation source has a few problems
- It is a little confusing for new users without backgrounds with Elasticsearch, aggregations, and geotile_grid aggregation.
- The UI is very tightly coupled to the implementation. In users minds, Heat map and Cluster vectors are very different. There is no reason to couple them in the UI just because they share the same underlying implementation.
I would like to propose spliting the existing Grid aggregation into two sources, Clusers and Heat map. This solves the above problems
- clustering is a pretty universal concept that most GIS users will understand.
- Heat maps can be easily found at the top UI level and are not buried under something that is not very related.
So instead of seeing a single source Grid aggregation that is confusing and hides Heat maps...

Users will see something more like the below where you have Clusters and Heat maps.

Thoughs? Feedback?
The existing
Grid aggregationsource has a few problemsI would like to propose spliting the existing
Grid aggregationinto two sources,ClusersandHeat map. This solves the above problemsSo instead of seeing a single source

Grid aggregationthat is confusing and hides Heat maps...Users will see something more like the below where you have Clusters and Heat maps.

Thoughs? Feedback?