Skip to main content

Last reviewed: 16 August 2026

Awa as the organising geography

Many GIS projects begin with parcels because parcel data is clean, national and easy to join to other administrative information.

An awa does not behave like a parcel.

Water moves. Upstream activity affects downstream places. Tributaries, wetlands, springs, groundwater, estuaries and coastlines are connected. Marae, kāinga, mahinga kai and restoration projects can sit along that network rather than inside one neat ownership polygon.

For freshwater kaupapa, organising the GIS around the awa can produce a more useful picture.

Catchment is useful, but it is not a rohe​

A catchment is a physical drainage unit. It is valuable for understanding water movement and environmental pressures.

It should not be presented as though it automatically represents:

  • mana whenua
  • hapū boundaries
  • cultural authority
  • customary relationships

Several iwi or hapū may have relationships with the same catchment. A rohe may cross several catchments.

Use the catchment for the hydrological question and keep cultural and governance relationships represented on their own terms.

Build the map from the water outward​

A useful awa-focused project may start with:

  • main stem
  • tributaries
  • springs and puna
  • lakes and repo
  • catchment and subcatchments
  • estuary and coastal receiving environment

Then add the relationships and pressures relevant to the kaupapa.

Add people and place​

Depending on authority and sensitivity, useful context may include:

  • marae
  • kāinga or settlements
  • approved ingoa wāhi
  • mahinga kai
  • restoration sites
  • monitoring locations
  • access points
  • historical places

Do not turn every relationship into a public point layer. Use the minimum spatial detail needed for the work.

Add pressures by pathway​

Freshwater GIS becomes more useful when pressures are related to where water moves.

Possible layers include:

  • water takes
  • discharges
  • wastewater and stormwater systems
  • consents
  • land cover
  • erosion
  • plantation forestry
  • stock access
  • barriers to fish passage
  • roads and culverts
  • flood and sediment pathways

The purpose is not to create a visual pile of regulatory data. It is to ask how activities connect through the awa system.

Upstream and downstream are relationships​

A consent point can be analysed in relation to:

  • upstream catchment
  • downstream reaches
  • nearby tributaries
  • receiving estuary
  • downstream marae or mahinga kai
  • cumulative activities in the same network

QGIS and ArcGIS network or hydrology tools can help with some of this. Even without advanced network analysis, simple catchment and subcatchment overlays can make the relationship clearer than a parcel-only map.

Use subcatchments for action​

A whole catchment can be too large for practical planning.

Subcatchments can support:

  • restoration prioritisation
  • monitoring design
  • riparian planting
  • sediment-control planning
  • community work programmes
  • reporting on progress

Do not assume administrative reporting units are the best scale. Choose a scale that matches the mahi and can still be understood by people working on the whenua.

Put monitoring in context​

A water-quality monitoring point is one observation location, not the awa.

Keep:

  • parameter measured
  • date and time
  • sampling method
  • source organisation
  • quality notes
  • upstream and downstream context

Where local observations are included, retain their source and context rather than merging them into a single anonymous water quality field.

Combine environmental data with kōrero carefully​

A useful awa map might bring together:

  • LAWA or council monitoring
  • national river and catchment data
  • local monitoring
  • historical imagery
  • flood information
  • restoration records
  • approved local kōrero

Do not make public scientific data the base truth and then add Māori values as a point layer.

Start with the questions the people responsible for the awa are trying to answer, then bring in each source for what it can contribute.

Historic change​

Awa mapping can reveal change through:

  • channel straightening
  • stopbanks
  • drainage
  • wetland loss
  • culverts and barriers
  • gravel extraction
  • urban expansion
  • forestry
  • changing access

Historic aerial imagery and old maps can be particularly useful.

Record dates carefully. A river is dynamic, and comparing geometry from different sources without dates can produce misleading conclusions.

Flooding and resilience​

An awa-focused GIS can support marae and whānau resilience by showing:

  • flood extents
  • likely access problems
  • bridges and crossings
  • alternative routes
  • high ground
  • marae and community facilities
  • water infrastructure

Keep personal information about vulnerable households separate from general hazard maps.

See Disaster and hazard mapping for iwi.

A practical QGIS project structure​

A simple project might contain groups such as:

01_Awa_and_catchment
02_Ingoa_and_places
03_Monitoring
04_Pressures
05_Mahinga_kai_restricted
06_Restoration_mahi
07_Hazards
08_Historical_change
09_Publishing_views

The group names should make sense to the people using the project, not only to GIS specialists.

Useful outputs​

Rather than one giant catchment map, produce several purpose-led maps:

  • whakapapa and place context, where appropriate
  • current state and monitoring
  • pressures and consents
  • restoration programme
  • access and hazards
  • historical change
  • public summary with sensitive detail removed

Each map can use the same awa structure without exposing every layer.

A practical workflow​

  1. Define the awa or freshwater kaupapa.
  2. Build the hydrological network and catchment context.
  3. Add marae and local place context appropriate to the work.
  4. Add pressures based on pathways through water, not just proximity.
  5. Add monitoring with dates and provenance.
  6. Add restoration and desired future states.
  7. Compare historical change where useful.
  8. Review sensitive information and authority.
  9. Create separate outputs for internal, partner and public audiences.
  10. Revisit the map with people who work with the awa, not only people who manage the GIS.

Sources​

Last updated on