Māori GIS data sovereignty and governance
Last reviewed: 26 August 2026
Māori GIS governance begins with the relationships around the information: the kaupapa it serves, the whenua and people it connects, the whakapapa and kōrero that give it meaning, and the responsibilities that continue after it has been mapped.
Technical governance still matters. Accounts, access, backups, metadata and publishing all need to work. Those controls are tools for carrying decisions into a system. They are not the source of those decisions.
This page is the short operational introduction. For the deeper treatment of Māori Data Sovereignty, mapping history, sensitive locations, cloud versus local GIS, security, costs, consultants, AI, case studies and practical templates, use Māori Data Sovereignty for GIS.
Use this when
This section is useful for mahi involving:
- iwi, hapū or whānau information
- mātauranga or cultural information
- whenua, wai, taiao or places of significance
- locally supplied ingoa wāhi or narratives
- imagery, photographs or documents with a limited audience
- information moving between Māori organisations, councils, Crown agencies, consultants or researchers
- cloud platforms, web maps, AI tools or external service providers
Start with kaupapa and relationships
A few questions usually clarify the shape of the work:
- What is the kaupapa?
- What whenua, wai, whakapapa, people or relationships sit around the information?
- Who is involved in the decisions about how it is represented and used?
- Does the information need to become GIS data at all?
- Who is each version for?
- What responsibilities continue when the project, supplier or staff member changes?
A permissions table can implement some of those decisions, but it cannot make them.
See What belongs in GIS?, Who decides what? and Whakapapa of data.
Administration and decision making
It helps to keep technical roles and kaupapa decisions distinct.
| Role or relationship | Practical meaning |
|---|---|
| decision group or process | shapes the kaupapa, representation, audience and later use |
| knowledge holder or source relationship | connects the information to people, place and kōrero |
| kaitiaki or custodian | carries continuing responsibility for care and context |
| technical administrator | manages accounts, systems, backups and technical controls |
| publisher | prepares a particular representation for an audience |
| service provider | hosts or processes information as part of the technical arrangement |
One person may carry several of these roles in a small organisation. The distinction is still useful because a database administrator and a kaitiaki are not the same thing simply because both can edit a layer.
Māori data is more than personal data
Māori Data Sovereignty concerns Māori rights, interests and relationships in Māori data. In GIS this can include:
- coordinates and geometry
- attributes and metadata
- ingoa wāhi
- imagery and photographs
- survey or monitoring observations
- linked documents and kōrero
- analyses derived from source data
- maps, dashboards and models
Some of this may be personal information. Much of it can be collective, place-based or culturally significant without identifying an individual.
A public source can also take on a different meaning when combined with locally held information or presented in a new spatial context.
Consent and collective context
Individual consent matters where people, interviews, photographs or personal information are involved. Collective knowledge can involve wider whānau, hapū, iwi, marae or kaitiaki relationships as well.
A useful project record can note:
- where the knowledge came from
- what kaupapa the work supports
- who was involved in the relevant decisions
- the audience for different versions
- any agreed expectations around reuse, copying or derived analysis
- what kind of change would prompt another kōrero
See Ethics, tikanga and consent and Working with iwi, hapū and whānau.
Sensitivity is relational
A simple technical classification can help a platform behave consistently, but the label is not the reason for care.
Possible access patterns include:
- public
- public but generalised
- whānau or hapū
- internal organisational
- named project group
- temporary external access
- highly restricted
- not digital
The useful level can vary by kaupapa, audience and representation rather than applying permanently to an entire dataset.
See Sensitive places, Spatial masking and Publishing maps with sensitive locations.
Sharing changes the relationship
When information moves to a council, Crown agency, researcher, consultant or another organisation, it can gain new audiences, copies, joins and possible uses.
Useful questions include:
- why the other party needs the information
- what benefit the sharing is expected to create
- whether a smaller or more generalised extract would do the job
- what analyses are part of the work
- whether the information will be linked with other datasets
- whether AI is part of the workflow
- where copies and backups will exist
- what happens when the project ends
A copyable outline is available in Templates and registers. For public and research data, see Open data and research partnerships.
Cloud and external services
Cloud and local infrastructure are both tools. Neither is automatically more or less Māori.
Useful technical facts include:
- who owns and can recover the organisational accounts
- where data is stored and processed
- where backups and disaster-recovery copies are held
- what jurisdictions and subprocessors are involved
- whether submitted content can be reused by the provider
- whether a complete export is possible
- what happens on non-payment or termination
- whether more than one person can keep the service running
Those facts can then be considered alongside rangatiratanga, resilience, cost, capability and kaitiakitanga.
See Cloud is not one thing, Local and hybrid GIS and Cost of a Māori GIS.
Metadata carries whakapapa
Metadata is more than a technical catalogue. It can preserve some of the whakapapa of the work.
Depending on the kaupapa, useful metadata can include:
- source and provenance
- source relationship where useful
- kaupapa and intended use
- audience or sharing context
- whether geometry is exact, indicative, interpreted or generalised
- known uncertainty or different accounts
- review date or review trigger
- contact or kaitiaki role
Not every detail belongs in metadata. The useful question is what a future kaimahi needs in order to understand the record without stripping it from its context.
See Whakapapa of data, Metadata and documentation and Provenance and source checking.
Long-term care
Kaitiakitanga of a GIS includes what happens after the first map is finished.
That can include:
- versioning and change records
- periodic review of access and purpose
- staff and kaitiaki succession
- backups and restoration
- migration to new systems
- preservation of meaning and provenance
- removal or replacement of old public outputs
- archive, return or deletion where that is part of the kaupapa
A system nominally held by an iwi but dependent on one departed contractor is not practically resilient.
See GIS succession, The one-person GIS and Backups are data too.
Common traps
- letting the organisation holding the file become the default decision-maker
- treating individual consent as the whole answer for collective knowledge
- assuming public source data makes every combined dataset public
- treating a Crown or council layer as the cultural source of truth
- collecting detail before deciding what the GIS is for
- using one operational layer for every audience
- losing provenance and tikanga notes during export
- allowing supplier accounts or platform defaults to shape the kaupapa
- using
kaitiakias a decorative label for an ordinary technical administrator
A small-project record
For a modest project, one page may be enough. It can record:
- kaupapa
- relevant people, whenua or place relationships
- who was involved in key decisions
- custodian and technical administrator
- data categories and audiences
- external systems or suppliers
- what happens at project end
- what would trigger a future review
The point is not paperwork. It is to leave enough context for the next person to understand the mahi and continue it well.