Color: [0, 38, 115, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Consent data that is linked to the Accela Management System. This is a copy of View_ConsentPointAccela which is updated nightly from the Accela database therefore any records added in Accela during the day will not show in this dataset until the following day. This feature class has been created for performance reasons.For the current view of the consents data see View_ConsentPointAccela.Note:The FullConsentNumber, X Coordinate and Y Coordinate fields are only filled in for those consents that were imported from the old consents database. All new consents created directly in Accela will only have a FeatureID associated with them. This is the link back into Accela.
Color: [255, 255, 255, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 11 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Shows the location and type of navigational aid. Data is created from a view of Accela tables and updated nightly. Any edits to this data should be made through Accela and NOT directly in GIS. Any edits made in GIS will be reversed when the update runs.
Description: Point showing location of the A Beacon at the entrance to Tauranga Harbour. Data used for mapping purposes.Coordinates obtained from LINZ Chart number 541.
Label Placement: esriServerPointLabelPlacementAboveRight Label Expression: "A Beacon" CONCAT NEWLINE CONCAT "Tauranga Harbour" Use Coded Values: true Symbol:
Color: [255, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Point features of reef locations in the Bay of Plenty. Data used for mapping purposes. Coordinates obtained from LINZ Chart number 541and 542as at December 2014
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Access lanes and reserved areas within the Bay of Plenty region. Council suspended two areas from the navigation and safety bylaw 2010 (Lakes affected: Lake Tikitapu & Lake Rotoma). The data displayed in the printed version of the 2010 bylaw is in the archive feature dataset.GPS coordinates were collected manually (using boats). Data was made into mapping polygons for publication
Color: [115, 223, 255, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [255, 255, 255, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: 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.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: The catchment boundaries were generated for the are of the 2006 Rotorua LiDAR where this was inside the Bay of Plenty regional boundary. However some catchments on the edges of the are covered by the LiDAR are not complete. They can be seen in the data as those with straight edges.The catchments were created from a 2m DEM.
Description: The Lake Rotorua catchment boundary is defined by the surface catchment, in part, and by the groundwater catchment outside the surface catchment.The surface catchment was defined at a 1:2000 scale using LIDAR digital terrain measurements.Then, the groundwater catchment wasdefined. This catchment generally coincides with the surface catchment. However, the catchment is outside the surface catchment over the Mamaku Plateau and the boundary is identified by data including: water budgets, digital terrain measurements, groundwater level measurements and estimates of specific discharge in streams.An assessment of the uncertainties in these data translate to estimates of uncertainty in the groundwater catchment. Boundaries of surface and groundwater catchments, and uncertainties in these boundaries, were developed as separate data sets(NutrientDischargeCatchmentGroundwaterRotoruaMinus_95percent, NutrientDischargeCatchmentGroundwaterRotoruaPlus_95percent).
Description: Rule 11 boundary. Follows catchment boundaries except where these catchments run outside the Bay of Plenty regionand includes all of Mamaku Township.
Description: Operational boundaries based on catchment boundaries with a few alterations as per jobs 499160 for TGA Harbour and 500531 for Eastern and Rotorua.
Description: DRAFT data only at this stage (18/08/2021)Created from vector.GIS.CatchmentSurfaceDrainage with the boundaries aligned to the REC 2.4 watersheds to ensure consistency with other work.For more information please documentation in Q:\GIS Projects\33_NPSFM_RNRP\4_Documentation\FreshwaterManagementUnitsFreshwater Management Units - 2021-01-26 - Mapping and Options Documentation - GSP-634855.docxAlign Freshwater Management Units to REC 2 - 2021-04-01.docx