Mapping values to diameter inflates them quadratically

What it is

Area-proportional symbol scaling lets value control visible area rather than a circle's diameter or radius directly. Because A = π(d/2)², doubling a diameter with value quadruples area and creates quadratic exaggeration. To make area proportional to a nonnegative value v, radius or diameter must vary with √v. This conclusion follows from geometry and does not depend on whether a reader underestimates area.

Why it happens

Graphics APIs often expose radius, diameter, or an ambiguously named size, while a product specification may intend “size” to mean area. This naming mismatch lets a linear mapping enter unnoticed. For any similar shapes, scaling every linear dimension by k scales area by k²; the issue is not circle-specific. Perceptual error occurs after either correct or incorrect geometry and should not be used to cancel a diameter-mapping defect.

Studying it

Begin with a mapping audit that needs no participant: render known test values, recover bounds or pixel areas, and verify that area ratios equal value ratios, including endpoints. Then compare correct area mapping, diameter mapping, and label assistance on ratio, order, and search tasks, reporting geometrical and human error separately. Property tests should verify monotonicity and explicit zero and missing-value policies, with the same transformation used in responsive layouts, animation, and legends.

Where it stops holding

Area cannot carry a negative value. If size represents magnitude, sign needs a separate position, direction, shape, or accessible-text encoding. Zero mapped to zero area becomes invisible and unfocusable, while missing must not masquerade as zero. A product can provide a minimum interactive mark or distinct zero/missing symbol, but that exception is no longer area-proportional and belongs in the legend. Fixed-width bars encode length and do not need a square root. Log and clipped mappings are different scales and require disclosure.

Applying it

• Specify “value → area” in the encoding contract. For circles use r ∝ √v; scale the linear dimensions of any similar glyph with √v as well.
• Define separate semantics and rendering for negatives, zero, and missing values. Never take the square root of a negative or reuse one minimum circle for both zero and no data.
• Reuse one tested scale for marks, size legend, hit target, and animation rather than reimplementing the transform in each layer.
• Verify areas with known-ratio rendering tests and evaluate judgment with intended readers. Geometric correctness is necessary, not evidence that area is precise enough.

Related

• Same group: U1.04.1 Perceived area systematically underestimates actual area · U1.04.3 3D volume encoding carries the largest error
• Adjacent: U2.06.2 Map values to bubble area, not radius · U1.03.4 Length can only encode non-negative quantities; negatives need position
• Search terms: area-proportional scaling · square-root scale · zero-size mark