Skip to main content

Overview

Atlas organizes civic work into a two-level taxonomy: domains (broad categories) and issue areas (specific topics). Every entry in the directory is tagged with one or more issue areas. The autodiscovery pipeline uses these to classify what it finds, and the search interface uses them for filtering.

How it works

  • Entries are tagged at the issue area level, not the domain level
  • An entry can be tagged with multiple issue areas across multiple domains — cross-cutting work is the norm
  • Domains exist for grouping and navigation only
  • The taxonomy evolves as Atlas covers more cities and issues emerge
You can retrieve the full taxonomy programmatically via GET /api/issue-areas and GET /api/domains. See the taxonomy API guide for request patterns.

The taxonomy

Economic Security

Issues around financial stability, employment, and economic opportunity.

Housing and the Built Environment

Issues around where and how people live.

Climate and Environment

Issues around environmental health, climate change, and sustainability.

Democracy and Governance

Issues around civic participation, electoral systems, and democratic institutions.

Technology and Information

Issues around digital life, information systems, and tech accountability.

Education

Issues around learning, access to education, and educational institutions.

Health and Social Connection

Issues around physical and mental health, community bonds, and care systems.

Infrastructure and Public Goods

Issues around the physical systems that communities depend on.

Justice and Public Safety

Issues around criminal justice, policing, and community safety.

Rural-Urban Divide

Issues around the diverging realities of rural and urban communities.

Labor and Worker Power

Issues around workers’ rights, organizing, and economic democracy.

Design principles

Multi-tagging is expected. A community land trust fighting displacement in a flood-prone neighborhood might be tagged housing_affordability + climate_adaptation_and_resilience + environmental_justice_and_pollution. That’s not over-tagging — it’s how Atlas surfaces the connections between issues. Granularity is at the “conversation” level. Each issue area is specific enough that two entries tagged the same way are recognizably working on related things, but broad enough that the taxonomy doesn’t balloon. The taxonomy evolves. As Atlas covers more cities, new issues and framings will emerge. New issue areas get added when existing ones can’t describe a meaningful cluster of entries.

Using the taxonomy in the API

Filter entities by issue area:
Retrieve all issue areas:
Get details for a specific issue area:
Use the MCP tool resolve_issue_areas to map natural language to Atlas issue area slugs:
“What Atlas issue areas relate to affordable childcare?”

Taxonomy API guide

Retrieve domains and issue areas from integrations.

Research a place

Use issue area slugs in place-first searches.

Data model

See how domains, issue areas, entities, and sources fit together.

Trust and provenance

Understand how issue tags should be interpreted with sources.