Skip to main content

A simple taxonomy for sites of significance in Māori GIS

Why taxonomy matters​

Many Māori GIS projects fail early because the data model becomes too complex too quickly. Long attribute tables, unclear categories, and mixed purposes make maps hard to maintain and risky to share. A simple taxonomy supports tikanga, reduces harm, and keeps projects usable by small teams working on their own. The goal is not to describe everything. The goal is to describe enough to be useful, safely.

Start with themes, not fine detail​

Begin with a small number of high level themes that reflect Māori ways of organising place, not Western asset registers. Common starting themes include:

  • Whenua
  • Wai
  • Moana
  • Marae
  • Mahinga kai
  • Ara and movement
  • Taonga and wāhi tapu These themes should stay stable over time. Avoid adding new themes lightly.

Use types within each theme​

Within each theme, define a short list of types. Keep the list tight. If a type only applies to one record, it probably does not need to exist yet. Examples: Whenua

  • pā site
  • kāinga
  • maunga
  • urupā Wai
  • awa
  • roto
  • puna
  • repo Moana
  • tauranga ika
  • takutai
  • toka
  • tauranga waka Mahinga kai
  • seasonal harvest area
  • permanent food source
  • historical use area Avoid mixing condition, status, or use into the type. Those belong in attributes.

Keep core attributes very small​

A safe and effective minimum schema for early stage work:

  • name
  • theme
  • type
  • description (plain language)
  • who provided the knowledge
  • when it was recorded
  • location accuracy
  • access level This keeps the dataset understandable and reviewable.

Location accuracy field​

Use words, not metres. This is easier for non technical users and safer for sensitive places. Suggested values:

  • exact
  • approximate
  • general area
  • intentionally generalised

Access level field​

This should be agreed early and enforced consistently. Suggested values:

  • private
  • restricted
  • internal
  • public summary only

Separate meaning from geometry​

Do not overload geometry with meaning.

  • geometry answers where, not what or why
  • meaning lives in attributes, metadata, and supporting kōrero
  • geometry can change without changing the identity of a place This separation makes obfuscation and future updates easier.

Avoid premature hierarchy​

Do not start with:

  • parent child trees
  • cultural significance scores
  • ranked importance fields These create conflict and are hard to maintain. Add structure later only if there is a clear use case.

Use notes before new fields​

If someone asks for a new attribute, test it by using a notes field for a while. If the same pattern repeats across many records, then promote it to a real field.

Metadata matters more than schema​

Every dataset should clearly state:

  • purpose of collection
  • limits of use
  • scale and accuracy limits
  • who to contact before reuse If this is missing, even a good schema will be misused.

A simple rule of thumb​

If a kaumātua, a planner, and a GIS beginner cannot all understand your schema after a short explanation, it is too complex for an early stage Māori GIS project. Start small. Record who, when, and how accurate. Add detail only when there is trust, time, and a real need.