> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/support-and-training/other-support/faqs/design-and-specification/climate/nz-climate-zones.md).
# NZ Climate Zones
New Zealand is divided into six main climate zones for building regulations, although it also has three broader climate zones. The six zones, used in the NZ Building Code, range from the warmest areas in the north (zones 1 and 2) to the coldest in the south (zones 5 and 6). The three broad zones are: subtropical (Northland, Auckland), oceanic/temperate (central and southern North Island, northern South Island), and continental/subantarctic (southern South Island, alpine regions).
### **Zone 1**
Warmest, including Northland and parts of the Auckland region.
### **Zone 2**
Warm, encompassing most of the rest of the North Island (excluding the Central Plateau).
### **Zone 3**
Moderate, including the Central Plateau, Wellington, Manawatū, and parts of the northern South Island (Nelson, Marlborough, West Coast).
### **Zone 4**
Moderate to cold, including the remaining northern South Island regions (Nelson, Marlborough, West Coast).
### **Zone 5**
Cold, including the eastern South Island (Canterbury, Otago).
### **Zone 6**
Coldest, including the far south of the South Island (Southland, Fiordland) and alpine regions.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.betterbuilding.io/support-and-training/other-support/faqs/design-and-specification/climate/nz-climate-zones.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
