Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>February 21, 2022</SPAN></P><P><SPAN>Open drains, sometimes called ditches, that are a part of the stormwater network.</SPAN></P></DIV></DIV></DIV>
FISH_PRES
(
type: esriFieldTypeString, alias: Fish Presence, length: 25
, Coded Values:
[Confirmed fish presence: If fish have been found to be present in the watercourse during any portion of their life cycle, then this watercourse is classified as “Fish presence” and is delineated by a red line in the Atlas. Fish presence does not necessarily mean fish are present at all times of the year.]
, [Unknown fish presence: In watercourses or portions of watercourses where fish have not been observed, a classification of “Unknown fish presence” applies. A yellow line in the Atlas delineates unknown fish presence. These watercourses require additional field investigations to determine if the habitat is used during any part of a fish life cycle. These watercourses should be treated as if fish are present when working in or near them.]
)
LOCALNAME
(
type: esriFieldTypeString, alias: Local Name, length: 50
)
SOURCETHM
(
type: esriFieldTypeString, alias: Source Filename, length: 50
, Coded Values:
[RAR Report: The information came from a RAR assessment report.]
, [RP Bio Report: The information came from an RP Bio Report that did not go through the RAR process.]
, [Registered Plan: The information came from a registered plan.]
, ...3 more...
)
LINE_TYPE
(
type: esriFieldTypeString, alias: Line Type, length: 50
, Coded Values:
[Chain and Compass: Compass survey chain or tape was used to collect data.]
, [GPS: Hand held device that uses satellites to determine positioning on the ground for data collection.]
, [Georeferenced: Image georeferenced and then digitized to interpret where features exist]
, ...4 more...
)
LINE_SRC
(
type: esriFieldTypeString, alias: Line Source, length: 20
, Coded Values:
[RAR: Ministry specifications in Riparian Regulations (usually SHIM standards).]
, [Refer to Report: Read the report linked to this feature to find out details on the methodology used.]
, [SHIM: Survey data was collected using SHIM standards.]
, ...2 more...
)
FISH_PRES
(
type: esriFieldTypeString, alias: Fish Presence, length: 25
, Coded Values:
[Confirmed fish presence: If fish have been found to be present in the watercourse during any portion of their life cycle, then this watercourse is classified as “Fish presence” and is delineated by a red line in the Atlas. Fish presence does not necessarily mean fish are present at all times of the year.]
, [Unknown fish presence: In watercourses or portions of watercourses where fish have not been observed, a classification of “Unknown fish presence” applies. A yellow line in the Atlas delineates unknown fish presence. These watercourses require additional field investigations to determine if the habitat is used during any part of a fish life cycle. These watercourses should be treated as if fish are present when working in or near them.]
)
SOURCETHM
(
type: esriFieldTypeString, alias: Source Filename, length: 50
, Coded Values:
[RAR Report: The information came from a RAR assessment report.]
, [RP Bio Report: The information came from an RP Bio Report that did not go through the RAR process.]
, [Registered Plan: The information came from a registered plan.]
, ...3 more...
)
LINE_TYPE
(
type: esriFieldTypeString, alias: Line Type, length: 50
, Coded Values:
[Chain and Compass: Compass survey chain or tape was used to collect data.]
, [GPS: Hand held device that uses satellites to determine positioning on the ground for data collection.]
, [Georeferenced: Image georeferenced and then digitized to interpret where features exist]
, ...4 more...
)
LINE_SRC
(
type: esriFieldTypeString, alias: Line Source, length: 20
, Coded Values:
[RAR: Ministry specifications in Riparian Regulations (usually SHIM standards).]
, [Refer to Report: Read the report linked to this feature to find out details on the methodology used.]
, [SHIM: Survey data was collected using SHIM standards.]
, ...2 more...
)
Description: iMap updated: February 8, 2021The CVRD has added a field called RD_Name and selected by location using Electoral Areas FC and calculated this field with "CVRD".See individual FC's for their respective metadata: FWA_GLACIERS_POLY, FWA_LAKES_POLY; FWA_MANMADE_WATERBODIES_POLY, FWA_RIVERS_POLY, FWA_WETLANDS_POLY.Link to Fresh Water Atlas technical reports:T:\Base\FreshWaterAtlas\Source\Documents
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: 10 Font Family: Times New Roman Font Style: italic Font Weight: bold Font Decoration: none
Min. Scale: 64000.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: [GNIS_NAME_1] Use Coded Values: true Symbol:
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: 10 Font Family: Times New Roman Font Style: italic Font Weight: bold Font Decoration: none
WATERBODY_TYPE
(
type: esriFieldTypeString, alias: Waterbody Type, length: 6
, Coded Values:
[G: Glacier: A mass of perminant snow and ice defined by literal limits which is typically
flowing in a particular direction.]
, [L: Lake - Definite: A body of fresh water that is completely surrounded by land.]
, [L_Ind: Lake - Indefinite: A body of fresh water that is completely surrounded by land.]
, ...6 more...
)
AREA_HA
(
type: esriFieldTypeDouble, alias: Area (hectares)
)
FISH_PRES
(
type: esriFieldTypeString, alias: Fish Presence, length: 25
, Coded Values:
[Confirmed fish presence: If fish have been found to be present in the watercourse during any portion of their life cycle, then this watercourse is classified as “Fish presence” and is delineated by a red line in the Atlas. Fish presence does not necessarily mean fish are present at all times of the year.]
, [Unknown fish presence: In watercourses or portions of watercourses where fish have not been observed, a classification of “Unknown fish presence” applies. A yellow line in the Atlas delineates unknown fish presence. These watercourses require additional field investigations to determine if the habitat is used during any part of a fish life cycle. These watercourses should be treated as if fish are present when working in or near them.]
)
SOURCETHM
(
type: esriFieldTypeString, alias: Soure Filename, length: 25
, Coded Values:
[RAR Report: The information came from a RAR assessment report.]
, [RP Bio Report: The information came from an RP Bio Report that did not go through the RAR process.]
, [Registered Plan: The information came from a registered plan.]
, ...3 more...
)
LOCALNAME
(
type: esriFieldTypeString, alias: Local Name, length: 50
)
LINE_TYPE
(
type: esriFieldTypeString, alias: Line Type, length: 20
, Coded Values:
[Chain and Compass: Compass survey chain or tape was used to collect data.]
, [GPS: Hand held device that uses satellites to determine positioning on the ground for data collection.]
, [Georeferenced: Image georeferenced and then digitized to interpret where features exist]
, ...4 more...
)
LINE_SRC
(
type: esriFieldTypeString, alias: Line Source, length: 20
, Coded Values:
[RAR: Ministry specifications in Riparian Regulations (usually SHIM standards).]
, [Refer to Report: Read the report linked to this feature to find out details on the methodology used.]
, [SHIM: Survey data was collected using SHIM standards.]
, ...2 more...
)
DATE_
(
type: esriFieldTypeDate, alias: Date Surveyed, length: 8
)
Description: This layer was created by intersecting the 2004 (Version 2) Eastern Vancouver Island and Gulf Island SEI layer 'sevi_2004.shp', with the Comox Valley Conservation Strategy (CVCS) project area boundary and then spatially joining with a 1:5K mapsheet grid layer. Then a permanent sort was done using ParentID and Mapsheet_5K. This layer was then re-digitized to show disturbance, using air photos from 2007-2012. Additional SEI polygons were identified and added to the database by the CVCS-CP SEI team. In addition to updating the spatial layer, the CVCS-CP SEI team recorded attributes including type of disturbance and primary and secondary ecosystem codes if these had changed since Version 2. The SEI database structure was updated with the addition of core Terrestrial Ecosystem Mapping (TEM) fields including ecosystem deciles, for viable ecosystems. This layer was modified again during QA to replace a few 2004 polygons that had been missed during analysis. Quality assurance was conducted on the output layer (SEI_2014_April8); with the exception of the TEM attributes; which still require quality assurance.The latest CVRD administrative boundary layer 'CVRD_AdminBndries.shp' was used to clip 'SEI_2014_April8' to create this layer.
Copyright Text: Comox Valley Conservation Strategy - Community Partnership;
Comox Valley Regional District;
VIU GIS student Amanda Hourigan