Designing Readable Maps with Clear Symbols, Labels and Color

cartographic design principles

Is your map cluttered or hard to read? The cartographic design principles that matter most come down to matching symbols, labels and color to one purpose and audience, then cutting everything else.

This guide is part of our wider look at geospatial data visualization.

Design detail Value
Common map text size 6pt
Contrast for shapes against background areas 3:1 contrast ratio
Hue limit before readers struggle to tell them apart seven categories
Basic geometry types for map features Points, lines or polygons

These figures come from the Ordnance Survey cartography guide and Esri’s accessibility documentation. They can change, so check the sources before you rely on them.

Start with purpose and audience

Ordnance Survey describes a map as a graphical or symbolised representation of reality, and says its form depends on what it will be used for. A map for a hillwalker in complex mountain terrain looks very different from one showing how votes split across a country or how birds migrate between continents, as the Ordnance Survey guide explains.

That makes the designer’s job a chain of decisions. According to the same guide, a cartographer is responsible for:

  • understanding the use case,
  • selecting the right data for the task,
  • deciding what to show or exclude,
  • presenting it in a way that is understandable and useful.

Write down the audience and the single question the map answers before you open any software. Every later choice, from symbol size to label color, can then be tested against that one purpose.

How should you choose point, line and polygon symbols?

Geographical features can generally be drawn as points, lines or polygons, and the choice often depends on map scale. The Ordnance Survey guide gives the example of a river: a polygon on a town-centre map, but a simple line on a national topographic map.

Point symbols come in three useful styles:

  • Geometric shapes such as circles, squares and triangles.
  • Conventional symbols, such as a red cross for a hospital.
  • Mimetic symbols that look like the object, such as an aeroplane for an airport.

Size can carry meaning too. A city symbol can be larger than the same symbol for a village, and road lines of one feature class can vary in color and width to show relative importance.

Polygons often form the background, so keep them quiet. Conventional fills such as green for woodland, yellow for sand and blue for water help readers decode an area without effort, and patterns such as tree or marsh symbols can add further clarity.

Labels that help instead of clutter

Text adds meaning, but poor use makes a map cluttered and difficult to read. Start with the typeface: Ordnance Survey advises sticking with commonly used, clear fonts and limiting how many appear in a single map.

Several text settings can separate one feature class from another:

  • Serif type often suits natural features, while sans-serif often suits human-made ones.
  • Bold can mark more important features, and italics are often used for historic ones.
  • Larger text signals importance, so a country label outranks a city label.
  • Wide character spacing lets a country or ocean name span its area.
  • Blue text for water and green text for parks echo the colors of the features.

Labels are smaller than most people expect: the Ordnance Survey guide notes that a common map text size is just 6pt. Test your labels at the size and device your readers will actually use.

Zoom level matters as well. In ArcGIS Pro, Esri’s label class guidance says that setting a minimum and maximum scale for labels can improve performance during redrawing, so labels appear only where they are most useful.

Color and visual hierarchy that works for everyone

Esri defines visual hierarchy as a technique that uses contrast and visual variables to draw attention to key details. Its accessibility documentation lists position, size, shape, value, color and pattern as the variables to choose from, based on use case.

cartographic design principles Planning materials
An open notebook and pencil sit among a camera, photographs and navigation accessories.

Use hue for categories and keep the count low. The same Esri page cites research that people struggle to distinguish visual differences beyond seven categories, and it recommends testing shapes against different background areas so they reach a 3:1 contrast ratio.

For ordered data, vary value, meaning lightness, while holding the hue constant. Because value relies on luminance, Esri says it adapts to grayscale better than hue does, which helps people with color vision deficiencies. A choropleth, where darker colors indicate a higher value, is the classic case, and our comparison of heat map vs choropleth map shows when each suits your data.

Check your palette before release. Esri suggests simulating color blindness with a tool such as Color Oracle, or starting from an existing color-blind-friendly ramp. Its related accessibility criteria are the Web Content Accessibility Guidelines on Use of Color and Contrast (Minimum).

A quick checklist before you publish

Run through these steps in order. Each one removes a common cause of unreadable maps.

  1. State the audience and purpose in one sentence.
  2. Remove every feature that does not serve that purpose.
  3. Pick point, line or polygon styling for each remaining feature class at your chosen scale.
  4. Limit fonts, then set label sizes and zoom ranges.
  5. Check hue counts, contrast and a grayscale or color-blind preview.
  6. View the map on the smallest screen or print size your readers will use.

If your map will be interactive, compare web mapping libraries with these steps in mind, so the tool you pick lets you control symbols and labels at each zoom level.

Frequently asked questions

Do I always need a legend?

Show answer

Not for every symbol. Conventional and mimetic point symbols can make features identifiable without a trip to the legend, as the Ordnance Survey guide describes, though unfamiliar or data-driven symbols still need one.

Should a map show every feature I have data for?

Show answer

No. A map that tries to show everything becomes cluttered and confusing, so choose features by the map’s purpose and audience, a point the Ordnance Survey guide makes directly.

Why are some of my labels missing?

Show answer

Label engines usually prevent overlap by default, which hides labels that collide. In ArcGIS Pro you can raise a label class’s priority or force placement, according to Esri’s label guidance, but forced labels can crowd the map.

Can color alone separate my categories?

Show answer

It is safer not to rely on it. Esri recommends patterns such as diagonal lines, dots or crosshatching as dual-encoding, giving readers a second cue that does not depend on color, per its visual hierarchy page.