WORKFLOW 04 · PUBLIC

Designing a map people can understand

What does this technical information mean for me?

REPRESENTATIVE WORKFLOW

Public-facing GIS has a different finish line. Accuracy is essential, but the experience also has to translate specialist language into recognizable places, likely changes, and clear next steps.

A user should not need to understand layer names, database fields, or agency structure before the map becomes useful. Information design decides what appears first and what remains available for deeper inspection.

THE INFORMATION THAT MATTERS

Layers become useful
in relationship.

  1. 01Plain-language labels
  2. 02Recognizable landmarks
  3. 03Layer hierarchy
  4. 04Popup content
  5. 05Responsive interaction

THE WORKFLOW

01

Start with the user question

Define the decision or understanding the visitor should leave with—not merely the data available to display.

02

Build a visual hierarchy

Prioritize the site, nearby context, and the few layers that directly support the answer.

03

Translate the attributes

Replace internal codes and field names with concise labels, explanations, and links to the source record.

04

Design the interaction

Make hover, click, search, legend, and mobile behavior support the same clear reading path.

05

Test for interpretation

Check whether someone unfamiliar with the project can explain what the map means after using it.

WHAT THE MAP COMMUNICATES

Where the subject is, why it matters, what may change, and where the user can verify or learn more.

OTHER APPLICATIONS

The same pattern.
Different questions.

TOOLS + METHODS

Experience BuilderArcGIS OnlinePopup designCartographyInformation design

This page describes a representative production pattern. Client-specific details and identifying information are intentionally excluded.