[Maps] split Grid aggregation source into Clusters and Heat map

[nreese]

The existing Grid aggregation source has a few problems

1. It is a little confusing for new users without backgrounds with Elasticsearch, aggregations, and geotile_grid aggregation.
2. 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

1. clustering is a pretty universal concept that most GIS users will understand.
2. 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?

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[nickpeihl]

👍, but I think we should take care before we add too many more layer options. Or maybe consider grouping layer options in the future.

[alexfrancoeur]

++ to Nick's comment, this list feels like it could continue to grow. Clustering feels like it's well known enough. How does this split affect existing layers in a map? Will it just rename the source details and split some of the styling options? I might be wrong here but I thought heatmap had some unique properties (I'd normally check by am mobile atm)

[nreese]

How does this split affect existing layers in a map? Will it just rename the source details and split some of the styling options?

This will be seamless to the user. Under the covers, a new source heatmap source will be created that just extents the existing geo_grid source.