Attachment 7 - Exhibit E - Plot Edit Sheet.pdf

Plot: Crew: Date:

Coastal Alaska Inventory Page 1 of 5

2026 Coastal Alaska Plot Edit Sheet

Plot Card Plot Card: filled out following guidelines in Appendix O, Completing a Plot. ☐ Header: fill out with crew names (First Initial, Last Name) and verify they match Plot Data printout. Name under Crew 1 on the printout should match name under Crew Leader on the Plot Card. Plot number written on front (back if needed) of the plot card.

Plot Travel Time: actual hike time LZ to PC and PC to LZ. ☐

Time on Plot: actual time on plot. Equals the time listed on the printout divided by the number of people on plot. ☐ Plot Diagram: For remeasurement plots, a plot diagram is only required if there has been a significant change since the last visit, if the previous sketch map is of poor quality, or if a cover check was completed. When a sketch map is required, condition classes, including Boundaries, Condition Status, Forest Type, and Stand Size Class, are clearly drawn and labeled. Notable features of plot area that may aid future crews in plot relocation are drawn on location sketch map.

Location Map: For remeasurement plots, a travel map is only required if the crew uses a different LZ or travel route than the previous visit, or if the previous travel map is of poor quality. When required, map must include PC, and LZ, and should indicate the route of travel and any landmarks or barriers.

Plot Card Scan (if applicable): Is high quality and easily legible. ☐

Plot Folder & Plot Data Print Out

Check all errors and warnings: Plots should have no errors when submitted for QA. All warnings should be carefully checked, and data updated as necessary. For warnings where no data needs to be updated, those with a [W] should be checked off while those with a [C] should have a clear explanation entered. All explanations must be checked against the data record in question and verified for accuracy.

When Edited: Make all necessary changes in MIDAS Mobile on the laptop and reprint the plot data PDF using MIDAS Control Panel. ☐

Before QA Review: Ensure plot edit sheet is complete and all items on the plot folder checklist have been filled out. Plot card has been scanned, and Javad files have been named and uploaded to the appropriate location. For FS Employees: Plot Data and Plot Card pdf files are placed in a folder named CTY.PLOT#.LASTNAME in QA folder on Box, along with notes about any errors that cannot be resolved.

After QA review: If necessary, plot is unpackaged and all required changes are made. If edits to the plot card are made, plot card is rescanned or re-saved in the correct location. Plot is uploaded on MIDAS Web. If there are bugs preventing plot upload, this is communicated to a QA.

Plot Data Crew Type (CREWT): Forest Service Crew=1, Contractor = 3; unless QA staff is present, then will = 2 ☐ Transportation to Plot (TRANS): generally, will = 1, unless accessed by road or boat. ☐ Date: the day when the plot was completed in the field, matching the End Date on the plot card. ☐ Time To-On-From Plot (TTP TOP TFP): different from plot card. Actual time to/from base of ops to PC. Time on plot = total person hours on plot. ☐

Topo Position (TOPO): verify based on local topography on plot, use topo map to help if plot falls within a broad topographic position (i.e. midpoint of a large, continuous mountain slope). ☐

Distance to Improved Road (RDIS): use photos, topo maps, and actual visual from heli to identify ☐ Water on Plot (WAT): Record the water source that has the greatest impact on the area within the accessible forest/nonforest land portion of any of the four subplots. ☐

Plot Access Description: Filled out according to guidelines in the manual. Written directions and description of landing zone/parking spot, travel route, and plot location are complete & accurate. ☐

Coastal Alaska Inventory Page 2 of 5

Plot Narrative: Filled out according to guidelines in the manual and is consistent with the plot data. Anything that is unusual about the plot that may not be evident in the data is described. ☐

Site Tree Data Site Index (SINDX): value will be auto populated based on age and height. Value range cannot be >30 for site trees collected for a single condition class. ☐

Questionable Site Tree Flag (QUES): unless tree is a "Last Resort' tree, QUES flag should be 1. Usually, 3 QUES=1 site trees are collected, yet collection of two or one is acceptable where 3 suitable trees are unavailable. A single QUES=0 (Last Resort) tree will be collected PER CONDITION when no suitable site trees are available.

If a site tree is collected as a ‘LAST RESORT’, there are no additional site trees collected for that condition class.

Regular and questionable trees w/in a single condition should not be mixed. Last resort site tree must have QUES flag = 0 with a SITE TREE NOTE explaining why (e.g. tree is >250 years old, tree age extrapolated, or tree has damages that do not affect height growth). Also need a plot note describing why the area is a last resort site.

Site Tree Notes: only pertain to that particular site tree record. Do not include notes about site trees pertaining to the entire plot or a condition class. Those types of notes should be recorded in PLOT NOTES. ☐

When there are no site trees recorded for a condition make sure there is a PLOT NOTE (in Plot Data screen) with a description of the site’s general topography, moisture regime, substrate material, and general tree growth.

General descriptors like "boggy black spruce area" or "shallow rocky soil" or "cold alpine area" are helpful. This note should be brief yet provide the necessary information to enable analysts assign a site class to the condition.

When a complete set of site trees cannot be collected for a condition make sure there is a PLOT NOTE describing the reason why a complete set was not available. ☐

Age Trees - If any age trees are used that are outside the stand size class provide an explanation in AGE TREE NOTES. If less than 3 age trees are collected for the condition provide an explanation in PLOT NOTES. ☐

Condition Class Data Reserved Status (RESV): Is the plot in a wilderness area or other restricted category? Check the RESV for each condition class. A list of current Reserved areas in Coastal AK is in Appendix G. ☐

Owner Group (OWNG) & Owner Class (OWNCD): do these correspond and match the plot folder or other owner data included in the folder? Ask field supervisor for correct info if in question. ☐

Forest Type (FTYP): Based on plurality of stocking for overstory trees. On a remeasurement plot, when live regeneration is not yet present after disturbance (stand is nonstocked), pre-disturbance Forest Type should be recorded.

Stand Size (STSZ): based on plurality of cover for non-overtopped (overstory) trees. Nonstocked conditions (i.e., burned, clearcut, or otherwise disturbed stands with <10% live cover but >=10% live plus missing cover) are considered forested w/ STSZ = 0

Stand Age (SAGE): For new plots: based on average of all age trees collected with appropriate number of years added for the species. For remeasure plots: stand age calculation based on current age trees should be checked against [previous stand age + years since last inventory]. If current stand age calculation differs by less than 10% from this value, use [previous stand age + time since inventory] with age basis code 40.

Physiographic Class (PHYS): Review previous crew's code and retain if reasonable. CONDITION CLASS NOTES are included if one of the "other" categories is used. ☐

Fuel Model: Coded based on keys/descriptions in "Fuel Model Guide to Alaska Vegetation." ☐

Disturbance and Treatment: Verify disturbance and treatment dates with observations on the ground, discussions with landowners, from GIS layers (i.e. fire maps) or other sources. NOT connected to Area of Observation. ☐

Cover Class: If greater than 10% live tree cover and live tree cover is taller than other classes = 1. Otherwise, use key in manual to assign cover class based on hierarchy. ☐

Coastal Alaska Inventory Page 3 of 5

Live and Live Plus Missing Canopy Cover (LCCV and LMCC): Represents the canopy cover in the condition, including inclusions (p. 131 & 134-135) Values should be different if there has been a recent (past 30 years) net reduction in canopy cover (due to fire, insects, cutting, etc.). The reduction in canopy cover does not need to qualify as a disturbance or treatment to be recorded. If LCCV ≠ LMCC, there is a CONDITION CLASS NOTE explaining the situation, unless a Disturbance or Treatment is recorded.

If FOREST TYPE, STAND SIZE CLASS, REGENERATION STATUS, or TREE DENSITY data items are different than the previous data due to previous crew error or not otherwise explained in the data, make sure there is a CONDITION CLASS NOTE explaining if the change is real change or previous crew error.

PREVIOUS PLOT MAPPING OR CONDITION ERROR: This data item is the code MAPER (Plot Level Data). It acts as a trigger variable allowing entry into the previous condition data screen to make updates. There is also a MAPER code within each subplot acting as a trigger variable to allow updates to previous data at the subplot and boundary level. Refer to the MAPER TABLE in Appendix O for descriptions of common situations of when to code MAPER Y or N and how to code Condition, Subplot and Boundary Data, and Notes for these scenarios.

Map Error and Change Matrix

If PREVIOUS CONDITION CLASS STATUS, PREVIOUS RESERVED STATUS, or PREVIOUS OWNER GROUP are changed to correct an error:

a. Plot MAPER should be Y (yes) ☐

b. Verify there is a detailed note in that previous condition record explaining the situation. ☐

c. If the previous condition was deleted to correct an error, make the explanation in PLOT NOTES. ☐

d. It is critical the note describes what the error was. ☐

e. Do not just note ‘previous crew was wrong’.

Cross check FOREST TYPE, STAND SIZE, REGENERATION STATUS, and TREE DENSITY with the previous data.

1. Plot MAPER should be N when there is any change to these data items regardless if it is due to previous crew error, real change or procedural change.

2. If any have changed since the previous inventory, make sure there is an explanation in the notes field for that condition record, if not obviously explained in the data (i.e. if stand size went from 3 to 0, there should be a treatment or disturbance coded that would explain the change and therefore a note is not necessary).

Subplot Data Subplot Center Condition (SCent) and Microplot Center Condition (MCent): Correspond with the actual condition classes at subplot and microplot center. ☐

Snow & Water Depth (SWD): This item is intended for temporary snow or water which covers substantial portions of subplots and affects plot measurements. Record “00” for streams and water in ponds/muskeg holes contained within their banks and not affecting any measurements. Otherwise, the recorded number should be the average of the approximate depth covering the 24.0 ft radius.

Unlisted Tree Present: if live stems >=5.0 inches DBH resembling trees in shape or form of the species that are not on the Master Tree Species List, or are on the Master Tree Species List but are excluded due to an exclusion list, are rooted within the subplot boundary = 1; if none such stems are present = 0.

Boundary Data Check for accuracy: that printed boundary map, drawing on plot card and description in plot write-up match and make sense. ☐

If boundary mapping has changed less than 10% since the previous inventory, previous and current boundary mapping are unchanged, unless one of the following situations occurs:

If there has been a clear physical change in a boundary since the previous inventory, current BOUNDARY MAPPING is updated regardless of the change in % mapped area on the subplot, with BOUNDARY CHANGE 1 recorded.

Coastal Alaska Inventory Page 4 of 5

If there has been a boundary change since the previous inventory resulting in a 10% change in mapped area, or a change in presence/absence of a condition on a subplot, and it is not a result of previous crew error in CONDITION CLASS STATUS, RESREVE STATUS, or OWNER GROUP, current BOUNDARY DATA is updated to reflect this change, with the appropriate BOUNDARY CHANGE recorded.

If there has been a boundary change since the previous inventory resulting in a 10% change in mapped area, or a change in presence/absence of a condition on a subplot, and the change is due to a previous crew error in CONDITION CLASS STATUS, RESERVE STATUS, or OWNER GROUP, Subplot MAPER = Y and current and previous boundary data is updated to reflect the correct mapping.

DATA EDITS: Unlisted Trees

Verify: make sure Genus and Species codes are selected from drop-down list or typed correctly. ☐ Verify: make sure that stem counts seem reasonable. ☐

DATA EDITS: Seedling Data Verify: that counts seem reasonable and seedling species are similar to tree species comprising the plot area. ☐

P2 Veg Species Data If multiple Condition Classes exist on the subplot make sure veg data record is broken by condition and recorded in the electronic files correctly ☐

Non-Tally Trees (Single stemmed shrubs in tree form): if present, recorded as SD or LT growth form. If both shrub and nontally growth forms of a species are present on a single subplot, assign the entire cover for the species on that subplot to the dominant growth form present.

Check unknown and genus only codes. Make sure all plants have been identified to the species level if possible.

Unknown or generic species codes (grasses) have a note describing the plant characteristics to allow differentiation from other species on plot. Remove any other unnecessary notes.

Specimen Officially Collected (COLL) : only code 1 = YES if the specimen is to be pressed and vouchered for submission for official ID. If specimen is "collected" for immediate ID at the field office COLL = 0 (NO), and a Not Collected Reason = 06 (collected for immediate ID). Make sure to update collected and veg id codes once specimen is ID'd at the end of the day. If unable to ID, label in plant press with a specimen label number.

P2 Veg Structure Data

Check that recorded values correlate reasonably with species cover estimates. ☐

Non-Tally Trees (Single stemmed shrubs in tree form): if present, recorded as nontally growth form. If a shrub species presents as both nontally and shrub growth form on a single subplot, the same species is not placed in multiple Structure Growth Habits on the same subplot/condition.

Invasive Species Data Verify: Recorded if found on any of the subplots regardless of percent cover. ☐

Tree Data Condition Class Number (CON#): assigned to each tree matches the actual condition the tree belongs in.

Sometimes boundaries are adjusted to represent the actual area due to mapping limitations in the MIDAS program. Use the boundary viewer printout or use the boundary view option in the boundary screen in MIDAS along with the drawing on the plot card to aid in verification

Reconcile: Verify all codes are correct. Saplings that grew into the microplot since last inventory then died get RECONCILE = 1. If in doubt refer to the Tree Coding Guide in Appendix E. ☐

Slope Distance to Witness (SDIST): check if it is logical compared to Horizontal Distance. If witness is a tally sapling, two records will be entered, one for tally sap with HD and AZIMUTH from microplot center, and another one for non-tally witness with SD and AZIMUTH taken from subplot center.

Coastal Alaska Inventory Page 5 of 5

Diameter Check (DCHE): If a previous diameter is moved, or determined to be incorrect at the previous visit, DIAMETER CHECK CODE is 2, a TREE NOTE is recorded explaining the situation and PREVIOUS DIAMETER is updated if appropriate. If multiple DIAMETER CHECK CODEs exist, code 2 takes precedence and other codes should be described in the TREE NOTE.

Damage Codes (DAM 1 2 3): check for unusual codes. GENERAL CODES should have a note. Is ROTTEN/MISSING CULL or ROUGH CULL appropriately recorded based on damage codes? ☐

Rough Cull: Small trees (5-9 inches for softwoods and 5-11 inches for red alder) that have poor form and are not expected to ever produce merchantable material should be coded 99 percent rough cull, or the remainder of the bole after ROTTEN/MISSING CULL deductions have been recorded.

Cause of Death: Code 70 is used only if absolutely necessary. Make your best educated guess. If COD 70 must be used, make sure there is a detailed TREE NOTE describing the situation. ☐

Tree Notes: Are all tree notes consistent with the recorded tree data? Do any tree notes allude to an error in the recorded tree data? Are there any typos in the tree notes? Are any notes ambiguous or unclear to someone that is not on plot?

Warnings: Carefully check all tree warnings and make sure that all appropriate changes have been made. Most common errors with tree data will come up during the error/warning check. ☐

DATA EDITS: Downed Woody Materials DWM Transect Line Segmenting: If condition breaks exist, are they realistic compared to the Boundary Mapping Data? If not, include notes explaining why. ☐

When multiple conditions exist on a transect, verify CWD CONDITION CLASS (code COND) for each piece of CWD is assigned to the correct condition on the ground. Use Boundary Mapping Data as a guide. ☐

CWD species: Confirm CWD species correspond with species in current (or pre-disturbance) stand. ☐ Verify: CWD diameters make sense for what was found on plot and that diameters have not been accidentally entered as inches/10ths. ☐

CWD History (HISTC): 1 = natural causes. 2-5 = other. ☐

SUBSECTION for ENTIRELY NONFOREST PLOTS: Complete the following additional edits when a plot is coded as PLOT STATUS = 2

Plot Status (PLSTA): = 2 ☐ Plot Narrative: If plot was flown over or ground visited, include a description of the predominant vegetation cover and topography present. Indicate whether you think the plot will convert to forest land in the future. ☐

Review FOREST LAND CONDITION STATUS CHANGE code (code FLCSC) for accuracy. ☐ Verify recorded COVER CLASS (code CC) is consistent with recorded LIVE CANOPY COVER (code LCCV). ☐

SUBSECTION for NONSAMPLED PLOTS WITH POSSIBILITY OF FOREST LAND: Complete the following additional edits when a plot is coded as PLOT STATUS = 3

Sample Method Code (METH): Unless the plot was field visited or viewed from a distance (flyover) it will most often = 3 (photo interpretation) because aerial photos and digital imagery are used to assess the forest land call in addition to previous inventory data.

If SAMPLE METHOD CODE = 4 (Other), make sure there is a PLOT NOTE describing what was used to make the condition call. ☐

When SAMPLE KIND = 2, CONDITION STATUS RECONCILE CODE = 1 (real change) for each subplot (Change Matrix code CDSTR) with a detailed note describing the situation.

Verify: recorded COVER CLASS (code CC) is consistent with recorded LIVE CANOPY COVER (code LCCV). ☐