[Lens] Multi-dimensional Legend - separate visually

[skearns64]

When creating a multi-dimentional visualization (e.g. Pie chart based on multiple levels of aggs), the legend can sometimes get unwieldy, as the values from both levels of aggregation are combined into a single list.
It would be nice to have the values separated into levels that correspond with the level of the Aggs. I could imagine going in two directions - one where the 2nd level is listed per first-level, and one where the values were simply grouped by level.

Example:
Data: Crime Data about car thefts, containing brand, model, color, etc.
Query: Terms aggregation - top 2 brands (by count of thefts), sub-aggregation: Terms Agg - top 3 models by count of thefts.

Legend Output today (made-up data!):
Ford and Chevrolet are brands that come from the top-level aggregation, while the rest are models that come from the

Ford 
F150
Chevrolet
Taurus
Corvette
Malibu
Fusion
Volt

Possibility 1

Level 1: 
  Chevrolet
  Ford
Level 2:
  F150
  Taurus
  Corvette
  Malibu
  Fusion
  Volt

Possibility 2 (could result in duplication of values, depending on the data)

Chevrolet
  Corvette
  Malibu
  Bolt
Ford
  F150
  Taurus
  Fusion

[ohTHATaaronbrown]

👍 this would make legends for charts with sub aggregations much more readable

[trevan]

I'm looking at implementing the second possibility. Should have a pull request today or tomorrow.

[TiNico22]

+1 this is really difficult to read the legend in case of multiple aggregation level

[GrahamHannington]

+1

Yes, the combined legend of a multilevel pie chart is confusing.

[bertol83]

+1

[kaib]

+1

[enp]

+1

[rggassner]

+1

[viniciuscoimbra]

+1

[iamkelvinloke]

+1

[dav3860]

I agree

[arich-net]

+1

[DanilKonon]

+1

[cwh1te]

+1

[ghudgins]

dependent elastic-charts issue: elastic/elastic-charts#223

[stratoula]

This is available in Lens and aggbased partition charts. Here is a screenshot of a multilevel pie chart with the nested legend switch set to true.

The issue mentioned above elastic/elastic-charts#223 is a bit different and of a larger scope. So I closing this :)