Rain-gages are critical instrumentation for documenting the rainfall forcing of post-wildfire hydrologic, erosional, and water-quality response. This USGS Data Release presents tipping-bucket rain gage data following two wildfires: the 2000 Cerro Grande Fire near Los Alamos, New Mexico and the 2010 Fourmile Canyon Fire near Boulder, Colorado. The data presented in this USGS Data Release are used for analyses that demonstrate important concepts in precipitation characteristics that relate to temporal and spatial scales. Further information regarding the location and data processing are available in the metadata.

This USGS Data Release section presents tipping-bucket rain gage data collected following the 2000 Cerro Grande Fire near Los Alamos, New Mexico. Further details are provided in https://onlinelibrary.wiley.com/doi/10.1002/hyp.6806.

This USGS Data Release section presents tipping-bucket rain gage data collected following the 2000 Cerro Grande Fire near Los Alamos, New Mexico. Further details are provided in https://onlinelibrary.wiley.com/doi/10.1002/hyp.6806.

This Data Release section presents tipping-bucket rain gage data collected following the 2010 Fourmile Canyon Fire near Boulder, Colorado. Further details are provided in: https://pubs.usgs.gov/sir/2011/5236 and https://onlinelibrary.wiley.com/doi/full/10.1002/hyp.9424.

This Data Release section presents tipping-bucket rain gage data collected following the 2010 Fourmile Canyon Fire near Boulder, Colorado. Further details are provided in: https://pubs.usgs.gov/sir/2011/5236 and https://onlinelibrary.wiley.com/doi/full/10.1002/hyp.9424.

Precipitation, volumetric soil-water content, videos, and geophone data characterizing postfire debris flows were collected at the 2022 Hermit’s Peak Calf-Canyon Fire in New Mexico. This dataset contains data from June 22, 2022, to June 26, 2024. The data were obtained from a station located at 35° 42’ 28.86” N, 105° 27’ 18.03” W (geographic coordinate system). Each data type is described below. Raw Rainfall Data: Rainfall data, Rainfall.csv, are contained in a comma separated value (.csv) file. The data are continuous and sampled at 1-minute intervals. The columns in the csv file are TIMESTAMP(UTC), RainSlowInt (the depth of rain in each minute [mm]), CumRain (cumulative rainfall since the beginning of the record [mm]), and VWC# (volumetric water content [V/V]) at three depths (1 = 10 cm, 2=30 cm, and 3=50 cm). VWC values outside of the range of 0 to 0.5 represent sensor malfunctions and were replaced with -99999 . Storm Record: We summarized the rainfall, volumetric soil-water content, and geophone data based on rainstorms. We defined a storm as rain for a duration >= 5 minutes or with an accumulation > 2.54 mm. Each storm was then assigned a storm ID starting at 0. The storm record data, StormRecord.csv, provides peak rainfall intensities and times and volumetric soil-water content information for each storm. The columns from left to right provide the information as follows: ID, StormStart [yyyy-mm-dd hh:mm:ss-tz] ([UTC], calculated as any time at least 0.2 mm of rain is detected), StormStop [yyyy-mm-dd hh:mm:ss-tz] ([UTC], timestamp of last rain gauge tip followed by at least 6 hours without precipitation), StormDepth [mm] (the total amount of rain that fell in the storm), StormDuration [h] (length of storm), I-5 [mm h-1] (peak 5-minute rainfall intensity), I-10 [mm h-1] (peak 10-minute rainfall intensity), I-15 [mm h-1] (peak 15-minute rainfall intensity), I-30 [mm h-1] (peak 30-minute rainfall intensity during the storm), I-60 [mm h-1] (peak 60-minute rainfall intensity), I-5 time [yyyy-mm-dd hh:mm:ss-tz] ([UTC], the time of the peak 5-minute rainfall intensity), I-10 time [yyyy-mm-dd hh:mm:ss-tz] ([UTC], the time of the peak 10-minute rainfall intensity), I-15 time yyyy-mm-dd hh:mm:ss-tz] ([UTC], the time of the peak 15-minute rainfall intensity), I-30 time yyyy-mm-dd hh:mm:ss-tz] ] ([UTC], the time of the peak 30-minute rainfall intensity), I-60 time [yyyy-mm-dd hh:mm:ss-tz] [UTC], (the time of the peak 60-minute rainfall intensity), VWC (volumetric water content [V/V] at three depths (1 = 10 cm, 2 = 30 cm, 3 = 50 cm) at the start of the storm, the time of the peak 15-minute rainfall intensity, and the end of the storm), Velocity [m s-1] of the flow, and Event (qualitative observation of type of flow from video footage). VWC values outside of the range of 0 to 0.5 represent sensor malfunctions and were replaced with -99999. Velocity was only calculated for flows with a noticeable surge as the rest of the signal is not sufficient for a cross-correlation, and Event was only filled for storms with quality video data. Values of -99999 were assigned for these columns for all other storms. Geophone Data: Geophone data, GeophoneData.zip, are contained in comma separated value (.csv) files labeled by ‘storm’ and the corresponding storm ID in the storm record and labeled IDa and IDb if the geophone stopped recording for more than an hour during the storm. The data was recorded at two geophones sampled at 50 Hz, one 11.5 m upstream from the station and one 9.75 m downstream from the station. Geophones were triggered to record when 1.6 mm of rain was detected during a period of 10 minutes, and they continued to record for 30 minutes past the last timestamp when this criteria was met. The columns in each csv file are TIMESTAMP [UTC], GeophoneUp_mV (the upstream geophone [mV]), GeophoneDn_mV (the downstream geophone [mV]). Note that there are occasional missed samples when the data logger did not record due to geophone malfunction

Precipitation, volumetric soil-water content, videos, and geophone data characterizing postfire debris flows were collected at the 2022 Hermit’s Peak Calf-Canyon Fire in New Mexico. This dataset contains data from June 22, 2022, to June 26, 2024. The data were obtained from a station located at 35° 42’ 28.86” N, 105° 27’ 18.03” W (geographic coordinate system). Each data type is described below. Raw Rainfall Data: Rainfall data, Rainfall.csv, are contained in a comma separated value (.csv) file. The data are continuous and sampled at 1-minute intervals. The columns in the csv file are TIMESTAMP(UTC), RainSlowInt (the depth of rain in each minute [mm]), CumRain (cumulative rainfall since the beginning of the record [mm]), and VWC# (volumetric water content [V/V]) at three depths (1 = 10 cm, 2=30 cm, and 3=50 cm). VWC values outside of the range of 0 to 0.5 represent sensor malfunctions and were replaced with -99999 . Storm Record: We summarized the rainfall, volumetric soil-water content, and geophone data based on rainstorms. We defined a storm as rain for a duration >= 5 minutes or with an accumulation > 2.54 mm. Each storm was then assigned a storm ID starting at 0. The storm record data, StormRecord.csv, provides peak rainfall intensities and times and volumetric soil-water content information for each storm. The columns from left to right provide the information as follows: ID, StormStart [yyyy-mm-dd hh:mm:ss-tz] ([UTC], calculated as any time at least 0.2 mm of rain is detected), StormStop [yyyy-mm-dd hh:mm:ss-tz] ([UTC], timestamp of last rain gauge tip followed by at least 6 hours without precipitation), StormDepth [mm] (the total amount of rain that fell in the storm), StormDuration [h] (length of storm), I-5 [mm h-1] (peak 5-minute rainfall intensity), I-10 [mm h-1] (peak 10-minute rainfall intensity), I-15 [mm h-1] (peak 15-minute rainfall intensity), I-30 [mm h-1] (peak 30-minute rainfall intensity during the storm), I-60 [mm h-1] (peak 60-minute rainfall intensity), I-5 time [yyyy-mm-dd hh:mm:ss-tz] ([UTC], the time of the peak 5-minute rainfall intensity), I-10 time [yyyy-mm-dd hh:mm:ss-tz] ([UTC], the time of the peak 10-minute rainfall intensity), I-15 time yyyy-mm-dd hh:mm:ss-tz] ([UTC], the time of the peak 15-minute rainfall intensity), I-30 time yyyy-mm-dd hh:mm:ss-tz] ] ([UTC], the time of the peak 30-minute rainfall intensity), I-60 time [yyyy-mm-dd hh:mm:ss-tz] [UTC], (the time of the peak 60-minute rainfall intensity), VWC (volumetric water content [V/V] at three depths (1 = 10 cm, 2 = 30 cm, 3 = 50 cm) at the start of the storm, the time of the peak 15-minute rainfall intensity, and the end of the storm), Velocity [m s-1] of the flow, and Event (qualitative observation of type of flow from video footage). VWC values outside of the range of 0 to 0.5 represent sensor malfunctions and were replaced with -99999. Velocity was only calculated for flows with a noticeable surge as the rest of the signal is not sufficient for a cross-correlation, and Event was only filled for storms with quality video data. Values of -99999 were assigned for these columns for all other storms. Geophone Data: Geophone data, GeophoneData.zip, are contained in comma separated value (.csv) files labeled by ‘storm’ and the corresponding storm ID in the storm record and labeled IDa and IDb if the geophone stopped recording for more than an hour during the storm. The data was recorded at two geophones sampled at 50 Hz, one 11.5 m upstream from the station and one 9.75 m downstream from the station. Geophones were triggered to record when 1.6 mm of rain was detected during a period of 10 minutes, and they continued to record for 30 minutes past the last timestamp when this criteria was met. The columns in each csv file are TIMESTAMP [UTC], GeophoneUp_mV (the upstream geophone [mV]), GeophoneDn_mV (the downstream geophone [mV]). Note that there are occasional missed samples when the data logger did not record due to geophone malfunction

This dataset represents 25 parallel longitudinal profiles that were extracted from terrestrial lidar point clouds taken during six survey periods. The six lidar surveys were conducted between 7 October 2010 and 8 October 2013. Over that time a colluvial hollow eroded into a fluvial channel. The longitudinal profiles show the topography of the colluvial hollow for each survey period. The width of the original colluvial hollow was approximately 1.25 m, and a longitudinal profile was extracted every 5 cm for the entire length of the hollow, resulting in 25 parallel longitudinal profiles. These data can be used to observe the transition of the colluvial hollow to a fluvial channel and furthermore they show the development of alternating steps and plunge pools. Within each of the 25 files, the column header describes the point number of the longitudinal profile, the distance downstream (meters), and the date of data collection. In addition, the file numbers represent profiles from west (1) to east (25).

This dataset represents 25 parallel longitudinal profiles that were extracted from terrestrial lidar point clouds taken during six survey periods. The six lidar surveys were conducted between 7 October 2010 and 8 October 2013. Over that time a colluvial hollow eroded into a fluvial channel. The longitudinal profiles show the topography of the colluvial hollow for each survey period. The width of the original colluvial hollow was approximately 1.25 m, and a longitudinal profile was extracted every 5 cm for the entire length of the hollow, resulting in 25 parallel longitudinal profiles. These data can be used to observe the transition of the colluvial hollow to a fluvial channel and furthermore they show the development of alternating steps and plunge pools. Within each of the 25 files, the column header describes the point number of the longitudinal profile, the distance downstream (meters), and the date of data collection. In addition, the file numbers represent profiles from west (1) to east (25).

This data release includes information used to support interpretations of relations between precipitation and soil moisture for a U.S. Geological Survey post-fire monitoring array installed near Malibu, CA following the 2007 Canyon fire. The 3 datasets are: 1) a time series of precipitation from three tipping bucket rain gages in individual files (Schmidt_2020_CANVQRG1.csv, Schmidt_2020_CANVQRG2.csv, and Schmidt_2020_CANTPRG3.csv; where RG in file name is abbreviation for rain gage), 2) a time series of a total of 9 soil moisture probes distributed with three soil moisture probes installed at varying depths from 3 individual soil pits in 3 individual files grouped by pit (Schmidt_2020_CANVQSM1.csv, Schmidt_2020_CANVQSM2.csv, and Schmidt_2020_CANVQSM3.csv; where SM in file name is abbreviation for soil moisture), and 3) locational and temporal record information for the instruments including manufacturer and serial number as tabular data (Schmidt_2020_Canyon_Fire_Instrument_info.csv) and a shapefile including location information (Schmidt_2020_instruments.shp) as well as a 4 band raster geospatial data file (Schmidt_2020_CAN_RG_SM.png). The data was generally collected from December 1, 2007 to September 5, 2008. Tipping bucket rain gages recorded 0.2 mm per tip with either an irregular time stamp representing each successive tip (CANVQRG1 and CANTPRG3) or at a regular four-minute interval (CANVQRG2) with all null values, representing no measurable precipitation, removed for clarity. Time-progressive cumulative rainfall is reported. Rain gage “CANVQRG1” was located closest to soil moisture monitoring instruments (“CANVQSM1, “CANVQSM2”, and “CANVQSM3”). Soil moisture probes recorded dimensionless volumetric water content in m^3/m^3 utilizing the dielectric constant of the media using capacitance or frequency domain technology. Probes were placed at three different depths in the soil: 5, 15 and 30 cm below the ground surface. Pit CANVQSM1 located closer to top of ridge, pit CANVQSM2 located mid-slope, and pit CANVQSM3 located downslope closer to the base of the hillslope. Soil moisture measurements were logged at regular time intervals, varying between two or six minutes, with recorded values reported as averages for that two- or six-minute interval. Column headers for soil moisture data denote unique instrument serial number and placement depth below ground surface in centimeters. Data pertaining to instrumental error was removed and entries left as null values. Negative reported values, outside of normal instrument recording range, during dry and likely hot conditions were left unmodified within data sets. All geographic coordinates reported as UTM NAD83 Zone 11N. All times are in Pacific Standard Time set to field laptop with migration forward one hour at 2 am on March 9, 2008.