Designing a Watershed Scale GIS Database for Riparian … · 2018-01-23 · Scientific_Name TEXT...

Designing a Watershed Scale GIS Database for Riparian Restoration: A

Case Study in the Colorado River Basin

Phoebe B. McNeally, Ph.D. Michael J. Campbell

Introduction

Photos: ERWP

Objective

• How to track and quantify riparian restoration work?

• Where are the partnerships in meeting treatment goals?

• Where are the partnerships in meeting restoration goals?

Metrics • Initial extent of invasives

o Acreage of riparian corridor, riparian cover, and invasives

• Extent of treatment o Acreage of primary treatment o Acreage of retreatment o Acreage of active revegetation

• Progress towards meeting treatment goals o Acres treated by species by year o Acres revegetated by species, type and year o Acres that meet restoration goals

• Progress towards meeting restoration goals o Relative and absolute cover of native and invasives in the corridor and treatment areas o Extent of natural recruitment in treatment areas

GIS Database Solution

• Standardizes data collection • Effective way to manage spatial and temporal

data and associated attributes • Provides an objective data collection approach • Supports automated report creation • Allows comparison between watersheds

Database Schema Challenges • 4 watersheds: Dolores, Escalante, Gila, Verde • Required data elements

oMinimum attribute information • Common terminology • Common data collection methods • Completeness of data

oCreating spatial data for previously nonspatial numbers o Populating full attribute data

Invasives_Treatment (polygon)Field Type Explanation Domain (if applicable)

Object_ID INTEGER

Auto-populated unique numerical identifier

Segment_ID TEXT Child attribute taken from parent feature Reporting_Segments

Riparian_Veg_ID(optional) TEXT Child attribute taken from parent feature

Riparian_Vegetation

Inventory_ID TEXT Child attribute taken from parent feature Invasive_Species_Inventory

Treatment_ID TEXT Unique identifier for each treatment

Treatment_Type TEXT Type of treatment [“PRIMARY”,”RETREATMENT”, “SECONDARY WEEDS”]

Method1 TEXT Method of treatment performed [“manual”, “mechanical”, etc.]


Species_Treated TEXT Species being treated [“Tamarisk”, “Russian Olive”, etc.]

Date DATE Treatment date

Year TEXT Year treatment conducted (April 1st – March 31st)

[Other OptionalFields] ---

The fields above are required for the proposed schema, however, if the watershed entity should choose to collect additional data beyond the requirement minimum fields, they can be included within the same dataset

Share TEXT Binary indicator of whether or not data can be shared publicly [“yes”, “no”]

Notes TEXT Free text field for note capture

Shape_Area DOUBLE Auto-populated area measurement (in m2)

Shape_Length DOUBLE Auto-populated perimeter length measurement (in m)

Invasive_Species_Inventory (polygon)Field Type Explanation Domain (if applicable)

Object_ID INTEGER




Riparian_Vegetation

Inventory_ID TEXT Unique identifier for the area found to contain invasive species

Inventory_Date DATE Date inventory was taken

Year Text Inventory year of the data (April 1st – March 31st)

Inventory_Person TEXT Name of person who inventories invasive species

Plant_Code TEXT Four-letter NRCS code for invasive species found [“AIAL”, “ARDO”, “TARA”, etc.]

Scientific_Name TEXT Full scientific name for invasive species found [“Ailanthus altissima”, “Arundodonax L.”, etc.]

Common_Name TEXT Common name for invasive species found [“Tree of Heaven”, “Giant Reed”, etc.]

Relative_Cover INTEGER

Percent of relative cover of the inventoried invasive species [1-10%, 11-20%, etc.]







Riparian_Corridor (polygon)Field Type Explanation Domain (if applicable)

Object_ID INTEGER


Riparian_Corridor_ID TEXT Unique identifier for each mapped riparian corridor






Invasive Species Database SchemaPrepared by DIGIT LabFebruary 6, 2017University of Utah

Planned_Treatments (polygon)Field Type Explanation Domain (if applicable)

Object_ID INTEGER




Riparian_Vegetation


Treatment_ID TEXT Unique identifier for each planned treatment

Treatment_Type TEXT Type of treatment planned[“PRIMARY TREATMENT”, “RETREATMENT”, “ACTIVE REVEGETATION”, etc.]

Method1 Text Type of treatment method planned to be used [“HAND”,MECHANICAL”, “CHEMICAL”, etc.]


Species_Treated TEXT Species planned to be treated [“Tamarisk”, “Russian Olive”, etc.]

Species_Planted TEXT Species planned to be planted [“Fremont Cottonwood”, “Boxelder”, etc.]

Year TEXT Year in which the treatment is planned to take place (April 1st – March 31st)

Percent_Complete INTEGER

Percent of the broader area completed in a given year







Riparian_Vegetation (polygon) – OptionalField Type Explanation Domain (if applicable)

Object_ID INTEGER



Riparian_Veg_ID TEXT Unique identifier for each mapped riparian area






Monitoring (point or polygon)Field Type Explanation Domain (if applicable)

Object_ID INTEGER



Monitoring_ID TEXT Unique identifier for each monitoring site

Monitoring_Date DATE Date when monitoring occurred

Absolute_Veg_Cover INTEGER

Percent of absolute cover of vegetation of any kind [1-10%, 11-20%, etc.]

Relative_Cover_Native INTEGER

Percent of relative cover of native vegetation [1-10%, 11-20%, etc.]

Native_Species_1 TEXT First, most abundant native species found [“Fremont Cottonwood”, “Boxelder”, etc.]

Native_Species_2 TEXT Second most abundant native species found [“Fremont Cottonwood”, “Boxelder”, etc.]

Invasive_Species_1 TEXT First, most abundant invasive species found [“Tamarisk”, “RussianOlive”, etc.]

Relative_Cover_Invasive1 INTEGER

Percent of relative cover of invasive vegetation by type [1-10%, 11-20%, etc.]

Invasive_Species_2 TEXT Second most abundant invasive species found [“Tamarisk”, “RussianOlive”, etc.]


Percent of relative cover of invasive vegetation by type, additional fields added to accommodate number of invasives

[1-10%, 11-20%, etc.]

Invasive_Species_3 TEXT Third most abundant invasive species found [“Tamarisk”, “RussianOlive”, etc.]



[1-10%, 11-20%, etc.]

Invasive_Species_4 TEXT Fourth most abundant invasive species found [“Tamarisk”, “RussianOlive”, etc.]



[1-10%, 11-20%, etc.]

Evidence_Natural_Recruitment

INTEGER

Indicates whether or not there is evidence of natural recruitment that meets defined threshold

[“YES”, “NO”]


[Other Optional Fields] ---


Reporting_Segments (polygon)Field Type Explanation Domain (if applicable)

Object_ID INTEGER


Segment_ID TEXT Unique identifier for each reporting segment

Meets_Restoration INTEGER

Field denotes whether or not that segment has met the restoration goal [“YES”, “NO”]






Active_Revegetation (polygon)Field Type Explanation Domain (if applicable)

Object_ID INTEGER




Riparian_Vegetation



Species_1 TEXT First species being revegetated [“Fremont Cottonwood”, “Boxelder”, etc.]

Species_2 TEXT Second species being revegetated [“Fremont Cottonwood”, “Boxelder”, etc.]

Species_3 TEXT Third species being revegetated [“Fremont Cottonwood”, “Boxelder”, etc.]

Species_4 TEXT Fourth species being revegetated [“Fremont Cottonwood”, “Boxelder”, etc.]

Type TEXT Maturity level of species being revegetated [“SEED”, “ROOTED”, “UNROOTED”]

Amount INTEGER

Amount of revegetation

Amount_Unit TEXT Unit for revegetation amount


Year TEXT Year active revegetation conducted (April 1st – March 31st)

[Other Optional Fields] ---The fields above are required for the proposed schema, however, if the watershed entity should choose to collect additional data beyond the requirement minimum fields, they can be included within the same dataset




This document provides an overview of the spatial database schema for inventorying, monitoring, and treatment of invasive species throughout the partner watersheds. The design is a nested hierarchy which allows for summarizing progress and results of monitoring, treatment, and restoration at a variety of levels. The arrows indicate the directionality of the parent-child database relationships. The tables shown each represent a unique feature class within the spatial database with associated required fields. Fields shown are geared specifically towards computing all of the desired metrics. Partner watersheds also have the option of including any additional fields that they would like to any of these feature classes.

Feature Class Descriptions:• Riparian_Corridor

• Area surrounding major river and streams that contains riparian vegetation. Feature is purely based upon topography.

• Reporting_Segments• Subdivision within riparian corridor that represents a

series of spatially distinct units linked to individual streams and/or stream segments delineated for reporting and management purposes.

• Riparian_Vegetation (optional)• Areas containing any riparian vegetation – invasive

and/or native – within the reporting segments. These areas can be mapped either using automated classification techniques or manually delineated.

• Monitoring• Point, line, or area locations where monitoring takes

place on a continued basis. These locations should be strategically placed throughout the reporting segments in order to be able to assess broad-scale progress in invasive species treatment and native species recruitment.

• Invasive_Species_Inventory• Areas known to contain invasive plant species within

the riparian corridor. Attributes contain information about which invasive species are present and the relative cover thereof.

• Planned_Treatments• Areas within the riparian corridor where primary

treatment, retreatment or active restoration are planned to take place.

• Invasives_Treatments• Areas within the riparian corridor where primary

treatment or retreatment are currently or have already taken place. Primary treatments are the initial hand, mechanical and/or chemical clearing of invasive species. Retreatment is areas where additional treatments are needed after the primary treatment.

• Active_Revegetation• Areas within invasive species treatment areas where

active restoration is currently or has already taken place. Active revegetation involves encouragement of native species recruitment through targeted planting.

Target Metrics and Associated Feature Classes (and Attributes):• Initial extent of invasives:

• Acreage of entire corridor• Riparian_Corridor [Shape_Area]

• Acreage of riparian cover within the corridor• Riparian_Vegetation [Shape_Area]

• Acreage of invasives within the riparian corridor• Invasive_Species_Inventory [Shape_Area]

• Relative cover of invasives• Invasive_Species_Inventory [Relative_Cover]

• Species of invasives• Invasive_Species_Inventory [Plant_Code, Scientific_Name,

Common_Name]• What is the planned extent of treatment:

• Clearing – by species and year• Planned_Treatments [Treatment_Type == “PRIMARY

TREATMENT”; Species_Treated; Year]• Planting – by plant type and species and year

• Planned_Treatments [Treatment_Type == “ACTIVE REVEGETATION”; Species_Planted; Year]

• Retreatment by year• Planned_Treatments [Treatment_Type == “RETREATMENT”;

Year]

• Where are the partnerships in meeting treatment goals• Acres cleared by species and year

• Invasives_Treatment [Shape_Area, Species_Treated, Date]• Acres planted by species, plant type (seed, shrubs, etc.) and year

• Active_Revegetation [Shape_Area, Species_Planted, Date]• Acres that meet restoration goals

• Reporting_Segments [Shape_Area, Meets_Restoration]

• Where are the partnerships in meeting restoration goals• Relative and absolute cover of natives and invasives in the corridor

• Monitoring [Absolute_Veg_Cover, Relative_Invasive_Cove (1-x)r, Relative_Native_Cover]

• Relative and absolute cover of natives and invasives in the treatment areas

• Monitoring [Absolute_Veg_Cover, Relative_Invasive_Cover(1-x), Relative_Native_Cover]

• What is the extent of natural recruitment in treatment areas• Monitoring [Shape_Area, Evidence_Natural_Recruitment]

Riparian_Corridor (polygon) Field Type Explanation Domain (if applicable)

Object_ID INTEGER Auto-populated unique numerical identifier

Riparian_Corridor_ID TEXT Unique identifier for each mapped riparian corridor

Stream_Name TEXT Name of the stream or river to which the corridor belongs

[Other Optional Fields] ---





Reporting_Segments (polygon) Field Type Explanation Domain (if applicable)


Segment_ID TEXT Unique identifier for each reporting segment

Meets_Restoration INTEGER Field denotes whether or not that segment has met the restoration goal [“YES”, “NO”]

[Other Optional Fields] --- Additional fields of interest to the watershed




Riparian_Vegetation (polygon) – Optional Field Type Explanation Domain (if applicable) Object_ID INTEGER Auto-populated unique numerical identifier


Riparian_Veg_ID TEXT Unique identifier for each mapped riparian area





Monitoring (point or polygon) Field Type Explanation Domain (if applicable) Object_ID INTEGER Auto-populated unique numerical identifier


Monitoring_ID TEXT Unique identifier for each monitoring site

Monitoring_Date DATE Date when monitoring occurred

Absolute_Veg_Cover INTEGER Percent of absolute cover of vegetation of any kind [1-10%, 11-20%, etc.]

Relative_Cover_Native INTEGER Percent of relative cover of native vegetation [1-10%, 11-20%, etc.]

Native_Species_1 TEXT First, most abundant native species found [“Fremont Cottonwood”, “Boxelder”, etc.]

Native_Species_2 TEXT Second most abundant native species found [“Fremont Cottonwood”, “Boxelder”, etc.]

Invasive_Species_1 TEXT First, most abundant invasive species found [“Tamarisk”, “Russian Olive”, etc.]

Relative_Cover_Invasive1 INTEGER Percent of relative cover of invasive vegetation by type [1-10%, 11-20%, etc.]

Invasive_Species_2 TEXT Second most abundant invasive species found [“Tamarisk”, “Russian Olive”, etc.]

Relative_Cover_Invasive2 INTEGER Percent of relative cover of invasive vegetation by type, additional fields added to accommodate number of invasives [1-10%, 11-20%, etc.]

Invasive_Species_3 TEXT Third most abundant invasive species found [“Tamarisk”, “Russian Olive”, etc.]


Invasive_Species_4 TEXT Fourth most abundant invasive species found [“Tamarisk”, “Russian Olive”, etc.]


Evidence_Natural_Recruitment INTEGER Indicates whether or not there is evidence of natural recruitment that meets defined threshold [“YES”, “NO”]



Invasive_Species_Inventory (polygon) Field Type Explanation Domain (if applicable) Object_ID INTEGER Auto-populated unique numerical identifier


Riparian_Veg_ID (optional) TEXT Child attribute taken from parent feature Riparian_Vegetation

Inventory_ID TEXT Unique identifier for the area found to contain invasive species

Inventory_Date DATE Date inventory was taken

Year Text Inventory year of the data (April 1st – March 31st)

Inventory_Person TEXT Name of person who inventories invasive species

Plant_Code TEXT Four-letter NRCS code for invasive species found [“AIAL”, “ARDO”, “TARA”, etc.]

Scientific_Name TEXT Full scientific name for invasive species found [“Ailanthus altissima”, “Arundo donax L.”, etc.]

Common_Name TEXT Common name for invasive species found [“Tree of Heaven”, “Giant Reed”, etc.]

Relative_Cover INTEGER Percent of relative cover of the inventoried invasive species [1-10%, 11-20%, etc.]






Planned_Treatments (polygon) Field Type Explanation Domain (if applicable) Object_ID INTEGER Auto-populated unique numerical identifier




Treatment_ID TEXT Unique identifier for each planned treatment

Treatment_Type TEXT Type of treatment planned [“PRIMARY TREATMENT”, “RETREATMENT”, “ACTIVE REVEGETATION”, etc.]



Species_Treated TEXT Species planned to be treated [“Tamarisk”, “Russian Olive”, etc.]

Species_Planted TEXT Species planned to be planted [“Fremont Cottonwood”, “Boxelder”, etc.]

Year TEXT Year in which the treatment is planned to take place (April 1st – March 31st)

Percent_Complete INTEGER Percent of the broader area completed in a given year



Notes TEXT Free text field for note capture Shape_Area DOUBLE Auto-populated area measurement (in m2)


Invasives_Treatment (polygon) Field Type Explanation Domain (if applicable)






Treatment_Type TEXT Type of treatment [“PRIMARY”,”RETREATMENT”, “SECONDARY WEEDS”]



Species_Treated TEXT Species being treated [“Tamarisk”, “Russian Olive”, etc.]


Year TEXT Year treatment conducted (April 1st – March 31st)






Active_Revegetation (polygon) Field Type Explanation Domain (if applicable) Object_ID INTEGER Auto-populated unique numerical identifier





Species_1 TEXT First species being revegetated [“Fremont Cottonwood”, “Boxelder”, etc.]

Species_2 TEXT Second species being revegetated [“Fremont Cottonwood”, “Boxelder”, etc.]

Species_3 TEXT Third species being revegetated [“Fremont Cottonwood”, “Boxelder”, etc.]

Species_4 TEXT Fourth species being revegetated [“Fremont Cottonwood”, “Boxelder”, etc.]

Type TEXT Maturity level of species being revegetated [“SEED”, “ROOTED”, “UNROOTED”]

Amount INTEGER Amount of revegetation

Amount_Unit TEXT Unit for revegetation amount


Year TEXT Year active revegetation conducted (April 1st – March 31st)






Outcomes • Standardized database template

o Independent of watershed o Reusable (available for others to use)

• Improves spatial and attribute data consistency and accuracy

• Supports data aggregation at multiple spatial levels • Standardizes reporting • Improves reporting efficiency

o Python scripts auto generate PDF and MS Excel reports

Thank you & Questions

[email protected]

Designing a Watershed Scale GIS Database for Riparian … · 2018-01-23 · Scientific_Name TEXT...

Documents

Transcript of Designing a Watershed Scale GIS Database for Riparian … · 2018-01-23 · Scientific_Name TEXT...