Symbology and Color Theory for Maps

Why Symbology Matters

A map is only useful if readers can extract the right information quickly and without confusion. Symbology — the system of marks, colors, shapes, and sizes used to represent geographic features — controls what readers see first, what they compare, and what conclusions they draw. Poor symbology buries the message; good symbology makes spatial relationships obvious at a glance. Because GIS professionals produce maps that inform land-use decisions, infrastructure planning, and public safety responses, clarity is an ethical obligation, not just an aesthetic preference.

The Visual Hierarchy Principle

Every map has a subject. The subject must be the most visually prominent element on the page. Supporting context — base layers, roads, county boundaries — should recede visually so they frame rather than compete with the data. Designers achieve hierarchy through contrast in color value, symbol weight, and line thickness. A common error is rendering background parcel boundaries with the same line weight as the thematic feature you are trying to highlight, making both layers fight for attention. Rule of thumb: foreground symbols are darker, thicker, or more saturated than background symbols.

Renderer Types in ArcGIS Pro

ArcGIS Pro offers several renderers in the Symbology pane:

• Single Symbol — every feature in the layer shares one symbol. Use this for reference layers (roads, county outline) where only location matters.
• Unique Values — each distinct attribute value gets its own symbol. Use this for nominal (categorical) data such as land-use codes or road surface type. Do not imply order with color when the data has none.
• Graduated Colors — sequential or diverging color ramps applied to numeric data divided into classes. Use this when magnitude matters (assessed value, population density).
• Graduated Symbols — symbol size scales with class breaks in a numeric field. Good for point features when you want readers to compare rough magnitudes.
• Proportional Symbols — symbol size scales continuously and exactly with the data value, not with class breaks. More precise than graduated symbols but harder to read when values span a wide range.

Choosing the wrong renderer introduces a lie. Applying graduated colors to a nominal field suggests an order or progression that does not exist in the data.

Color Theory Essentials

Color has three perceptual dimensions that map designers control:

• Hue — the basic color identity (red, blue, green).
• Saturation — the intensity or purity of the color.
• Value (lightness/darkness) — how light or dark the color appears.

For sequential data (low to high), use a single-hue ramp where value increases with the data: light tones for low values, dark tones for high values. This respects the intuitive association between darkness and magnitude.

For diverging data (values that deviate above and below a meaningful midpoint, such as population change relative to a base year), use two contrasting hues that converge at a neutral midpoint color.

For qualitative (nominal) data, use distinct hues with similar saturation and value so no category appears more important than another.

ColorBrewer2.org, developed by cartographer Cynthia Brewer, provides rigorously tested palettes for all three data types. The site flags which palettes are safe for print, screen, and photocopying. Always start here rather than inventing a palette.

Color-Vision Deficiency Accessibility

Approximately 8% of men and 0.5% of women have some form of color-vision deficiency (CVD). The most common form, red-green deficiency (deuteranopia and protanopia), makes red and green appear similar. A map that relies solely on red-versus-green contrast to distinguish categories is unreadable for a significant portion of your audience.

Best practices:

1. Prefer ColorBrewer palettes tagged as CVD-safe. These are tested against the most common deficiency types.

2. Pair color with a second visual variable — pattern, shape, or label — so color is not the only differentiator.

3. Test your map using a simulator such as Coblis (Color Blindness Simulator) before final production. Upload a screenshot and cycle through deficiency types.

4. Avoid pure red/green pairings for any map intended for public use or regulatory submission.

Legend and Symbol Consistency

Every symbol on the map must appear in the legend with a label that matches the data, not the field name. Field names in databases (e.g., `LU_CODE`, `ASSR_VAL`) are never appropriate legend text. Labels should be plain English: Agricultural Land Use, Assessed Parcel Value (USD).

Symbol sizes, line weights, and colors in the legend must exactly match what appears on the map. ArcGIS Pro populates the legend automatically from the Symbology pane, so editing symbols in the pane — not directly in the layout — keeps legend and map in sync.

Legibility at Print Scale

Design at the scale you intend to print or share. A map designed at 1:5,000 on screen may have lines too thin to reproduce at 1:24,000 on a plotter. Point symbols smaller than approximately 4 points (pt) and lines thinner than 0.3 pt are typically lost in print. When producing a map for a large-format plotter, proof a section at full size before final output.

Safety Note

When using a large-format plotter or color printer, follow the equipment manufacturer's operating instructions. Ensure the paper path is clear before feeding media, keep hands clear of moving rollers, and use proper ventilation when handling solvent-based inks. If the plotter is shared lab equipment, sign it out per the lab's schedule and leave the work area clean for the next user.