Appendix 1.

Terrasoft procedure for following the interior watershed assessment procedure

The following paper consists of an in-depth description of the steps involved using the GIS software Terrasoft to complete the major portion of a level 1 watershed assessment as described in the interior watershed assessment procedure (IWAP).

Establishing watershed boundaries

1. Use the BC Environment digital file of the community watersheds and merge it in.
2. Create the boundaries on either 1:50 000 or 1:20 000 topographic maps and then digitize the linework onto a map which will cover the entire district and then merge in the linework required.

Obtaining contour data

1. get the appropriate TRIM maps and create the elevation layer (see Appendix 1)
2. digitize the contours.

(Digitizing paper contour maps is a long process but this information may prove useful to other projects as well.)

Map types

1. Blocks of FC1 (forest cover digital maps)
2. A single map of the entire district with no forest cover information on it.

Section 1

One map for the entire district

This map will include the following information:

• watershed linework and tags
• soil linework and tags and associated database
• riparian buffer linework and tags
• road linework and tags.

1. Digitize the watersheds and tags so that they can be exported to the block maps created in Section 2.
2. Leave this map until the block maps in Section 2 have been completed.
3. Import the digital soil map.
4. From the completed block maps, import the necessary feature classes for riparian buffers, roads, and blocks with tree height less than 10 m.
5. Create necessary themes.
6. Do required overlay extracts and report files.

Watershed linework and tags

If you fail to check your watershed boundaries you may be doing a lot of work for nothing.

Creating numeric identifiers for the watersheds

Give each watershed a unique, numeric identifier.

The numbering system is based on a two digit number for a main watershed, a three digit number for the main watershed’s sub-drainages, a four digit number for the sub-drainages of those, and so on.

For example, there are 10 watersheds:
Ottawa, Kingston, Peterborough, Havelock, Bobcaygeon, Guelph,
Heckston, Lanark, Mountain, and Kemptville.

The four main drainages are Ottawa (15), Kingston (16), Peterborough (17) and Guelph (18).
Kingston (16) and Guelph (18) are stand alone drainages.

Kemptville (151) and Lanark (152) are sub-drainages of Ottawa (15).
Havelock (171) and Bobcaygeon (172) are sub-drainages of Peterborough.
Mountain (1511) and Heckston (1512) are sub-drainages of Kemptville (151).

This is a very important step as it will allow the files generated in Terrasoft to be examined in an orderly and easily understandable fashion. Certain functions of Terrasoft will only recognize numeric descriptors, therefore they must be used. Make certain that the watershed linework was entered using TS10 feature class (FC) WATERSHD, and the numeric descriptors were entered using FC WATERSHD_T. You may also enter an alphabetic name for the watershed using FC WATERSHD_D.

Once you have digitized all of the watershed information, leave this map and begin Section 2.

Once the block maps have been completed, it is possible to complete the map of the entire district as described in Section 1.

Obtain the following linework:

Riparian zone linework and tags.

Road linework. (The riparian and road can be imported from the block maps which are created as described in Section 2.)

Create area theme (WATERSHD).
This will allow for the creation of the WATERSHD raster layer. Also this will be extracted into the ROADS.DBF.

Theme name: WATERSHD
Description: Individual watersheds
Default Data Table

Table Name: WATERSHD
Index: WATERSHD
Key field: WATERSHD
Key field width: 16

Source Feature Classes from Map

linear: WATERSHD
data key: WATERSHD_T

Go to dBASE. Fill field WTRSHD with the numeric value which identifies that watershed.

Create area theme (SOILS).
This will allow for the creation of the HIGHMASS raster layer. Also this will be extracted into the ROADS.DBF.

Theme name: SOILS
Description: Surficial Geology
Default Data Table

Table Name: SOILS
Index: SOILS
Key field: POLY_NUM
Key field width: 16

Source Feature Classes from Map

linear: SOILS,WATER_SOIL,NEATLINE
data key: SOIL_T

Note: Use the data base which comes with the soil data.

Create Area Theme (HT_LT_10M).
(The purpose of this is to create an area theme for those forest areas with tree cover less than 10 m.) This will allow for the creation of the TREED raster layer.

Theme name: HT_LT_10M
Description: Basicl =0,HtProj <=9
Default Data Table

Table Name: HT_LT_10
Index: HT_LT_10
Key field: HT_LT_10M
Key field width: 16

Source Feature Classes from Map

linear: HT_LT_10M
data key: HT_LT_10M

Create Identifiers

Sequentially
Update only unlinked YES

Create Centroids
Attribute Maintenance

Make data table from SAT
add field TREED, N,2,0

Go into dBASE

if area is denuded, TREED = 0
if area has trees >9 m, TREED =1

Create Area Theme (BUFFZONE).
This will be extracted into the RD_DIST.DBF

Theme name: BUFFZONE
Description: 100 m Riparian Buffer
Default Data Table

Table Name: BUFFZONE
Index: BUFFZONE
Key field: BUFFZONE
Key field width: 16

Source Feature Classes from Map

linear: RIP_BUFF
data key: RIP_BUFF

Create the FEATURE theme (RD_DIST).
This will be used to answer major watershed assessment questions.

Theme name: RD_DIST
Description: Roads within the watersheds
Default Data Table

Table Name: RD_DIST
Index: RD_DIST
Key field: RD_DIST
Key field width: 16

Source Feature Classes from Map

linear: ROAD_ALL
data key:

Go to theme processing

break spaghetti using FC’s ROAD_ALL, WATERSHD, RIP_BUFF, SOIL, and WATER_SOIL.

Go to theme processing

create identifiers
create centroids
create database using SAT
place additional fields

Create the RASTER theme (OPERABILITY).
This theme is to cover the entire mapsheet.

Now the map is clean and ready for processing.
Run the TPL file ENT_DIST.TPL.
Contents of file ENT_DIST.TPL.

CREATE RASTER OPERABILITY LAYER TREED FROM HARVESTED FIELD TREED

CREATE RASTER OPERABILITY LAYER WATERSHD FROM WATERSHD FIELD WTRSHD

CREATE RASTER OPERABILITY LAYER HIGHMASS FROM SOILS FIELD HIGHMASS

REPORT RASTER CROSSTAB OPERABILITY FILE SIWAP_16.RPT LAYERS "WATERSHD, HIGHMASS, TREED"

UPDATE TABLE RD_DIST FROM PARENT WATERSHD FIELD WATERSHD

UPDATE TABLE RD_DIST FROM PARENT BUFFZONE FIELD BUFFZONE

UPDATE TABLE RD_DIST FROM PARENT SOILS FIELD SOILS

UPDATE TABLE RD_DIST FROM PARENT SOILS KEYFIELD SOILS FIELDS "HIGHMASS:HIGHMASS"

Now go into a database manager and do the appropriate number crunching.

Section 2

Forest cover block maps

The information that must be found in these maps is listed below.

• forest cover linework and tags and the associated data base (SEG or FIP)
• operability linework and tags (this may not exist for all maps or districts)
• ownership linework and tags
• Digital Elevation Model (DEM) points or contour lines
• stream linework
• road linework.

Once the block files have been created, one can commence with the following process.

The basis of a GIS is its ability to relate spatial to nonspatial data. Terrasoft accomplishes this through the use of THEMES.

The following pages descibe those themes and types of themes which must be created.

Create area theme (WATERSHD).
This will allow for the creation of the WATERSHD raster layer. Also, this will be extracted into the ROADS.DBF and STREAMS.DBF.

Import the FC’s WATERSHD and WATERSHD_T from the entire district map. (See Section 1.)

Theme name: WATERSHD
Description: Individual Watersheds
Default data table

Table name: WATERSHD
Index: WATERSHD
Key field: WATERSHD
Key field width: 16

Source Feature Classes from Map

linear: WATERSHD
data key: WATERSHD

Go to dBASE. Fill field WTRSHD with the numeric value which identifies that watershed.

Determining the H60 elevation.
This process has been partially automated by TPL processing.

This assumes that the operator has already created a raster layer ELEV_100 which breaks the elevations into categories of 100 m intervals (i.e., 1250-1350, 1350-1450, etc.).

Exit Menu System
Run H60.tpl

Contents of H60.tpl which resides in the user account.

CREATE RASTER OPERABILITY LAYER WATERSHD FROM WATERSHD FIELD WTRSHD

REPORT RASTER CROSSTAB OPERABILITY FILE H60.RPT LAYERS "WATERSHD,ELEV_100"

This must be run for every block file and the resulting H60.rpt files are to be appended into one file. If all block files are not included, incorrect H60s will result for those watersheds which span more than one block.

Use H60.RPT to determine the H60 (elevation for which 60% of the watershed area is above and 40% is below).

Once the H60 has been determined continue in Terrasoft.

Create area theme (H60).
This will allow for the creation of the H60 raster layer. Also this will be extracted into the ROADS.DBF.

Enter graphics. Using Feature Class H60 enter the appropriate H60 in each watershed.

Note: You can use the raster layer ELEV_100 to show you where to enter the line.

Using Feature Class H60 enter the text OVER or UNDER in the appropriate spots (i.e., whether the polygon will be over or under the H60 line. The polygons will be created from H60 and WATERSHD linework).

Theme name: H60
Description: H60 elevation (over/under)
Default data table

Table name: H60
Index: H60
Key field: H60
Key field width: 16

Source Feature Classes from Map

linear: H60, WATERSHD
data key: H60

When making the database from the SAT file, add the field H60_N, N, 3, 0.

Next go into dBASE and fill the field H60_N with value 1 if UNDER or value 0 if OVER.

Create area theme (FOREST).
This will allow for the creation of the HT_LT_10M linework and area theme, as well as the HT_PROJ and BASICL raster layers.

Theme name: FOREST
Description: Basic Forest Theme

Default data table
Table name: FOREST
Index: FOREST
Key field: POLYGON
Key field width: 16

Source Feature Classes from Map

linear: FOREST, BLOCK_NEAT
data key: FOREST_T

Create area theme (OPERABLE).
This will allow for the creation of the INOPER raster layers.

Theme name: OPERABLE
Description: OPERABILITY LINES (FC1)
Default data table

Table name: OPERABLE
Index: OPERABLE
Key field: OPERABLE
Key field width: 16

Source Feature Classes from Map

linear: N_OPER
data key: N_OPER_T

Create area theme (OWNER).
This will allow for the creation of the OWNER raster layers. Also, this will be extracted into the
ROADS.DBF and STREAMS.DBF.

First change all FC OWNER_T to OWNER_D. Next change the 62-C, 70-N, etc. portion of OWNER_D to OWNER_T. This will allow the ownership polygons to be tagged with the land status rather than a number.

Theme name: OWNER
Description: Ownership (Numeric Identifiers)
Default data table

Table name: OWNER
Index: OWNER
Key field:.OWNER
Key field width: 16

Source Feature Classes from Map

linear: OWNER
data key:OWNER_D

Create area theme (HT_LT_10M).
The purpose of this is to create an area theme of logged or denuded areas.
This will be extracted into the ROADS.DBF and STREAMS.DBF.

Go into graphics.

Use theme

• FOREST

Query as follows

• BASICL = 0
• HT_PROJ _ =10

Sidebar menu:

• Merge Polygons
• Make new Boundaries
• use FC (HT_LT_10M)

Go into graphics.

(If there are non-harvested islands within harvested polygons, label them TREES using FC HT_LT_10M.)

Theme name: HT_LT_10M
Description: Basicl =0, HtProj < =9
Default data table

Table name: HT_LT_10
Index: HT_LT_10
Key field: HT_LT_10M
Key field width: 16

Source Feature Classes from Map

linear: HT_LT_10M
data key: HT_LT_10M

Link labels.
Create Identifiers:

Sequentially
Update only unlinked YES

Create centroids.
Attribute maintenance:

Make data table from SAT

Create feature theme (STREAMS).
Many of the IWAP calculations will be based on the resulting dbf file. This theme will be used in numerous theme overlays.

Theme name: STREAMS
Description: Streams within watersheds
Default data table

Table name: STREAMS
Index: STREAMS
Key field: STREAMS
Key field width: 16

Source Feature Classes from Map

linear: WATER_SNG
data key:

Go to theme processing

create identifiers, sequentially, update only unlinked NO
create centroids
create database using SAT
place additional fields

WATERSHD, C,16,0
HT_LT_10M, C,16,0
OWNER C,16,0
RIPARIAN, N,2,0

Go to THEME DEFINITION MANAGER.
Select OPERABILITY.

Go to THEME PROCESSING.

Create a raster layer RIPARIAN, FROM A VECTOR THEME.

Name of layer to create: RIPARIAN
Description: From Streams Theme
Source Vector Theme: STREAMS
Using field: RIPARIAN

Create a buffered layer.

Name of layer to create: RIPARIAN
Description: 100 M RIPARIAN ZONE
Buffer setup name: RIP_BUFFER
Modify existing layer: No

Create a raster layer through classification.

Name of layer to create: RIP_BUFF
Description: 100 M RIPARIAN ZONE (1 value only)
Buffer setup name: RIP_BUFF

(The reason for the classification is to simplify the linework which will be created in the next step.)

[V] Convert raster layer into vector linework

Place linework in FC RIP_BUFF
Use raster layer RIP_BUFF

Go to theme definition manager.
Create area theme (BUFFZONE).

Theme name: BUFFZONE
Description: 100 m Riparian Buffer
Default data table

Table name: BUFFZONE
Index: BUFFZONE
Key field: BUFFZONE
Key field width: 16

Source Feature Classes from Map

linear: RIP_BUFF
data key: RIP_BUFF

Go to THEME PROCESSING.
Process the polygons.

Go into graphics.
Label the polygons using FC RIP_BUFF.
Note: label the contributing polys IN and the noncontibutors, OUT.
Go to theme processing

link labels
create identifiers, sequentially, update only unlinked YES
create centroids
create database using SAT

Create area theme (SLOPE4CL). Four slope classes.
This will be extracted into the ROADS.DBF.

There are several methods with which one can derive the area theme SLOPE4CL, however, the important thing is that one ends up with a raster layer with the following pixel values:

and an area theme as described below.

Define the theme.
(This theme assumes that the linework is in FC SLOPE4CL and the tags in SLOPE4CL are in the 1-4 range with the tag being the slope class.)

Theme name: SLOPE4CL
Description: 4 slope classes
Default data table

Table name: SLOPE4CL
Index: SLOPE4CL
Key field: SLOPE4CL
Key field width: 16

Source Feature Classes from Map

linear: SLOPE4CL
data key: SLOPE4CL

Process polygons.

Create the FEATURE theme (ROADS).
Many of the IWAP calculations will be based on the resulting dbf file. This theme will be used in numerous theme overlays.

Go into graphics. Copy RD_LOGGING, RD_SECOND and RD_TRAIL to feature class ROAD_ALL.

Examine the linework in ROAD_ALL and check to see if some of the lines are duplicated. (This was the case on some of the road linework in the Vernon Forest District.)

Theme name: ROADS
Description: Roads within the watersheds
Default data table

Table name: ROADS
Index: ROADS
Key field: ROADS
Key field width: 16

Source Feature Classes from Map

linear: ROAD_ALL,
data key:

Go to theme processing.
Break spaghetti using FC’s ROAD_ALL, WATERSHD, H60, SLOPE4CL, RIP_BUFF, and OWNER.

(The purpose of this is to break up the roads into segments which will fall into the polygons created by these different area themes.)

Go to theme processing:

create identifiers
create centroids
create database using SAT
place additional fields

Now the map is clean and ready for processing. It is now possible to run another tpl file which will do the following:

• create numerous raster layers
• create raster crosstab files
• update databases through vector theme overlay processes.
• Exit menu system.
• Contents of ALL_IN_1.tpl which resides in the user account.

CREATE RASTER OPERABILITY LAYER HT_PROJ FROM FOREST FIELD HT_PROJ

CREATE RASTER OPERABILITY LAYER OWNER FROM OWNER FIELD OWNER_N

CREATE RASTER OPERABILITY LAYER INOPER FROM OPERABLE FIELD OPER_CODE

CREATE RASTER OPERABILITY LAYER H60 FROM H60 FIELD H60_N

REPORT RASTER CROSSTAB OPERABILITY FILE SIWAP_1.RPT LAYERS
"WATERSHD, OWNER, BASICL, INOPER"

REPORT RASTER CROSSTAB OPERABILITY FILE SIWAP_7.RPT LAYERS
"WATERSHD, OWNER, BASICL, H60, HT_PROJ"

REPORT RASTER CROSSTAB OPERABILITY FILE SIWAP_10.RPT LAYERS
"WATERSHD, OWNER, BASICL, SLOPE4CL, HT_PROJ"

REPORT RASTER CROSSTAB OPERABILITY FILE SIWAP_36.RPT LAYERS
"WATERSHD, OWNER, INOPER, SLOPE4CL"

UPDATE TABLE ROADS FROM PARENT WATERSHD FIELD WATERSHD

UPDATE TABLE ROADS FROM PARENT BUFFZONE FIELD BUFFZONE

UPDATE TABLE ROADS FROM PARENT H60 FIELD H60

UPDATE TABLE ROADS FROM PARENT SLOPE4CL FIELD SLOPE4CL

UPDATE TABLE ROADS FROM PARENT OWNER FIELD OWNER

UPDATE TABLE STREAMS FROM PARENT WATERSHD FIELD WATERSHD

UPDATE TABLE STREAMS FROM PARENT HT_LT_10M FIELD HT_LT_10M

UPDATE TABLE STREAMS FROM PARENT OWNER FIELD OWNER

Back to section 1 to complete the entire district map.