EOTW G-Z LTIRSC LiDAR Process

End of the World G-Z Volume Estimation Process
Raymond Craig, Forester – Nez Perce Clearwater National Forest Volume Estimates Based on Individual Lidar Derived Trees Provided by Eyler White. Trees from 2015 Lidar and 2019 Lidar were kept as separate feature classes to prevent incorrect growth being applied.
Using Jungle Bird Cruise Data from 2020 Compared to Cruise data from same plots in 2025. The trees on each plot where then compared and any trees that grew into plot or died where removed along with extreme outliers (trees that had a negative growth or grew at a rate of 1”+ per year) were removed from the analysis. The avg growth was then calculated on the remaining trees and found to be 0.537770898 inches dbh and 5.682656827 feet height from 2020 to 2025. Tree growth of .11” / year dbh growth (rounded value) and 1.1’ / year height growth (rounded value). any height or bdh that had an end measure less than the start measure are not included.
The Lidar identified trees were grown at the above per year rate from 2015 or 2019 based on Lidar collection date to 2026 year of planned contract award. This equates to a total of 1.21” of dbh growth and 12.1’ of height growth for 2015 and .77” of dbh growth and 7.7’ of height growth for 2019. These adjusted dbhs and heights were used to estimate the project volume.
When comparing the Jungle Bird units cruised cut volume with the Lidar derived volume for those same units it was determined that the Lidar derived total volume was approximately the same. So, for all other project areas it was assumed that the Lidar derived volume would be the cut volume for those units.
Individual Lidar trees volume was estimated using ((dbh^2)*ht)/100 Using select by location each individual tree point was then assigned to the appropriate project area.
The individual tree volumes were then summed by project area and logging system. See below for Logging System determinations.
Logging Systems Determination

R01_NCF_ELEVATION_LIDAR was converted to integer type = LoggingBreaks_FromRaster LoggingBreaks_FromRaster Converted to polygons = RasterTo_LoggingPoly1 The grid code field in RasterTo_Poly1 was then used to determine ground-based vs skyline where ground based is all values < 36 and skyline is all values >=36 this polygon was then dissolved bases on the ground-based and skyline categories to create EOTW_EstimatedLoggingSystem and then clipped by the End of the World NEPA polygons. To create EstimatedLoggingSystems_EOTW_NEPA_Units polygon and changed from multi