R2SuppFSVegSpatialUserGuide_20201203.docx

R2 Supplemental User Guide for FSVeg Spatial 12/3/2020 R2 Supplement to the FSVeg Spatial User Guide Contents

Objective & Desired Product

By definition the vegetation layer is dynamic. Existing vegetation characteristics are constantly changing due to successional processes and disturbance events. Both natural and artificial disturbance events influence changes in vegetation. The vegetation polygon layer is the Region 2 corporate layer that describes existing vegetation. The vegetation data in the FSVeg Spatial database is also used as the base layer that feeds other vegetation and habitat analysis programs and models.

The layer was created to meet the following objectives:

· Existing vegetation and other ground cover is described on the landscape, through a consistent protocol.

· Basic information on existing vegetation is provided in a common format using standard terms, definitions, and measurements.

· The existing vegetation layer is consistent throughout the Rocky Mountain Region.

· The vegetation unit layer is updated as necessary when management activities and natural processes occur and as new information becomes available.

National System FSVeg Spatial Objectives:

FSVeg Spatial is a national geodatabase system, which meets the following objectives:

· Provides guidelines, hierarchy, and structure for mapping all existing vegetation and non-vegetative ground cover.

· The SDE geodatabase Feature dataset, tables, and associated editing and analysis tools can be exported to a personal geodatabase for distribution to others (internal and external).

· Provides nationally consistent data mangement tools and processes with national training and support to assist users in management and maintenance of this vegetation data.

· Data is updated using ‘checkout’ and ‘checkin’ editing, which maintains data integrity by allowing only one user access to edit an area at a time.

· Disconnected editing increases user efficiency by allowing editors to be off-line and disconnected from the Forest Service network while editing and updating vegetation data.

The vegetation layer shall be developed at a 1:24,000 map scale or better following minimum standards that:

4. Delineations cover 100% of the area of the administrative unit, with no overlap and no gaps.

5. Are easy to understand and maintain using the various spatial editing tools that are provided.

Polygon Maintenance Requirements

Policy The Forest FSVeg Spatial GeoDataBase shall be maintained regularly and consistently so that it reflects the most recent sample of existing vegetation type, condition, and attributes available. It is the responsibility of users of the vegetation data to participate in updating the database and/or coverage when they become aware of either actual changes on the ground or errors in the data. At a minimum, field personnel shall complete the ‘R2 FSVeg Spatial Polygon Vegetation Attributes’ form during field visits to update existing vegetation data. Since FSVeg Spatial is a GeoDataBase, the tabular and spatial are generally edited together and the system maintains the 1:1 synchronization.

Forests shall establish an FSVeg maintenance team, consisting of the GIS Coordinator, the FSVeg Spatial Steward, and designated Editors who are responsible for data collection, data entry, data organization, database edits and maintenance, delegating of work, and training users to complete these tasks. Other personnel who use FSVeg Spatial information must be aware of and trained in the processes involved in database maintenance, data collection and data entry. The Washington Office FSVeg Group and your Regional FSVeg Spatial Coordinator provide classroom, on-line, and virtual trainings to assist you with use of this application. The Regional office also provides specific direction for R2 use of FSVeg Spatial to maintain consistency across all Forests and Grasslands.

The FSVeg Spatial inventory contains basic data as well as summary calculations from this basic data. Each supplemental data collection will also consist of attributing the basic data necessary to perform the summary calculations, whether from photo interpretation or a field inventory. The existing vegetation coverage must be updated annually as a minimum, and may be updated more frequently if necessary for specific projects or circumstances. Updates should reflect changes due to vegetation treatment, natural changes, or new inventories, and may include such items as timber harvests, fires, insect and disease effects, blow down, etc. Updates may include field verified information and may simply result in changes in the polygon attributing, as opposed to polygon boundary changes. However, it is critical that the polygon delineation is accurate prior to spending money on office or field data attributing.

The intent is to maintain FSVeg Spatial within the bounds of the delineating and attributing specifications. FSVeg Spatial is intended to be current and applicable to the Forest-wide analysis scale and project scale. Updates, at a minimum, will be commensurate with the Forest-wide scale of resolution. Forests shall make updates at a finer scale for individual project resolution. Minimum size of delineated areas is generally 1 acre but may be smaller if needed for a particular purpose. As a minimum, an archive copy of the FSVeg Spatial geodatabase will be made annually.

Editor Role -- Editing and Check-In Review Requirements:

To ensure integrity of the forests’ FSVeg Spatial database, editors must attend a FSVeg Spatial training session and demonstrate to the Forest Data Steward that they have the skills and knowledge to edit and manage this vegetation database. It is also highly recommended that editors have knowledge and experience in collecting and analyzing Common Stand Exam point data, since the CSE point data in FSVeg tabular is now integrated with FSVeg Spatial, and editors will need to make informed decisions on managing the point data when performing polygon edits. Decisions made when splitting polygons will actually edit and change point data in the CSE FSVeg tabular point database upon check-in.

Once editors are finished with edits and updates for the checkout, a thorough review of the data must be completed before handing off to the Forest Data Steward for check-in. To assist with this review, the TOC in the FSVeg Spatial database now contains new feature classes where editors can easily identify where new polygons were created, where shapes were edited, where locations were changed, where polygon ids were changed, and where attributes were edited. The review would also include verifying that all required data has been populated, the delineations meet standards, there are no topology errors, and that the GIS calcs, R2Calcs (and Old Growth Calcs if applicable) have been successfully run.

The ‘Spot Check’ tool is also useful for displaying the ‘before’ and ‘after’ values of edited fields. When running the R2Calcs, the software checks for the required information that is needed. If data is missing, an error message will be written in the field called CALCS_MESSAGE in the table. All errors must be corrected before the calcs can be successfully run and the data checked back in. It is very important for analysis that the master database always has the required information for every polygon.

Data Steward Role – Review and Check-In Requirements:

The Data Steward is responsible for the pre-Check-In review, and must ensure the data is complete and meets delineation and attributing standards. When performing the review and check-in using Citrix, with the FSVeg Spatial geodatabase located on the T: drive, you must login to Citrix, open ArcGIS in NRM Citrix, navigate to the folder created for the checkout, and open the .mxd originally created by the checkout. If you are reviewing and checking in using the PC client, you must have the editor zip the entire checkout folder package so you can copy to your C: drive and unzip. Once unzipped, you must navigate to and open the .mxd originally created by the checkout to review and check-in this data.

There have been many spatial tools developed to assist Data Stewards with tracking and locating changes made by the editor. In the TOC in the FSVeg Spatial database, stewards can now isolate where new polygons were created, where shapes were edited, where locations were changed, where poly ids were changed, and where attributes were edited. Data Stewards must also review the table for any errors in the CALCS_MESSAGE field. The ‘Spot Check’ tool is also useful for displaying the ‘before’ and ‘after’ values of edited fields to assist in your review.

Other checks should be made for completeness of the data. The topology should be validated and delineation should cover 100% of the area within the boundary of the administrative unit including private lands, with no gaps or overlaps. Private land or other administrative boundaries must not be used as delineators. Location boundaries may be modified if necessary since the objective is to delineate homogeneous polygons and not to have two adjacent polygons in different locations with identical attributes.

It is important to check to make sure that the basic vegetation attributes in the table were not accidently over-written using the gdb loader for summarized tree data from stand exam points. For each polygon, there must be at least one record in the table with the “R2_” grouping protocol. The basic vegetation data in the table with the “R2_” Group should always be loaded first, and the R2Calcs run on those vegetation records. The ‘R234 Summary’ Group can be populated from the stand exam point data (if there are ‘linked’ points associated with the polygon), and these records may be appended to the table afterwards.

(Note: If new point data was loaded, linked or edited during this checkout, you must first check-in the data to reconcile those changes, and then you can obtain another checkout to run the ‘R234 Summary’, append those records to the R2 Group records in the table, and then check back in again.)

Polygon Shape Updates The FSVeg Spatial tools are designed to split or merge polygons and to incorporate new polygon boundaries in the existing feature class. Updating the polygon feature class means deciding which lines to keep or replace and how to change the tabular data for the resulting polygons.

There are certain rules that pertain to the FSVeg Spatial geodatabase:

· Maintain existing delineation and attributing information

· Coincidence to water and riparian polygons must be maintained at the level initially implemented

· Tabular data is always checked/edited whenever a polygon shape is altered or a new polygon is created

· The minimum specified data fields are always maintained

Coincidence to locations does not have to be strictly maintained and there are tools to modify those boundaries when necessary. Location boundaries must not be disjoint. The intent of the location is to identify a contiguous group of polygons and the polygon numbers assigned are unique within the location. The concatenation of location and polygon id is unique across the Forest or Grassland. Refer to Exhibit 1 for generalized flowchart related to maintenance of FSVeg Spatial.

R2 FSVeg Spatial Maintenance Flowchart The following events may create a new polygon or update existing polygons. Significant vegetation changing activities that can be seen on a photo will require an update to the database.

Tornados, windstorms, and other events can result in FSVeg Spatial polygons needing updates.

Any recorded completed activity in FACTS or other systems that has an accurate spatial boundary may be used for FSVeg Spatial updates.

Delineating Vegetation Polygons

Overview This chapter describes the process for mapping existing vegetation (current as of the inventory or change date). Existing vegetation is what currently exists on a site as compared to potential natural vegetation (PNV) that exists when successional sequences are completed (climax). If successional sequences are complete on a particular site, potential and existing vegetation are the same. All of Region 2 has been mapped and there is 100% coverage of each Forest and Grassland in the FSVeg Spatial database. Region 2 is currently in the maintenance phase. In order to properly maintain the data it is important to understand the delineation rules used to initially create the layer. Many of the attributes were initially populated using photo interpretation but during the maintenance phase many of the polygon attributes are updated based on field collected data.

Existing vegetation is mapped and attributed in FSVeg Spatial as individual vegetation polygons. The Vegetation Unit layer is a map of existing vegetation data in a geographic information system. Individual polygons are generally homogeneous in dominant lifeform, species composition, percent crown cover, size, vertical and horizontal structure, and tree crown condition and occasionally other features indicative of vegetation change such as a major break in slope.

Steps for Developing the Existing Vegetation Polygon Layer The following list outlines the steps to follow in developing the vegetation unit map layer. It is not traditional to create the map first, and then attribute as a second step, but is much more efficient and consistent.

1. The first step is photo delineation of polygons. Existing maps, aerial photographs, and local knowledge of the area are combined in an effort to accurately delineate polygons representing uniform conditions with respect to existing lifeform, dominant species, crown cover, size, vertical and horizontal structure, and tree crown condition. If the available photo set does not have effective area delineated on it, this must be done prior to delineating polygons.

2. The polygons are transferred to a registered map base that is ready for scanning or transferred to registered Digital Ortho Quads using on screen digitizing (more recently polygons are digitized directly on screen using a NAIP image or resource image).

3. The maps are scanned, edited and a spatial layer is assembled; or in the case of on-screen digitizing, the spatial layer is assembled and edited. Additional integration with watersheds or other partitions is done in the GIS environment. When the final GIS map is complete, all polygons are numbered within locations or other partitions using an automated numbering system.

4. Once a final GIS map has been prepared and polygons have been identified, vegetation polygons are interpreted. Each polygon is attributed by one of more records of data describing lifeform or ground surface cover, species, layer, size, and cover percent. This information is entered into the corporate data base.

Vegetation Polygon Delineation Procedures Vegetation polygons depict existing vegetation covering a specified area in a specific period of time. The polygon is generally uniform in vegetation characteristics (delineation criteria) and is based on physical, observable, largely quantifiable, features and attributes. Some polygons may be void of vegetation but should still be homogeneous in terms of rock outcrops or other physical characteristics observable via stereoscopic interpretation. Non-vegetated polygons are identified by their ground surface cover (GSC) type. Some examples of non-vegetated polygons are rock slides, quarries, glaciers, and wide roads. Water polygons are also mapped. Where non-vegetated areas (all GSCs, including water areas) are less than the minimum practical mapping size, they are considered inclusions within the polygon and are assigned a cover percent. The initial delineation will delineate 100% of the area within the project boundary with polygons covered by vegetation, other ground surface cover types or water.

Delineation Standards The minimum standards are based on the scale of photography that is generally used for initial project planning and Forest Planning (1:24,000 scale or better). Minimum standards imply that differences within the criteria must be broken out at least to these standards. For example, it is not acceptable to not separately delineate a 5 acre tree polygon within the center of a 30 acre grass polygon. However, sometimes it is useful to delineate a polygon smaller than the minimum standard especially considering the new available digital image technology. Experience has demonstrated that a properly delineated diverse National Forest of about 2 million acres in size will be represented on the average by 50,000 existing vegetation/ground cover polygons at the 1:24000 scale. The minimum standards for delineating vegetation polygons are:

1. Polygons are generally homogeneous in lifeform, species, crown cover, size, vertical structure, and tree crown condition.

2. The minimum size for non-riparian vegetationpolygons is 5 acres and at least 160 feet wide (2 mm at 1:24,000). However, smaller polygons may be delineated as necessary to represent significant ecological communities.

3. The minimum size for a vegetation polygon created by a significant veg change activity such as harvest is generally 1 acre.

4. A 2 acre minimum and 80 foot width (1mm at 1:24,000) is applied to polygons with riparian vegetation along streams or wet areas. Any change in delineation standards that is equal to or larger than these minimum sizes determines when a separate polygon is delineated. Vegetation unit polygons that are designated as riparian (eg. riparian polygons) must have riparian vegetation species that contribute 50% or more of the total crown cover for the polygon. As technology improves smaller riparian polygons may be delineated.

5. A 1 acre minimum and 80 foot width (1mm at 1:24,000) is applied to water polygons. Water polygons have relatively permanent water cover, not marshes, and are to be delineated at the high water mark. Smaller that 1 acre polygon delineation may be specified as needed.

6. Existing vegetation polygons can generally be recognized on the ground.

7. Polygons, at a minimum, should logically close past the project boundary. The project boundary must be completely within the vegetation unit mapping area.

8. Political boundaries including forest boundaries are never used as delineation criteria.

9. Forested areas greater than 5 acres should be separated from non-forest areas.

10. Non-vegetative featuressuch as rock outcrops or scree fields, should be separated from vegetation areas if they are at least 5 acres.. In some cases it may be desirable to separate out even smaller areas.

Delineation Criteria Vegetation polygons are delineated based on identifiable changes in vegetation characteristics as seen on project imagery, generally 1:24,000 scale natural color aerial photos. With digital imagery, delineation is often performed at a scale as large as 1:5000.. Imagery is interpreted using tonal contrasts or colors, texture, and patterns and ideally stereo pairs are used. Polygon boundaries are drawn around homogenous vegetation areas and obvious changes in the vegetation compositions. Delineation criteria can be subtle, but most often are readily seen on a stereo view. Often stereo is not available with digital imagery, but other layers such as topographic layers may be used.. Occasionally, a major break in slope or other subtle factor can indicate a vegetation change dependent upon specific knowledge of the area.

The vegetation characteristics always used for delineation criteria are lifeform, species, size, percent plant cover, vertical structure, and tree crown condition. Contiguous areas of dead trees should also be delineated (refer to Crown Condition). For a particular polygon, each criterion may be the dominant condition, may be the only condition, or may occur more than once. A description of the delineation criteria in the order they are generally evaluated follows below.

Lifeform This is the growth habit of the vegetation according to shape and structure (usually Family). The lifeforms used are trees, shrubs, forbs, and grasses. For the purposes of the existing vegetation inventory, grasses include members of the family Poaceae (Gramineae) as well as other grass-like plants. Grass-like plants are members of the Cyperaceae (sedge) and Juncaceae (rush) families that vegetatively resemble a true grass of the Gramineae family. Within this User Guide, when the term ‘grass’ is used, it also refers to these grass-like plants. Vegetation of similar lifeforms are delineated as a group. For example, an area with a mixture of treeland and shrubland would generally be delineated into separate polygons if each group meets the minimum polygon size criteria and the two lifeforms were not well integrated. Areas not covered by vegetation are delineated based on their ground surface cover.

Species Distinct changes in species composition require further delineation. Species determination is optional for shrubs, forbs, and grasses since species identification for these lifeforms are difficult to determine from aerial photos. However, additional information and field calibration can be used to determine species, especially for shrub species. Trees and common and abundant shrubs with a taller growth form should be identified by species.

Size Changes in vegetation size require delineating a new polygon for tree and shrub lifeforms. The size classes for trees are established (seedling), small, medium, large, and very large, based on diameter of the stem at breast height. The size classes for shrubs are small, medium, and large, based on height. The size of shrubs is often difficult to observe from aerial photos; therefore, the size of shrubs must be obvious to be used as a delineation factor.

Plant Cover Significant, easily observable differences in plant cover require additional polygon delineation. Generally, this is about a 20 percent difference. Delineations are based on groupings of similar plant cover patterns or density patterns.

Vertical Structure This is the layering of vegetation occurring in tree and shrub lifeforms. Where both lifeforms exist, layering is considered separately. A layer should generally have 10 percent or more plant cover within a horizontal component in order to be recognized. Layering is difficult to see on aerial photographs for grass and forb lifeforms and is not a delineator for those lifeforms.

Crown Condition (Trees) For tree stands, tree crown condition is a delineator for tree lifeforms and may be an indicator of stand maturity. It consists of four classes describing the presence or absence of declining crowns or standing dead trees. Declining crowns are those that have dead or dying, flattened, or unusually large branched tops. In some tree species these conditions are easily recognized, but in others, they are more obscure, so this factor is used when the condition is very obvious. To delineate a separate polygon, at least 5 acres of mostly contiguous trees in the polygon must be affected. Scattered dead trees among the live trees in a homogeneous pattern would not require a new polygon to be delineated.

Quality Control The purpose of quality control is to maintain consistent and accurate polygon delineations that are as homogeneous as practical. These are some steps used to insure quality in the photo delineation:

Photo interpreters are expected to be adequately trained, experienced with photos and photo interpretation procedures with specific on the ground knowledge of the vegetation communities in the area that will be delineated.

An initial field overview shall be done as each interpreter encounters new vegetation characteristics or areas. Interpreters visit the area to visually recognize delineation criteria as it appears on the photo.

Photo interpreters shall work closely together and review each other’s polygon delineations to calibrate to each other. Prior to completion of each quad map, delineations are reviewed by the project leader. Areas where interpreters disagree are re-delineated or settled by consensus.

Attributing Vegetation Polygons

The Existing Vegetation Polygon Data field form and corresponding instructions specify how to attribute FSVeg Spatial polygons either in the field or in the office.* There are two general sources for vegetation attributes:

1) Photo Interpretation in the Office or some other sort of remote sensing

2) Field Collected/Verified Data

*Additional data not shown on the field form can be collected. Refer to Appendix B – Optional Data.

Photo Interpreted Data When attributing data from remote sensing imagery in the office, only the total crown cover percent of what you can see needs to be accounted for. The “CROWN” cover method is always used for remote sensing attributing and your total cover % for all vegetation in the polygon must not exceed 100. When attributing using remote sensing you cannot see under the top layer of vegetation unless the vegetation is sparse in the top layer. What you can record using remote sensing interpretation is limited to what you can see on the imagery.

Field Collected/Verified Data When collecting Field Data and using the “CROWN” species survey method, cover percent should add up to 100% for the polygon. The polygon survey is not intended to collect the same level of detail as you would with a point survey (such as a range cover/frequency or Common Stand Exam intensive tree data plot), but will describe the general vegetation composition of the polygon. Code all of the tree species and the major shrub species. The dominant forb or grass species will be coded depending on the need and the standard data set for the Forest. Any indicator species used to identify cover type or habitat type should also be coded. For “CROWN” species survey methods, not all of the cover for grass and forbs has to be identified by species, but can just be identified to the lifeform.

Using the “CROWN” method, field observers would ignore and NOT record any trees, shrubs, forbs, grass, water, rocks, or other features obscured by the main canopy from above. Using the “CROWN” method, all attributes are recorded as viewed from one plane looking down, and must not exceed 100%, and therefore can have NO OVERLAP. The “CROWN” method is primarily used for remote sensing of vegetation attributes, but may also be used for walk through field verifications. However, note that when using this method for field verification, field observers should not record any understory vegetation obscured by overhead canopy layers.

*When using the “CROWN” Species Survey Method the following rules apply:

1) The sum of plant cover percents (crown) for all Lifeforms and layers must be equal to the total cover percent for the entire polygon, which must equal 100%.

2) The sum of plant cover percents (crown) for all layers may NOT exceed 100% for the entire polygon.

3) Vegetation layers are recorded by subtracting overlap from overhead canopies. Understory vegetation obscured by overhead vegetation canopies is NOT recorded.

4) The ‘CANOPY CLOSURE TREES’ field is not applicable.

5) When DEAD PERCENT is recorded,the total live tree cover percent plus the total tree dead percent must not exceed 100.

When collecting Field Data and using the “CANOPY” species survey method, (often the preferred method for field surveys), each LAYER of vegetation could have up to 100% cover, so the total cover percent of vegetation for the entire polygon may exceed 100% if you have overlapping canopy layers. Some of the local R2 Calcs require knowing the horizontal plane CROWN cover of trees, so when using the “CANOPY” survey method, the ‘CANOPY CLOSURE TREES’ field must be estimated and filled in by viewing the aerial photograph or other remote sensing imagery and recording the CROWN cover of all the trees on one horizontal plane as viewed from above.

*When using the “CANOPY” Species Survey Method the following rules apply:

1) The maximum cover percent (canopy) for any given layer must be less than or equal to the total cover percent for the entire polygon.

2) The maximum cover percent (canopy) for any given layer cannot exceed 100%.

3) The sum of cover percents (canopy) for all layers must be equal to or greater than the cover percent for the entire polygon.

4) The sum of cover percents (canopy) for all layers may exceed 100% for the entire polygon.

5) The ‘CANOPY CLOSURE TREES’ field must be equal to or greater than the sum of tree cover percents for the layer with the largest cover percent. When ‘equal to’ the layer with the largest cover percent, this would assume that ALL other tree layers totally overlap with the layer that has the largest cover percent.

6) The ‘CANOPY CLOSURE TREES’ field must be equal to or less than the total sum of tree cover percents in ALL layers. When ‘equal to’ the total sum of ALL tree cover percents in ALL layers, this would assume that there is NO overlap between any of the tree layer canopies.

The ‘R2 FSVEG SPATIAL POLYGON VEGETATION ATTRIBUTES FORM’ is used to record the general vegetation composition for each polygon.

Record the following information for each polygon: (*required)

Data located in NRIS_VegPoly table

CROWN = Non overlapping crowns – total adds to 100% CANOPY = Overlapping crowns from different layers (see detailed descriptions and rules above)

The following are valid codes for R2 and are checked by the R2 data entry programs. Bold lettering represents current recommended codes. Other codes are legacy codes that are no longer in use, but may be present in existing data.

CS Strata Mean Est from Location Inventory (R2 Veg Update using modeling with field data) CV Cover Vegetation (R2 Veg data associated with FSVeg Points for Veg Cover) GL On ground sampling with low or uncalculated statistical reliability (R2 Tools 3 and 4) LI Lidar (Use when creating R2 vegetation data using Lidar imagery) PR Photo inventory (R2 Veg Survey Photo Interpretation) SI Satellite Imagery (Landsat derived vegetation data) WV Walk-through survey or visual observation (R2 Veg Field Survey)

ID Insect and Disease(R2 vegetation data is associated with an I&D survey) IM Inventory and Monitoring (R2 vegetation data is associated with IM) OF Office Update (Updating R2 vegetation data in the office – Used for Missionary Ridge) PF Fire Update (R2 Veg Survey or Update after a fire) PH Post harvest update (R2 Veg Survey updated due to harvesting) PI Plantation inventory (R2 Veg Survey associated with a plantation inventory) PT Photo estimate unsupported by field examination QS Quick plot stand exam (R2 Vegetation survey associated with a quick plot stand exam) RA Riparian Area Survey RE Regeneration/Stocking (R2 Vegetation survey associated with a regeneration exam) RL Range Inventory: Qualitative (Range Inventory Data Interpreted as R2 Veg Data) RN Range Inventory: Quantitative (Range Inventory Data Interpreted as R2 Veg Data) RP Resource Specialty (R2 Vegetation Survey in association with special resource survey) SE Stand Exam (R2 Vegetation survey associated with a standard stand exam) TH Thinning Exam (R2 Vegetation survey associated with a thinning exam) WA Walk-through WT Walk-through with update (Minor corrections to existing R2 Veg Exam)

NOTE: This is NOT the same as the Purpose Code for point data collected using the Common Stand Exam (CSE) data collection protocols – this code is for describing HOW the attributes in the table were derived.

Data located in NRIS_VegCharacterizations table

Y (Yes) A stocking survey has been completed and the regenerating stand meets the regional stocking standards. If the crown cover is less than 25%, the calculated dominant lifeform field (DLF_GSC) will be set to T (Tree) and Cover Type will be set to the Regen EV Code that has been entered. Trees entered in the sub populations table will be ignored.

F (Forested) For established stands with low tree stocking due to harvest or fire (greater than or equal to 10% tree crown cover and less than 25% tree crown cover) the STOCKING_FLAG may be entered as F (for forested). If the STOCKING_FLAG = F, and the Change Category code indicates harvest or fire, the calculated dominant lifeform field (DLF_GSC) will be set to T (Tree) and Cover Type will be based on the trees entered in the sub populations table. The Regen EV Code field will be ignored. These are usually mature stands managed as forested with no planned reforestation activities, and are expected to be well delineated with trees distributed throughout the stand.

* Refer to Appendix A for further information on using code F.

If the polygon does not currently have a total of 25% crown cover of trees, but was previously tree cover and is currently not stocked due to a recent harvest or burns, enter the expected regenerating cover type or the previous cover type:

TAA – Aspen TBS – Blue Spruce TBS – Bristlecone Pine TBO – Bur Oak TCW -- Cottonwood TDF – Douglas-fir TER – Eastern Red Cedar TAE – Green Ash TJP – Jack Pine TLP – Lodgepole Pine TLI – Limber Pine TPB – Paper Birch TPJ – Pinyon/Juniper TPP – Ponderosa Pine TRJ – Rocky Mountain Juniper TSC – Salt Cedar TSP – Scotch Pine TSF – Spruce and Fir TWP – Southwestern White Pine TWF – White Fir TWB – Whitebark Pine TWS – White spruce

Vegetation information is attributed to a site based on a delineated polygon which is homogeneous as possible given the size constraints of 1:24000 remotely sensed imagery. Some polygons represent natural mosiacs consisting of patchy polygons. If the patches make up at least 20 percent of the polygon, then the polygon is considered to be patchy and not continuous.

Continuous The continuous polygon has vegetation or other cover that is uniformly or consistently distributed throughout. An example of a continuous (C) polygon composed of two tree species, such as spruce and fir as shown in the figure on the left below. Both species are evenly distributed throughout the stand.

Patchy A patchy polygon has vegetation that is discontinuous throughout the stand, occurring in clumps that may or may not vary in size. The figure on the right below shows a polygon with lodgepole pine continuously distributed throughout the stand and containing patches of aspen. For the polygon to be coded as patchy, at least 20 percent of the area must be in patches. Patchiness may sometimes be linear such as a power line too small to delineate that goes across the polygon.

A – Signs of declining crowns are absent P – Signs of declining crowns or scattered dead trees present in 5-15% of trees D – Dead or declining crowns present in 16-50% of trees S – Significant amount of dead or declining crowns present (over 50%)

Canopy Closure TREES (*required when Species Survey Method is CANOPY) Used for the CANOPY survey method only. Record the total crown cover of LIVE trees within the polygon on one plane as viewed from above, with no overlap since “closure”. Codes 1-100. Refer to Appendix A for a useful chart to help with coding this field.

Habitat Structural Stage (field interpreted/observed)

(NOT recommended for field interpretation in R2, as this item will be populated with the R2Calcs using the field collected vegetation composition data in the table) Record the habitat structural stage as observed in the Field:

1M Grass-Forb, natural meadow 1T Grass-Forb, previously trees 2S Shrub-Seedling, natural shrubland 2T Shrub-Seedling, previously trees 3A Sapling-Pole, Crown cover percent < 40% crown cover 3B Sapling-Pole, Crown cover percent >= 40 and < 70% corwn cover 3C Sapling-Pole, Crown cover percent >= 70% crown cover 4A Mature and Over Mature, Crown cover percent < 40% cover 4B Mature and Over Mature, Crown cover percent >= 40 and < 70% cover 4C Mature and Over Mature, Crown cover percent >= 70% cover 5 Old Growth, Forest Criteria and Documentation usually determined by a scoring system (Note that Region 2 decided to separate old growth from HSS in 1994 but some forests still use the “5” code)

Data located in NRIS_VegPolyLocal table

N – No Major Disturbance H – Harvest H11 – Clearcut H12 – Prep. Cut H13 – Seed Cut H14 – Removal Cut H15 – Selection Cut H22 – Commercial Thinning H23 – Sanitation T – Thinning T51 – Release and Weeding T52 – Precommercial Thinning F – Fire FR – Fuels Reduction W – Wind I – Insect and Disease O – Other

Data located in NRIS_VegSubpopulations table

the dominant lifeform or ground surface cover, using one of the codes listed. Use those lifeform codes for vegetation life-forms and non-vegetated ground surface cover types. For non-vegetated ground surface types, record the ground surface cover to the level that can be accurately interpreted.

T Trees are woody plants possessing at maturity a well-developed stem, are generally at least 3 inches in diameter at DBH or DRC, have a definite formed crown of foliage, and are generally a height of at least 16 feet.

S Shrubs are plants with persistent woody stems, a relatively low growth habit, and generally produce several basal shoots instead of a single well developed stem. Shrubs also differ from trees by their low stature and non-arborescent form, and are usually less than 16 feet tall at maturity.

G Grasses. Members of the family Poaceae (Gramineae), or other grass-like plants such as Cyperaceae (sedge) or Juncaceae (rush).

F Forbs. Herbaceous plants other than those in the Poaceae (grass), Cyperaceae (sedge), or Juncaceae (rush) families.

W Water B Barren areas with unknown composition, lacks vegetation BS Bare soil RS Rock and soil, soil with significant surface rock (not distinguishable from one another on photo) RO Rock, all sizes LD Litter/duff WO Wood IC Permanent ice/snow LI Lichen AL Algae CA Cactus FG Fungus VI Vine MO Moss (The individual Lifeform/GSC and Layer codes are combined as Group codes for FSVeg Spatial. See list of Group Codes below.)

0 Unknown (SHRUBS ONLY) 1 Top layer 2 Middle layer 3 Bottom layer

located at National Plants Database (Natural Resources Conservation Service official National Plants codes). http://plants.usda.gov/java/ For trees and shrubs, all species must be accurately identified on the data sheet. If species is unknown, identify to genus, using the proper NRCS genus codes. Grass and forb species are not required to be identified separately, but may be grouped collectively or classified to the genus. If grouping, the field observer should include all grasses which occur into one data entry coded by lifeform (G) and all forbs into a separate line entry coded by lifeform (F).

E - Established seedlings. Mostly comprised of trees 0.0 - 0.9 “ dbh S - Small. Trees 1.0 - 4.9” dbh M - Medium. Trees are 5.0 - 8.9” dbh L – Large. Trees are 9.0-15.9” dbh V - Very Large. Trees are 16.0”+ dbh

Woodland species are measured at the root collar (DRC).

S = Small shrubs less than 2.5 feet tall M = Medium shrubs 2.5 – 6.4 feet tall L = Large shrubs greater than 6.4 feet tall U = Unknown

Lifeform/Ground Surface Cover and Layer are combined into the following Groups:

F

R2 FORB/HERB

G

R2 GRASS/GRASS-LIKE

B

R2 BARE

W

R2 WATER

BS

R2 BARE SOIL

RS

R2 ROCK/SOIL

LD

R2 LITTER/DUFF

WO

R2 DOWN WOOD

IC

R2 PERM ICE/SNOW

LI

R2 LICHEN

AL

R2 ALGAE

CA

R2 CACTUS

FG

R2 FUNGUS

VI

R2 VINE

MO

R2 MOSS

Filling out the R2 FSVEG SPATIAL POLYGON VEGETATION ATTRIBUTES FORM is not difficult. Most people are used to photo interpreting cover type, size class and density and it does not have to be any harder than that.

For example a pine/oak stand might have the following composition using the “CROWN” Species Survey Method:

Subpopulations Table Attributes

Lifeform/

GSC

Layer Species Symbol

G

RS

Required elements for different lifeforms: r = required; o = optional

r

The following table lists several examples of interpreting these items using the form. The examples are presented in their most simplistic form.

Sample Photo Interpretation Shortcut Data to Enter for species composition records in the table Sample Poly

CLASS

COVER %

T

PIPOS

PIPOS

V S

S

PIPOS

QUGA

V U

T

PIEN

ABLA

V V

T

PIEN

POTR5

L M

Entering and Loading R2 Polygon Data Using Program VEGCOV

VEGCOV replaces the previous PIVEG data entry program. The VEGCOV program and files are NOT compatible with old data files created by PIVEG. VEGCOV supplements the standard FSVeg Spatial data entry capabilities for R2 by providing a stand alone tool that can be used with a PC or field data recorder. The program does not require a US Forest Service image which allows for off-site data entry by Contractors.