nz-open-data-connectors

Useful for

Use cases llm-inferred

Pull LAWA river quality monitoring sites near a project reach for a water-quality baseline · Screen LRIS land and soil layers for ground-condition context in a preliminary site assessment · Search MfE and LINZ layer catalogues to find environmental and boundary datasets for NZ-based reporting · Identify NZTA open data hub datasets for transport or civils inputs, checking each dataset's licence first

Audience llm-inferred

environmental consultants · hydrologists · GIS analysts · planners · data engineers building NZ data pipelines

Limitations

Constraints llm-inferred

New Zealand data only; no UK coverage, which limits use for UK-focused projects · Data licences vary by publisher; NZOR content is non-commercial (CC BY-NC-SA 3.0 NZ), so check before commercial reuse · Python and Ruby ports cover only 8 of 14 adapters; arcgis, lawa, mfe, lris, nzta and nzta-open-data are TypeScript-only · Python and Ruby ports are not on PyPI or RubyGems and must be installed from the repo · Live third-party endpoints with no uptime guarantee; per-source checks are dated (e.g. 2026-10-05) · Rate-limited responses (HTTP 429) are flagged retryable; the self-hosted API defaults to 60 requests per minute per IP · Some sources need an API key for full results, and the entry's auth field lists STATS_NZ_SUBSCRIPTION_KEY although the docs describe it as optional · Resolution, update frequency and MCP argument schemas are not documented

Example tool calls docs-verified

{
  "tool": "geonet",
  "arguments": {}
}

{
  "tool": "lawa",
  "arguments": {}
}