A map that encodes value in area only tells the truth if its projection actually preserves area

What it is

Maps that encode values through area—choropleths, proportional-symbol maps—must use an equal-area projection. This is a coding-consistency requirement, not a style preference: the visual grammar of these maps is "area size = value size," and readers compare regions by area; under a non-equal-area projection, areas are systematically distorted (at different rates per region), breaking the correspondence between area and value—the channel readers compare through outputs a distorted signal.

Why it happens

The necessity comes from the fairness precondition of area as an encoding channel: comparisons drawn from a choropleth ("this province is darker / larger than that one") are a compound judgment of area and color, and area distortion stacks onto the color mapping. The canonical harm: a global GDP choropleth in Mercator inflates the visual area of high-latitude countries (Canada, Russia, Greenland) severalfold—even with correct colors, "big dark blocks" carry visual weight far beyond their true data share, systematically steering readers' attention and memory toward high latitudes. Equal-area projections (Albers equal-area conic, equal-area cylindrical, Mollweide, sinusoidal) guarantee that any enclosed region's map area is a fixed proportion of its true area, so the "area = comparison basis" premise holds. Proportional-symbol (bubble) maps differ slightly: symbol size encodes value and position encodes place, so the basemap's area distortion does not directly pollute symbol size—but it distorts spatial relations and density impressions (high-latitude symbols pushed apart), so an equal-area basemap remains the fairer choice. Filled heatmaps and hexbin maps follow the same logic: unequal bin areas distort density perception.

Where it stops holding

Equal-area's cost is shape distortion: regions at high latitudes and projection edges get flattened or stretched, making shape recognition ("is this Italy?") harder—an inevitable exchange of equal-area, mitigated by choosing projection parameters that place the region of interest at the distortion minimum (e.g., Albers standard parallels set within the data extent). Equal-area does not always "look natural": Web maps commonly use Web Mercator basemaps, and overlaying equal-area data creates misalignment between regions and basemap—the correct fix is matching data and basemap projections. When the map serves only as a positional reference (which city a point is in) and carries no area comparison, the equal-area requirement can relax—the requirement follows the encoding channel, not the map itself.

Applying it

• Default choropleths and hexbin maps to an equal-area projection; when overlaying choropleths on web maps, confirm basemap-data projection consistency.
• Configure equal-area parameters to the data's coverage (e.g., Albers standard parallels at 1/6 and 5/6 of the range).
• Prefer equal-area basemaps for proportional-symbol maps too, so density impressions are not skewed by projection.
• Verification: render the same choropleth under an equal-area and a non-equal-area projection and compare readers' judgments of "the largest region"; inconsistency means the projection is influencing value interpretation.

Related

• Same group: U12.01.1 No planar projection can preserve area, angles, and distances simultaneously · U12.01.3 The Mercator projection severely inflates areas at high latitudes · U12.01.4 Projection choice must change with the map's coverage · U12.01.5 The projection used should be stated in the caption
• Nearby: U12.01.3 The Mercator projection severely inflates areas at high latitudes · U12.01.1 No planar projection can preserve area, angles, and distances simultaneously
• Search terms: equal-area projection · choropleth · Albers