Draft LiDAR StrategyDraft LiDAR StrategyPacific Northwest Region

Regional Strategy TeamRegional Strategy TeamPete Heinzen, DRMBrian Wing, Pacific Southwest

StationTom DeMeo, NRLeah Rathbun, NRKim Mellen-McLean, NRRobyn Darbyshire, NRJosh Chapman, NRDorothy Thomas, DRMMike Simpson, Deschutes NF

Why Needed?Why Needed?Coordinate efforts for efficiency and

knowledge transfer

Provide for processing and storage of LiDAR data

Provide standard outputs which are relatively user friendly and easily used with other corporate data/tools

Why Needed?Why Needed?Guidebook for the LiDAR data

collection process

Increase opportunities for funding and interagency cooperation

Create opportunities for shared model development

Strategy componentsStrategy componentsLiDAR acquisition

LiDAR data processing

LiDAR data storage

Standardized outputs from LiDAR data

Strategy componentsStrategy componentsVegetation field data

Support for model development

Integration with mapping

Training opportunities

LiDAR acquisitionLiDAR acquisitionDRM will continue to leverage

our current relationship with BLM to acquire data in Oregon through the Oregon LiDAR Consortium (DOGAMI)

Exploring IDIQ contracts with USGS for Washington acquisitions

P

P

LiDAR data processingLiDAR data processingProducts provided from DRM

Bare Earth DEM Bare Earth Hillshade Canopy Surface Canopy Surface Hillshade Crown Closure Tree Points LAS files

P

Data StorageData StorageCurrent and future options for

storing the raw and processed LiDAR data Local storage, e.g., NAS drives T: drive availability (except LAS) Image server options NRM proposal

P

Standardized outputsStandardized outputsStandardized outputs which do

not require field data:Digital Elevation ModelCanopy Cover Canopy Structure (Single Story vs. Multi-Story) Mean Tree HeightMaximum Tree Height Individual Overstory Tree LayerUnderstory Cover (Shrubs & CWD combined)Generic Stream Classification Improved Road LayerTopography & Aspect

T

Standardized outputsStandardized outputsStandardized outputs which

require field data: Stand density index

(SDI) Herbaceous cover

TPA by size class Wetland delineation Canopy structure class Riparian vegetation

condition Understory vegetation

cover Road condition and erosion

risk Live tree density &

stem maps Improved soil inventory

Snag density & stem maps

Stream classification

DWD presence Historic stream channel migration

Crown fuel weight Landslide occurrence and risk

Canopy bulk density Identification of scarps, Canopy base height areas of avalanche concern,

and

rock outcrops

T

Vegetation field dataVegetation field dataCollection

Coordination with RO is available to leverage existing monitoring data and for support in sampling design development and field data collection software

Storage Corporate database FSVeg should be

used to allow for data sharing and ensure data is available for future projects. L

Vegetation field dataVegetation field dataCoordination with RO is available

to link different datasets together and to help process data

L

L

Integration with mappingIntegration with mapping

SupportSupport for model for model developmentdevelopmentMultiple partnership opportunities

exist to develop models which link field, LiDAR, and remote sensed data: RSAC PNW Research Station RO

It is important to understand the dimensions of working with each group

L

Training (Existing)Training (Existing)Websites and webinars

Geospatial Training and Awareness website: http://fsweb.geotraining.fs.fed.us/www/index.php?logout=true

RSAC: http://www.fs.fed.us/eng/rsac/lidar_training/

Workshops Bend, OR February 2015 La Grande, OR March 2015

L

Training (Future needs)Training (Future needs) Troubleshooting Technical and general audiences Online resources DRM, Ecology, Inventory,

Eastside Strategy, others to provide

L

Next stepsNext stepsYour review comments by

January 15

Strategy team edits based on comments

Proposed final draft January 31

Present to leadership