GIS can make community knowledge legible to decision-makers. It must not make that knowledge easier to extract.
Maps can help communities document water sources, track restoration, make land-use proposals and communicate with agencies on more equal terms. Satellite imagery and mobile data collection can add valuable evidence.
Yet every map also answers a difficult question: who gets to see, copy, interpret and act on the information?
For Indigenous territories and culturally sensitive places, “open” data can create risk. A public layer may expose sacred sites, medicinal plants, hunting grounds or routes to unwanted scrutiny and commercial use. A technically elegant map can still be unjust if it transfers control away from the people whose knowledge made it possible.
The CARE Principles for Indigenous Data Governance offer a practical starting point: collective benefit, authority to control, responsibility and ethics. In a community GIS project, that means agreeing data rules before collection; separating public, community-only and restricted layers; naming community decision-makers; documenting consent; and budgeting for local skills, hardware and long-term stewardship. It also means returning useful maps in forms the community chooses. The point is not simply to put more places on a platform. It is to strengthen the ability of communities to govern their territories on their own terms.
CARE and GIS also invite humility from researchers and NGOs. A point on a map is never the whole story of a place. It cannot contain every relationship, seasonal variation, spiritual meaning or disagreement. Maps should therefore travel with explanation: community narratives, agreed limits, attribution chosen by contributors and a route for correction or withdrawal. When used this way, mapping can strengthen a community’s voice in planning.
When used carelessly, it can convert living knowledge into a resource for others. The difference lies in who controls the process and who benefits from the result.
Technical choices follow from those decisions. Can the map be updated offline? Who has the passwords and copies of the files? Is the data stored on a service governed by terms the community understands? Can local trainees edit the layers without depending indefinitely on outside consultants?
We believe that a project with expensive equipment and no maintenance plan may be less useful than a simple system that local coordinators can sustain. The aim is not to create a perfect dataset. It is to create information that is accurate enough, safe enough and useful enough for the decisions that matter.
A useful community GIS process begins with a question, not a platform. A community may want to document flood paths before a road project, identify restoration priorities, show customary use of a landscape, or prepare for a dialogue with a public agency. Each purpose calls for different information and different safeguards. The group should decide early which layers can be public, which are for community use only, and which should not be digitized at all. It should be possible to say no to a data request without losing access to partnership or funding.