How to Create a Community Heritage Map Together

Start with a shared question, not a blank basemap

To create a community heritage map, assemble a group with real connections to the place, agree on one useful question, set consent and access rules, gather varied sources, record uncertainty, and review the draft with contributors before publishing. Choose tools only after deciding what the map is for. A paper map covered in careful stories can be more valuable than a dazzling website no one consented to join.

A community heritage map might document neighborhood gathering places, changing street names, local industries, migration routes, lost buildings, food traditions, or memories of a landscape. It does not need to contain everything. In fact, “everything” is usually where a promising project wanders into the brambles.

1. Define the purpose in one sentence

Write a sentence that names the place, subject, audience, and use. For example:

We are mapping places where residents gathered between the 1960s and 1990s so present-day neighbors can understand how community life changed.

That is workable. “We are mapping local heritage” is too broad. A sharper purpose guides which people to invite, which sources to seek, what time period matters, and what should appear in the legend.

Ask the group:

• Who should use this map?
• What question should it help them answer?
• What geographic and time boundaries are useful?
• Who is represented in the likely sources—and who is missing?
• Is public publication actually the right outcome?

Record the answers in a short project charter. Include who can make decisions, how disagreements will be handled, and when the group will revisit the scope.

2. Build a team that shares authority

Invite people because of their relationships and knowledge, not only their job titles. A useful team may include residents, cultural practitioners, librarians, archivists, youth, elders, local historians, accessibility advocates, language speakers, and someone comfortable with mapping tools.

Representation is not accomplished by placing one person from a community on a committee and handing them the entire burden of correction. Decide how contributors will be paid or otherwise supported, how meetings will be accessible, and how language or transport barriers will be addressed.

Clarify roles:

One person can hold several roles in a small project, but the responsibilities should still be named. Otherwise “someone should back that up” becomes a traditional song performed shortly after a laptop fails.

3. Agree on ethics before collecting stories

Decide what the map will never publish, what needs permission, and who can change an access decision. Sensitive material may include precise locations of sacred places, archaeological sites, endangered species, private homes, burial grounds, undocumented migration, or accounts that could expose people to harm.

Consent must be informed and specific. A contributor should know:

• The project's purpose and organizers
• What will be recorded or collected
• Whether their name will appear
• Where the map may be published
• Whether files will be downloadable
• How quotations, audio, images, and locations may be used
• Whether they can review material before release
• How to request a correction, restriction, or removal

For Indigenous cultural heritage and other community-held knowledge, an individual's willingness may not be sufficient authority to publish. Follow the relevant community's own governance and protocols. The guide to ethical cultural heritage mapping treats these decisions as the map's foundation, not its final disclaimer.

4. Design the information before choosing software

Create a simple record template. Each place might have:

• Unique record ID
• Public title
• Place type
• Approximate or precise location
• Time period
• Description
• Source or contributor
• Evidence type
• Confidence or uncertainty note
• Usage rights
• Access level
• Review status
• Date added and last checked

Separate a claim from its source. “This building hosted dances in 1974” belongs in one field; the interview, photograph, or newspaper citation supporting it belongs in another. If two sources disagree, keep both and explain the disagreement rather than voting history off the island.

Use controlled terms for repeated fields, such as confirmed, probable, approximate, and contested. Define them in a data dictionary so different volunteers apply them consistently.

5. Gather several kinds of evidence

No source type is complete. Combine:

• Historical and current maps
• Directories, registers, and public records
• Newspapers and community publications
• Photographs and captions
• Organizational records and ephemera
• Buildings and landscapes observed in the field
• Oral histories and personal collections

Check rights and access for every image, scan, recording, and text. Online availability is not automatic permission to republish. The Library of Congress, for example, advises users to inspect an item's specific Rights and Access or Rights Advisory statement; other repositories set their own terms.

Cite the exact item, collection, repository, creator if known, date, stable URL or identifier, and date accessed. “Found online” is not a citation so much as a cry for help.

When interviewing, follow a transparent process from consent through preservation and access. The oral-history mapping workflow explains how to connect a narrated memory to place without presenting memory as a cadastral survey.

6. Choose a mapping format that fits the project

Start with the lightest tool that meets the purpose.

Paper or wall map

Best for workshops, low-connectivity settings, tactile group discussion, and early discovery. Use removable notes or transparent overlays so corrections do not require heroic erasing.

Spreadsheet plus online map

Useful for a modest public point map. Keep a master spreadsheet with stable IDs and clean columns. Confirm the platform's privacy, ownership, export, and account-continuity terms before uploading sensitive information.

Desktop GIS

Useful for layered analysis, historical rasters, uncertain boundaries, custom symbols, and durable local data. It requires more training but provides control over files and geography. If an old scan needs alignment, follow the separate QGIS historical-map georeferencing guide.

Printed booklet or exhibition

Sometimes the best final map is not interactive. Print can preserve a curated sequence, work without internet, and stay accessible to people who do not use digital platforms. Plan how corrections will be recorded for a later edition.

7. Map uncertainty visibly

Historical geography is often approximate. A narrator may remember a shop on the correct block but not the exact storefront. An old map may distort distance. A place name may refer to a broad landscape rather than one point.

Match the geometry to the evidence:

• Use a point for a known building or marker
• Use a line for a route
• Use a polygon for an area with defensible boundaries
• Use a broad zone, blurred location, or no public geometry for sensitive or uncertain places

Add uncertainty to the pop-up or legend. Phrases such as “approximate location,” “boundary interpreted from a 1912 map,” or “one narrator's recollection” are informative, not embarrassing. False precision merely dresses uncertainty in very small coordinates.

8. Draft the story around relationships

A heritage map should do more than scatter pins. Group records into a narrative or question: how a street changed, where mutual aid operated, how waterways shaped work, or why several names exist for one place.

Write concise entries that distinguish evidence from interpretation. A useful entry often contains:

1. What the place is
2. Why it matters to the project question
3. When the described activity occurred
4. Who supplied or documented the account
5. What remains uncertain

Avoid claiming a site was “the first,” “the oldest,” or “the only” unless strong evidence supports the exact scope. Local-history superlatives are tiny magnets for larger corrections.

9. Review with contributors before release

Run at least two reviews.

Source review checks names, dates, citations, geography, quotations, media rights, and uncertainty labels.

Community review asks whether the map represents the agreed purpose, follows cultural protocols, exposes anything it should not, and gives people a practical way to respond.

Provide more than one review format: a meeting, printed draft, phone call, accessible digital version, or one-on-one conversation. Do not interpret silence as approval when contributors lacked time, access, language support, or a clear request.

Record decisions and version the files. Keep the unedited source material separate from the public derivative. A public map may use a generalized location while the restricted archive preserves more precise information under agreed access conditions.

10. Publish with a stewardship plan

Every public map needs:

• An about page naming the organizers and purpose
• Methods and source notes
• A legend, dates, and geographic scope
• Accessibility features, including readable contrast and text alternatives
• A correction and takedown route
• A privacy statement
• A named person or organization responsible for updates
• An export and backup plan

Choose a review date. Links break, platforms close, people revise consent, scholarship advances, and place names change. If no one can maintain an interactive map, preserve a static export, data documentation, and a clear final version rather than leaving a slowly malfunctioning artifact online.

A compact project checklist

Before collection: define purpose, authority, boundaries, consent, sensitive material, roles, and storage.
During collection: document sources, rights, uncertainty, contributor choices, and stable IDs.
Before publication: verify facts, review with contributors, generalize sensitive locations, test accessibility, and prepare corrections.
After publication: back up, monitor, revise, honor access changes, and record versions.

A community heritage map succeeds when people recognize both their places and their agency in it. The map is the visible artifact. The deeper work is building a trustworthy process for deciding what becomes visible at all.