Interface SeriesGroups

Single → BAR layer; multiple → one segmented layer.

One DOT layer each, in series order.

One LOLLIPOP layer each, in series order.

Merged into a single multi-line layer (one entry per line) — a LINE, or the BUMP the same lines become when they carry ranks. The two are one bucket because they are one layer: what differs is how the numbers are announced, not which mark each position addresses.

Merged into a single STEP layer, the staircase counterpart of the above.

Merged into one AREA / STACKED_AREA / NORMALIZED_AREA layer.

Merged into a single RADAR layer (one entry per closed outline).

Merged into a single POLAR_AREA layer, the wedge counterpart of the above.

One HISTOGRAM layer each, in series order.

One HEATMAP layer each, in series order.

One PIE layer each, in series order.

One FUNNEL layer each, in series order.

One WATERFALL layer each, in series order.

One CANDLESTICK layer each, in series order.

A candlestick and an OHLC share the bucket for the reason they share a trace type: the same five numbers, a different mark, and the same one column per candle for the highlight to point at (#1053).

One DUMBBELL layer each, in series order.

One GANTT layer each, in series order.

One TREEMAP, ICICLE or SUNBURST layer each, in series order.

One bucket for three layouts because they are one tree drawn three ways and the highlight walks the same nodes whichever it is. Which mark to measure is decided from the layer's trace type where the resolver is built, since that is the part that differs.

One WORD_CLOUD layer each, in series order.

One SANKEY or CHORD layer each, in series order.

One bucket for both because they are one weighted graph drawn two ways — the same extractFlowLinks walk, the same ribbon per link — and only the announced type differs. An ArcDiagram lands here too, as a sankey. A declared alluvial does not: it is the same am5flow series read a third way, so it travels in declaredList with the other declared layers.

One NETWORK layer each, in series order.

One CHOROPLETH layer each, in series order.

The one bucket that carries a declaration alongside the series, because a map is the one type this adapter reads BOTH ways: an am5map MapPolygonSeries bound to a valueField is a choropleth on its own, and one whose value hangs on a column amCharts was never told about is a choropleth the author declared. Both emit TraceType.CHOROPLETH, so one ordered bucket keeps the layers and their sources in step — which two buckets could not, since the layers interleave in series order.

One layer each for the series that declared what they mean, in series order — a survival curve, an error bar, a forest plot, a cloud.

Kept as the plan rather than as a series list: a declared layer routinely spans several series (the column drawing an interval, the arms merged into one curve), and the highlight has to walk exactly the ones the layer was built from.