Maps

Categorical / unique-value map

Assigns geographic features distinct colours or symbols according to category.

  • Map
  • Geography
  • Classification

What it answers

Where are different geographic categories located?

Shape
Features coloured by category
What it shows
Spatial distribution of classes.

Example

The question

Which sales team covers each region?

Regions by responsible sales team (categorical map)

Regions by responsible sales team (categorical map)Each region filled with its team’s colour and labelled. North team: 5 regions; Coast team: 5 regions; City team: 5 regions; South team: 4 regions.North teamCoast teamCity teamSouth teamR1R2R3R4R5R6R7R8R9R10R11R12R13R14R15R16R17R18R19
Regions by responsible sales team (categorical map)Each region filled with its team’s colour and labelled. North team: 5 regions; Coast team: 5 regions; City team: 5 regions; South team: 4 regions.North teamCoast teamCity teamSouth teamR1R2R3R4R5R6R7R8R9R10R11R12R13R14R15R16R17R18R19
Each region filled with its team’s colour and labelled. North team: 5 regions; Coast team: 5 regions; City team: 5 regions; South team: 4 regions.

Illustrative data. It belongs to no company.

When to use it

Use it when

Land use, administrative types or discrete classifications.

Avoid it when

Using a sequential palette that implies category order.

How to read it

Match feature colours or symbols with category labels.

Note

Use a categorical legend.

The data you need

Layout
Attribute table plus geographic boundaries
Fields
FeatureID: text; Category: text; geometry or geographic boundary reference
One row is
One geographic feature with a category. What is the grain?
Rules
Join category records to the matching features. Use consistent category labels and a categorical legend.
Optional
Names alone may be ambiguous. Geometry can be GeoJSON, a spatial file or a tool-supported boundary lookup.
Preparation
Validate the input grain and missing values. Join category records to the matching features. Use consistent category labels and a categorical legend.
Units
Categories have no numeric order or common denominator unless separately supplied.
Example of the input layout: Attribute table plus geographic boundariesAn attribute table joined to map shapes by a shared region code.RegionValueR1R2R3R4Joined by region code
An attribute table joined to map shapes by a shared region code.

Worked example

R1=Urban, R2=Rural. Assign distinct categorical fills; neither colour implies a larger amount.

FeatureIDCategory
R1Urban
R2Rural