This dataset provides river name lines for mainland New Zealand. It is part of a pilot to understand the benefit of combining river names and location, and making these openly available through the LINZ Data Service.

Unnamed rivers are also included in this dataset.

How this data can be used

Together with the NZ River Name Polygons (Pilot) dataset, these are the first openly available datasets with NZ river names attributed to geometry features (lines and polygons). This data can be used for searching for a named river and zooming to its extents, extracting geometries of a named river, creating digital cartographic products displaying river names, and analysing other features against named rivers (e.g. identifying buildings or properties within a specified distance of a particular river).

Data vintage

The river names and extents in this dataset are based on the cartographic text shown on NZ Topo50 maps as of December 2018, and are an approximation and should not be taken as official. Further details are included in the 'Naming Extents Methodology' section in the 'Lineage' of this metadata. Please refer to the NZ River Name Lines and Polygons (Pilot) Data Dictionary for detailed metadata and information about this dataset.

Related data

NZ River Name Polygons (Pilot) - contains larger rivers captured as polygon features instead of lines.

We recommend using the two river name datasets with the following NZ Topo50 layers for connectivity and visualisation of inland hydrographic features.

• NZ Coastlines (Topo, 1:50k)

• NZ Island Polygons (Topo, 1:50k)

• NZ Lagoon Polygons (Topo, 1:50k)

• NZ Lake Polygons (Topo, 1:50k)

• NZ Pond Polygons (Topo, 1:50k)

• NZ Swamp Polygons (Topo, 1:50k)

The NZ River Name Lines and Polygons (Pilot) Data Dictionary provides details on how to download the matching time period snapshots of this data.

Please note

• Official geographic names as listed in the New Zealand Gazetteer of place names must be used in all official documents as per the New Zealand Geographic Board (Ngā Pou Taunaha o Aotearoa) Act 2008.

• This pilot dataset is unlikely to be updated, however feedback will be used for future enhancements to LINZ river datasets.

APIs and web services This dataset is available via ArcGIS Online and ArcGIS REST services, as well as our standard APIs. LDS APIs and OGC web services ArcGIS Online map services

This web map can also be accessed via the LINZ Storymap about NZ Key Datasets for Resilience and Climate Change https://storymaps.arcgis.com/stories/b4dd46f15cea4234a098b4c8caae5b3d The River Environment Classification (REC) is a database of catchment spatial attributes, summarised for every segment in New Zealand's network of rivers. The attributes were compiled for the purposes of river classification, while the river network description has been used to underpin models. Typically, models (e.g. CLUES and TopNet) would use the dendritic (branched) linkages of REC river segments to perform their calculations. Since its release and use over the last decade, some errors in the location and connectivity of these linkages have been identified. The current revision corrects those errors, and updates a number of spatial attributes with the latest data. REC2 provides a recut framework of rivers for modelling and classification. It is built on a newer version of the 30m digital elevation model, in which the original 20m contours were supplemented with, for example, more spot elevation data and a better coastline contour. Boundary errors were minimized by processing contiguous areas (such as the whole of the North Island) together, which wasn't possible when the REC was first created. Major updates include the revision of catchment land use information, by overlaying with land cover database (LCDB3, current as at 2008), and the update of river and rainfall statistics with data from 1960-2006. The river network and associated attributes have been assembled within an ArcGIS geodatabase. Topological connectivity has been established to allow upstream and downstream tracing within the network. REC2 can be downloaded as a zip file and used directly in ArcMap. Alternatively, the layers can be extracted as shape files. The three REC2 based layers contained within this web map consist of the following (metadata is contained in the Layers section below).NZ Large Catchments, are basically the local watersheds of the REC2V5 dissolved into large sea draining catchments.River Environment Classification REC2 V5 (as National and local rivers) NZ Rivers and Names is a cut down version of the REC2V5 with river and waterway names added where available.

Field Type Descriptions for all REC2 associated feature layers within this webmap.RivName The names for any waterway where available taken from original topo data ( only for the NZ Large Catchments and NZ River and Names layers)

Catarea Real Watershed area in m2 CUM_Area Real Area upstream of a reach (and including this reach area) in m2. Nzsegment Integer Reach identifier to be used with REC2 (supercedes nzreach in REC1).

Lengthdown Real The distance to coast from any reach to its outlet reach, where the river drains (m). Headwater Integer Number (0) denoting whether a stream is a “source” (headwater) stream. Non-zero for non-headwater streams.

Hydseq Integer A unique number denoting the hydrological processing order of a river segment relative to others in the network.

StreamOrder Integer A number describing the Strahler order a reach in a network of reaches.

euclid_dist Real The straight line distance of a reach from the reach “inlet” to its “outlet”. upElev Real Height (asl) of the upstream end of a reach section in a watershed (m). downElev Real Height (asl) of the downstream end of a reach section in a watershed (m).

upcoordX Real Easting of the upstream end of a river segment in m (NZTM2000). upcoordY Real Northing of the upstream end of a river segment in m (NZTM2000). downcoordX Real Easting of the downstream end of a river segment in m (NZTM2000).

downcoordY Real Northing of the downstream end of a river segment in m (NZTM2000). sinuosity Real Actual distance divided by the straight line distance giving the degree of curvature of the stream nzreach_re Integer The REC1 identifiying number for the corresponding\closest reach from REC1 (can be used to retrieve the REC management classes) headw_dist Integer Distance of the furthermost “source” or headwater reach from any reach (m). Shape_leng Real The length of the reach (vector) as calculated by ArcGIS. Segslpmean Real Mean segment slope along length of reach.

LID Integer Lake Identifier number(LID) of overlapping lake.

Reachtype

Integer A value of 2 is assigned if the segment is an outlet to the lake, otherwise 0 or null. nextdownid integer segment number of the most downstream reach

NIWA acknowledges funding from the MBIE SSIF towards the preparation of REC v2.5 River Environment Classification._Item Page Created: 2021-07-09 05:37 Item Page Last Modified: 2025-04-05 18:53Owner: steinmetzt_NIWANZ River Names (REC2)Item id: 502212e71bce4c029de8a82cd5bc6302NZ Regional Rivers (REC2)Item id: 502212e71bce4c029de8a82cd5bc6302NZ National Rivers (REC2)Item id: 3a4b6cc2c1c74fbb8ddbe25df28e410cNZ Large River CatchmentsItem id: 28d23ad94c2a4846b7634f4cdbba178f

This dataset provides river name polygons for mainland New Zealand. It is part of a pilot to understand the benefit of combining river names and location, and making these openly available through the LINZ Data Service.

Unnamed rivers are also included in this dataset.

How this data can be used

Together with the NZ River Name Lines (Pilot) dataset, these are the first openly available datasets with NZ river names attributed to geometry features (lines and polygons). This data can be used for searching for a named river and zooming to its extents, extracting geometries of a named river, creating digital cartographic products displaying river names, and analysing other features against named rivers (e.g. identifying buildings or properties within a specified distance of a particular river).

Data vintage

The river names and extents in this dataset are based on the cartographic text shown on NZ Topo50 maps as of December 2018, and are an approximation and should not be taken as official. Further details are included in the 'Naming Extents Methodology' section in the 'Lineage' of this metadata. Please refer to the NZ River Name Lines and Polygons (Pilot) Data Dictionary for detailed metadata and information about this dataset.

Related data

NZ River Name Lines (Pilot) - contains smaller rivers captured as line features instead of polygons.

We recommend using the two river name datasets with the following NZ Topo50 layers for connectivity and visualisation of inland hydrographic features.

• NZ Coastlines (Topo, 1:50k)

• NZ Island Polygons (Topo, 1:50k)

• NZ Lagoon Polygons (Topo, 1:50k)

• NZ Lake Polygons (Topo, 1:50k)

• NZ Pond Polygons (Topo, 1:50k)

• NZ Swamp Polygons (Topo, 1:50k)

The NZ River Name Lines and Polygons (Pilot) Data Dictionary provides details on how to download the matching time period snapshots of this data.

Please note

• Official geographic names as listed in the New Zealand Gazetteer of place names must be used in all official documents as per the New Zealand Geographic Board (Ngā Pou Taunaha o Aotearoa) Act 2008.

• This pilot dataset is unlikely to be updated, however feedback will be used for future enhancements to LINZ river datasets.

APIs and web services This dataset is available via ArcGIS Online and ArcGIS REST services, as well as our standard APIs. LDS APIs and OGC web services ArcGIS Online map services

This feature layer is designed for the purpose of assignment of waterway names (where named) to all segments within the River Environment Classification version two (REC2). This layer can also be joined to the main REC2 feature class layer via the unique joining variable called "nzsegment".The River Environment Classification (REC) is a database of catchment spatial attributes, summarised for every segment in New Zealand's network of rivers. The attributes were compiled for the purposes of river classification. Examples where the REC can be used include, catchment rainfall calculations, catchment river flows, flood forecasting, land use and catchment associations.Creationthe REC was originally created using a hydrological networking tools and a digital elevation model.In preparing The New Zealand Rivers and Names, all reasonable skill and care was exercised and the best available data and methods were used. Nevertheless, NIWA does not accept any liability, whether direct, indirect or consequential, arising out the use of this tool and its associated data and statistical information._Item Page Created: 2021-10-05 03:31 Item Page Last Modified: 2025-04-05 16:10Owner: NIWA_OpenData

estimated_dwThis file contains the estimated dry weight for all individual macroinvertebrates collected across 25 streams in New Zealand. Below are the column names and a brief description of them. site = Site name; character string. surber = Surber sample that individual was collected in (s1, s2, or s3). linear_meas = linear measurement of the individual in millimeters. dw = estimated dry weight of individual in units of grams. FFG = functional feeding group; CB = collector browser, G = grazer, P = predator, FF = filter feeder, S = shredder, O = omnivore, NA = unknown.gradient_chemistryThis file contains chemical data for 25 streams in New Zealand across an acid mine drainage gradient. pH and conductivity were recorded in the field using standard meters (YSI 550A & YSI 63). Element concentrations were estimated using ICPMS analysis of a filtered (pore size = 0.45 um) water sample collected in the field. site = site name. cond = specific conductivity (microsiemens per centimeter). E...

Layer used in public web app https://niwa.maps.arcgis.com/apps/webappviewer/index.html?id=933e8f24fe9140f99dfb57173087f27d to provide Flood Estimation for New Zealand 1. Modelled flood frequency estimates on river lines.NZREACH NZ digital network 1 ID no.River name where availableAreakm2 catchment area draining to the downstream end of this reach (square kilometres)q100_reach ratio of Q100 (1% aep flood) to mean annual floodH&C18_MAF mean annual flood (cumecs)H&C18_5-yr 5-yr (20% aep) flood (cumecs)H&C18_10y 10-yr (10% aep) flood (cumecs)H&C18_20y 20-yr (5% aep) flood (cumecs)H&C18_50y 50-yr (2% aep) flood (cumecs)H&C18_100y 100-yr (1% aep) flood (cumecs)H&C18_1000y 1000-yr (0.1% aep) flood (cumecs)HCse_MAF standard error of mean annual flood (cumecs)HCse_5y standard error of 5-yr (20% aep) flood (cumecs)HCse_10y standard error of 10-yr (10% aep) flood (cumecs) HCse_20y standard error of 20-yr (5% aep) flood (cumecs)HCse_50y standard error of 50-yr (2% aep) flood (cumecs)HCse_100y standard error of 100-yr (1% aep) flood (cumecs)HCse_1000y standard error of 1000-yr (0.1% aep) flood (cumecs)Strm_Order Strahler stream order (1=headwater, two ones join to make an order 2, etc.) 2. 2. At-site flood statistics at flow recorders used in the model development

Siteno NIWA reference number for flow recorder Name Flow recorder name generally 'river' at 'location' NZTM_E NZTM easting NZTM_N NZTM northingRegion Regional council or unitary authority territoryOperator Organisation that oprates the flow recorder Funder Organisation that funds the flow recorder (can be more than one)Area_km2 catchment area draining to the flow recorder (square kilometers)No_years Number of years in the annual flood series (allowing for years with missing data)L1_mean Mean of the annual flood series (linear moment 1)L2 Linear moment 2 of the annual flood series (analogous to standard deviation)Lcv Linear CV of the annual flood series (L2/L1) T3_Lskew Linear skew ratio of the annual flood series T4_Lkurt Linear kurtosis ratio of the annual flood series Gumb_u Gumbel distribution u of the annual flood series Gumb_alpha Gumbel distribution alpha of the annual flood series GEV_u Generalised Extreme Value u of the annual flood seriesGEV_alpha Generalised Extreme Value alpha of the annual flood series GEV_k Generalised Extreme Value k of the annual flood series GEV_z Hosking-Wallis normal standard variate to test significance of GEV-k (is the at-site distribution Gumbel or not?)Data 2.33y mean annual flood (2.33-yr assuming Gumbel, or 43% aep)Data 5y 5-yr (20% aep) flood (cumecs)Data 10y 10-yr (10% aep) flood (cumecs)Data 20y 20-yr (5% aep) flood (cumecs)Data 50y 50-yr (2% aep) flood (cumecs)Data 100y 100-yr (1% aep) flood (cumecs)Data 250y 250-yr (0.4% aep) flood (cumecs)Data 500y 500-yr (0.2% aep) flood (cumecs) Data 1000y 1000-yr (0.1% aep) flood (cumecs)se_2.33y standard error of mean annual flood (%) se_5y standard error of 5-yr (20% aep) flood (%)se_10y standard error of 10-yr (10% aep) flood (%)se_20y standard error of 20-yr (5% aep) flood (%)se_50y standard error of 50-yr (2% aep) flood (%)se_100y standard error of 100-yr (1% aep) flood (%)se_250y standard error of 250-yr (0.4% aep) flood (%)se_500y standard error of 500-yr (0.2% aep) flood (%) se_1000y standard error of 1000-yr (0.1% aep) flood (%)

1. Return period estimates of the area-rain intensity values for small catchments. Where results display '-1' the catchment is greater than 30 square kilometres and no answer is available. Numbers need to be multiplied by the Rational Method 'C' factor to give the required flood magnitude. NZREACH NZ digital network 1 ID no. AREA_km2 catchment area draining to the flow recorder (square kilometers)QIA_5y 5-yr (20% aep) IA estimateQIA_10y 10-yr (10% aep) IA estimate QIA_20y 20-yr (5% aep) IA estimateQIA_50y 50-yr (2% aep) IA estimateQIA_100y 100-yr (1% aep) IA estimate QIA_1000y 1000-yr (0.1% aep) IA estimate4. Annual data values at flow recorders used in the model development. Layer coming later.Spatial Reference: New Zealand Transverse Mercator (NZTM) EPSG:2193 (2193) XMin: 1090154.6277 YMin: 4748852.6367 XMax: 2089112.8753000004 YMax: 6193369.0554_Item Page Created: 2019-03-15 05:14 Item Page Last Modified: 2025-04-05 20:42Owner: NIWA_OpenData

This dataset is one of several segments of a regional high detailed stream flowpath dataset. The data was separated using the TOPO 50 map series extents.The stream network was originally created for the purpose of high detailed work along rivers and streams in the Wellington region. It was started as a pilot study for the Mangatarere subcatchment of the Waiohine River for the Environmental Sciences department who was attempting to measure riparian vegetation. The data was sourced from a modelled stream network created using the 2013 LiDAR digital elevation model. Once the Mangatarere was complete the process was expanded to cover the entire region on an as needed basis for each whaitua. This dataset is one of several that shows the finished stream datasets for the Wairarapa region.The base stream network was created using a mixture of tools found in ArcGIS Spatial Analyst under Hydrology along with processes located in the Arc Hydro downloadable add-on for ArcGIS. The initial workflow for the data was based on the information derived from the help files provided at the Esri ArcGIS 10.1 online help files. The updated process uses the core Spatial Analyst tools to generate the streamlines while digital dams are corrected using the DEM Reconditioning tool provided by the Arc Hydro toolset. The whaitua were too large for processing separated into smaller units according to the subcatchments within it. In select cases like the Taueru subcatchment of the Ruamahanga these subcatchments need to be further defined to allow processing. The catchment boundaries available are not as precise as the LiDAR information which causes overland flows that are on edges of the catchments to become disjointed from each other and required manual correction.Attributes were added to the stream network using the River Environment Classification (REC) stream network from NIWA. The Spatial Join tool in Arcmap was used to add the Reach ID to each segment of the generated flow path. This ID was used to join a table which had been created by intersecting stream names (generated from a point feature class available from LINZ) with the REC subcatchment dataset. Both of the REC datasets are available from NIWA's website.

Please read: This layer is part of the comprehensive Full Landonline Dataset and is designed for use only by data professionals who require the complex version of our property ownership and boundary data for advanced uses.

This entity stores names associated with features and includes Streams, Rivers, Mountains, etc. Its main function is the storage of hydrographic polygons. For full Feature Name data, see the Landonline: Feature Name Point layer.

Please refer to the LDS Full Landonline Data Dictionary and Models for detailed metadata about this layer.

Layer used in public web app https://niwa.maps.arcgis.com/apps/webappviewer/index.html?id=933e8f24fe9140f99dfb57173087f27d to provide Flood Estimation for New Zealand 1. Modelled flood frequency estimates on river lines.NZREACH NZ digital network 1 ID no.River name where availableAreakm2 catchment area draining to the downstream end of this reach (square kilometres)q100_reach ratio of Q100 (1% aep flood) to mean annual floodH&C18_MAF mean annual flood (cumecs)H&C18_5-yr 5-yr (20% aep) flood (cumecs)H&C18_10y 10-yr (10% aep) flood (cumecs)H&C18_20y 20-yr (5% aep) flood (cumecs)H&C18_50y 50-yr (2% aep) flood (cumecs)H&C18_100y 100-yr (1% aep) flood (cumecs)H&C18_1000y 1000-yr (0.1% aep) flood (cumecs)HCse_MAF standard error of mean annual flood (cumecs)HCse_5y standard error of 5-yr (20% aep) flood (cumecs)HCse_10y standard error of 10-yr (10% aep) flood (cumecs) HCse_20y standard error of 20-yr (5% aep) flood (cumecs)HCse_50y standard error of 50-yr (2% aep) flood (cumecs)HCse_100y standard error of 100-yr (1% aep) flood (cumecs)HCse_1000y standard error of 1000-yr (0.1% aep) flood (cumecs)Strm_Order Strahler stream order (1=headwater, two ones join to make an order 2, etc.) 2. 2. At-site flood statistics at flow recorders used in the model development

Siteno NIWA reference number for flow recorder Name Flow recorder name generally 'river' at 'location' NZTM_E NZTM easting NZTM_N NZTM northingRegion Regional council or unitary authority territoryOperator Organisation that oprates the flow recorder Funder Organisation that funds the flow recorder (can be more than one)Area_km2 catchment area draining to the flow recorder (square kilometers)No_years Number of years in the annual flood series (allowing for years with missing data)L1_mean Mean of the annual flood series (linear moment 1)L2 Linear moment 2 of the annual flood series (analogous to standard deviation)Lcv Linear CV of the annual flood series (L2/L1) T3_Lskew Linear skew ratio of the annual flood series T4_Lkurt Linear kurtosis ratio of the annual flood series Gumb_u Gumbel distribution u of the annual flood series Gumb_alpha Gumbel distribution alpha of the annual flood series GEV_u Generalised Extreme Value u of the annual flood seriesGEV_alpha Generalised Extreme Value alpha of the annual flood series GEV_k Generalised Extreme Value k of the annual flood series GEV_z Hosking-Wallis normal standard variate to test significance of GEV-k (is the at-site distribution Gumbel or not?)Data 2.33y mean annual flood (2.33-yr assuming Gumbel, or 43% aep)Data 5y 5-yr (20% aep) flood (cumecs)Data 10y 10-yr (10% aep) flood (cumecs)Data 20y 20-yr (5% aep) flood (cumecs)Data 50y 50-yr (2% aep) flood (cumecs)Data 100y 100-yr (1% aep) flood (cumecs)Data 250y 250-yr (0.4% aep) flood (cumecs)Data 500y 500-yr (0.2% aep) flood (cumecs) Data 1000y 1000-yr (0.1% aep) flood (cumecs)se_2.33y standard error of mean annual flood (%) se_5y standard error of 5-yr (20% aep) flood (%)se_10y standard error of 10-yr (10% aep) flood (%)se_20y standard error of 20-yr (5% aep) flood (%)se_50y standard error of 50-yr (2% aep) flood (%)se_100y standard error of 100-yr (1% aep) flood (%)se_250y standard error of 250-yr (0.4% aep) flood (%)se_500y standard error of 500-yr (0.2% aep) flood (%) se_1000y standard error of 1000-yr (0.1% aep) flood (%)

1. Return period estimates of the area-rain intensity values for small catchments. Where results display '-1' the catchment is greater than 30 square kilometres and no answer is available. Numbers need to be multiplied by the Rational Method 'C' factor to give the required flood magnitude. NZREACH NZ digital network 1 ID no. AREA_km2 catchment area draining to the flow recorder (square kilometers)QIA_5y 5-yr (20% aep) IA estimateQIA_10y 10-yr (10% aep) IA estimate QIA_20y 20-yr (5% aep) IA estimateQIA_50y 50-yr (2% aep) IA estimateQIA_100y 100-yr (1% aep) IA estimate QIA_1000y 1000-yr (0.1% aep) IA estimate4. Annual data values at flow recorders used in the model development. Layer coming later.Spatial Reference: New Zealand Transverse Mercator (NZTM) EPSG:2193 (2193) XMin: 1090154.6277 YMin: 4748852.6367 XMax: 2089112.8753000004 YMax: 6193369.0554_Item Page Created: 2019-03-15 05:14 Item Page Last Modified: 2025-04-05 20:42Owner: NIWA_OpenData

Covers the whole of the Bay of Plenty Region. Provides those boundaries that have been defined for all major river catchments, most stream catchments and many of their tributaries.Any changes that staff notice need to be made to this dataset must first go through John Douglas (Senior Land Management Officer)Each Polygon identified by hierarchy decending from primary catchment to subsequent tributaries/lakes. Catchments will be defined firstly by the named river or estuary that feeds to the coast. For instance the Motu and Whakatane rivers are obvious examples, but the Maraetotara Stream is also an example. For estuaries, Ohiwa estuary is an example where the Nukuhou River is part of the Ohiwa estuary catchment.In instances where the catchments of 'primary' rivers/streans have not been defined, the area that they occur within will be referred to as 'xxxxx coastal'. Examples on the current map are the Te Kaha and Waikawa Coastal catchments.Instances where some tributaries have been defined for a primary river, lake or estuary but others between these are still aggregated into one area, then this will be known as 'xxxxx area'. Examples of these are Rangitaiki/Kaingaroa area that lies between two defined tributaries, and the Kaituna/Lake Rotorua/Haumarana area.The catchments layer will exclude the lake polygons. The catchment for each lake will include the surface of the lake. If lake surface area is needed to be calculated then the lakes layer needs to be used in conjunction with this layer.Where a lake has no defined flowing surface-outlet that feeds to the coast, then that lake becomes the primary catchment. For example, Lakes Rotoma, Okaro and Rotoehu.As the catchments of tributaries to the 'primary' rivers/streams are defined they will named in a hierarchical fashion. For instance: if Brown River is a sub-catchment of Jones River, then that catchment will be labelled 'Jones/Brown'. Then if Bloggs River is a tributary of Brown River then it's catchment will be labelled 'Jones/Brown/Bloggs'. Where natural lakes occur as part of the catchment they will be considered in similar manner to a tributary (note that this means that individual lake catchments can be queried but that linkages between lakes are not shown as clearly. This mainly relates to the Lakes Rotorua - Rotoiti and Lakes Tarawera - Okareka linkages). For example, the Tarawera River starts at the outlet of Lake Tarawera and the Lake Okareka outlet feeds to Lake Tarawera. The Tarawera River below Lake Tarawera that is not defined into tributaries is called the Lower Tarawera. The Lake Tarawera catchment is called Lake Tarawera with the lake being included. The Lake Okareka catchment is called Lake Okareka.Where man-made lakes occur in rivers and the river continues above the lake, then that lake may become a catchment 'area' with its feeding tributaries to its shoreline, but any tributaries above the lake revert to the primary river. For instance, on the Rangitaiki River, Lake Aniwhenua could have its own tributaries if it is defined as an area, but the Horomanga and Whirinaki rivers remain secondary tributaries of the Rangitaiki, not Lake Aniwhenua. Naming conventions need to be firstly the official name as in 'Catchments of New Zealand, by Soil Conservation and Rivers Control Council, December 1956'. Otherwise an agreed 'local' name can be used. Where multiple local names are being used the alternatives should also be stored as part of the dataset for that catchment.Scale needs to be clearly defined for each catchment/sub-catchment. This will be based on the worst quality portion of the boundary capture. For example for a very large catchment there may be portions of the boundary captured at 1:10000, but if the majority has been captured at 1:50000, then 1:50000 is the appropriate scale to use the data for this catchment. Each database can choose the level/scale of sub-catchment 'definition' that is relevant to that database.User-defined catchments are useful in some catchments. However these will be identified on a separate layer and by a separate set of attributes to the sequential tributary attributes above. For instance, in the Rangitaiki the 'Kaingaroa area' has been split by some users into the 'Upper Rangitaiki' and 'Kaingaroa' catchments. (based on drainage to a certain point but excluding some major tributaries to the Rangitaiki River in these areas).Note that diversions such as for hydro-electric power stations have not been addressed in this layer. Subsequent refinement to the catchment boundaries is likely to continue to occur as the layer is used. Any suggested changes to the boundaries need to be QC'd by appropriately knowledgeable staff. John Douglas will be the first point of contact for Geospatial staff who have received such a request. He will then consult appropriate staff to gain a consensus on the relevance or otherwise of the requested boundary change.

Intended UseThe River Network is a geometric network and should be used for visualising the main rivers, streams and drains in Canterbury. It forms the basis for the Rivers for Allocation layer and Stream Depletion Calculations, which link to the Water Allocation Calculator— allocation summary reports to be used by the Customer Services, Planning, Consents, and Science teams.The River Network is based on LINZ river layer and aerial imagery. Attributes include Māori and English river names, river type, feature type, and source metadata. The River Network is hydrologically connected and traceable. Attributes still to be assigned to network include drain type, permanence, and bed extent. Attributes from NIWA’s River Environment Classification (REC) layer that make up the river type classification (network position, climate, source of flow, geology, landcover and valley landform) have been spatially associated but still need to be quality checked.Information users are urged to contact the Water Data Programme (WDP) directly if errors are identified.DisclaimerThis information is accurate to the best of Environment Canterbury’s knowledge and belief. While Environment Canterbury has exercised reasonable skill and care in the preparation, recording and management of this information, this information may be subject to changes as more information becomes available.Environment Canterbury accepts no liability in contract, tort or otherwise for any direct, indirect, consequential or incidental damage, loss, injury or expense that arises from any errors in the information, whether due to Environment Canterbury or a third party, or that arises from the provision, use, or misuse, of the information available from this site.Attribute InformationRiver Information:RiverName – name of river, catchment, or surface water body as defined by LINZMāoriName – Māori name of river, catchment, or surface water body as defined by LINZDrainType – type of drain, as described in Hinds drains layer (i.e. Main, Secondary)Permanence – permanence of river flow (i.e. Perennial (P), Ephemeral (E), Intermittent (I)); null values for now, as these category definitions still need to be agreed upon across teamsBedExtent – width of the riverbed; will accompany braided river polygon layerRiverType – river classification based on REC characteristics and water quality scientist review; values have been spatially derived, but need to be reconfirmedFeatureType – type of line feature (i.e. river, drain, braided river centreline)Environmental Characteristics: see REC attributes metadataClimate – affects patterns of water quality, flood frequency, low flow period, evapotranspiration; climate categories (i.e. warm-dry WD, cool-extremely-wet CX)SourceOfFlow – topography influences sediment patterns, erosion, precipitation storage, and river form; flow categories assigned using a mix of topographic data (i.e. glacial-mountain GM, mountain M, hill H, low-elevation L, lake Lk) and manual designation (i.e. spring Sp, wetland W, regulated R)Geology – catchment geology controls groundwater storage capacity and transmissivity; developed from the toprock category in the Land Resources Inventory (LRI) (i.e. alluvium Al, hard sedimentary rocks HS, soft sedimentary SS, volcanic basic VB, volcanic acidic VA, plutonics Pl, miscellaneous M)Landcover – control for rainfall capture or runoff and potential evapotranspiration; categories developed from New Zealand Land Cover Database (LCDB) (i.e. bare ground B, indigenous forest IF, scrub / tussock T, pastoral P, exotic forestry EF, urban U)NetworkPosition – stream order relates to river form (i.e. low-order LO for headwater streams, middle-order MO for tributaries, high-order HO for main stems)ValleyLandform – indicative of geology and geomorphology, including erosive / depositional setting; derived from slope (i.e. high-gradient HG, medium-gradient MG, low-gradient LG)GIS Attributes:Spatial IDs: ObjectID, GlobalIDSpatial Fields: Shape, Shape.STLength()Source – data source (LINZ river lines, aerial imagery, ECan)SourceNote – note about data source (i.e. specific source layer)History Fields: CreatedBy, CreatedDate, ModifiedBy, ModifiedDate

Covers the whole of the Bay of Plenty Region. Provides those boundaries that have been defined for all major river catchments, most stream catchments and many of their tributaries.Each Polygon identified by hierarchy decending from primary catchment to subsequent tributaries/lakes. Catchments will be defined firstly by the named river or estuary that feeds to the coast. For instance the Motu and Whakatane rivers are obvious examples, but the Maraetotara Stream is also an example. For estuaries, Ohiwa estuary is an example where the Nukuhou River is part of the Ohiwa estuary catchment.In instances where the catchments of 'primary' rivers/streans have not been defined, the area that they occur within will be referred to as 'xxxxx coastal'. Examples on the current map are the Te Kaha and Waikawa Coastal catchments.Instances where some tributaries have been defined for a primary river, lake or estuary but others between these are still aggregated into one area, then this will be known as 'xxxxx area'. Examples of these are Rangitaiki/Kaingaroa area that lies between two defined tributaries, and the Kaituna/Lake Rotorua/Haumarana area.The catchments layer will exclude the lake polygons. The catchment for each lake will include the surface of the lake. If lake surface area is needed to be calculated then the lakes layer needs to be used in conjunction with this layer.Where a lake has no defined flowing surface-outlet that feeds to the coast, then that lake becomes the primary catchment. For example, Lakes Rotoma, Okaro and Rotoehu.As the catchments of tributaries to the 'primary' rivers/streams are defined they will named in a hierarchical fashion. For instance: if Brown River is a sub-catchment of Jones River, then that catchment will be labelled 'Jones/Brown'. Then if Bloggs River is a tributary of Brown River then it's catchment will be labelled 'Jones/Brown/Bloggs'. Where natural lakes occur as part of the catchment they will be considered in similar manner to a tributary (note that this means that individual lake catchments can be queried but that linkages between lakes are not shown as clearly. This mainly relates to the Lakes Rotorua - Rotoiti and Lakes Tarawera - Okareka linkages). For example, the Tarawera River starts at the outlet of Lake Tarawera and the Lake Okareka outlet feeds to Lake Tarawera. The Tarawera River below Lake Tarawera that is not defined into tributaries is called the Lower Tarawera. The Lake Tarawera catchment is called Lake Tarawera with the lake being included. The Lake Okareka catchment is called Lake Okareka.Where man-made lakes occur in rivers and the river continues above the lake, then that lake may become a catchment 'area' with its feeding tributaries to its shoreline, but any tributaries above the lake revert to the primary river. For instance, on the Rangitaiki River, Lake Aniwhenua could have its own tributaries if it is defined as an area, but the Horomanga and Whirinaki rivers remain secondary tributaries of the Rangitaiki, not Lake Aniwhenua. Naming conventions need to be firstly the official name as in 'Catchments of New Zealand, by Soil Conservation and Rivers Control Council, December 1956'. Otherwise an agreed 'local' name can be used. Where multiple local names are being used the alternatives should also be stored as part of the dataset for that catchment.Scale needs to be clearly defined for each catchment/sub-catchment. This will be based on the worst quality portion of the boundary capture. For example for a very large catchment there may be portions of the boundary captured at 1:10000, but if the majority has been captured at 1:50000, then 1:50000 is the appropriate scale to use the data for this catchment. Each database can choose the level/scale of sub-catchment 'definition' that is relevant to that database.User-defined catchments are useful in some catchments. However these will be identified on a separate layer and by a separate set of attributes to the sequential tributary attributes above. For instance, in the Rangitaiki the 'Kaingaroa area' has been split by some users into the 'Upper Rangitaiki' and 'Kaingaroa' catchments. (based on drainage to a certain point but excluding some major tributaries to the Rangitaiki River in these areas).Note that diversions such as for hydro-electric power stations have not been addressed in this layer. Subsequent refinement to the catchment boundaries is likely to continue to occur as the layer is used.

The rivers of Australia and New Zealand dataset is derived from the World Wildlife Fund's (WWF) HydroSHEDS drainage direction layer and a stream network layer. The source of the drainage direction layer was the 15-second Digital Elevation Model (DEM) from NASA's Shuttle Radar Topographic Mission (SRTM). The raster stream network was determined by using the HydroSHEDS flow accumulation grid, with a threshold of about 1000 km² upstream area. The stream network dataset consists of the following information: the origin node of each arc in the network (FROM_NODE), the destination of each arc in the network (TO_NODE), the Strahler stream order of each arc in the network (STRAHLER), numerical code and name of the major basin that the arc falls within (MAJ_BAS and MAJ_NAME); - area of the major basin in square km that the arc falls within (MAJ_AREA); - numerical code and name of the sub-basin that the arc falls within (SUB_BAS and SUB_NAME); - area of the sub-basin in square km that the arc falls within (SUB_AREA); - numerical code of the sub-basin towards which the sub-basin flows that the arc falls within (TO_SUBBAS) (the codes -888 and -999 have been assigned respectively to internal sub-basins and to sub-basins draining into the sea). The attributes table now includes a field named "Regime" with tentative classification of perennial ("P") and intermittent ("I") streams.

This dataset contains adjacency matrices of food webs from New Zealand streams. These matrices were modified from the originals as described in the manuscript text. Briefly, they were subset to only include predator-prey interactions, and the taxa were aggregated to avoid naming discrepancies between food webs. The original food webs can be found at: https://www.nceas.ucsb.edu/interactionweb/resources.html

"Fine sediment is the collective term for inorganic particles deposited on the streambed less than 2mm in size. Urban development and agriculture and forestry around waterways can increase the amount of sediment entering river systems. Sedimentation can clog space between pebbles that are used by aquatic insects and fish, alter food sources, and remove sites used for egg laying. Excess sediment can affect the appeal of rivers and streams for recreation. This dataset relates to the ""Streambed sedimentation"" measure on the Environmental Indicators, Te taiao Aotearoa website.

Field names NZREACH Stream segment label SEDO Predicted observed percentage fine sediment cover, i.e. contemporary state SEDE Predicted expected percentage fine sediment cover, i.e. reference state. "