Treemaps cannot show negatives or support cross-branch comparison

What it is

Rectangle area represents nonnegative magnitude and cannot simultaneously encode a negative sign, so an ordinary treemap cannot faithfully show losses, net outflow, or negative change. It also does not support direct magnitude comparison between parents, children, and objects at different depths: a parent encloses descendants and represents their aggregate rather than an independent mark. “Cross-branch” is not mathematical impossibility in every case. When same-unit leaf values share one global area scale, leaves on different branches remain area-comparable, but nesting makes that comparison indirect and error-prone.

Why it happens

Area has a nonnegative domain. Absolute value removes sign, clamping hides negatives, and colour-for-sign still leaves ambiguous whether area means absolute or net magnitude. Hierarchically, parent and descendants occupy the same space, so comparing them double-counts. Leaves across branches may share global proportional area but lack a common baseline, and parent shapes and borders interfere. Local share also uses each parent as denominator and must not be mislabeled as global value.

Studying it

Construct additive hierarchies containing positive, zero, and negative values and compare treemaps with diverging bars, waterfalls, ranked bars, and coordinated tables. Test sign, net value, parent-child relation, same-level rank, cross-branch leaf comparison, and local share; measure error, time, and denominator confusion. Compare value and share labels to see whether readers mistake a local denominator for the global one. State the compared level and aggregation contract rather than pooling all cross-branch judgments.

Where it stops holding

Separate positive and negative treemaps can show absolute scale on each side, but lack a common zero baseline for direction or net comparison and need a diverging display or table. Zero-area and missing nodes both vanish unless given distinct states. When parents are containers rather than independent values, global leaf comparison across branches is geometrically valid; if exact ranking matters, sorted position or length is still better.

Applying it

• Validate sign, zero, missingness, units, parent-child totals, and denominators before layout. Never silently take absolute values, clamp negatives, or hide unallocated amounts.
• Use diverging bars for sign, waterfalls for contributions to a net, and ranked bars or tables for precise cross-branch comparison; retain treemaps for hierarchical share overview.
• Distinguish raw value, global share, and within-parent share in labels, and list zero, negative, and missing records accessibly.
• Test sign, parent-child, same-level, and cross-branch tasks. Prohibit the inference or change the graphic if readers compare parent with child or confuse denominators.

Related

• Same group: U2.11.1 Treemaps encode shares as areas of nested rectangles · U2.11.2 Deep-node areas get too small to read; cap the depth · U2.11.3 Layout algorithms fix aspect ratios; thin strips resist comparison · U2.11.4 Adjacent rectangles need borders or gaps to show hierarchy
• Adjacent: U2.04.3 Stacking suits totals, not per-series trends · U2.17.1 A mismatched chart forces readers to compute the answer mentally
• Search terms: treemap negative values · cross-level comparison · local share · hierarchical denominator