-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #280 from NASA-IMPACT/develop
Production deploy v0.9.0
- Loading branch information
Showing
14 changed files
with
115 additions
and
27 deletions.
There are no files selected for viewing
Submodule ui
updated
52 files
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
--- | ||
id: fire | ||
name: Fire Perimeters | ||
description: Fire perimeters generated from VIIRs sensor observations. | ||
usage: | ||
- url: https://nasa-impact.github.io/veda-docs/notebooks/tutorials/mapping-fires.html | ||
label: View example notebook | ||
title: VEDA documentation for visualization and download | ||
media: | ||
src: ::file ./fire--dataset-cover.jpg | ||
alt: Forest burning at night | ||
author: | ||
name: Matt Howard | ||
url: https://unsplash.com/photos/eAKDzK4lo4o | ||
thematics: | ||
- eis | ||
|
||
layers: | ||
- id: eis_fire_perimeter | ||
stacCol: eis_fire_perimeter | ||
name: Fire Perimeter | ||
type: vector | ||
description: eis_fire_perimeter | ||
zoomExtent: | ||
- 5 | ||
- 20 | ||
--- | ||
|
||
<Block> | ||
<Prose> | ||
## FEDs Fire Perimeters | ||
|
||
Fire perimeter data is generated by the FEDs algorithm. The FEDs algorithm tracks fire movement and severity by ingesting observations from the VIIRS thermal sensors on the Suomi NPP and NOAA-20 satellites. This algorithm uses raw VIIRS observations to generate a polygon of the fire, locations of the active fire line, and estimates of fire mean Fire Radiative Power (FRP). The VIIRS sensors overpass at ~1:30 AM and PM local time, and provide estimates of fire evolution ~ every 12 hours. The data produced by this algorithm describe where fires are in space and how fires evolve through time. This CONUS-wide implementation of the FEDs algorithm is based on [Chen et al 2020’s algorithm for California.](https://www.nature.com/articles/s41597-022-01343-0) | ||
|
||
</Prose> | ||
</Block> | ||
<Block> | ||
<Prose> | ||
## Scientific Application Using FEDS Fire Perimeters | ||
FEDS Fire Perimeters offer insight into pre-fire risk, fire behaviour, and post-fire effects. The Earth Information System - Fire team is using FEDs perimeters to <Link to='/discoveries/fire-life-cycle'>understand the full lifecycle of a fire</Link> | ||
</Prose> | ||
</Block> | ||
<Block> | ||
<Prose> | ||
## Datasets generated using FEDs Fire perimeters | ||
|
||
* <Link to='/data-catalog/caldor-fire-behavior-burn-severity'>Caldor Fire Behavior and Burn Severity</Link> | ||
* <Link to='/data-catalog/barc-thomasfire'>Burn Area Reflectance Classification for Thomas Fire</Link> | ||
* <Link to='/data-catalog/frp-max-thomasfire'>Maximum Fire Radiative Power for Thomas Fire</Link> | ||
|
||
</Prose> | ||
</Block> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters