Skip to content

Workflow for generating burn severity maps in google earth engine using the most recent landsast or sentinel2 imagery

Notifications You must be signed in to change notification settings

jdilger/nrt_burn_severity

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

61 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

nrt_burn_severity

Workflow for generating burn severity maps in google earth engine from user-provided fire perimeters

NRT_readme_pic_conus

Steps to Map Burn Severity:

  1. Download Fire Perimeter vector data from a reliable source.
    • On Our latest use of this repository, we used pull_nifc_fires.py, but we also have CLI scripts for CalFIRE and MTBS fire perimeters.
  2. Upload those Fire Perimeters to GEE as a FeatureCollection.
  3. Use the BS_Mapper.ipynb to produce categorical burn severity ee.Image's, plugging the Fire Perimeter ee.FeatureCollection(s) in as the inputs. Then export either to GEE Asset or Google Drive.

NOTE: For use in FireFactor product cycle, export yearly CONUS-wide BS to ee.Images under this GEE Asset folder: projects/pyregence-ee/assets/workflow_assets/ and use the base name prefix - BS_[perimetersSource]_[YEAR]. Those ee.Image's will be consumed by this CLI script for FireFactor: https://github.com/pyregence/landfire/blob/main/src/CreateDistLayer/create_dist_wildfire.py.

About

Workflow for generating burn severity maps in google earth engine using the most recent landsast or sentinel2 imagery

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •