Interface PlotlyTrace

Line styling. shape is how plotly joins consecutive samples: linear and spline interpolate, while hv, vh, hvh and vhv draw a piecewise-constant staircase.

What the trace fills towards: tozeroy, tonexty, toself, … Plotly resolves an unfilled trace to the string 'none' rather than dropping the attribute, so a filled trace is any other non-empty value.

The stack this trace belongs to. Plotly stacks scatter traces that name the same group, drawing them as an area chart whose bands sit on one another; an empty or absent value means the trace stands alone.

How a stack group is rescaled: percent makes each column sum to 100, fraction to 1. Empty or absent leaves the bands at their own totals.

A heatmap's grid of magnitudes — and a choropleth's flat column of them, which is the same attribute carrying one value per region rather than one per cell.

A grid cell may be null: that is how plotly's own documentation writes a hole in a field, and the readers here treat any non-number as one.

Value-axis offset every bar-like size is measured from. An ARRAY floats each bar from its own offset, which is how a schedule is drawn: the bar starts at base[i] and runs for the duration in x[i].

Text drawn at, or associated with, each point. A word cloud is a scatter whose terms live here, and a choropleth names its regions here when the locations themselves are codes.

Hover-only text. Plotly.py's hover_name resolves to this.

Glyph styling for the text marks. An ARRAY of sizes is what makes a text scatter a word cloud: the size is per term rather than per trace.

Author-supplied values carried through to hover templates and events.

Plotly's own arbitrary-metadata attribute, and the slot a co-located maidr declaration rides in — trace.meta.maidr. Typed unknown because it is very often a plain string that has nothing to do with MAIDR; readDeclarationSlot narrows it.

How wide each bar is drawn, in position-axis units. Ordinary bar styling — which is exactly why a non-uniform array is NOT read as a marimekko on its own. It becomes data only once a trace declares type: 'mosaic'.

What each step does to the running total: relative contributes, total restates it, absolute resets it. Parallel to the position array, and relative where it says nothing.

Which half of each violin is drawn. positive is plotly's own ridgeline recipe: the curves are halved so they can overlap without hiding one another.

Inner box overlay. Plotly draws path.box only when visible is true.

Mean line overlay drawn across the violin.

Bin bounds for a histogram binned up the y axis. Plotly puts the samples on y and the counts on x for orientation: 'h', and the bin size moves to ybins with them.

How a histogram reduces the samples that fall in a bin. Plotly's default is 'count', which is why a 2D histogram's cells are counts unless the trace says otherwise.

Slice labels, in the order the trace was authored.

Slice magnitudes, parallel to labels.

Each sector's parent, parallel to labels. An empty string means the sector sits at the root. Plotly matches these against ids when a trace has them and against labels otherwise.

Sector ids, for a hierarchy whose labels repeat. Parallel to labels.

How many levels below the entry point are drawn; -1 for all of them.

The sector the layout is entered at, drawing that subtree alone.

The nodes the flows run between.

The flows themselves, held as three parallel arrays. source and target are INDICES into node's labels rather than the names a MAIDR flow carries.

The measure a gauge draws.

What the measure is called. Only the indicator traces carry one.

The dial. Present only when mode includes gauge.

The comparison an indicator draws its delta against.

Which polar subplot the trace is drawn on (polar, polar2, …). Polar traces carry this instead of an xaxis/yaxis pair.

Radial coordinates — the magnitude on each spoke.

Angular coordinates — which spoke each value sits on.

Which geo subplot the trace is drawn on (geo, geo2, …). A choropleth carries this instead of an xaxis/yaxis pair.

The regions shaded, named the way locationmode addresses them — an ISO code, a state name, a GeoJSON feature id. Parallel to the values in z.

One entry per axis, each carrying the whole column of observations. Plotly stores the transpose of the row-per-observation grid MAIDR reads.

Whether plotly reorders the slices largest-first before drawing them. Defaults to true, so the authored order is NOT the drawn order unless a trace turns this off.

Fraction of the paper the trace occupies, [start, end] in [0, 1] on each side. A pie is positioned by this rather than by axes, so it is the only thing that says where one sits relative to its siblings.

The iso-value curves the trace draws.