Skip to main content

How to use council GIS portals

A council viewer is often the quickest way to discover a useful layer. For repeatable GIS work, the next task is to identify what sits behind the viewer.

Discovery workflow​

Conceptual flow

1. Begin with the official maps page​

Use the council's official landing page rather than a search-engine result pointing directly to an old application. Councils replace platforms while old URLs can remain indexed.

Example: Environment Southland replaced Beacon with SouthMaps in 2025. The official council announcement provides the migration context.

2. Identify the exact layer name​

Turn the layer on in the viewer and record its title. If it is a hazard layer, record scenario/date. If it is a planning layer, check whether it belongs to the operative plan, proposed plan or another informational map.

Common platform patterns:

  • Open Data
  • GeoHUB
  • ArcGIS Hub
  • Data Portal
  • Download data
  • Extract

Auckland GeoMaps, for example, provides a Data Extract Tool that can download selected datasets for a defined area and lets the user choose a coordinate system such as NZTM.

4. If ArcGIS is underneath, find the service​

ArcGIS-based apps often consume a MapServer or FeatureServer. A FeatureServer is usually more useful for vector analysis because it exposes features/attributes and query operations. A MapServer can still be useful for display, identify/query and sometimes dynamic data access.

See ArcGIS REST and live services.

5. Read service metadata​

Check:

  • service description
  • layer name
  • publisher/copyright
  • spatial reference
  • update/review date where provided
  • fields
  • max record count
  • query formats/capabilities
  • licence or item terms

A service being technically queryable does not mean every field was designed for external reuse.

6. Add to QGIS​

For ArcGIS REST vector services, QGIS can connect through the ArcGIS Feature Server provider or through a service URL supported by the current interface. For WFS use Layer → Add Layer → Add WFS / OGC API - Features Layer….

Where a fixed source version matters, export a dated local copy after checking licence/terms.

7. Save the provenance​

Record:

layer title
council
official landing page
service/download URL
access date
source/update date
CRS
dataset purpose
licence/terms
known limitations

8. Recheck volatile sources​

Planning, hazards, consents and infrastructure layers can change. For formal work, re-open the official source and check whether a newer layer/scenario exists before reusing last year's download.

When a viewer is enough​

For quick orientation at a hui or early research stage, the viewer may be all you need. Do not build an API workflow merely because the endpoint exists.

For systematic research, repeated mapping or analysis, obtaining the underlying features generally gives better provenance and reproducibility.

Last reviewed: 26 August 2026

Last updated on