U3.08.1Polar coordinate mappingdesign

Polar coordinates map one variable to angle, the other to radius

Aliases: polar mapping · radial charts

What it is

Cartesian charts map both variables to linear position (horizontal, vertical); polar coordinates speak a different spatial language: angle carries one variable (going around), radius the other (growing outward). Time drawn around a circle gives the clock plot; direction as angle gives the wind rose; categories arranged around a ring give the rose chart. The reading rules change accordingly: not "left to right, bottom to top" but "clockwise advance, farther from centre means larger." Polar coordinates are not a decorative variant but an encoding system with its own semantics and traps — the next four leaflets settle its accounts one by one.

Why it happens

The changed mapping migrates the whole reading grammar: angle is a circular channel (360° returns to start, no first or last), radius a monotone channel (increasing outward from centre). That makes it a natural fit for "one cyclical variable plus one magnitude" data (hour × traffic, bearing × wind frequency); conversely, mapping two linear variables (income × age) forcibly welds linear structure into a ring, and tracing order along an arc costs far more than along a line. Angle and radius also have asymmetric perceptual precision (both angle differences and radial lengths discriminate more poorly than linear position — fifth leaf), the root of polar charts' generally laboured reading.

Where it stops holding

This leaf sets only the coordinate semantics; the radius's area inflation (second leaf), periodic fit (third), radar arrangement (fourth), and magnitude-comparison disadvantage (fifth) each stand in their own place. One boundary deserves advance notice: polar charts carry a heavier coordinate-declaration burden than Cartesian — the angle origin (where 0° sits, clockwise or counter-) and the radius origin (centre = zero, or truncated) must both be explicit, since no industry default unifies these conventions and readers' guesses scatter wildly.

Applying it

  • Audit the data's shape before going polar: one cyclical variable plus one magnitude enters; two linear variables return to Cartesian.
  • Make conventions explicit: annotate the angle origin and direction, the radius origin and scale (centre = 0 must hold — second leaf).
  • Verification: ask readers to say in one sentence "how is this chart read" (what goes around, what goes outward); an inability to answer means the mapping went undeclared — add annotations.

Related

  • Same group: U3.08.2 Equal radius increments give unequal areas; outer rings are systematically enlarged · U3.08.3 Polar coordinates suit inherently periodic variables · U3.08.4 Radar-chart axis order changes the polygon's shape and area · U3.08.5 Magnitude comparison under polar coordinates is harder than in Cartesian
  • Nearby: U3.03.3 The scale type must be prominently labelled · U2.07.1 Angles read imprecisely
  • Search terms: polar coordinates · radial chart · angle radius mapping · cyclic plot

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/U3.08.1