Node ordering and crossing count decide readability

What it is

Node order determines whether bands cross, bend, or detour between Sankey stages, affecting whether readers retain a flow's identity. Crossing control often minimizes crossings or path length and keeps high-volume flows straight, but crossing count is not the sole definition of readability. Domain sequence, chronology, adjacency, label space, and stable identity across views may matter more. Ordering is a task-driven view transformation, not a unique order inherent in the data.

Why it happens

Bands are more likely to cross when their endpoints have inconsistent relative orders. Each crossing or close parallel run adds visual rebinding, especially for similar colours, thin widths, and long paths. Layouts commonly use barycentric, median, or swapping heuristics to reorder nodes within layers. The problem admits multiple local solutions, and initialization, weights, and constraints affect the result. Straightening major flows can serve the primary task while pushing thin flows into longer, denser routes.

Studying it

Hold flow values constant and compare domain order, value sorting, and multiple layout algorithms on named-flow tracing, source or destination lookup, node-total auditing, and unusual-path detection. Manipulate crossing count and angle, path length, width, colour or pattern, node count, and display size. Measure errors, time, backtracking, pointer traces, or gaze. Report task performance alongside crossings; preference for a tidy layout is not evidence of readability. Perturb initialization to see whether an important finding depends on one layout.

Where it stops holding

Do not break a meaningful chronology, process sequence, or hierarchy merely to reduce crossings. Nodes may be reordered within stages while stage order remains fixed. A minimum-crossing layout does not prove that adjacent nodes are similar or important. Colour and outlines support tracking, but translucent mixtures at crossings can imply nonexistent categories; critical flows need direct labels and focus states. Interactive reordering should be reversible and preserve node, band, filter, and screen-reader focus identity. Backward links require separate treatment as cyclic structure.

Applying it

• Declare ordering goals and hard constraints: preserve domain order, prioritize critical flow, reduce crossings, or shorten paths. Do not present an automatic layout as natural order.
• Fix seeds and parameters and record pinned nodes. Keep positions stable through refreshes, filters, and related pages when feasible.
• Give critical bands direct labels, keyboard focus, endpoint summaries, and non-colour highlighting. Let screen-reader users traverse by source or destination.
• Test end-to-end tracing of representative medium and thin flows. When errors cluster at crossings, reorder, stage, filter, or split the view, accepting improvements by task rather than a universal crossing limit.

Related

• Same group: U2.12.1 Sankey diagrams encode conserved flows as band width · U2.12.3 With huge magnitude gaps, small flows vanish · U2.12.4 Backflow and loops disqualify the Sankey · U2.12.5 Band width is a length encoding; one scale for the whole diagram
• Nearby: U2.10.2 Row and column ordering decides whether structure is visible · U2.03.3 Beyond a few lines, tracking collapses
• Search terms: Sankey node ordering · crossing minimization · barycentric heuristic · flow tracing