| File Identifier: | FE003082-52FC-47AC-8974-81575C4D9FF0 | Parent Identifier: | B75CFC59-92F9-458D-A879-3855CA90D436 |
|---|
| Hierarchy Level: | feature | Hierarchy Level Name: | feature of Water Allocation Calculator (WAC) Catchments and Aquifers - GIS Layer |
|---|
| Abstract: | Layer contains catchments defined for use with WRC Water Allocation Calculator (WAC). Attributes include monthly totals of allocated water aggregated to catchments from IRIS authorisations and applications and includes ecological limits and modelled water usage. |
|---|
| Statement: | These catchments were derived using the NIWA River Environment Classification (v1) watershed database as input. For cases where a catchment has been derived for static flow gauges, map references for each river flow gauge were collated from Environment Waikato’s Located application. The watershed that each gauge is located in was identified and recorded as the catchment start point. For other catchments (Regional Plan catchments and catchments of interest) start point reach ID’s were similarly recorded.
All upstream watersheds were then identified using the REC supplied TNODE/FNODE relationship and the REC Tracer application. All upstream watersheds were merged to produce the single upstream watershed feature.
The WAC script makes numerous calculations aggregating results to these catchments by using Oracle spatial queries with the Applications and Authorisations data from IRIS, GIS_ALL.ALLOC_IRIS_AUTH_TAKE_SEASONAL and GIS_ALL.ALLOC_IRIS_APPN_TAKE_SEASONAL (see Discover document# 1087095).
For detail about the automated processes see Discover document# 1089431 (and #1337989 for the permitted water model). The process runs every four hours recalculating data from Council's live database. See Bryan Clements or the Database Administrator if you have any queries. |
|---|
| Other Information: | Geographic Extent:
Waikato Region, plus any catchments that extend beyond the legal boundary of the Region.
Projection and Co-ordinates:
Data is stored in NZTM.
Positional Accuracy:
Catchments have been primarily derived using the River Environment Classification (REC) watersheds (see EWDOC# 935413 for further information about the REC). REC watersheds are based upon a 30m digital elevation model. See the REC metadata for positional accuracy of this source data.
Downstream ends of catchments are matched to the nearest REC reach. This may mean in some cases that the downstream extent of a catchment extends past the point of flow measurement. If this occurs the extension is generally less than 10 meters.
Aquifers are approximated from topographic maps and other source data. Spatial accuracy is unknown but aquifers are not intended for analysis at close-up scales.
Period and Frequency of Record:
The initial set of catchments for use with the Water Allocation Calculator was derived between July 2004 and July 2005. Catchments are added, deleted or modified as required over time.
August 2007: Present "Common Catchments" (sub-region and expiry dates) in their own GIS layer; as defined in Chapter 3 Table 3-3, Waikato Regional Plan Proposed Variation 6, p.15, EWDOCS-#1102641.
September, November 2007: Various catchments added by EdB and BryanC on behalf of Cameron King (RUG), including West Coast catchments required for proposed wind farm.
November 2007, February 2008: Significant Coromandel catchments added; includes upland/lowland differentiation as per Waikato Regional Plan Variation 6, EWDOCS-#1102641.
November 2009: Data and scripts built to support ground water and hydro power calculators. Additional attributes stored against catchments. For a complete up to date list of attributes refer to EWDOCS-#1401511-Water Allocation Calculator - Geomedia user guide.
February 2010: Groundwater and Hydro Power calculators and supporting layers were built; discrete version of allocation catchments was built.
2013-2014: Versions of most layers were created to reflect that data are derived from IRIS which has superseded RUAMS. Note that catchment and aquifer geometry or design has not changed but some attribute changes will have occurred reflecting the new IRIS data model.
Data Quality:
The spatial accuracy of the catchments is determined by the REC used to derive them. See EWDOC# 935143 for further information about the spatial accuracy of the catchments.
Attribute Accuracy:
All calculated values are dependent on accurate data being stored in the IRIS application for Surface water takes. Values used in the WAC scripts for these fields are read directly from IRIS. Other attributes are as supplied and quality assured by Waikato Regional Council staff (RIG).
Completeness:
This dataset is complete as at this date. New catchments may be added in the future, and amendments/deletions to current catchments may also occur.
Logical Consistency:
High
Data form and digital format as a layer in Waikato Regional Council’s GIS / Oracle database.
Applications:
These calculators are primarily designed as a means of assessing current and future water takes in conjunction with Q5 levels. They provide a current understanding of water availability within identified catchments and directly assist consents staff to assess whether a water take application is likely to be approved based on the calculated attributes. The consents data (applications and authorisations) and the catchment tallies are freely shared with other organisations. |
|---|
| Keywords: | Allocation,Catchment,Download,WAC,Waikato Data Portal,Water allocation |
|---|
| Topic Category: | environment:environmental resources, protection and conservation
inlandWaters:inland water features, drainage systems and their characteristics |
|---|
| Resource Reference Date: | 17-APR-2014 |
|---|
| Name | Description | Notes | Restricted | Primary Key |
|---|
| ID | Catchment ID | Famous catchments are sometimes casually referred to with IDs, for example, Waikato River at CMA is 397 and Waikato River at Karapiro Dam is 227. | N | N |
| CATCH_DESC | Catchment description, or full name | | N | N |
| CATCH_GROUP | The major river body group that the catchment is contributing to. | | N | N |
| CATCH_SUBREGION | Subregions that the catchment is in. Subregion is collection of catchment groups. | | N | N |
| RP_TABLE_3_5_DESC | Regional Plan Table 3-5 Description. | This signifies which Table 3-5 item this catchment is associated to. Table 3-5 gives primary and secondary allocable flow percentages. | N | N |
| AREA_KM2 | Catchment area in km2 | | N | N |
| SITE_STATION_KEY | The catchment outlet location ID | | N | N |
| Q5_M3S | Q5 estimate at the outlet of the catchment. | | N | N |
| QUALITY_DESCRIPTION | The derivation method for the Q5 and reliability of the Q5 estimate. | | N | N |
| DATE_OF_Q5 | The date that the Q5 was updated | If the Q5 date is greater than 5 years old, science team needs to update it. | N | N |
| PRI_ALLB_M3S | Primary allocable flow for the catchment m3/s | This is calculated from the percentage value from Table 3-5. | N | N |
| SEC_ALLB_M3S | Secondary allocable flow for the catchment m3/s | This is calculated from the percentage value from Table 3-5. | N | N |
| TOT_PER_M3S | Estimated Total Permitted Take | Permitted takes are animal, human drinking water and any domestic takes smaller than 15 m3/d. They are not registered in our database individually, so the total is estimated based on head counts within the catchment. We have used the property and the Agribase data to achieve this. | N | N |
| DATA_SOURCE | | | N | N |
| TAG_24HOUR | Some catchments has large enough river storage that attenuates the water take impacts in the river flow (typically catchments > 1000 km2) | These catchments are tagged "24-hour", and the water allocation calculator code would summarise maximum daily water take rate limit, instead of maximum instantaneous rate limits. All smaller catchments that do not have this tag will be summarised with maximum instantaneous rate limits, which is more conservative (or stringent) way of accounting water takes. | N | N |
| REC_DOWNSTREAM_REACH_ID | REC is a river network model and this is a technical field that associates the catchment to a REC reach | This number signifies the river reach that the catchment outflow is contributing to. | N | N |
| REC_DIST_TO_SEA_M | REC distance to sea in m | This shows the river length distance between the outlet of the catchment to the sea. If this is zero, this means the catchment outflow is directly going out to the sea. | N | N |
| GEOMETRY | | | N | N |
| TAKE_INFO_UPDATED | This field shows the time when the entry was updated | If the timestamp is older than one or two days, we should contact the IT. This means the WAC stopped running. The update frequency is 4-hourly during business hours. No update gets done during the night or in weekend. | N | N |
| JAN_SUM_AUTH_TOT_M3S | January: sum of all authorisations, replacement apps, and permitted activity takes | | N | N |
| JAN_SUM_TOT_M3S | January: sum of JAN_SUM_AUTH_TOT_M3S and all proposed application volumes. | This is what the allocation would become if WRC grant all applications in the catchment. | N | N |
| JAN_PRI_TOT_AUTH_AVL_M3S | January: available allocation headroom in primary allocable flow band, when you regard JAN_SUM_AUTH_TOT_M3S as allocated. i.e. = PRI_ALLB_M3S - JAN_SUM_AUTH_TOT_M3S. | This signifies the allocation pressure based on current authorised takes only. | N | N |
| JAN_SEC_TOT_AUTH_AVL_M3S | January: available allocation headroom in secondary allocable flow band, when you regard JAN_SUM_AUTH_TOT_M3S as allocated. i.e. = PRI_ALLB_M3S + SEC_ALLB_M3S - JAN_SUM_AUTH_TOT_M3S. | This forecasts the allocation pressure based on current authorised takes only. | N | N |
| JAN_PRI_TOT_AVL_M3S | January: available allocation headroom in primary allocable flow band, when you regard JAN_SUM_TOT_M3S as allocated. i.e. = PRI_ALLB_M3S - JAN_SUM_AUTH_TOT_M3S | This field forecasts what the allocation pressure will be if WRC grants all applications in the catchment. | N | N |
| JAN_SEC_TOT_AVL_M3S | January: available allocation headroom in secondary allocable flow band, when you regard JAN_SUM_TOT_M3S as allocated. i.e. = PRI_ALLB_M3S + SEC_ALLB_M3S - JAN_SUM_AUTH_TOT_M3S | This field forecasts what the allocation pressure will be if WRC grants all applications in the catchment. | N | N |
| FEB_SUM_AUTH_TOT_M3S | | | N | N |
| FEB_SUM_TOT_M3S | | | N | N |
| FEB_PRI_TOT_AUTH_AVL_M3S | | | N | N |
| FEB_SEC_TOT_AUTH_AVL_M3S | | | N | N |
| FEB_PRI_TOT_AVL_M3S | | | N | N |
| FEB_SEC_TOT_AVL_M3S | | | N | N |
| MAR_SUM_AUTH_TOT_M3S | | | N | N |
| MAR_SUM_TOT_M3S | | | N | N |
| MAR_PRI_TOT_AUTH_AVL_M3S | | | N | N |
| MAR_SEC_TOT_AUTH_AVL_M3S | | | N | N |
| MAR_PRI_TOT_AVL_M3S | | | N | N |
| MAR_SEC_TOT_AVL_M3S | | | N | N |
| APR_SUM_AUTH_TOT_M3S | | | N | N |
| APR_SUM_TOT_M3S | | | N | N |
| APR_PRI_TOT_AUTH_AVL_M3S | | | N | N |
| APR_SEC_TOT_AUTH_AVL_M3S | | | N | N |
| APR_PRI_TOT_AVL_M3S | | | N | N |
| APR_SEC_TOT_AVL_M3S | | | N | N |
| MAY_SUM_AUTH_TOT_M3S | | | N | N |
| MAY_SUM_TOT_M3S | | | N | N |
| MAY_PRI_TOT_AUTH_AVL_M3S | | | N | N |
| MAY_SEC_TOT_AUTH_AVL_M3S | | | N | N |
| MAY_PRI_TOT_AVL_M3S | | | N | N |
| MAY_SEC_TOT_AVL_M3S | | | N | N |
| JUN_SUM_AUTH_TOT_M3S | | | N | N |
| JUN_SUM_TOT_M3S | | | N | N |
| JUN_PRI_TOT_AUTH_AVL_M3S | | | N | N |
| JUN_SEC_TOT_AUTH_AVL_M3S | | | N | N |
| JUN_PRI_TOT_AVL_M3S | | | N | N |
| JUN_SEC_TOT_AVL_M3S | | | N | N |
| JUL_SUM_AUTH_TOT_M3S | | | N | N |
| JUL_SUM_TOT_M3S | | | N | N |
| JUL_PRI_TOT_AUTH_AVL_M3S | | | N | N |
| JUL_SEC_TOT_AUTH_AVL_M3S | | | N | N |
| JUL_PRI_TOT_AVL_M3S | | | N | N |
| JUL_SEC_TOT_AVL_M3S | | | N | N |
| AUG_SUM_AUTH_TOT_M3S | | | N | N |
| AUG_SUM_TOT_M3S | | | N | N |
| AUG_PRI_TOT_AUTH_AVL_M3S | | | N | N |
| AUG_SEC_TOT_AUTH_AVL_M3S | | | N | N |
| AUG_PRI_TOT_AVL_M3S | | | N | N |
| AUG_SEC_TOT_AVL_M3S | | | N | N |
| SEP_SUM_AUTH_TOT_M3S | | | N | N |
| SEP_SUM_TOT_M3S | | | N | N |
| SEP_PRI_TOT_AUTH_AVL_M3S | | | N | N |
| SEP_SEC_TOT_AUTH_AVL_M3S | | | N | N |
| SEP_PRI_TOT_AVL_M3S | | | N | N |
| SEP_SEC_TOT_AVL_M3S | | | N | N |
| OCT_SUM_AUTH_TOT_M3S | | | N | N |
| OCT_SUM_TOT_M3S | | | N | N |
| OCT_PRI_TOT_AUTH_AVL_M3S | | | N | N |
| OCT_SEC_TOT_AUTH_AVL_M3S | | | N | N |
| OCT_PRI_TOT_AVL_M3S | | | N | N |
| OCT_SEC_TOT_AVL_M3S | | | N | N |
| NOV_SUM_AUTH_TOT_M3S | | | N | N |
| NOV_SUM_TOT_M3S | | | N | N |
| NOV_PRI_TOT_AUTH_AVL_M3S | | | N | N |
| NOV_SEC_TOT_AUTH_AVL_M3S | | | N | N |
| NOV_PRI_TOT_AVL_M3S | | | N | N |
| NOV_SEC_TOT_AVL_M3S | | | N | N |
| DEC_SUM_AUTH_TOT_M3S | | | N | N |
| DEC_SUM_TOT_M3S | | | N | N |
| DEC_PRI_TOT_AUTH_AVL_M3S | | | N | N |
| DEC_SEC_TOT_AUTH_AVL_M3S | | | N | N |
| DEC_PRI_TOT_AVL_M3S | | | N | N |
| DEC_SEC_TOT_AVL_M3S | | | N | N |
| OBJECTID | | | N | N |