Alluvial diagram

A flow visualization whose blocks represent groups at successive stages and whose width-scaled streams show how members or quantities move among those groups over time or categories.

Version

v2 · 2026-09-19 · History

Domain-specific #

3261

Domain group

Interdisciplinary & Synthetic

Origin domain

Data Science & Analytics

Subdomains

Data Visualization, Flow Diagrams → Data Science & Analytics

Core Idea

An alluvial diagram depicts changes in composition by connecting category blocks across axes with ribbons proportional to transferred quantity. Records or weights are aggregated by their sequence of category memberships, and each aggregate becomes a ribbon whose splits and merges reveal structural change. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of data visualization. It is composition-over-stage visualization emphasizing splits, merges and group persistence. That residual remains recognizable when examples, notation, scale, or implementation change, but it disappears if the carrier is mistyped, the condition that block and ribbon widths use a consistent quantitative scale and flows reconcile with declared gains, losses or totals fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test.

How would you explain it like I'm…

River Ribbons Picture

Imagine a picture of kids moving between play corners during recess. Each corner is a block, and colored ribbons show how many kids went from one corner to the next, with fatter ribbons for more kids. You can see groups split up, join together or stay the same. That kind of picture is called an alluvial diagram.

Ribbons Between Groups

An alluvial diagram is a chart that shows how groups change from one stage to the next. It has several columns, and each column is stacked with blocks for the categories at that stage, like which club each student is in each year. Ribbons connect the blocks, and a ribbon's thickness shows how many people or things moved along that path. When a ribbon splits you see a group breaking apart, and when ribbons join you see groups merging. For the chart to be honest, the widths must all use the same scale and the numbers must add up.

Splits-and-Merges Flow Diagram

An alluvial diagram visualizes how the composition of a set changes across stages or categories. Each axis represents a stage, with blocks for the categories at that stage, and ribbons join blocks on neighboring axes. Records are grouped by their sequence of category memberships, and each group becomes a ribbon whose width is proportional to the quantity that moved along that path. Its purpose is to reveal splits, merges and which groups persist. It only works if all block and ribbon widths use one consistent scale and the flows add up correctly with any stated gains, losses or totals; otherwise the picture misleads.

 

An alluvial diagram is a data-visualization form for composition over stages. The data are records (or weights) each carrying a sequence of category memberships across ordered axes. Records are aggregated by their full membership sequence, and each aggregate is drawn as a ribbon connecting the category blocks it passes through, with width proportional to the aggregated quantity. Reading the ribbons shows structural change: splits where a group divides, merges where groups combine, and persistence where a group stays together. The defining constraint is quantitative consistency: block heights and ribbon widths use one scale, and flows reconcile with declared gains, losses or totals between stages. Without that, a chart may look similar but no longer supports the inferences about transfer that make the form useful.

Scope of Application

Alluvial diagram belongs to data visualization and is useful where the analyst can specify successive categorical partitions or stages, blocks sized by quantity, flows linking blocks, stream widths, ordering and color, conserved or changing membership and labels, then evaluate block and ribbon widths use a consistent quantitative scale and flows reconcile with declared gains, losses or totals. The scope is broad within that domain but bounded by the need for block and ribbon widths use a consistent quantitative scale and flows reconcile with declared gains, losses or totals. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity

The abstraction clarifies a crowded vocabulary by making block and ribbon widths use a consistent quantitative scale and flows reconcile with declared gains, losses or totals the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Alluvial diagram can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Alluvial diagram. Alluvial diagram compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

1. Identify the carrier. State what the elements, states, objects, or observations are: successive categorical partitions or stages, blocks sized by quantity, flows linking blocks, stream widths, ordering and color, conserved or changing membership and labels. Reject examples whose alleged carrier belongs to a different problem.
2. Lock the constitutive rule. Express block and ribbon widths use a consistent quantitative scale and flows reconcile with declared gains, losses or totals independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of data visualization because they reuse successive categorical partitions or stages, blocks sized by quantity, flows linking blocks, stream widths, ordering and color, conserved or changing membership and labels, Records or weights are aggregated by their sequence of category memberships, and each aggregate becomes a ribbon whose splits and merges reveal structural change., and type the carrier, state every parameter and convention in the definition, test that block and ribbon widths use a consistent quantitative scale and flows reconcile with declared gains, losses or totals, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Current abstraction Alluvial diagram Domain-specific

Parents (1) — outgoing typed relations

• Alluvial diagram is a kind of Representation Prime

  The diagram represents categorical change through width-encoded flows.

Hierarchy path (1) — routes to 1 parentless root

• Alluvial diagram → is a kind of Representation → presupposes Abstraction

Neighborhood in Abstraction Space

Alluvial diagram sits in a crowded region of the domain-specific corpus (33^rd percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Data Grouping & Rate Measures (5 abstractions)

Nearest neighbors

• Mosaic plot — 0.90
• Area chart — 0.88
• Partition algebra — 0.88
• Mathematical diagram — 0.87
• Scatter plot — 0.87

Computed from structural-signature embeddings · 2026-10-25