The Practice Of Community Mapping For Resilience And Belonging

James C. Scott's Seeing Like a State opens with a meditation on scientific forestry in 18th-century Prussia. The state needed to measure trees for tax purposes, so it reduced forests to board-feet of timber. Over a generation, this measurement reshaped the forest itself — diverse ecosystems got replaced with monocultures of straight-growing Norway spruce, planted in grids, optimized for legibility. The first generation of these forests thrived because they were parasitic on the soil built up over centuries of diverse growth. The second generation collapsed. The German forestry service invented a word for what happened: Waldsterben. Forest death.

Scott's larger argument is that states have always needed to make complex reality legible in order to govern it, and that the act of simplification inevitably destroys information that turns out to be essential. The map is not the territory, but states have historically had the power to reshape the territory to match the map.

Community mapping is a direct response to this problem. It's the practice of reinserting the information states delete.

Government GIS systems are extraordinary technical achievements. A modern municipal database can tell you parcel boundaries, zoning, tax history, utility easements, flood zones, soil types, traffic counts, crime incidents, school boundaries, bus routes. This is useful data. Planners, emergency managers, utility companies, real estate agents all rely on it. But the data schema itself determines what can be known.

A parcel database cannot tell you that three generations of one family have lived in the house on a specific lot. A crime incident map cannot tell you that the "dangerous intersection" is actually where teenagers hang out because there's nowhere else to go. A bus route map cannot tell you that half the riders on the 14B are nursing home aides working two shifts. A flood zone map cannot tell you which basements have been pumped by which neighbors for decades.

The information states exclude isn't random. It's specifically the relational, narrative, and emotional texture that makes a place a place rather than a grid of coordinates. It gets excluded because it's hard to standardize, impossible to aggregate, resistant to being entered into a database field. So it disappears from the record. So it disappears from decision-making.

This is not a conspiracy. It's a structural feature of how states see. And the cost of this structural blindness is paid by communities every time a highway gets routed through a neighborhood because a planner in a distant office was looking at a map that didn't show the church, the barber shop, and the sixty years of interwoven relationships about to get bulldozed.

The modern participatory mapping movement has several distinct lineages worth knowing about.

Parish mapping (UK, 1980s-present). Common Ground, a UK charity founded by Sue Clifford and Angela King in 1983, launched the Parish Maps project in 1985. The idea was simple: invite local people to map what they valued about their place, in whatever form suited them. By the 1990s, thousands of parishes across Britain had produced their own maps — paintings, tapestries, collages, booklets — celebrating local distinctiveness. The maps weren't for planning purposes. They were acts of collective attention. Common Ground argued that noticing what you have is the prerequisite for defending it, and that communities who can articulate their distinctiveness are harder to steamroll.

Asset-Based Community Development (ABCD) mapping. John McKnight and Jody Kretzmann published Building Communities from the Inside Out in 1993, introducing ABCD as a framework. Their central critique was that "needs assessments" — the standard tool of social service planning — systematically produced deficit-based maps of communities, cataloging what was broken and teaching residents to see themselves as problems to be solved. ABCD inverted this by mapping assets: individual skills, associations, local institutions, physical resources, the local economy. The practice of asset mapping became foundational in community organizing, shifting countless neighborhoods from a deficit frame ("we are poor") to an asset frame ("we have these 127 specific capacities").

Green Map (1992-present). Wendy Brawer started Green Map in New York as an ecological mapping project. Over three decades, it evolved into a system with a shared icon set that's been adapted in 65+ countries, mapping everything from community gardens to toxic sites to cultural heritage. Green Map pioneered the idea of a common visual grammar that let local maps remain locally specific while being mutually legible across regions.

MIT CoLab and planning justice. The Community Innovators Lab at MIT has worked since the early 2000s on participatory planning methodologies, often in partnership with grassroots organizations. Their work on "planning justice" treats the methodology of how a community is planned as inseparable from the justice of the outcome. CoLab projects have ranged from neighborhood planning in Boston's Dudley Square to land use planning with favela residents in Rio.

PlaceMatters and PublicEngine (2005-2015 era). Based in Denver, PlaceMatters developed and popularized digital tools for public engagement in planning processes, including "keypad polling" and interactive mapping interfaces. Their work demonstrated that technology could either amplify or undermine participatory processes depending on whether it was designed to surface local knowledge or to extract predetermined inputs.

Public Participation GIS (PPGIS). The academic field of PPGIS emerged in the 1990s around the question of how GIS technology could be made accessible to communities rather than being a tool of state and corporate power. The debates within PPGIS are worth reading — they surface the tensions between technical rigor and participatory legitimacy that show up in any community mapping practice.

Counter-mapping. Indigenous and marginalized communities have used mapping as an act of political assertion since long before "community mapping" was a term. Nancy Peluso's 1995 paper "Whose Woods Are These? Counter-Mapping Forest Territories in Kalimantan, Indonesia" is a foundational text. Counter-mapping uses the language and authority of cartography to assert claims that state maps deny — land tenure, sacred sites, customary use, historical occupancy.

A community map typically has layers that a state map doesn't.

Assets layer. Individual skills and capacities, local associations, informal institutions, physical resources held by residents, local economic activity that doesn't show up in tax records. The retired nurse three doors down. The guy with the pickup truck. The church basement that could hold 80 people in an emergency. The informal childcare network run by four grandmothers.

Narrative layer. Stories attached to specific places. The site of the old school. The tree planted when the neighbor's daughter was born. The corner where the neighborhood was founded. The alley where the riot happened in 1967. The restaurant that used to be a speakeasy.

Emotional layer. Places of fear, places of safety, places of memory. The streetlight that's out. The intersection where someone died. The stoop where people sit on summer evenings. The spot that "doesn't feel right."

Relational layer. Who knows who. Who checks on whom. Who's related to whom. Who has a key to whose house. Who's been feuding since 1988. Who the actual mayor of the block is, regardless of who the elected official is.

Historical layer. Demolished buildings still remembered. Former uses of current sites. Residents who've moved or passed. The bakery that closed in '97. The grove that was cut for the parking lot.

Hazards layer (local knowledge version). Not FEMA flood zones — the specific basements that flood. Not crime statistics — the specific stretches where you don't walk alone after 9. Not official contamination records — the lot where everyone knows something was buried.

Needs layer. Specific, granular, relational. Not "the neighborhood needs better transit" but "Ms. Henderson needs rides to dialysis on Tuesdays and Thursdays."

None of this is legible to a GIS database. All of it is essential to actually living there.

The sociological research on community mapping converges on a finding that practitioners have known for decades: the map is less valuable than the mapping.

Robert Putnam's work on social capital (Bowling Alone, 2000) documented the collapse of American civic associational life across the second half of the 20th century. One of the hardest losses to replace was the structure of routine, low-stakes interaction that used to produce neighborhood familiarity — the bowling leagues, the PTA meetings, the bridge clubs, the union halls. People who never meet don't build trust. People who never build trust don't cooperate. People who don't cooperate don't solve collective problems.

Community mapping sessions rebuild this structure in compressed form. A two-hour mapping session produces:

- Face-to-face contact between neighbors who might otherwise never speak. - Shared attention to a common object (the map). - Exchange of specific, local, non-political information. - Surfacing of individual expertise ("oh, I used to do that for a living"). - Discovery of latent assets ("I had no idea you had a truck"). - Mild but real collective agency ("we should do something about that streetlight").

The research on "place attachment" (see Setha Low, Place Attachment: A Critical Inquiry) shows that these are the exact ingredients that convert a group of residents into a functional community. Not demographic similarity. Not ideological alignment. Shared attention to place, plus low-stakes opportunities to share knowledge, plus the resulting discovery of one another.

This is why mapping is a tool of resilience. Communities don't become resilient during disasters. They become resilient in the months and years beforehand, through the slow accumulation of the kind of relationships a mapping session produces. When the storm hits, the pipes burst, the power fails, the mill closes — resilient communities don't need to invent the social infrastructure. They just activate what already exists.

Daniel Aldrich's research, synthesized in Building Resilience: Social Capital in Post-Disaster Recovery, tracked recovery trajectories across multiple disasters — the 1995 Kobe earthquake, Hurricane Katrina, the 2004 Indian Ocean tsunami, the 2011 Tohoku disaster. His finding, controlling for damage severity, infrastructure, and aid received: social capital was the strongest predictor of recovery. Neighborhoods with denser pre-existing networks recovered faster. Neighborhoods where residents already knew each other by name didn't need to spend the first two weeks of a disaster figuring out who was missing.

Community mapping is one of the cheapest, lowest-friction ways to build this capital.

The methodology varies across traditions, but a workable baseline session looks like this.

Before: convene and prepare.

Identify the scale you're mapping. A block, a street, a neighborhood of 500 households, a small town. Too big and the map becomes abstract. Too small and the network is too thin. 50-200 households is a sweet spot for a first session.

Recruit 8-15 participants. Diversity matters — longtime residents and newcomers, elders and young adults, different blocks, different backgrounds. Personal invitations work better than flyers. Feeding people always helps.

Print a large base map. A big aerial photo works well, printed 3x4 feet or larger, taped to a wall or laid on a table. Include enough context to orient people but not so much detail that you're reifying state categories. Some practitioners deliberately strip administrative overlays and use only the physical landscape.

Get sticky notes, markers, tape. Have a notetaker and a facilitator. The facilitator should be from the community if possible.

During: the session itself.

Open with 10 minutes of context — what this is, why we're doing it, how the session will flow. Be explicit that there is no "right" map, that this is not a government process, and that nothing said here is going to be used against anyone.

Do an introductions round where each person names themselves, how long they've lived there, and one thing they love about the place. This signals that stories are welcome.

Structure the mapping in passes:

- Pass 1: Assets. "Mark places that matter. Places you love, places that help, places people gather." Let people walk up and place notes on the map. Encourage storytelling as people mark things. The facilitator asks follow-up questions: why does that matter? What happens there?

- Pass 2: Hazards and concerns. "Mark places that worry you, places that aren't working, things that need attention." Different colored notes. Same process.

- Pass 3: Memory. "Mark places that used to be something. Places with history. Things people should know about this neighborhood." This pass often unlocks the richest storytelling and the deepest relationship-building. Elders become visible as carriers of knowledge the newcomers didn't know they needed.

- Pass 4: People. "Who lives where? Who has what skills? Who needs checking on? Who's new? Who should we know?" This is the most sensitive pass and has to be handled with care — consent matters, privacy matters. But done well, this pass is the core deliverable.

Close with a reflection round. What did you learn? What surprised you? What's one thing you want to do next?

After: document and continue.

Transcribe the map into a version that can be shared. Return it to participants first. Do not share publicly without explicit consent from the people whose information is on it.

Schedule a follow-up within 30 days. Mapping sessions that don't lead to a next gathering tend to fade. The follow-up can be a second mapping session expanding to new participants, a working group tackling one specific thing that surfaced, or a simple block party to thank people and maintain momentum.

Extractive mapping. An outside organization runs a mapping session to harvest local knowledge for their own purposes — a grant application, a planning document, a research paper. The community provides data; the organization reaps the benefit. This replicates the state logic that community mapping is supposed to resist. If you're running a session and the output goes to an outside entity, be explicit about that, give the community veto power, and share authorship.

Professionalization. Consultants learn the vocabulary, run the sessions as a paid service, produce professional-looking deliverables, and leave. The relationships don't form because the facilitator isn't part of the community. The map is more polished but less alive. Community mapping works best when the mapmakers are also the mapped.

Over-digitization. Fancy tools can crowd out the human practice. A laptop-based mapping interface often produces worse relational outcomes than paper and sticky notes, because people look at their own screen instead of at each other. Digitize later if useful, but map together on paper first.

Skipping the relational layer. Some community mapping projects focus narrowly on physical assets and miss the people. An asset map without the relational information is half a map. You learn that the church has a commercial kitchen, but you don't learn that Deacon Williams would actually let you use it at 3am in an emergency.

Privacy violations. Marking "Ms. Henderson, dialysis Tuesdays" on a public map is dangerous. Some layers of a community map should never be public. The methodology needs to distinguish between layers intended for publication (assets, history, narrative) and layers that stay in the community (specific names, medical needs, household details). A good mapping practice has explicit consent protocols for every layer.

No follow-up. The single biggest failure mode. A session happens, the energy is real, and then nothing. Six months later, the relationships have faded and the map is in a drawer. Momentum requires maintenance. Even a monthly 30-minute check-in keeps the thing alive.

You don't scale community mapping the way you scale a platform. You can't centralize it and keep what makes it work. But you can proliferate the practice.

A town of 10,000 people doesn't need one map. It needs 40 blocks that have done their own. A city of 200,000 needs 800 blocks that have done their own. The maps can talk to each other — shared visual language (Green Map's icon system, for example), shared data standards for the layers that should be public, optional aggregation for city-wide planning — but the sessions happen at the block and neighborhood scale because that's where the relational work actually happens.

Some municipalities have begun to support this infrastructure without controlling it. Portland's "Neighbors Together" framework funded neighborhood mapping grants without dictating methodology. Vancouver's Engaged City framework built mapping into its participatory budgeting process. These are early experiments. The risk in all of them is co-optation — the moment the state makes community mapping a prerequisite for funding, it becomes a compliance exercise and the practice dies.

The healthier pattern is civil society scaffolding. Groups like the Asset-Based Community Development Institute, the Orton Family Foundation's "Community Heart & Soul" initiative, and the Tamarack Institute have trained thousands of practitioners who now run sessions in their own neighborhoods without needing permission from anyone. The model is open-source. Anyone can learn it. The practice spreads peer-to-peer.

1. Your block, one hour. Print or sketch your block. Walk the whole thing. Mark every house. Write down what you know about each — who lives there, how long, what they do, anything memorable. Be honest about the blanks. Bring the map to one neighbor and ask them to fill in what they know. Notice how much of your own block you don't know.

2. The elder interview. Find someone who's lived in your neighborhood for 40+ years. Ask them to walk a block with you and tell you what used to be there. Record it with permission. You will hear things that exist nowhere else.

3. The asset audit. Make a list of every skill you know your neighbors have — from professional expertise to hobby competence. Write down at least 25 specific capacities within a three-block radius. If you can't get to 25, you have your assignment: find out.

4. The convening. Invite six neighbors to your kitchen table. Have a printed map of the block and sticky notes. Two hours, three passes (assets, concerns, history). Bring food. Do not skip the food.

5. The scenario. After your block map exists, sit with it alone and imagine: three-day power outage in February. Who has a generator? Who needs checking on first? Where does everyone gather? Who has the skills to keep a shelter running? If you can't answer these, you know what your next mapping session is about.

- Scott, J. (1998). Seeing Like a State. Yale University Press. - McKnight, J., & Kretzmann, J. (1993). Building Communities from the Inside Out. ACTA Publications. - Aldrich, D. (2012). Building Resilience: Social Capital in Post-Disaster Recovery. University of Chicago Press. - Putnam, R. (2000). Bowling Alone. Simon & Schuster. - Low, S., & Altman, I. (Eds.) (1992). Place Attachment. Plenum Press. - Peluso, N. (1995). "Whose Woods Are These? Counter-Mapping Forest Territories in Kalimantan, Indonesia." Antipode, 27(4). - Common Ground UK. Parish Maps project archives — commonground.org.uk. - Green Map System — greenmap.org. - MIT Community Innovators Lab — colab.mit.edu. - ABCD Institute — resources.depaul.edu/abcd-institute. - Orton Family Foundation, Community Heart & Soul methodology.

If every person said yes to their neighbors once — yes to two hours at a kitchen table with a map, yes to sharing what they know about the block, yes to hearing what their neighbor knows — the information required to solve the local half of world hunger and world peace would already be drawn. It would turn out your block already has the food, the skills, the shelter, the childcare, the medical knowledge, the tools, and the relationships it needs. It's all there. It's just never been mapped.

The next session is on you.