Checking for non-preferred file/folder path names (may take a long time depending on the number of files/folders) ...

SNOTEL Data for analysis of snowpack vulnerability to wildfire


Authors:
Owners: This resource does not have an owner who is an active HydroShare user. Contact CUAHSI (help@cuahsi.org) for information on this resource.
Type: Resource
Storage: The size of this resource is 30.4 KB
Created: Dec 15, 2025 at 5:55 p.m. (UTC)
Last updated: Dec 17, 2025 at 9:02 a.m. (UTC) (Metadata update)
Published date: Dec 17, 2025 at 9:02 a.m. (UTC)
DOI: 10.4211/hs.8161299b910b4b13ac631e6c94bc1b9c
Citation: See how to cite this resource
Sharing Status: Published
Views: 28
Downloads: 1
+1 Votes: Be the first one to 
 this.
Comments: No comments (yet)

Abstract

The summarized SNOTEL data used for analyzing the impacts of wildfire on snow phenology measures (i.e. annual maximum SWE, date of annual maximum SWE, and melt-out date). The data were originally sourced from the Natural Resources Conservation (NRCS) Report Generator (https://wcc.sc.egov.usda.gov/reportGenerator/) and subsequently quality controlled for systematic data errors. All errors were verified with the NRCS staff before removal from the analysis dataset. The data includes the period of record (through 2019) at SNOTEL sites which were identified by NRCS staff as being impacted from wildfire. The summarized SNOTEL data have been processed to create a table of inputs at each site burned prior to 2020.

Subject Keywords

Coverage

Spatial

Coordinate System/Geographic Projection:
WGS 84 EPSG:4326
Coordinate Units:
Decimal degrees
North Latitude
49.4262°
East Longitude
-102.6123°
South Latitude
30.6580°
West Longitude
-125.2002°

Temporal

Start Date:
End Date:

Content

How to Cite

Giovando, J. (2025). SNOTEL Data for analysis of snowpack vulnerability to wildfire, HydroShare, https://doi.org/10.4211/hs.8161299b910b4b13ac631e6c94bc1b9c

This resource is shared under the Creative Commons Attribution CC BY.

http://creativecommons.org/licenses/by/4.0/
CC-BY

Comments

There are currently no comments

New Comment

required