Attachment F-1 R6 TES Plant Element Occurrence Protocol and Field Guide.pdf

Threatened, Endangered And Sensitive Plants Element Occurrence

Protocol and Field Guide

United States Department of Agriculture

Forest Service

Rangeland Management Staff

Washington, DC

February, 2015

USDA Forest Service

Threatened, Endangered and Sensitive Plants

Element Occurrence Protocol and Field Guide

Table of Contents

OVERVIEW

GENERAL DESCRIPTION

NATIONAL STANDARDS

MAPPING

MONITORING TES PLANT OCCURRENCES (REVISITS)

EXTIRPATED OCCURRENCES

QUALITY CONTROL

PLANT OCCURRENCE FIELD FORM INSTRUCTIONS

GENERAL INFORMATION

ELEMENT OCCURRENCE DATA

SITE MORPHOMETRY

SOIL CHARACTERISTICS AND LIGHT CONDITIONS

SITE CLASSIFICATIONS

HABITAT QUALITY AND MANAGEMENT

LIFEFORMS AND GROUND COVER

ASSOCIATED SPECIES

EO SPECIMEN DOCUMENTATION

IMAGE INFORMATION

LOCATION INFORMATION

DIRECTIONS

APPENDIX A – REFERENCES

APPENDIX B - LIST OF VALUES (STANDARD CODES)

APPENDIX C - TES PLANT ELEMENT OCCURRENCE FIELD FORM

Overview

Following is an overview and general description of the Forest Service’s national protocol for collecting information about Threatened, Endangered and Sensitive plant occurrences.

General Description

The Threatened, Endangered and Sensitive (TES) Plant Protocol focuses on tracking the presence, location, extent, and abundance of TES plant occurrences. Tracking of “watch” species, species of concern, or locally rare species at a Forest level, may also be accomplished using this protocol. The protocol also includes methods to record and track site information for each TES plant occurrence, such as site morphometry, plant community, associated species, soil characteristics, disturbances or threats. One method of monitoring TES plant occurrences consists of repeated observations over time, noting relative changes in location, extent, and density of the plant population, as well as changes in existing or potential threats and habitat conditions. This method of monitoring may also be accomplished using the protocol.

Standardized tracking of TES plant occurrences directly supports the policy and legal requirements to maintain the viability of such species on National Forest System lands (FSM

2670; National Forest Management Act; Endangered Species Act). Business needs of the national TES Plant Program that will be supported by this protocol include:

Completion of Biological Assessments (BAs) and Biological Evaluations (BEs), Status summaries for TES plants, Completion of conservation assessments and conservation strategies for TES plants, Occurrence-level monitoring of TES plant populations over time (presence/absence, or abundance as measured by repeated censuses of the populations), and

Establish plant-habitat relationships.

National Standards

Following a corporate approach for collection of TES plant occurrence data facilitates:

Data sharing within the agency, Data sharing with partners, Data storage, tracking and reporting, and

Program consistency and efficiencies.

The national TES Plant Program has developed agency data standards for collection and storage of TES plant data. Beginning in November 2001, a program working group, consisting of the

Regional Botanists and a small number of botanists on the National Forests and Ranger Districts, provided the guidance for draft protocol development. In May 2004, the draft products were further reviewed by a larger group of field botanists across the agency, representing the program user community. Additional protocol modifications were included in early 2005 as a result of feedback during prototype testing of the corporate database application for TES plants.

Throughout the course of protocol development, reference was made to requirements in Biotics, the NatureServe database application used nationally by the network of state Natural Heritage

Programs. TES plant information gathered by Forest Service personnel will be entered and stored in the NRM TESP-IS corporate database of record. NRM design will also facilitate cooperation with NatureServe to electronically submit new element occurrence data from TESP-

IS to the Biotics databases at individual Natural Heritage Programs.

An element occurrence (EO) is an area of land and/or water in which a TES plant species is, or was, present. TES plant occurrences that are entered in the TESP-IS Application are synonymous with the element occurrences that are entered in Biotics by the Natural Heritage

Programs. The terms “plant occurrence”, “element occurrence”, “EO” or “occurrence” as used in this document may be considered interchangeable.

A required set of core attributes must be collected during field work and electronically stored in the corporate TESP-IS Application to meet the minimum business needs of this protocol.

Required attributes are established to meet corporate expectations of reporting, monitoring or data sharing (e.g., with Biotics). All other fields are considered optional and can be used as needed or conditionally required at the Regional or local level to meet specific program objectives. All required and optional fields in this protocol are supported in the TESP-IS

Application. Table 1 lists the required attributes for TES plant occurrences. Some attributes are auto-generated and populated in the application from the spatial feature. Detailed attribute descriptions and collection standards follow later in this document.

Required Attributes

Plant Occurrence Point or Polygon (spatial feature)

Site ID

Date

NRCS Plant Code for EO species

Scientific Name for Plant Code (generated from Plant Code)

Record Source

Locational Uncertainty

Examiner(s)

Ownership

Table 1: Fields required by Forest Service TES Plant Element Occurrence Protocol

Data can be recorded in the field using the standard field form for TES Plant Element

Occurrences (Appendix C) and then entered into TESP-IS. Regions or Forests may want to modify the field form using Appendix C as a template to focus on those items collected in the local program. The TESP-IS Application uses ArcMap, “Task Assistant” and data entry forms to guide the user through a standard workflow to enter and edit the spatial representation of the plant occurrence site and the associated attribute data. The data entry screens mimic the workflow as presented on the paper field form. Block headings on the paper form generally correspond to tabs or buttons on the electronic forms.

This TES Plant Element Occurrence Protocol and Field Guide makes occasional references to the NRM TESP-IS Application. However, the field guide is not meant to be a user guide for the application as a whole. Application User Guides, Administrative Guides, Stewardship Guides and other relevant information can be accessed via the NRM TESP-IS Product Page

(http://fsweb.nris.fs.fed.us/products/TESP_Invasive_Species/index.shtml) and moving to

Documentation.

Mapping

This protocol requires spatially locating and delineating each element occurrence. TES plant occurrences can be mapped and stored as either points or polygons. Occurrences that could be mapped as “lines,” such as those occurring along ridges or streams, will be stored as long, narrow polygons. Spatial representation can be created by a number of methods:

Hand-drawing the perimeter of the occurrence or a representative point on maps or aerial photos, then delineating the occurrence within the NRM TESP-IS Application;

Using a GPS (Global Positioning System) device to define smaller areas, especially for points, converting them to a shapefile, and importing the file;

Digitizing the occurrence with a computerized mapping system (Geographic Information

System [GIS]) and importing it.

Regardless of the method used to delineate a TES plant occurrence in the field, the protocol requires that the point or polygon be digitized and stored in ArcMap format. The point or polygon feature must be entered into TESP-IS before additional tabular attributes can be entered.

To ensure consistency, the scale for hand-drawn occurrences on maps should be 1:24,000. This is the scale of United States Geological Survey (USGS) 7.5-minute quadrangle (quad) maps.

Note that maps with a variety of scales are utilized in Alaska. (Note: the 1:24,000 scale is also the standard for invasive plant mapping as recommended by the International Mapping

Standards for Invasive Plants). Aerial photos, orthophoto quads and remote sensing approaches can also be useful formats for delineation.

There is no minimum size for a delineated polygon; however, occurrences less than .01 acre are generally mapped as points. The TESP-IS Application will allow very small occurrences to be accurately depicted and located. It will also facilitate monitoring small changes in size.

A single TES plant occurrence may be comprised of more than one polygon (Figure 1). For example, a single occurrence may be defined by clumps of the same population in close proximity with intervening habitat. Recorded plant occurrence data, however, apply to the entire occurrence. Detailed data for each “subpopulation” of the survey is not specifically tracked in the

TES plant occurrence data collection methods, field form, or NRM TESP-IS Application. Each subpopulation can be individually drawn as polygons in the application if desired. Acres for all subpopulations comprising a particular occurrence are combined to calculate and auto-populate the occurrence area in the application (this is considered a multi-part polygon). Text notes about specific subpopulations can be recorded and stored in the “EO comments” field.

Figure 1: EO 1 is single element occurrence represented by one contiguous polygon.

EO 2 is a single element occurrence represented by a multi-part polygon.

Tabular location fields are provided in the field form and the application, but are purely optional.

These fields can be used to record a representative point or area for the plant occurrence when desired (available tabular location fields are outlined in the “Location Details Section”).

Monitoring TES Plant Occurrences (Revisits)

An essential element of TES plant management is monitoring changes or stability in populations over time. Subsequent visits to a known site for remeasurement will be considered revisits.

Revisiting TES plant occurrences may also allow for detection of changes of threats to an occurrence. Each visit to a TES plant occurrence will require the completion of a new element occurrence form and the creation of a new record in the TESP-IS Application to document that visit. The Site ID must remain constant for a particular occurrence through time (see data field descriptions later in this document). Record “Revisit” in the “Record Source” Field. Some of the general site and location information from the previous visit can be automatically transferred to the new record within the TESP-IS Application when appropriate. You can then update information about the plant occurrence based on the current visit.

Changes in the occurrence data (i.e. size, shape, plant abundance, habitat or threats) can be traced over time through subsequent visits, differentiated by the Visit Date. The TESP-IS application will track these changes through time and record or display the history of any given site.

Extirpated Occurrences

All visual evidence of a formerly documented occurrence could be lacking during a revisit of the site. Though the plant may have disappeared above ground, there may be roots, rhizomes, or other plant parts that may recover and sprout. The relative time of visit compared to other years and/or yearly climate fluctuations may also affect the observation. Also, seeds of some species are stored in the soil and may remain viable for many years. For these reasons it is important to monitor some sites for many years, even after all evidence of the plant may have disappeared during an earlier visit.

For revisits that turn up no visual evidence of the TES plant, enter a new polygon or point representing the occurrence by copying the most recent spatial feature for that EO. Enter “No” for the “Plants Found” field and uncheck this flag in the application. Enter a canopy cover and plant count of zero (0). Enter appropriate comments in the “Population Comment” field and the

“Revisit Justification” field. Other fields pertaining to habitat and threats (which may or may not be causal agents for change to the plant population) should be recorded. Recording a new revisit polygon/point and related data in the interim allows for monitoring of the site until there is adequate evidence that the occurrence has in fact disappeared.

Quality Control

The TESP-IS Application for TES Plant Occurrences includes a quality control (Q/C) flag to indicate when the information for a particular EO is complete and has been reviewed and accepted by the appropriate data steward. At that point it is deemed ready for use in comprehensive analysis and for data sharing with partners (“no” is the default value until certified). All required field work and data entry must be complete before a TES plant occurrence can be certified. The certification date and the person’s name are auto-populated in the database form when the certification flag is switched to “yes.” Only a person with the

Steward Role can certify the plant occurrence record within the application. Persons with the

TESP Editor Role can enter and edit data as appropriate. Once an occurrence is certified by the data steward, it is locked and cannot be further edited by those without the steward role.

Plant Occurrence Field Form Instructions

Following is a list of data attributes (or data fields) and instructions for recording specific data about a TES plant occurrence. These attributes are supported by the methods of this protocol and by the TESP-IS Application.

Collecting information for a TES plant occurrence such as soil characteristics, existing vegetation community type, associated species, potential vegetation types, aspect, slope and elevation is encouraged, but not required by the national protocol. This information will be useful in establishing habitat relationships and modeling to predict where one might find or search for a particular species, as well as inferring the potential for a particular species to occur in an area either at present or in the future. Additional information about dominant ecological processes, threats, and current or expected management activities aid in predicting stability of that particular occurrence.

Required data fields are indicated below and on the attached field form. Data attributes are grouped into general categories. Categories and field numbers correspond to the layout and naming conventions used on the attached TES Plant Occurrence field form. Comment fields are

2000 characters in length. Fields that have a standard “List of Values” associated with them include “(LOV)” next to the field name. The specific values for each LOV are listed in

Appendix B. The field form layout may be used as is or modified to cater to your unit (e.g., drop fields never used on your Forest, pre-populate Region or Forest fields, etc.) However, please note:

Only the attributes listed on the field form along with the documented coding conventions are supported in the NRM TESP-IS Application.

The workflow within the application will mimic the grouping, flow and presentation of data fields as presented in the attached standard EO field form.

General Information

1) Site ID: Required.

Site_ID is the Forest Service’s unique identifier for an element occurrence. The Site ID can be any combination of letters and numbers up to 30 characters in length. Regions are encouraged to adopt a standard coding convention to facilitate tracking. It is highly recommended that the combination of Region, Forest and District numbers and the letters, “EO” form the first eight digits of the Site ID (example: RRFFDDEO##### [060805EO00055]). This convention will facilitate consistent tracking, sorting and reporting of Element Occurrence records at the Forest and Regional level. Since field sheets may get split up, it is a good idea to repeat the Site ID at the top of each page. Each TES plant occurrence will be mapped separately so that each Site ID will document a single occurrence. Revisits to the same occurrence must continue to track using this same Site ID but with a different date.

The Natural Heritage Program is responsible for assigning element occurrence (EO) numbers.

Thus, an EO number will not be available as a unique identifier for new occurrences, until they are assigned by the State Natural Heritage Program. Since Forest Service objectives for delimitation may vary from the Natural Heritage Program, multiple “Site IDs” can be assigned the same EO#. In addition, “watch” species or Forest “species of concern” that wouldn’t be submitted to the State Natural Heritage Program will need a unique Site ID for tracking, but will not receive an actual EO number.

2) Date: Required.

Date when the field data for this plant occurrence was collected (not the date the record was entered into the computer). Use date format of: MM/DD/YYYY. Date provides information about the time of year plants and habitats were observed and indicate the age of the occurrence information, which may help identify the need for revisits.

3) Site Name:

Informal descriptive name assigned to the plant occurrence site or area in general.

4) NRCS Plant Code: Required (LOV):

The NRCS accepted plant symbol for the species. Plant Code is required by the application, but not on the field-form if scientific name is entered. Enter one code for the TES plant being documented in this particular EO. Codes for plant species must follow the USDA PLANTS database, plant symbols convention (USDA, NRCS 2002). Botanical nomenclature should follow a standard flora for the geographic area being sampled.

5) Scientific Name: (Generated, View-only).

Enter the scientific name of the TES plant on the field form if the NRCS code is not known. It is a good habit, however, to write out the name or portion of the name on the field form to minimize misapplication of plant codes. The TESP-IS Application will auto-populate the scientific name when codes are entered or will auto-populate the NRCS plant code when the scientific name is chosen from a standard list. Include the genus, species, and subspecies or variety as needed to properly identify the TES plant.

6) Record Source: Required (LOV).

Indicate the source of data for the EO record, such as Field Survey or herbarium specimen.

7) Survey ID:

If the record source is “Field Survey,” indicate the Survey ID Number, if known. Refer to the

Survey Protocol for Survey ID coding conventions.

9) Examiner(s): Required (LOV).

Examiner is the First and Last name(s) of the individuals that detected the element occurrence.

This will provide a point of contact for questions during data entry or for future reference.

10) Ownership: Required (LOV).

Record the land ownership where the occurrence is located. Where the occurrence exists on two or more ownerships or jurisdictions, enter all that apply.

11) Locational Uncertainty: Required (LOV).

An indication of how confident you are in the accuracy of defining the location of the EO. When following the accuracy standards as described within this protocol, locational uncertainty should generally be negligible (accurate within 20 feet). The TESP-IS Application will default this field to negligible.

12a) Uncertainty Distance: Conditionally Required (LOV).

This field is required only if ‘Aerial Estimated’ is selected in the ‘Locational Uncertainty’ field.

Select from a range of values, in meters, or select ‘Custom.

12b) Custom Distance: Conditionally Required.

Populate with your ‘aerial estimated’ distance if custom distance was selected in the previous field.

12c) UOM (for Custom Distance): Conditionally Required (LOV).

Select ‘feet’ or ‘meters’ as the unit of measure for your ‘aerial estimated’ distance.

13) EO Number:

The unique identifier assigned by the State Heritage Program to an element occurrence. This will be null for new occurrences that are not yet submitted for Heritage review. Element occurrence number does not have to be unique for each TESP Site. Sometimes multiple Forest

Service TESP Sites get combined into one element occurrence by the Heritage program. This field can help to track this concept.

19) Area (Area of Occupancy), (Generated, View-only):

The area in acres occupied by the TES plant occurrence. You may wish to record the estimated size of the area occupied on the field form. The area will, however, be auto-populated in the

TESP-IS Application from the spatial feature once the polygon(s) are created. If subpopulations exist and are mapped, size will be calculated by adding the area from all related subpopulations to determine the total size of the EO. If the EO is a point, the application does not display area in the data editing forms, but for output and reporting purposes points will be buffered and reported as having an area of 0.001 acres.

20) Area Unit of Measure:

Record the unit of measure if an area estimate is entered on the field form. Units can be acres, square meters, or hectares, but acres will be used in the TESP-IS Application.

Element Occurrence Data

Canopy Cover A measurement of canopy cover is encouraged for the EO species and optional for associated species and lifeform classes. Ocular estimates of canopy cover of live foliage for plant species or groups of plant species are an effective way to quickly collect abundance information about plants. Cover is a meaningful attribute for nearly all plant life forms, which allows their abundances to be evaluated in comparable terms (Daubenmire 1968, Mueller-Dombois and

Ellenberg 1974). Percent cover can be defined generically as “the vertical projection of the crown or shoot area to the ground surface expressed as … percent of the reference area”

(Mueller-Dombois and Ellenberg 1974). Canopy cover is “the percentage of ground covered by a vertical projection of the outermost perimeter of the natural spread of foliage of plants, small openings within the canopy are included” (SRM 1989, NRCS 1997). Canopy cover is synonymous with canopy closure (Helms 1998). For woody plants, canopy cover is synonymous with crown cover (NRCS 1997, Helms 1998).

Cover values are estimated and recorded for the EO polygon(s) or site as a whole (e.g., these values are not recorded using plot- or transect-based methods). The purpose for entering cover values is simply to provide relative estimates that might be used to compare the abundance of species at the EO site. As such, these cover values would not be appropriate for more rigorous quantitative analyses of vegetation data. If such rigorous data are desired, then the examiner(s) should use one of the appropriate vegetation protocols available such as ocular macroplot, cover-frequency, or line intercept (USDA Forest Service, 2007). These guides are available on-line at:

http://fsweb.nris.fs.fed.us/products/Rangeland_Inventory_Monitoring/getstarted.shtml

Estimating Canopy Cover Project the outline of the plant’s live foliage vertically to a horizontal plane to determine what percentage of the EO polygon area that it covers at the time of the survey. For canopy cover by lifeform or for associated species, contributing plants do not have to be rooted in the polygon to be counted for canopy cover (e.g., they can overhang the edges of the polygon in which cover is being estimated). The area of foliar cover included in the polygon, expressed as a percent of the total sampling area, represents the canopy cover for that individual species or plant group being estimated. Different lifeform groups or plants may overlap and, therefore, it is common for the canopy cover “sum” across lifeforms or across multiple plant species to be greater than 100% within a polygon. No single lifeform class or plant species, however, can total greater than

100%.

Canopy cover information can be collected using actual values or by using established canopy cover classes. If canopy cover classes are used to measure canopy cover, indicate the Cover

Class Set used.

21) Canopy Cover Method: Conditionally Required (LOV).

If cover values are recorded for any of the cover fields, then indicate the one method used for making any cover estimates at this site. Choices are Percent (0.1-100%), Daubenmire (modified)

Cover Class Set, and National Range Cover Ten Class Set. See Appendix B for a list of canopy cover sets and the cover class codes for each set.

22) EO Canopy Cover:

The percent cover or cover class of the TES plant species within the EO polygon(s) or site..

Refer to discussion above for canopy cover concepts.

23) Lifeform: (LOV).

Lifeform is the characteristic form or appearance of a species at maturity. Default values are autopopulated in the TESP-IS Application by plant code.

24) Subpopulations:

The number of groups or ‘subpopulations’ that may comprise an occurrence. If the EO is not mapped as one contiguous polygon, map each subpopulation considered to be a component of this particular EO. Attributes stored in the application, however, will be relevant to the entire EO polygon only, and detailed data for each subpopulation is not tracked in the application. Text notes about subpopulations can be recorded and stored in the EO comment field. Although each

“subpopulation” will be sketched, acres for all subpopulations for a particular EO will be combined to calculate and auto-populate an accurate size in the application for the entire EO.

25) Plant Found (for Revisits) (LOV):

Indicate whether the EO plant species was observed during a revisit to the EO. The default is

“Yes” for all new occurrences. If the plant is not observed during a revisit to the EO, record

“No” in the application.

26) Plant Count:

Indicate the number of individual plants of the EO species within that occurrence.

27) Plant Count Type: (LOV).

http://fsweb.nris.fs.fed.us/products/Rangeland_Inventory_Monitoring/getstarted.shtml

Indicate what was counted: Genets, Ramets, or Undetermined. Counts of genets represent the number of genetically independent individuals in an occurrence. Counts of ramets represent the number of vegetative units that are produced by the genets in an occurrence. For example, a plant occurrence that has five individual plants, each of which has produced five stems, consists of 5 genets and 25 ramets.

28) Estimate:

Yes or No flag field to indicate if the plant count was a precise count or an estimate. Record Yes if the count is a qualitative estimate or No if all plants were actually counted.

29) Revisit Needed:

A “Yes” or “No” field that indicates a need for a follow-up visit. Record yes if fieldwork is not completed and an additional visit is needed or yes if a follow-up visit is anticipated or desired for monitoring purposes.

30) Planned Revisit Date:

Record a Planned date to re-visit the occurrence if that is identified. For example, enter a projected date if a particular study or set of circumstances require the EO to be re-examined two years from now or for monitoring purposes after project completion, or perhaps later in the same growing season. For visits over multiple years, it is generally best to compare sites at the same time each year.

31) Revisit Justification:

A text field to record reasons a revisit is desired. Examples include: post-project monitoring, successional monitoring, recovery or stability after protection, where revisits are part of a sampling method for a particular species protocol, etc.

32) Phenology by %:

Record the percentage of the occurrence that was in each stage at the time of visit: vegetative, flower/bud, fruit/dispersed, seedlings/juvenile. Values should total to 100%.

33) Population Comments:

A text field to record observations regarding the status of the population, including distribution, vigor, density, phenology and dispersal.

34) Evidence of disease, competition, predation, collection, trampling, or herbivory:

A “Yes” or “No” field to indicate any evidence of these effects on the population.

35) Evidence Comments:

If the Evidence Field is checked “Yes”, Evidence Comments provides a text field for a brief explanation. If possible, record the cause of the effect(s).

36) Pollinator Observed: (LOV).

A Yes or No Field that indicates whether pollinators were observed visiting flowers or reproductive structures of the TES plant.

37) Pollinator Type(s): (LOV).

The organism(s) observed pollinating the TES plant.

38) Pollinator Comments:

AText field, if needed, for further explanation of pollinator observations.

Site Morphometry

39) Percent Slope:

The average slope that is characteristic of the EO polygon or site, expressed as a percentage as measured in the field.

40) Slope position: (LOV).

Record the two-dimensional position of the occurrence on the landform as observed in the field.

41) Aspect:

Record the predominant aspect as measured in the field that is characteristic of the EO polygon or site. Either azimuth in degrees (preferred) or cardinal direction can be used.

Azimuth:

(Range 0-360). The direction that the landscape predominantly faces at a defined position, such as the center point of the occurrence. Azimuth is recorded in degrees from north, in a clockwise manner. Use “360” for north. Use “0” when there is no slope.

Cardinal: (LOV).

The generalized cardinal direction that the landscape predominantly faces at a defined position, such as the center point of the occurrence. (Accuracy Standard: ± 11.25 degrees).

42) Elevation:

For the spatial extent of the occurrence, record the average (or a “predominant”) elevation of the area occupied by the species as measured either in feet or meters above sea level. Minimum and maximum elevation should be recorded only if it is determined that the elevation range is significant for that particular occurrence (e.g., an occurrence on a steep slope or a large occurrence on an undulating landscape).

43) Elevation Unit of Measure: Conditionally Required (LOV).

Record the unit elevation was measured in; feet or meters.

Soil Characteristics and Light Conditions

44) Substrate on which EO occurs: (LOV).

Record the predominant substrate that the rare plant species is rooted in.

45) Parent Material: (LOV).

The unconsolidated material, mineral or organic, from which the substrate in the occurrence polygon developed.

46) Soil Moisture: (LOV).

Moisture state of the soil for the time period being described.

47) Soil Texture: (LOV).

The code for the proportions of the various size groups of individual mineral soil grains less than two millimeters equivalent diameter in a mass of soil, expressed as a class, or names for other materials or physical state, measured at the surface horizon.

48) Soil Type:

If desired, record the dominant soil map unit or soil series as indicated on a soils or ecological unit inventory map. Refer to locally stewarded soil maps or GIS layers to obtain this information. This information is not entered into the NRIS TES Plant Application. It would be obtained by intersecting appropriate spatial layers.

49) Light Exposure: (LOV).

Record the predominant light exposure throughout the occurrence polygon. Choose one of three values (full sun/ partial shade/ full shade).

Site Classifications

Record taxonomic units by type if published classifications exist for the area. Taxonomic classifications are not developed at the time of TES plant inventory. Use locally appropriate field keys and guides to describe the TES plant occurrence habitat within the terms of locally accepted and published classification systems. Contact your local or Regional ecologist for appropriate information available for use in your area. Available taxonomic classifications sanctioned for your area by regional and local stewards have been previously entered into NRIS and are used in the TES plants application as Lists of Values.

Taxonomic information about plant communities and site potential, along with other site morphometry measures and associated species, provide valuable information to model, track and predict the potential for TES plant species occurrences in time and space. Examples include focusing surveys on suspected habitats, predictive insight on the stability or successional status of the associated vegetation for a given population, and the ability to document and refine predictive models. Available taxonomic classifications and detail vary by Region within the

USFS.

Existing Vegetation classifications provide context regarding the seral stage or current plant community in which the species occurs and should be recorded whenever possible. Existing vegetation classifications developed by the USFS, NatureServe or other partners may include hierarchical levels (i.e. classification levels) such as broad cover types, or alliances, or more detailed classifications at the association or community type level. Since most classification systems are hierarchical by design, record the most detailed classification level available (e.g., an association vs. an alliance).

Potential vegetation (or “Potential Natural Vegetation”) or Ecological Type classifications provide context to determine areas that may now or in the future contain suitable habitat for a given species, and predictive insight on the stability of the population on that particular site in time. For example, based on knowing the site capability where the EO occurs, the site may become more or less favorable through time for that particular TES plant species. Potential vegetation classifications include hierarchical levels (i.e. classification levels) with nomenclature such as series, plant association, habitat types, or phases of plant associations and habitat types.

Ecological type information, which by design integrates soil, geology, geomorphology and potential vegetation, should be used at the landtype or landtype phase level when available.

50) Existing Veg: (LOV).

Record the taxonomic classification name or code for the existing vegetation type that accurately describes the EO. In addition to code and name, the following fields are used in NRIS (as stewarded and stored regionally) to locate the correct record from a List of Values:

Classification Level, Classification Code, Classification Short Name and Classification Set.

51) Potential Veg: (LOV).

Record the taxonomic classification name or code for the potential natural vegetation type that accurately describes the EO. In addition to code and name, the following fields are used in NRIS

(as stewarded and stored regionally) to locate the correct record from a List of Values:

Classification Level, Classification Code, Classification Short Name and Classification Set.

52) Ecotype: (LOV).

Record the taxonomic classification name or code for the ecological type classification that accurately describes the EO. In addition to code and name, the following fields are used in NRIS

(as stewarded and stored regionally) to locate the correct record from a List of Values:

Classification Level, Classification Code, Classification Short Name and Classification Set.

Habitat Quality and Management

53) Habitat Description:

A text field torecord descriptions or observations about the habitat that the EO occupies.

54) Dominant Process: (LOV).

Record a value indicating the dominant disturbance regime influencing the EO, if any

55) Process Comment:

Text field. Record any comments about the observed dominant disturbance.

56) Community Quality: (LOV).

Enter a qualitative ranking for the overall quality of the habitat or plant community(-ies) with which the TES plant is associated. Choices: Low, Medium, High.

57) Landscape Integrity: (LOV).

Enter a qualitative ranking for the overall quality of the landscape setting in which the TES plant is located. Choices: Low, Medium, High.

58) Threats (present or imminent): (LOV).

Record threats or potential threats, e.g., noxious weeds, OHV trails, or environmental problems that could affect the TES plant habitat.

59) Disturbance/Threat Comment:

Record any comments about the extent or severity of the threat(s).

60) Non-native Species Comment:

A text field where comments and observations can be entered concerning non-native species occurrences within or adjacent to the specific EO.

61) Current Land Use Comment:

A text field where comments and observations can be entered concerning current land uses within or adjacent to the EO, including recommendations for modifications.

Lifeforms and Ground Cover

These lifeform canopy cover and ground cover estimates are approximate values. They are intended simply to give a general picture of the composition and relative abundance by lifeform category at the EO site during the visit. Use the same method for estimating covers as indicated in field 21, “Canopy Cover Method”. See the Canopy Cover Section earlier for more detail regarding the use of cover data in this form.

62) Lifeform Canopy Cover (% Cover or Class): (LOV).

Record the canopy cover for each lifeform represented in the EO, expressed as either percent cover values or canopy cover classes. Use the same method or class set for estimating cover for all cover estimates made for various lifeforms at this EO.

63) Ground Cover Type (% Cover or Class): (LOV).

Record the composition of the ground surface within the EO at the time of visit. Record each ground surface cover type present in the EO, expressed as a percent cover value or cover class code. This includes organic material, vegetation basal cover (live and standing dead), mosses, lichens, litter/duff, and inorganic material such as exposed mineral soil, gravel, rock, bedrock and any road surface. Ground surface for each type is estimated within only a two dimensional plane (unlike foliage cover); thus the total of all types should approximate 100%.

Associated Species

Associated species are those found in the same habitat and same location as the EO and should not include species that are not directly within or related to the EO polygon or site. Associated species help to establish habitat relationships and can help in habitat modeling. Associated species in the area beyond the EO polygon can be listed on the TES plant field survey form

(survey area species tab).

There is no limit to the number of species that may be entered. It is a good habit to write out the name or portion of the name on the field form to minimize misapplication of plant codes. The

NRIS TES Plant application will, however, auto-populate the entire scientific name when plant codes are entered, and can auto-populate the NRCS plant code when the scientific name is queried from the look-up list. Include the genus, species, and subspecies or variety as needed to properly identify the plant.

64) Completeness of Species List: Conditionally required (LOV).

It is helpful to know if the species list is a best attempt to document all associated species at the

EO site (complete list) or if just certain species of interest were listed (selected or reduced by some abundance level, or due to time constraints). Indicate how thorough the list of associated species is for an EO observation by selecting one of the standard values from the LOV. This field is conditionally required if associated species are listed.

65) Plant List Comment:

A text field to describe what guidelines were used for recording species or to give a text description of how complete or thorough the associated species list is. It is good practice to explain in this comment section what criteria were used to collect any partial plant list.

66) and 67) NRCS Plant Code and Scientific Name:

Record all associated plant species (plant code and/or scientific name) that are to be included in the EO site plant list. Codes for plant species must follow the USDA PLANTS database, plant symbols convention (USDA, NRCS, 2008). Botanical nomenclature should follow a standard flora for the geographic area being sampled.

68) Lifeform: (LOV).

Lifeform is defined as the characteristic form or appearance of a species at maturity. As desired, enter the lifeform code for each associated species listed for the EO. Default values are autopopulated in the NRIS application by plant code.

69) Dominant: (LOV).

If desired, indicate whether the species is dominant at this site (Y = yes)

70) Percent Cover or Class: (LOV).

These cover estimates are approximate values, and are intended simply to give a general picture of the composition and relative abundance of each species at the EO site during this visit. Use the same method for estimating covers as indicated in, “Canopy Cover Method” field. See the

Canopy Cover Section earlier for more detail regarding the use of cover data in this form.

EO Specimen Documentation

Record appropriate documentation for EO voucher specimens collected for non-federally listed plants.

73) Lead Collector:. Conditionally Required. (LOV)

Required if a voucher specimen is collected. Record the lead collector of the specimen, who is responsible for assigning the collection number.

Other Collectors:

If additional collectors were involved in the collection.

74) Collection #: Conditionally Required.

Required if a specimen is collected. Record a unique number, assigned by the primary collector, for the specimen. If no collection number is assigned to the specimen, enter “s.n.”

75) ID Confirmed: Conditionally Required (LOV).

A Yes/No Field required if a specimen is collected. It indicates whether a positive identification has been confirmed for the specimen.

76) Verification:

A text field where name and institution or agency of the individual who provides authoritative verification of the specimen identification can be entered.

77) Specimen Repository: Conditionally Required.

A locally stewarded list of values that indicates the herbarium or location where the collected specimen is stored. Required if a specimen is collected.

Attachments: Image Information

Photos or PDFs can be stored electronically within the TESP-IS Application. Use this functionality for pictures specific to characteristics of the TESP site or to scan maps or diagrams of the EO site.

78) Date:

Date field used to denote date the attachment was created.

79) Description(s):

Text field used to describe the subject of any photograph or electronic image taken.

Name:

Text field used to denote the name of the attachment.

Author/Photographer:

Text field used to denote the name of the author of the PDF document or Photographer of the attached photo.

Location Information

This protocol requires spatially delineating each TES plant occurrence to document the location and extent of the occurrence (refer to Mapping the Survey Area on page 7). In addition to storing the spatial representation, you may wish to populate geopolitical units on the field form based or alternative location details on the location of the occurrence polygon or point.

Geopolitical Units

It can be useful to record the political or administrative units on the field form. While these fields are not entered in the TESP-IS Application, some programs may require them to be entered on paper field forms. An occurrence may span two or more geopolitical units for any particular field. For example, a survey may extend across a state, county or National Forest boundary. In this case, record all that apply.

14) State:

It is useful to enter this information on the field form. Record the code for the state in which the site is located. These codes are the same as the postal state codes.

15) County Name:

It is useful to enter this information on the field form. Enter the county in which the EO is located. If the element occurrence crosses county lines, record appropriate counties.

16) Region:

It is useful to enter this information on the field form. Record the Region number where the occurrence is located, regardless of which Region is currently administering the site.

17) National Forest/Grassland:

It is useful to enter this information on the field form; however, this will be auto-populated in the application when the spatial feature (EO polygon) is entered. Record the National Forest or

Grassland where the occurrence is located. Forest/Grassland codes will be auto-populated in the application as the VPD unit code when the spatial feature is created.

18) District:

It is useful to enter this information on the field form. Record the Ranger District number(s) where the site is located.

Alternative Location Methods

Tabular location fields beyond those mentioned above are also provided in the field form and in the application, but are purely optional. These fields can be used to record a representative point or area for the location of the plant occurrence, when desired. Tabular data can be recorded about quad maps or legal description.

80) USGS Quad Number:

The number of the primary USGS quadrangle map containing the survey. These codes are stewarded nationally by the ALP application. (Note: only one representative quad can be entered in the NRIS application. EOs may cross into more than one)

81) USGS Quad Name:

The name of the primary USGS quadrangle map containing the survey. These codes are stewarded nationally by the ALP application. (Note: currently only one representative quad can be entered in the NRIS application. EOs may cross into more than one)

82) Forest Quad Number:

The locally stewarded number for the primary USGS quad map where the survey is located.

(Note: currently only one representative quad can be entered in the NRIS application. EOs may cross into more than one)

83) Forest Quad Name:

The locally stewarded name for the primary USGS quad map where the survey is located. (Note:

currently only one representative quad can be entered in the NRIS application. EOs may cross into more than one)

84) Legal Description (Public Land Survey System or “PLSS”):

For areas of the country where the Public Land Survey System is available, it is desirable and required to record this information to an appropriate level of detail on the field form only.

Since legal descriptions will not be auto-populated in the application, this information must be manually entered into the NRM TESP data entry form if it is desired to be electronically stored.

(These fields can be used only to record a representative point or area for the EO, when desired.)

Meridian: (LOV)

Record the code for the line of longitude from north to south that is the basis for local legal descriptions. These lines are also known as Principal Meridians and have distinct names. This information is available on the USGS Quadrangle map.

Township/Direction: (LOV).

A Township is a unit of land containing 36 mile-square sections. Townships run in rows that parallel the local Base line. Each Township row is sequentially numbered relative to the row’s order from, and whether it’s north or south of, the local Base line; e.g., T2N

(for the second township row north of the local Base line). To accommodate fractions of townships an additional code is required after the Township number, where 0 will equal no fraction; 1 equals ¼; 2 equals ½, and 3 equals a ¾ township (see table of examples below). This information is available on the USGS Quadrangle map.

Range/Direction: (LOV).

The Range numbers run parallel to the local Principal Meridian. Range rows are sequentially numbered relative to the row’s order from, and whether it’s east or west of, the Principal Meridian; e.g. R2E (for the second Range row east of the Principal

Meridian). This information is available on the USGS Quadrangle map.

Township & Range Example Description

7 N 14 E Township 7 North, Range 14 East

7.1 N 16 E Township 7 1/4 North, Range 16 East

8.2 N 12.0 W Township 8 1/2 North, Range 12 West

Section: (LOV).

Each 36 square-mile township is subdivided into smaller squares called Sections. Record the Section where the center of the EO is located. A Section is equal to one square mile,

2.59 square kilometers, 640 acres, or 1/36 of a township. This information is available on the USGS Quadrangle map. (Note: Only one representative section can be entered in the application and surveys may commonly cross into more than one)

Quarter Section: (LOV).

The quarter-section subdivision where the center of the EO is located. For example: the

NE quarter of section 4 (NE ¼).

Quarter, Quarter Section: (LOV).

The quarter-quarter section subdivision where the center of the EO is located. For example: the NW quarter of the NE quarter of Section 4 (NW ¼ NE ¼).

Quarter, Quarter, Quarter Section: (LOV).

The quarter-quarter-quarter section subdivision where the center of the EO is located.

For example: the SE quarter of the NW quarter of the NE quarter of Section 4 (SE ¼ NW

¼ NE ¼).

Quarter, Quarter, Quarter, Quarter Section: (LOV).

The quarter-quarter-quarter-quarter section subdivision where the center of the EO is located. For example: the SW quarter of the SE quarter of the NW quarter of the NE quarter of Section 4 (SW ¼ SE ¼ NW ¼ NE ¼).

85) Latitude and Longitude:

Arbitrary measurements used to describe any point on the Earth or similar globe. Borrowing from theories of ancient Babylonians, later expanded by the famous Greek thinker and geographer Ptolemy, a full circle is assigned 360 degrees. Latitude is the term for the distance from the middle of the circle, or, in the case of the Earth, the equator. The equator is designated 0 degrees, with each pole being 90 degrees. Longitude is the vertical measurement--current convention places the zero degree point at Greenwich, England (also known as the Prime

Meridian), with 180 degrees being on the opposite point on the globe. Latitude and Longitude may be entered in the field form, however Lat/Long in Decimal Degrees will be automatically entered in the application when the feature is created based on the centroid of the polygon or the location of the point.

87) GPS Equipment Used:

The manufacturer and model number of the GPS unit used.

http://www.answers.com/main/ntquery;jsessionid=noidrillscfd?method=4&dsid=2222&dekey=Geographical+pole&gwp=8&curtab=2222_1&sbid=lc03b

88) Directions:

A general description of the EO location, with directions as needed to return to the area including

Metes and Bounds if appropriate. Metes and bounds is a system or method of describing property or real estate when it is surveyed. The system was used in England and, by custom, was applied in the original 13 colonies that became the United States.