This digital data specification applies to:

Fish Habitat Assessment Procedures: Overview Assessment

Fish Habitat Assessment Procedures: Level 1 Assessment

As described in:

B.C. Environment has defined spatial and attribute data standards. Spatial data is stored in Arc/Info Geographic Information System. Attribute data is captured using a data entry tool called WRPDES and is stored in Oracle Relational Database Management System. Further details on GIS standards are available at http://www.env.gov.bc.ca/gis. Further details on WRPDES and attribute standards are available at: http://www.env.gov.bc.ca/fsh/wrp/

Data accuracy requirements for the requested data is +/- 10 meters, using the North American Datum of 1983. For field collection of locational information, this requires the use of a GPS unit with a differential correction beacon or differential readiness. Alternatively, locations can be marked on 1:20,000 scale TRIM hardcopy maps.

Digitizing features accurately from TRIM will involve using a digital TRIM base map for water features. This can be supplied by the MELP contract monitor through a signed loan agreement. Data will be supplied in either the original MOEP binary format, or in B.C. Environment standard Arc/Info coverages. Data will be made available to the contractor through a password controlled File Transfer Protocol account only. Arrangements must be made between the contractor and the MELP contract monitor at the onset of the contract to set up accounts and data availability.

Data transfer and spatial data capture should be performed by a qualified GIS contractor, with full capabilities to supply in B.C. Environment standards. It will be the responsibility of the contractor to secure such services, including hardware, software, communications and technical expertise. For futher information, the MELP contract monitor will be the only contact. For further information, contact your MELP contract monitor.

• 1m coordinate precision must be maintained (7 significant digits).
• line work from digital TRIM maps should be digitally copied, not redigitized.
• Points must be snapped (with zero tolerance) to TRIM water features.
• Transfer of lines and points from photo must be +/- 10m of location of photograph (i.e.-use photographs of 1:20 000 scale or larger).
• Pseudo nodes should be removed unless crucial to data representation or are due to a system limitation.
• All digitized mapping will be carefully registered to within 0.004 relative mean square (RMS) of the corners of TRIM mapsheets. Data coordinates will adhere to the standards of storage, datum and projection specified above. Air photos to be digitized will be registered using 1:50 000 NTS maps showing flightlines and photo centres for tendered air photo contracts.
• All feature attribute tables (i.e. .pat and .aat) must be defined exactly as in the appropriate section of this document. ‘c’ refers to type character, and ‘I’ to type integer. The input and output width must be defined as indicated. All Arc/Info generated items (i.e. area, perimeter, cover-#) are to be left in original state. Additional items specified are to be added IN ORDER SPECIFIED after the last item.
• Linear features must be topologically "clean". All lines must be broken where they intersect and line endpoints must meet exactly (zero tolerance) at intersections. The arc/info BUILD ARC command must be used to build linear topology and must run without errors or warning.
• Polygons must have complete and clean topology. The Arc/Info BUILD POLY command must be used to build polygonal topology and must run without errors. NODEERRORS must report 0 dangling nodes. LABELERRORS must report no label errors, with the exception of polygon 1, which may be reported to have 0 label points. The coverage shall contain no arcs that have the same polygon on both sides (no unclosed polygons or dangles).
• Point features must have verified topology, and the BUILD POINT used to build point topology , without errors.

The spatial data coverages and related info files (where necessary to preserve a one to many relationship between point occurrences and observations) to be delivered for the Overview Assessment are:

1. TWSR{wsname} - Stream Reach Breaks
2. TFDZ{wsname} - Fish Distribution Zones
3. FDZI{wsname} - a related info file for fish distribution zones
4. TOBS{wsname} - Stream Obstructions
5. TSTB{wsname} - Boundary of the Study Area

Where {wsname} is a 4 character code abbreviation for the watershed (or project) name. i.e. White River = whtr. This code should be agreed upon in advance by the ministry contract monitor.

Meta data info files should be named as {covername}.meta i.e. TWSR{wsname}.meta. The covername must match exactly. When the ARC export command is used, this info file will be contained in the export file. Additionally, delivery as an ascii text file may be desirable to facilitate review by the contract monitor.

The spatial data are to be delivered in the following format:

• ARC/INFO export format with no compression and capable of being imported into ARC/INFO v7.04
• Exported coverage files must be named in the format "coveragename.e00"
• Related attributes files (i.e. FDZI) are to be exported as "infoname.e00"

The media for delivery is to be one of:

• network ftp
• High Density 3.5 inch Floppy disks?
• 4 mm dat tape or other format agreed to in advance by regional staff (* there may be different preferences with different regions - we do all have ftp, but not necessarily these other formats*)

Attribute Data is to be submitted using the WRP Data Entry System (WRPDES). WRPDES allows the recording of field notes via an electronic version of the forms provided in WRP Technical Circular #8 Appendix F. For the Overview Assessment the following forms must be completed:

1. Form 1 Overview Assessment - Fish Distribution Summary Form
2. Form 2 Overview Assessment - Habitat Conditions Form
3. Form 3 Overview Assessment Preliminary Habitat Assessment Form

WRP DES is available at http://www.env.gov.bc.ca/fsh/kootenay/is/fhap.htmlwrp/. Details for downloading, installing and using WRPDES are available on the web page.

Attribute data are to be delivered in the following format::

• the data file from WRPDES FHAPDATA.MDB, renamed to WRPD{wsname}.MDB where {wsname} is a 4 character code abbreviation for the watershed (or project) name. i.e. White River = whtr. This code should be agreed upon in advance by the ministry contract monitor.

The media for delivery is to be one of:

• network ftp
• High Density 3.5 inch Floppy disks?
• 4 mm dat tape or other format agreed to in advance by regional staff

A combination of watershed code and Reach Number will be used to link WRPDES data to the spatial data. Therefore, it is important to ensure that the watershed codes and reach numbers coincide with those used in the digital mapping.

2. Attribute Files for Fish Species Distribution and Obstructions
3. Why not just enforce deliverables from WRPDES?
4. Construct attribute tables as per Appendix A in MS Excel or in a spreadsheet or database program capable of exporting files in Excel (.xls) format.
5. Descriptions (Obstructions), species, life stage (Fish Distribution), coordinates and unique identifiers (both) will be transferred from the comments section of field cards to the attribute tables and FDZONES_TAG and OBSTRUCT_TAG codes will be built by combining the watershed code for the stream and the unique identifier (FDZ_ID or OBS_NUM). See section 3: "Fish Species Distribution" and "Obstructions", for further clarification on building these codes.
6. The attribute data deliverables are the two attribute files for Fish Distribution and Obstructions for the watershed delivered in an approved format on high density 3.5" floppy disks with no compression and no file splitting across disks.
7. The following attribute tables will be submitted:
8. FS+first five letters of watershed name+.xls
9. OB+first five letters of watershed name+.xls

This coverage must have polygonal topology verified.

Delineate the study area (i.e. watershed boundary or sub-basin) on TRIM hard copy maps, carefully matching across map sheet edges. Digitize the polygon within the above defined tolerances and specifications for polygonal topology. To the .pat add the following items:

TSTB_ID (mandatory c4) - {ws_name} code identifying the watershed

WS_CODE (mandatory c45) - watershed code

To the .aat add the following item:

FCODE (mandatory c10) - feature code

This coverage must have line topology.

1. Create a single coverage called TWSR{wsname} by amalgamating double and single line stream features from the TRIM B.C. Environment standard TWTR coverage(s). Include only those features that correspond to the geographic extent of the watershed.

• Arcs in the TWTR coverage must be found in the TWSR{wsname} coverage with exact coincidence and the same FCODE value (FCODE values available as outlined in section 1).
• For those arcs that pass across TRIM mapsheet boundaries, connectivity must be established and where possible, the pseudo node removed. If the establishment of connectivity changes the coincidence of an arc, the location of the node corresponding to the upstream arc may be moved.
• Ensure arc/line topology is present.
• Add the following items to TWSR{wsname}.aat
• WS_CODE (Mandatory, c 45). It will be the full watershed code identified in the attribute database. The watershed code can be found on the B.C. Environment GIS web site.
• TWSR_NUM (Mandatory, c 3).
• TWSR_TAG (Mandatory, c 48).

This combination of WS_CODE and TWSR_NUM items will be combined to produce the TWSR_TAG, which will provide the common link to attribute tables (WRPDES) once such information is downloaded to the B.C. Environment ORACLE database. The WS_CODE will be the first part of the TWSR_TAG (up to 45 characters), followed by the TWSR_NUM item (3 characters).

2. Break the watershed into reaches as described in the Channel Assessment Procedure (WRP Technical Circular #7), available from the Regional WRP Coordinator.
1. Segment the corresponding stream/river vector in the TWSR{wsname} coverage to produce a node. Specifically for the following feature categories:

• Single line stream/river - segment to produce a node
• Double line stream/river - segment both lines (banks) to produce 2 nodes which are perpendicular to the perceived centreline of the stream/river

• Braided stream/river - Segments that have identical data and are directly adjacent to each other are to be treated as a single reach i.e.- segment all vectors as for the double-line method above
• Stream/River with multiple mouths - Segments with identical data and are adjacent to each other are to be treated as a single reach i.e.- segment all vectors as for the double-line method above

For each reach segment, assign a unique identifier in the context of the stream. Begin numbering from the most downstream segment and number sequentially from there upstream. Store this number in the TWSR_NUM item found in the TWSR{wsname}.aat. Ensure that the same unique identifier is assigned to corresponding attribute data output from WRP DES. Begin numbering from 1.

In some cases, a single reach may span across two or more linear segments due to the presence of an unremoveable node or the nature of the feature as specified in the previous section. In this case, number all adjacent segments with the same unique identifier.

Multiple species and life stages may have the same upper limit of distribution. This creates a relationship of one spatial feature (a point) to one or many observations (attribute records). As the GIS cannot store this relationship within a single coverage, the observations are broken out from the points coverage in to a seperate info file. The spatial and attribute features are related through a common key, which is the unique identifier for the point.

1. Delineate points on the TRIM streams indicating locations of upper (and if applicable, lower) limits of distribution by species and life stage (adult or juvenile). Where more than one species or life stage have the same upper or lower limits, a single point is used. The multiple records are given the same FDZ_ID in the related attribute file (see below). Uniquely identify each point with a sequential code using the unique numeric identifier for the reach, and a letter in the alphabet, starting from A and lettering sequentially upstream. For example, the third upper limit for a fish species (ID=C) found in reach 2 (ID=002) of a given stream would be identified as"002C".
2. Digitally capture points from hard copy TRIM maps to a point coverage called TFDZ{wsname}. To TFDZ{wsname}.pat add the following items:

• FCODE (mandatory, c10) - feature code
• WS_CODE (mandatory, c45) - watershed code
• FDZ_ID (mandatory, c4) - unique identifier for the point
• TFDZ_TAG (mandatory, c49) - created by combining WS_CODE and FDZ_ID (WS_CODE first)

• WS_CODE - mandatory, as above
• FDZ_ID - mandatory, as above

• SOURCE (mandatory, c 4) - codes defined in Circular No. 8
• SURVEY_METHOD (optional, c 2) - codes defined in Circular No. 8. The survey method may be included at the sample point level, if more appropriate.
• SPECIES (mandatory, c 3) - codes defined in Circular No. 8, appendix D
• LIFE_STAGE (optional, c 1) - A for adult, J for juvenile

1. Delineate points on the TRIM streams indicating the location of permanent obstructions Uniquely identify each point with a sequential code using the unique numeric identifier for the reach, and a number, beginning with 1 and numbering sequentially upstream. For example, the first obstruction (ID=1) found in reach 3 (ID=003) of a given stream would be identified as "0031".
2. Digitally capture points from hard copy TRIM maps to a coverage called TOBS{wsname}. To the .pat add the items:

• OBS_NUM (mandatory, c4) - unique identifier for the point
• WS_CODE (mandatory, c45) - watershed code
• FCODE (mandatory, c10) - feature code
• TOBS_TAG (mandatory, c49) - created by combining WS_CODE with OBS_NUM (WS_CODE first)
• DESCRIPTION (optional, c30) - additional descriptive information
• HEIGHT (optional, I2) - height of obstruction in meters
• LENGTH (optional, I2) - length of obstruction in meters

• SPL_NUM (mandatory, c 3) - unique identifier for the point
• WS_CODE - (mandatory c45) watershed code as above
• FCODE (mandatory c10) - feature code from B.C. Environment standards
• SURVEY_METHOD (optional, c 2) - as defined in Circular No. 8
• COMMENTS (optional, c 30) - additional notes of importance
• TSPL_KEY - (mandatory, c48) created by concatenating WS_CODE with

The deliverables for the Level 1 Assessment are the same as for the Overview Assessment, with the following exceptions:

• For the WRPDES portion of the deliverables the following forms must be completed:
• Form 4 Level 1 Habitat Survey Data Form
• Form 5 Level 1 Fish Distribution Data Form
• Form 6 Level 1 Habitat Diagnosis Form

• For the Spatial portion of the deliverables an additional coverage is required:
• TSPL{wsname} - Sample Locations
• Only reaches where field surveys took place will be mapped for coverages TWSR, TFDZ, TSPL AND TOBS.

• SPL_NUM (mandatory, c 3) - unique identifier for the point
• WS_CODE - (mandatory c45) watershed code as above
• FCODE (mandatory c10) - feature code from B.C. Environment standards
• SURVEY_METHOD (optional, c 2) - as defined in Circular No. 8
• COMMENTS (optional, c 30) - additional notes of importance
• TSPL_KEY - (mandatory, c48) created by concatenating WS_CODE with