Find research datasets worth reusing

Observational rainfall data of the 2021 mid-July flood event in Belgium – Part 1. Rain gauges observations

From July 13th to 16th 2021, a long period of sustained and heavy rainfall affected Central Europe producing extreme rainfall amounts in western Germany, eastern Belgium, Luxembourg and The Netherlands. In Belgium, this unusual event induced massive flooding on a large part of the country and was responsible for 39 fatalities and strong damages to buildings and infrastructures.Such extremely rare event needs to be documented as much as possible and data must be made available for further studies in hydrology, in urban planning and, more generally, in all multi-disciplinary studies aiming at identifying and understanding all factors leading to such disaster.The observational rainfall data available for Belgium during the period from July 13th to July 16th 2021 are here shared with the scientific community. These data are twofold and provided in 2 parts: Part 1. <a href="https://doi.org/10.5281/zenodo.7739983">Observations from high-quality rain gauges</a>The dataset includes daily precipitation accumulation recorded by 323 weighing and manual rain gauges in Belgium as well as 5-min precipitation data recorded by 168 weighing rain gauges. These data were checked for possible errors and inconsistencies.The rain gauges observations are provided in csv format in 2 files:<ul><li>RainGaugesData_FLOOD21_daily.csv</li><li>RainGaugesData_FLOOD21_5min.csv</li></ul> Part 2. <a href="https://doi.org/10.5281/zenodo.7740059">Radar-based quantitative precipitation estimation (RADFLOOD21)</a>This product provides a quantitative precipitation estimation of the event at high spatial (i.e., 1 km) and temporal (i.e., 5 min and hourly) resolutions. It is obtained after a careful processing of the weather radar measurements and a merging with rain gauge measurements. The data is provided in hdf5 format. In addition, an animation of the 5-min RADFLOOD21 data is also made available. These data are exposed and discussed in <a href="https://hess.copernicus.org/articles/27/3169/2023/">https://hess.copernicus.org/articles/27/3169/2023/</a>. In particular, several analyses of these data are performed to describe the spatial and temporal distribution of rainfall during the event and to illustrate its exceptional character.

Supporting data for "Stratospheric Gas-Phase Production Alone Cannot Explain Observations of Atmospheric Perchlorate on Earth" by Chan et al.

Model code, simulation outputs, digitized observation-summary tables, and Python scripts for reproducing the analysis results/ figures presented in "Stratospheric Gas-Phase Production Alone Cannot Explain Observations of Atmospheric Perchlorate on Earth" by Yuk-Chun Chan et al. Please refer to the publication and readme.txt for more information.

EO4WildFires: An Earth Observation multi-sensor, time-series machine-learning-ready benchmark dataset for wildfire impact prediction

This paper presents a benchmark dataset called EO4WildFires; a multi-sensor (multi spectral; Sentinel-2, Synthetic-Aperture Radar - SAR; Sentinel-1, meteorological parameters; NASA Power) time-series dataset that spans 45 countries, which can be used for developing machine learning and deep learning methods targeted for the estimation of the area that a forest wildfire might cover. This novel EO4WildFires dataset is annotated using EFFIS (European Forest Fire Information System) as forest fire detection and size estimation data source. A total of 31,742 wildfire events are gathered from 2018 to 2022. For each event, Sentinel-2 (multispectral), Sentinel-1 (SAR) and meteorological data are assembled into a single data cube. The meteorological parameters that are included in the data cube are: ratio of actual partial pressure of water vapor to the partial pressure at saturation, average temperature, bias corrected average total precipitation, average wind speed, fraction of land covered by snowfall, percent of root zone soil wetness, snow depth, snow precipitation, as well as percent of soil moisture. The main problem that this dataset is designed to address, is the severity forecasting before wildfires occur. The dataset is not used to predict wildfire events, but rather to predict the severity (size of area damaged by fire) of a wildfire event, if that happens in a specific place under the current and historical forest status, as recorded from multispectral and SAR images, and meteorological data. Using the data cube for the collected wildfire events, the EO4WildFires dataset is used to realize three (3) different preliminary experiments, in order to evaluate the contributing factors for wildfire severity prediction. The first experiment evaluates wildfire size using only the meteorological parameters, the second one utilizes both the multispectral and SAR parts of the dataset, while the third exploits all dataset parts. In each experiment, machine learning models are developed, and their accuracy is evaluated.

opencc-by-4.0Feb 2023View details →

Data: Contrasting current and future surface melt rates on the ice sheets of Greenland and Antarctica: lessons from in situ observations and climate models

These data accompany the publication "Contrasting current and future surface melt rates on the ice sheets of Greenland and Antarctica: lessons from in situ observations and climate models". The data are organized as follows: - two files with time series (csv) of hourly near-surface climate and surface energy balance values for Neumayer station (ice shelf, East Antarctic ice sheet) and automatic weather station S5 (southwest Greenland ice sheet) - two files (nc) with monthly melt fields from the regional climate model RACMO2.3p2 forced by ERA5 over Greenland (0.05-degree resolution) and Antarctica (0.25-degree resolution) - two files (nc) with annual melt fields from the regional climate model RACMO2.3p2 forced by CESM2 over Greenland (0.1-degree resolution) and Antarctica (0.25-degree resolution) or the historical period (1950-2014) - two files (nc) with annual melt fields from the regional climate model RACMO2.3p2 forced by CESM2 over Greenland (0.1-degree resolution) and Antarctica (0.25-degree resolution) for the future emission scenario SSP5-8.5 (2015-2099)

Dataset: Correlative Light, Electron Microscopy and Raman Spectroscopy Workflow to Detect and Observe Microplastic Interactions with Whole Jellyfish

ABSTRACT Many researchers have turned their attention to understanding microplastic interaction with marine fauna. Efforts are being made to monitor exposure pathways and concentrations, and to assess the impact such interactions may have. To answer these questions, it is important to select appropriate experimental parameters and analytical protocols. This study focuses on medusae of Cassiopea andromeda jellyfish: a unique benthic jellyfish known to favor (sub-)tropical coastal regions which are potentially exposed to plastic waste from land-based sources. Juvenile medusae were exposed to fluorescent poly(ethylene terephthalate) and polypropylene microplastics (< 300 µm), resin embedded, and sectioned before analysis with confocal laser scanning microscopy as well as transmission electron microscopy and Raman Spectroscopy. Results show the fluorescent microplastics were stable enough to be detected with the optimized analytical protocol presented, and that their observed interaction with medusae occurs in a manner which is likely driven by the microplastic properties (e.g. density, hydrophobicity).

opencc-by-4.0Jan 2023View details →

A dataset of Earth Observation Data for Lithological Mapping using Machine Learning

Dataset Information Machine Learning (ML) algorithms had successfully contributed in the creation of automated methods of recognizing patterns in high-dimensional data. Remote sensing data  covers  wide  geographical areas and could be used to solve the problem of the demand of various  in-situ data.  Lithologicall mapping using remotely sensed data  is one of the most challenging  applications of ML algorithms. In the framework of the “AI for Geoapplications” project , ML and especially Deep Learning (DL) methodologies are investigated  for  the identification and characterization of the lithology based on remote sensing data in various  pilot areas  in Greece.  In order to train and test the various ML algorithms, a dataset consisting of  30 ROIs selected  mainly  from low -vegetated areas,  that cover 2% of the total  area of Greece was created Dataset Preprocessing Dataset preprocessing was executed using a combination of SNAP, QGIS and ENVI tools. Preprocessing steps: Defining areas with the following properties: <ul> <li> Zero cloud and snow coverage </li> <li> No water bodies </li> <li> Minimum vegetation </li> </ul> For the Aster Images: <ul> <li> Subset on defined areas </li> <li> Mosaic images when needed </li> <li> Digitising clouds </li> </ul> For the Labels: <ul> <li> We got the Soil map from YPEN (<a href="https://ypen.gov.gr/">https://ypen.gov.gr/</a>) </li> <li> Subset on defined areas </li> <li> All categories are represented with good analogies </li> <li> Clip label files with digitised clouds </li> <li> Rasterize </li> </ul>   For the Labels we have eighteen categories for the twenty-eight areas that we collected data. We use the following coding for the Labels of our Dataset: <table> <tbody> <tr> <td> Alluvial deposits </td> <td> 0 </td> </tr> <tr> <td> Limestone colluvial deposits </td> <td> 1 </td> </tr> <tr> <td> Limestones </td> <td> 2 </td> </tr> <tr> <td> Schists </td> <td> 3 </td> </tr> <tr> <td> Quaternary sediments </td> <td> 4 </td> </tr> <tr> <td> Gneiss </td> <td> 5 </td> </tr> <tr> <td> Slope fan debris </td> <td> 6 </td> </tr> <tr> <td> Mixed flysch </td> <td> 7 </td> </tr> <tr> <td> Flysch shale and cherts </td> <td> 8 </td> </tr> <tr> <td> Dolomites </td> <td> 9 </td> </tr> <tr> <td> Granite </td> <td> 10 </td> </tr> <tr> <td> Sandstone flysch </td> <td> 11 </td> </tr> <tr> <td> Flysch colluvial deposits </td> <td> 12 </td> </tr> <tr> <td> Peridotite and Gabbro </td> <td> 13 </td> </tr> <tr> <td> River bed deposits </td> <td> 14 </td> </tr> <tr> <td> Gneiss colluvial deposits </td> <td> 15 </td> </tr> <tr> <td> Not available </td> <td> -100 </td> </tr> <tr> <td> cloud coverage </td> <td> -999 </td> </tr> </tbody> </table> The following table lists the available areas and the categories that each contains: <a href="https://docs.google.com/spreadsheets/d/17q0L5Ltz7V4uBY9i6DhULJsJCtf7BOY1nbblB-hf3Pw/edit?usp=share_link">Lithology_Dataset</a>   For the Sentinel-2 images, we made the following process: <ul> <li> Resampling 10m </li> <li> Subset on defined areas </li> </ul> The Sentinel-2 map contains: Sentinel 2 false colour composite 11/8/4 with OSM background The Final step is the collocation of the previous into a datacube i.e a multidimensional array with 25 bands (datacube dimensions differentiate for every area) using the Aster image as base (15m spatial resolution).  <ul> <li> Bands 1-14: Aster </li> <li> Bands 15-24: S2 </li> <li> Band 25: Label </li> </ul> The code for preprocessing the dataset in order to be used for machine learning algorithms can be found in the following link:   <a href="https://github.com/georgegiannop/Lithology">https://github.com/georgegiannop/Lithology</a> Citation If you use this dataset in your work, please cite our paper: Vernikos, I., Giannopoulos, G., Christopoulou, A., Begaj, A., Stefouli, M., Bratsolis, E., and Charou, E.: A dataset of Earth Observation Data for Lithological Mapping using Machine Learning, EGU General Assembly 2023, Vienna, Austria, 24–28 Apr 2023, EGU23-17570, <a href="https://doi.org/10.5194/egusphere-egu23-17570">https://doi.org/10.5194/egusphere-egu23-17570</a>, 2023.

opencc-by-4.0Apr 2023View details →

High-quality NEID Solar Observations (January 2021 - June 2022)

NExScI archives all NEID Solar observations at <a href="https://neid.ipac.caltech.edu/search_solar.php">https://neid.ipac.caltech.edu/search_solar.php</a>.  NEID takes data even during inclement weather, and the official <a href="https://neid.ipac.caltech.edu/docs/NEID-DRP/index.html">NEID Data Reduction Pipeline</a> does not differentiate between those taken in excellent or poor observing conditions.  This CSV file contains a list of all NEID Solar observations from January 1, 2021 to June 13, 2022, identifies which are currently believed to be of high-quality, and provides diagnostic information used (so users can easily adapting the selection criterion for their needs). Columns: filename:  Name of file as provided by NExScI bjd: Barycentric Julian Date mask: true for observations considered of high quality; false for observations suspected to be low quality;  See selection criterion specified below pyrflux_mean: mean flux observed by pyrheliometer during exposure pyrflux_rms: root mean square deviation from mean of flux observed by pyrheliometer during exposure expmeter_mean: mean of exposure meter during exposure (summed over wavelength channels) expmeter_rms:  root mean square deviation from mean of exposure meter during exposure (summed over wavelength channels) airmass:  airmass of sun a time of observation hour_angle: hour angle of sun at time of observation driftfun: value of DRIFTFUN copied from FITS header of filename wavecal: value of WAVECAL copied from FITS header of filename expmeter_mean_blue:  mean of exposure meter during exposure (summed over bluest third of wavelength channels) expmeter_mean_green: mean of exposure meter during exposure (summed over middle third of wavelength channels) expmeter_mean_red:  mean of exposure meter during exposure (summed over reddest third of wavelength channels)   Selection criteria for setting mask to true: 1.  Require E_VER from fits file matches v1.1.* (Data processed with common minor version of NEID DRP) 2.  Require driftfun  == "dailymodel0" and wavecal == "LFCplusThAr"  (Wavelength calibration used) 3. Start time of exposure lies between 17:30:00 and 22:12:00 (Removes data taken while wavelength calibration is changing rapidly) 4. Exclude dates: October 2, 2021 to October 27, 2021 (due to a cabling issue) 5.  Require airmass <= 2.25  (Exclude data taken at high airmass) 6.  Require mean_pyroflux >= 10^2.95 (Require sufficient flux reaching the pyrheliometer) 7.  Require expmeter_mean >= 1.0e5  (Require sufficient flux reaching the exposure meter) 8.  Require rms_pyroflux <= 0.0035 * mean_pyroflux   (Steady atmospheric transparency) 9.  Require expmeter_rms <=  0.003 * expmeter_mean  (Steady transparency & pointing) 10. Require expmeter_mean >= 150 * pyrflux_mean  (Good pointing) 11. Exclude dates: June 6, 2021, June 16, 2021, July 7, 2021, July 18, 2021, and July 19, 2021 (Dates with poor wavelength calibrations.  This list may be updated upon further analysis.)

opencc-by-4.0Apr 2023View details →

Low-level mixed-phase clouds at the high Arctic site of Ny-Ålesund: A comprehensive long-term dataset of remote sensing observations

This dataset contains a comprehensive set of quality-controlled remote sensing observations of low-level mixed-phase clouds collected at the high Arctic site of Ny-Ålesund, between 10 October 2021 and 31 December 2022. Cornerstones of the dataset are observations from a 35-GHz polarimetric scanning Doppler cloud radar and a 94-GHz zenith-pointing Doppler cloud radar. Radar data are complemented with thermodynamic retrievals from a microwave radiometer, liquid base height from a ceilometer and wind fields from large-eddy simulations. All data have undergone extensive quality control, especially the cloud radar data, which are accurately calibrated, matched, and corrected for gas and liquid-hydrometeor attenuation, ground clutter and range folding. This dataset is especially suited for cloud microphysical studies, and the high number of events included allows for the compiling of robust statistics. The dataset is accompanied by a data descriptor article, which is available at <a href="https://doi.org/10.5194/essd-15-5427-2023" target="_blank" rel="noopener">doi.org/10.5194/essd-15-5427-2023</a>.   Dataset overview The files include only low-level mixed-phase cloud (LLMPC) events, as well as the 2 hours preceding and following events. Each file contains an individual event, unless multiple events are less than 4 hours apart, in which case they are combined into the same file. LLMPC events are detected by requiring that ice and liquid phase coexist in a cloud layer with top below 2500 m for at least one hour. All radar variables observed in zenith (Doppler moments at 35 and 94 GHz, linear depolarization ratio (LDR) at 35 GHz), as well as microwave radiometer retrievals (temperature (T), liquid water path (LWP), integrated water vapor (IWV)), liquid base height from the ceilometer, and model data (horizontal wind speed and direction) are brought to the same time and range grids (respectively named ‘time_zen’ and ‘range_zen’ in the files). Off-zenith radar variables (reflectivity, differential reflectivity (ZDR), maximum spectral ZDR (sZDRmax), correlation coefficient (RhoHV), differential phase shift (PhiDP), and specific differential phase (KDP)) are stored on separate coordinates (named ‘time_slant’ and ‘range_slant’). All derived corrections are already applied to the data, and stored in the files, in case the user is interested in reconstructing the original data. A number of flags have been included in the files: in particular ‘MPC_detected’ indicates whether a LLMPC event was detected, and ‘liquid_attenuation_correction_flag_zen’ and ‘liquid_attenuation_correction_flag_slant’ indicate whether radar reflectivities were corrected for attenuation due to liquid hydrometeors. Liquid attenuation corrections should be especially taken into account when computing the dual-wavelength ratio (i.e., the difference between reflectivity at 35 GHz and at 94 GHz, both expressed in dBZ), and performing quantitative analyses of reflectivity fields.

opencc-by-4.0Nov 2021View details →

GWTC-3: Compact Binary Coalescences Observed by LIGO and Virgo During the Second Part of the Third Observing Run — O3 search sensitivity estimates

This material is part of several data products associated with GWTC-3, the third Gravitational-Wave Transient Catalog from the <a href="https://www.ligo.org/">LIGO</a> Scientific Collaboration, the <a href="https://www.virgo-gw.eu/">Virgo</a> Collaboration, and the <a href="https://gwcenter.icrr.u-tokyo.ac.jp/en/">KAGRA</a> Collaboration. For more information, see the papers (<a href="https://dcc.ligo.org/LIGO-P2000318/public">dcc.ligo.org/LIGO-P2000318/public</a> and <a href="http://dcc.ligo.org/LIGO-P2100239/public">dcc.ligo.org/LIGO-P2100239/public</a>), the related material linked from this page, and the GWTC-3 data release documentation (<a href="https://www.gw-openscience.org/GWTC-3/">www.gw-openscience.org/GWTC-3/</a>). Observing Run 3 (O3) Search Sensitivity Estimates This document contains HDF injection summary files for search sensitivity estimates spanning the LIGO–Virgo–KAGRA (LVK) Collaborations' third observing run (O3). Details of the individual files can be found in <ul> <li>  o3-sensitivity-estimates.md</li> </ul> including descriptions of the injected distributions and the HDF file format adopted. Separate files are provided for the two parts of the run, O3a and O3b, specified by the GPS start times and durations in the filenames, and for the entire O3 run (filename with no times specified). Separate files are also provided for subpopulations that span the Binary Neutron Star (bns), Neutron Star–Black Hole (nsbh), Binary Black Hole (bbh), and Intermediate Mass Black Hole (imbh) mass ranges. The subpopulations are combined into a single file (mixture) containing a mixture model that spans the union of all subpopulation. How to download all files from this page If you would like to download all files on this page, we recommend <a href="https://gitlab.com/dvolgyes/zenodo_get">zenodo_get</a>: <pre><code class="language-bash">pip install zenodo_get zenodo-get RECORD_ID_OR_DOI </code></pre> where the record ID for the most recent version of this page is 5546675 and IDs for other versions can be found in the Versions section at the side of this page.   For more general background on gravitational-wave search analyses, try the materials from a <a href="https://www.gw-openscience.org/workshops/">GW Open Data Workshop</a> or the <a href="https://doi.org/10.1088/1361-6382/ab685e">guide to LIGO–Virgo data analysis</a>.

opencc-by-4.0Nov 2021View details →

GWTC-3: Compact Binary Coalescences Observed by LIGO and Virgo During the Second Part of the Third Observing Run — O1+O2+O3 Search Sensitivity Estimates

This material is part of several data products associated with GWTC-3, the third Gravitational-Wave Transient Catalog from the <a href="https://www.ligo.org/">LIGO</a> Scientific Collaboration, the <a href="https://www.virgo-gw.eu/">Virgo</a> Collaboration, and the <a href="https://gwcenter.icrr.u-tokyo.ac.jp/en/">KAGRA</a> Collaboration. For more information, see the papers (<a href="https://dcc.ligo.org/LIGO-P2000318/public">dcc.ligo.org/LIGO-P2000318/public</a> and <a href="http://dcc.ligo.org/LIGO-P2100239/public">dcc.ligo.org/LIGO-P2100239/public</a>), the related material linked from this page, and the GWTC-3 data release documentation (<a href="https://www.gw-openscience.org/GWTC-3/">www.gw-openscience.org/GWTC-3/</a>). O1 + O2 + O3 Search Sensitivity Estimates This document contains HDF injection summary files for search sensitivity estimates spanning the LIGO–Virgo–KAGRA (LVK) Collaborations' first (O1), second (O2), and third (O3) observing runs. Details of individual files can be found in <ul> <li>  o1+o2+o3-sensitivity-estimates.md</li> </ul> including descriptions of the HDF file format adopted. Separate files are provided for individual subpopulations that span the Binary Neutron Star (bns), Neutron Star–Black Hole (nsbh), Binary Black Hole (bbh), and Intermediate Mass Black Hole (imbh) mass ranges. Additionally, a single file spanning the union of those mass ranges (mixture) is provided. Sensitivity estimates for O1 and O2 are available via semi-analytic methods (estimates of the optimal network signal-to-noise ratio). Sensitivity estimates for O3 are available from real search results. Analysts should specify detection thresholds separately for each type of sensitivity estimate (e.g., a signal-to-noise cut for O1+O2 and a false alarm rate cut for O3). How to download all files from this page If you would like to download all files on this page, we recommend <a href="https://gitlab.com/dvolgyes/zenodo_get">zenodo_get</a>: <pre><code class="language-bash">pip install zenodo_get zenodo-get RECORD_ID_OR_DOI </code></pre> where the record ID for the most recent version of this page is 5636815 and IDs for other versions can be found in the Versions section at the side of this page.   For more general background on gravitational-wave search analyses, try the materials from a <a href="https://www.gw-openscience.org/workshops/">GW Open Data Workshop</a> or the <a href="https://doi.org/10.1088/1361-6382/ab685e">guide to LIGO–Virgo data analysis</a>.

opencc-by-4.0May 2023View details →

Direct observation of geometric phase in dynamics around a conical intersection

The CSV files contain experimental and theoretical data corresponding to figures 3 and A1 of the paper "Direct observation of geometric phase in dynamics around a conical intersection", available at <a href="http://arxiv.org/abs/2211.07320">arxiv:2211.07320</a>.  The contents of the files are described in README.txt.

opencc-by-nc-sa-4.0Jun 2023View details →

Heatwaves characterization derived from observations and climate projections to assess thermal behavior of 7 European city-hubs: Milano, Athens, Logroño, Cork, Gdynia, Lillestrøm and Amsterdam (1981-2100)

This dataset includes the processing results used to create the interactive climate service <a href="https://thermal-assessment.urban.tecnalia.dev/">Thermal Assessment Tool</a>. It provides frequency and severity of heatwaves under past, current and future climate conditions which allows to estimate the thermal behavior of regions and cities in Europe during episodes of extreme heat. A heatwave is typically defined as a “prolonged” period of “extremely high” temperature for a particular region or location. In REACHOUT, “prolonged” is defined by a period of two or more days and “extremely high” is determined per region when daily maximal temperature exceeds its threshold (95th percentile) and the daily minimum temperature exceeds its threshold (90th percentile). The percentiles were obtained considering the values of maximum and minimum temperatures of the region during the summer season of the baseline period of 1981 to 2010. To provide homogeneous data for the whole EU, the input variables used to generate this dataset come from the public, independent and authoritative <a href="https://climate.copernicus.eu/">Copernicus Climate Change Service</a> (C3S). For the observations the <a href="https://cds.climate.copernicus.eu/cdsapp#!/dataset/insitu-gridded-observations-europe?tab=overview">e-OBS</a> dataset is used and for the future projections the <a href="https://cds.climate.copernicus.eu/cdsapp#!/dataset/projections-cordex-domains-single-levels?tab=overview">EURO-CORDEX</a> dataset. The intermediate (RCP4.5) and very high (RCP8.5) emissions scenarios were considered. All the data was downloaded from the <a href="https://cds.climate.copernicus.eu/">Copernicus Climate Data Store</a> (CDS). The database is organized in three datasets: Regional_eobs_thresholds_Reachout.csv: contains the thresholds that were used to detect the heatwaves for each region. They were calculated considering the values of maximum and minimum temperatures during the summer season of the baseline period (1981-2010). The columns are: <ul> <li>region: unique identifier of the corresponding EUROSTAT NUTS_ID or GISCO_ID.</li> <li>tmax: daily maximum temperature threshold.</li> <li>tmin: daily minimum temperature threshold.</li> </ul> Historical_eobs_heatwaves_Reachout.csv: heatwaves of the historical period (1981-2021) for each region. The columns are: <ul> <li>region: unique identifier of the corresponding EUROSTAT NUTS_ID or GISCO_ID.</li> <li>start: first date of the heatwave.</li> <li>tmax: maximum temperature reached during the heatwave.</li> <li>intensity: the sum of the degrees of the maximum and minimum temperatures over their corresponding thresholds.</li> <li>duration: duration of the heatwave.</li> </ul> Future_and_baseline_eobs_heatwaves_Reachout.csv: ensemble future projections of heatwaves. The columns are: <ul> <li>hazard_level: it can be a warning, an alert or an alarm.</li> <li>region: unique identifier of the corresponding EUROSTAT NUTS_ID or GISCO_ID.</li> <li>experiment: emission scenario. It can be baseline, rcp-4-5 or rcp-8-5.</li> <li>period: it can be 1981-2010 for the baseline or 2011-2040, 2021-2050, 2031-2060, 2041-2070, 2051-2080, 2061-2090 or 2071-2100 for the future.</li> <li>decade_frequency: decade mean frequency. In the case of the future this is the ensemble of the models.</li> <li>decade_frequency_best: only applicable to the future. It determines the best projection among the models.</li> <li>decade_frequency_worst: only applicable to the future. It determines the worst projection among the models.</li> <li>year_days: average annual days.</li> <li>year_tmax_intensity: the average annual degrees of the maximum temperature over its corresponding threshold.</li> <li>year_tmin_intensity: the average annual degrees of the minimum temperature over its corresponding threshold.</li> </ul>

opencc-by-4.0Dec 2022View details →

Supporting Information for "The First GECAM Observation Results on Terrestrial Gamma-ray Flashes and Terrestrial Electron Beams"

Additional Supporting Information <ol> <li>GECAM_TGF_Catalog.xls</li> <li>GECAM_TEB_Catalog.xls</li> <li>Fig1AC_UT2021-07-05T07-45-41.783530_CPD.xls</li> <li>Fig1AC_UT2021-07-05T07-45-41.783530_GRD.xls</li> <li>Fig1AC_UT2021-07-05T07-45-41.783530_Sim.xls</li> <li>Fig1BD_UT2021-04-26T12-16-34.637228_CPD.xls</li> <li>Fig1BD_UT2021-04-26T12-16-34.637228_GRD.xls</li> <li>Fig1BD_UT2021-04-26T12-16-34.637228_Sim.xls</li> <li>Fig4A_UT2021-02-01T02-09-25.691512_CPD.xls</li> <li>Fig4A_UT2021-02-01T02-09-25.691512_GRD.xls</li> <li>Fig4A_UT2021-02-01T02-09-25.691512_Sim.xls</li> <li>Fig4B_UT2021-07-10T21-19-04.519543_CPD.xls</li> <li>Fig4B_UT2021-07-10T21-19-04.519543_GRD.xls</li> <li>Fig4B_UT2021-07-10T21-19-04.519543_Sim.xls</li> <li>Fig4C_UT2022-01-22T22-24-49.664579_CPD.xls</li> <li>Fig4C_UT2022-01-22T22-24-49.664579_GRD.xls</li> <li>Fig4C_UT2022-01-22T22-24-49.664579_Sim.xls</li> <li>Fig4D_UT2021-03-07T19-13-49.995485_CPD.xls</li> <li>Fig4D_UT2021-03-07T19-13-49.995485_GRD.xls</li> <li>Fig4D_UT2021-03-07T19-13-49.995485_Sim.xls</li> <li>Fig4E_UT2021-03-29T06-56-37.831848_CPD.xls</li> <li>Fig4E_UT2021-03-29T06-56-37.831848_GRD.xls</li> <li>Fig4E_UT2021-03-29T06-56-37.831848_Sim.xls</li> <li>Fig4F_UT2021-08-14T09-54-29.177203_CPD.xls</li> <li>Fig4F_UT2021-08-14T09-54-29.177203_GRD.xls</li> <li>Fig4F_UT2021-08-14T09-54-29.177203_Sim.xls</li> <li>Fig4G_UT2021-08-16T17-02-27.908009_CPD.xls</li> <li>Fig4G_UT2021-08-16T17-02-27.908009_GRD.xls</li> <li>Fig4G_UT2021-08-16T17-02-27.908009_Sim.xls</li> <li>Fig4H_UT2022-03-29T08-56-28.599361_CPD.xls</li> <li>Fig4H_UT2022-03-29T08-56-28.599361_GRD.xls</li> <li>Fig4H_UT2022-03-29T08-56-28.599361_Sim.xls</li> <li>Fig5C_UT2021-09-11T18-34-40.551997_CPD.xls</li> <li>Fig5C_UT2021-09-11T18-34-40.551997_GRD.xls</li> <li>Fig5C_UT2021-09-11T18-34-40.551997_Sim.xls</li> <li>Fig5D_UT2021-07-10T01-46-36.709997_CPD.xls</li> <li>Fig5D_UT2021-07-10T01-46-36.709997_GRD.xls</li> <li>Fig5D_UT2021-07-10T01-46-36.709997_Sim.xls</li> <li>Fig5A_UT2021-10-27T22-49-33.082008_CPD.xls</li> <li>Fig5A_UT2021-10-27T22-49-33.082008_GRD.xls</li> <li>Fig5A_UT2021-10-27T22-49-33.082008_Sim.xls</li> <li>Fig5B_UT2022-07-26T00-16-13.728010_CPD.xls</li> <li>Fig5B_UT2022-07-26T00-16-13.728010_GRD.xls</li> <li>Fig5B_UT2022-07-26T00-16-13.728010_Sim.xls</li> <li>Fig5EF_WWLLN_Lightning.txt</li> <li>GLD360data_forTGFUTC2021-02-22T00-17-18.034461.xlsx</li> <li>GLD360data_forTGFUTC2021-03-07T19-13-49.995436.xlsx</li> <li>GLD360data_forTGFUTC2021-03-25T09-48-08.785508.xlsx</li> <li>GLD360data_forTGFUTC2021-03-29T06-56-37.830006.xlsx</li> <li>GLD360data_forTGFUTC2021-04-17T20-10-34.446509.xlsx</li> <li>GLD360data_forTGFUTC2021-04-25T23-07-27.616005.xlsx</li> <li>GLD360data_forTGFUTC2021-04-29T18-12-43.227007.xlsx</li> <li>GLD360data_forTGFUTC2021-05-09T19-50-01.720689.xlsx</li> <li>GLD360data_forTGFUTC2021-05-10T21-38-43.498955.xlsx</li> <li>GLD360data_forTGFUTC2021-05-10T21-43-27.914962.xlsx</li> <li>GLD360data_forTGFUTC2021-05-12T09-58-08.470159.xlsx</li> <li>GLD360data_forTGFUTC2021-05-15T08-38-22.505997.xlsx</li> <li>GLD360data_forTGFUTC2021-05-16T08-43-35.339273.xlsx</li> <li>GLD360data_forTGFUTC2021-06-20T15-37-51.777130.xlsx</li> <li>GLD360data_forTGFUTC2021-06-21T22-38-57.377719.xlsx</li> <li>GLD360data_forTGFUTC2021-07-22T23-38-31.513009.xlsx</li> <li>GLD360data_forTGFUTC2021-08-16T15-11-40.193070.xlsx</li> <li>GLD360data_forTGFUTC2021-09-24T13-55-59.153000.xlsx</li> <li>GLD360data_forTGFUTC2021-10-05T10-16-04.302001.xlsx</li> <li>GLD360data_forTGFUTC2021-11-09T03-10-44.188748.xlsx</li> <li>GLD360data_forTGFUTC2021-12-04T01-37-23.893950.xlsx</li> <li>GLD360data_forTGFUTC2021-12-06T12-15-46.564243.xlsx</li> <li>GLD360data_forTGFUTC2021-12-12T21-41-33.038999.xlsx</li> <li>GLD360data_forTGFUTC2021-12-13T23-34-18.149995.xlsx</li> <li>GLD360data_forTGFUTC2021-12-22T19-36-38.765547.xlsx</li> <li>GLD360data_forTGFUTC2021-12-28T03-16-31.018224.xlsx</li> <li>GLD360data_forTGFUTC2022-02-16T15-26-20.379956.xlsx</li> <li>GLD360data_forTGFUTC2022-03-09T04-37-21.765997.xlsx</li> <li>GLD360data_forTGFUTC2022-03-11T04-56-30.604005.xlsx</li> <li>GLD360data_forTGFUTC2022-03-17T23-01-55.158520.xlsx</li> <li>GLD360data_forTGFUTC2022-03-26T20-48-39.098469.xlsx</li> <li>GLD360data_forTGFUTC2022-03-27T19-13-33.058448.xlsx</li> <li>GLD360data_forTGFUTC2022-03-30T19-35-55.714452.xlsx</li> <li>GLD360data_forTGFUTC2022-04-20T20-47-17.811510.xlsx</li> <li>GLD360data_forTGFUTC2022-05-03T03-38-25.725991.xlsx</li> <li>GLD360data_forTGFUTC2022-05-13T20-32-32.157110.xlsx</li> <li>GLD360data_forTGFUTC2022-05-13T20-36-38.126223.xlsx</li> <li>GLD360data_forTGFUTC2022-06-15T18-06-04.110702.xlsx</li> <li>GLD360data_forTGFUTC2022-06-24T10-42-13.680445.xlsx</li> <li>GLD360data_forTGFUTC2022-06-25T09-09-44.289205.xlsx</li> <li>GLD360data_forTGFUTC2022-07-20T20-59-28.784931.xlsx</li> </ol>   Data Description We have uploaded 86 data files. These are: <ol> <li>The list of 147 TGFs observed by GECAM from December 10, 2020 until August 31, 2022. The file includes information about a) the UTC time of observation, b) the longitude, latitude and altitude of the GECAM position, c) the duration calculated by the Bayesian Block algorithm, d) the number of net counts, e) the hardness ratio (energy limitation 200 keV), f) the CPD/GRD counts ratio. These data were used to produce Figure 1 and Figure 2.</li> <li>The list of 2 typical TEBs and 2 TEB-like events observed by GECAM from December 10, 2020 until August 31, 2022. The file includes information about a) the UTC time of observation, b) the longitude, latitude and altitude of the GECAM position, c) the duration calculated by the Bayesian Block algorithm, d) the CPD/GRD counts ratio, e) the longitude and latitude of the northern and sourthern magnetic footpoint. These data were used to produce Figure 1 and Figure 2.</li> <li>The CPD data of a cosmic-ray event. The CPD data include: a) the relative time to reference time (UT 2021-07-05T07:45:41.783530), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure S1A&S1C.</li> <li>The GRD data of a cosmic-ray event. The GRD data include: a) the relative time to reference time (UT 2021-07-05T07:45:41.783530), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure S1A&S1C.</li> <li>The SimEvt data of a cosmic-ray event. The CPD data include: a) the relative time to reference time (UT 2021-07-05T07:45:41.783530), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure S1A&S1C.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-04-26T12:16:34.637228), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure S1B&S1D.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-04-26T12:16:34.637228), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure S1B&S1D.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-04-26T12:16:34.637228), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure S1B&S1D.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-02-01T02:09:25.691512), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3A.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-02-01T02:09:25.691512), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3A.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-02-01T02:09:25.691512), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3A.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-07-10T21:19:04.519543), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3B.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-07-10T21:19:04.519543), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3B.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-07-10T21:19:04.519543), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3B.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2022-01-22T22:24:49.664579), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3C.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2022-01-22T22:24:49.664579), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3C.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2022-01-22T22:24:49.664579), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3C.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-03-07T19:13:49.995485), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3D.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-03-07T19:13:49.995485), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3D.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-03-07T19:13:49.995485), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3D.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-03-29T06:56:37.831848), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3E.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-03-29T06:56:37.831848), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3E.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-03-29T06:56:37.831848), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3E.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-08-14T09:54:29.177203), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3F.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-08-14T09:54:29.177203), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3F.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-08-14T09:54:29.177203), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3F.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-08-16T17:02:27.908009), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3G.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2021-08-16T17:02:27.908009), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3G.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2021-08-16T17:02:27.908009), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3G.</li> <li>The CPD data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2022-03-29T08:56:28.599361), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 3H.</li> <li>The GRD data of a TGF event. The GRD data include: a) the relative time to reference time (UT 2022-03-29T08:56:28.599361), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 3H.</li> <li>The SimEvt data of a TGF event. The CPD data include: a) the relative time to reference time (UT 2022-03-29T08:56:28.599361), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 3H.</li> <li>The CPD data of a TEB-like event. The CPD data include: a) the relative time to reference time (UT 2021-09-11T18:34:40.551997), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 4C.</li> <li>The GRD data of a TEB-like event. The GRD data include: a) the relative time to reference time (UT 2021-09-11T18:34:40.551997), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 4C.</li> <li>The SimEvt data of a TEB-like event. The CPD data include: a) the relative time to reference time (UT 2021-09-11T18:34:40.551997), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 4C.</li> <li>The CPD data of a TEB-like event. The CPD data include: a) the relative time to reference time (UT 2021-07-10T01:46:36.709997), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 4D.</li> <li>The GRD data of a TEB-like event. The GRD data include: a) the relative time to reference time (UT 2021-07-10T01:46:36.709997), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 4D.</li> <li>The SimEvt data of a TEB-like event. The CPD data include: a) the relative time to reference time (UT 2021-07-10T01:46:36.709997), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 4D.</li> <li>The CPD data of a typical TEB event. The CPD data include: a) the relative time to reference time (UT 2021-10-27T22:49:33.082008), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 4A.</li> <li>The GRD data of a typical TEB event. The GRD data include: a) the relative time to reference time (UT 2021-10-27T22:49:33.082008), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 4A.</li> <li>The SimEvt data of a typical TEB event. The CPD data include: a) the relative time to reference time (UT 2021-10-27T22:49:33.082008), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 4A.</li> <li>The CPD data of a typical TEB event. The CPD data include: a) the relative time to reference time (UT 2022-07-26T00:16:13.728010), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. CPD01 to CPD08). Data are used in Figure 4B.</li> <li>The GRD data of a typical TEB event. The GRD data include: a) the relative time to reference time (UT 2022-07-26T00:16:13.728010), b) the deposited energy (keV), c) the event type, d) the time type, e) the detector ID (i.e. GRD01 to GRD25). Data are used in Figure 4B.</li> <li>The SimEvt data of a typical TEB event. The CPD data include: a) the relative time to reference time (UT 2022-07-26T00:16:13.728010), b) The Simultaneous Events Number (SimEvtNum). Data are used in Figure 4B.</li> <li>The specific WWLLN data of the TEB-like event UT 2021-09-11T18:34:40.551997. The WWLLN data include: a) WWLLN Lighning UT Time, b) WWLLN Lighning UNIX Time, c) WWLLN Lighning Longitude (deg) , d) WWLLN Lighning Latitude (deg) , e) WWLLN Lighning Energy (J) , f) WWLLN Lighning Energy Error (J). Data are used in Figure 4E&4F.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-02-22T00:17:18.034461 +/- 1 minute. The GECAM-B nadir (129.7E, 10.9N) of this TGF is located in the east Asia region (EAR, 77E-138E, 13S-30N). The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg) , c) Lighning Peak Current (kA) , d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-03-07T19:13:49.995436 +/- 1 minute. The GECAM-B nadir (92.2E, 4.7N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-03-25T09:48:08.785508 +/- 1 minute. The GECAM-B nadir (101.4E, 3.5N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-03-29T06:56:37.830006 +/- 1 minute. The GECAM-B nadir (105.0E, 2.4S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-04-17T20:10:34.446509 +/- 1 minute. The GECAM-B nadir (131.0E, 2.4N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>51) The specific GLD360 data near GECAM TGF UT 2021-04-25T23:07:27.616005 +/- 1 minute. The GECAM-B nadir (117.1E, 29.0N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>52) The specific GLD360 data near GECAM TGF UT 2021-04-29T18:12:43.227007 +/- 1 minute. The GECAM-B nadir (77.9E, 5.3N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-05-09T19:50:01.720689 +/- 1 minute. The GECAM-B nadir (119.4E, 15.5N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-05-10T21:38:43.498955 +/- 1 minute. The GECAM-B nadir (105.2E, 5.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-05-10T21:43:27.914962 +/- 1 minute. The GECAM-B nadir (119.5E, 3.5S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-05-12T09:58:08.470159 +/- 1 minute. The GECAM-B nadir (122.8E, 12.9N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-05-15T08:38:22.505997 +/- 1 minute. The GECAM-B nadir (115.3E, 10.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-05-16T08:43:35.339273 +/- 1 minute. The GECAM-B nadir (103.6E, 8.5N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-06-20T15:37:51.777130 +/- 1 minute. The GECAM-B nadir (128.0E, 21.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-06-21T22:38:57.377719 +/- 1 minute. The GECAM-B nadir (124.4E, 13.3N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-07-22T23:38:31.513009 +/- 1 minute. The GECAM-B nadir (117.2E, 16.3N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-08-16T15:11:40.193070 +/- 1 minute. The GECAM-B nadir (126.9E, 28.8N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-09-24T13:55:59.153000 +/- 1 minute. The GECAM-B nadir (131.1E, 5.2N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-10-05T10:16:04.302001 +/- 1 minute. The GECAM-B nadir (115.3E, 10.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-11-09T03:10:44.188748 +/- 1 minute. The GECAM-B nadir (114.8E, 6.6N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-12-04T01:37:23.893950 +/- 1 minute. The GECAM-B nadir (126.7E, 10.5S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-12-06T12:15:46.564243 +/- 1 minute. The GECAM-B nadir (128.9E, 10.6N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-12-12T21:41:33.038999 +/- 1 minute. The GECAM-B nadir (119.0E, 11.2S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-12-13T23:34:18.149995 +/- 1 minute. The GECAM-B nadir (117.0E, 7.2N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-12-22T19:36:38.765547 +/- 1 minute. The GECAM-B nadir (104.2E, 3.4N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2021-12-28T03:16:31.018224 +/- 1 minute. The GECAM-B nadir (117.7E, 3.4N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-02-16T15:26:20.379956 +/- 1 minute. The GECAM-B nadir (102.0E, 3.6S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-03-09T04:37:21.765997 +/- 1 minute. The GECAM-B nadir (109.5E, 5.3S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-03-11T04:56:30.604005 +/- 1 minute. The GECAM-B nadir (114.3E, 8.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-03-17T23:01:55.158520 +/- 1 minute. The GECAM-B nadir (120.4E, 9.7S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-03-26T20:48:39.098469 +/- 1 minute. The GECAM-B nadir (111.5E, 3.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-03-27T19:13:33.058448 +/- 1 minute. The GECAM-B nadir (113.7E, 5.0S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-03-30T19:35:55.714452 +/- 1 minute. The GECAM-B nadir (102.1E, 4.0N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-04-20T20:47:17.811510 +/- 1 minute. The GECAM-B nadir (104.9E, 1.8S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-05-03T03:38:25.725991 +/- 1 minute. The GECAM-B nadir (109.0E, 11.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>81) The specific GLD360 data near GECAM TGF UT 2022-05-13T20:32:32.157110 +/- 1 minute. The GECAM-B nadir (115.8E, 0.1N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-05-13T20:36:38.126223 +/- 1 minute. The GECAM-B nadir (128.2E, 7.4N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-06-15T18:06:04.110702 +/- 1 minute. The GECAM-B nadir (109.7E, 10.9S) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-06-24T10:42:13.680445 +/- 1 minute. The GECAM-B nadir (116.8E, 10.4N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-06-25T09:09:44.289205 +/- 1 minute. The GECAM-B nadir (127.3E, 13.2N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> <li>The specific GLD360 data near GECAM TGF UT 2022-07-20T20:59:28.784931 +/- 1 minute. The GECAM-B nadir (97.4E, 22.8N) of this TGF is located in the EAR. The GLD360 data include: a) GLD360 Lighning UT Time, b) GLD360 Lighning Longitude (deg) and Latitude (deg), c) Lighning Peak Current (kA), d) Intracloud (IC) Lightning (Cloud=1) or Cloud-to-Ground Lighning (Cloud=0). Data are used in Figure 1B & 1C & 1D.</li> </ol>

opencc-by-nc-sa-4.0Jun 2023View details →

Heatwaves characterization derived from observations and climate projections to assess thermal behavior of regions in Europe (1981-2100)

This dataset provides frequency and severity of heatwaves under past, current and future climate conditions which allows to estimate the thermal behavior of regions in Europe during episodes of extreme heat. A heatwave is typically defined as a “prolonged” period of “extremely high” temperature for a particular region or location. In REACHOUT, “prolonged” is defined by a period of two or more days and “extremely high” is determined per region when daily maximal temperature exceeds its threshold (95th percentile) and the daily minimum temperature exceeds its threshold (90th percentile). The percentiles were obtained considering the values of maximum and minimum temperatures of the region during the summer season of the baseline period of 1981 to 2010. To provide homogeneous data for the whole EU, the input variables used to generate this dataset come from the public, independent and authoritative <a href="https://climate.copernicus.eu/">Copernicus Climate Change Service</a> (C3S). For the observations the <a href="https://cds.climate.copernicus.eu/cdsapp#!/dataset/insitu-gridded-observations-europe?tab=overview">e-OBS</a> dataset is used and for the future projections the <a href="https://cds.climate.copernicus.eu/cdsapp#!/dataset/projections-cordex-domains-single-levels?tab=overview">EURO-CORDEX</a> dataset. The intermediate (RCP4.5) and very high (RCP8.5) emissions scenarios were considered. All the data was downloaded from the <a href="https://cds.climate.copernicus.eu/">Copernicus Climate Data Store</a> (CDS). The database is organized in three datasets: Regional_eobs_thresholds_Europe.csv: contains the thresholds that were used to detect the heatwaves for each region. They were calculated considering the values of maximum and minimum temperatures during the summer season of the baseline period (1981-2010). The columns are: <ul> <li>region: unique identifier of the corresponding EUROSTAT NUTS_ID.</li> <li>tmax: daily maximum temperature threshold.</li> <li>tmin: daily minimum temperature threshold.</li> </ul> Historical_eobs_heatwaves_Europe.csv: heatwaves of the historical period (1981-2021) for each region. The columns are: <ul> <li>region: unique identifier of the corresponding EUROSTAT NUTS_ID.</li> <li>start: first date of the heatwave.</li> <li>tmax: maximum temperature reached during the heatwave.</li> <li>intensity: the sum of the degrees of the maximum and minimum temperatures over their corresponding thresholds.</li> <li>duration: duration of the heatwave.</li> </ul> Future_and_baseline_eobs_heatwaves_Europe.csv: ensemble future projections of heatwaves. The columns are: <ul> <li>hazard_level: it can be a warning, an alert or an alarm.</li> <li>region: unique identifier of the corresponding EUROSTAT NUTS_ID.</li> <li>experiment: emission scenario. It can be baseline, rcp-4-5 or rcp-8-5.</li> <li>period: it can be 1981-2010 for the baseline or 2011-2040, 2021-2050, 2031-2060, 2041-2070, 2051-2080, 2061-2090 or 2071-2100 for the future.</li> <li>decade_frequency: decade mean frequency. In the case of the future this is the ensemble of the models.</li> <li>decade_frequency_best: only applicable to the future. It determines the best projection among the models.</li> <li>decade_frequency_worst: only applicable to the future. It determines the worst projection among the models.</li> <li>year_days: average annual days.</li> <li>year_tmax_intensity: the average annual degrees of the maximum temperature over its corresponding threshold.</li> <li>year_tmin_intensity: the average annual degrees of the minimum temperature over its corresponding threshold.</li> </ul>

opencc-by-4.0Jun 2023View details →

DeepRainForest Output Data : Simulated daily rainfall output (2001-2020) under observed tree cover and no deforestation scenarios in South America

This dataset deposited contains simulation data related to the analysis of forest-rainfall relationships and the impact of historical deforestation on rainfall patterns in South America. The data includes outputs from a spatiotemporal neural network model, DeepRainForest, developed to simulate rainfall based on vegetation and climate inputs in South America. This dataset is the data necessary to recreate the figures that appear in an accepted (but yet to be published manuscript) in Global Change Biology titled "Assessing the impact of past and ongoing deforestation on rainfall patterns in South America". When the manuscript is accepted then the article will be linked from here. DeepRainForest_daily_rainfall_with_observed_treecover.nc: contains simulated daily rainfall data spanning from 2001 to 2020, considering the observed tree cover.  DeepRainForest_daily_rainfall_with_2000_treecover.nc: contains simulated daily rainfall output for the same time period (2001-2020) but assumes no deforestation from 2000 onwards.  DeepRainForest_daily_rainfall_with_1982_treecover.nc:contains simulated daily rainfall output for the same time period (2001-2020) but assumes no deforestation from 1982 onwards.

Surface chemical observations

Hourly surface measurements of PM2.5, PM10, SO2, NO2, O3, and CO concentrations in Korea (www.airkorea.or.kr) and China (www.cnemc.cn) from Feb 20 to Mar 31, 2019.

Estimating three-dimensional structures of eddy in the South Indian Ocean from the satellite observations based on the isQG method

Supporting data for Estimating three-dimensional structures of eddy in the South Indian Ocean from the satellite observations based on the isQG method Matlab Codes to reconstruct the subsurface structures (Codes without Figure_*.m) and plot the figures (Figure_*.m) in the manuscript. The file in Netcdf format is our reconstructed 3D density and currents.

Data for ECHAM-HAM in the Publication "Evaluation of aerosol and cloud properties in three climate models using MODIS observations and its corresponding COSP simulator, as well as their application in aerosol–cloud interactions"

This repository contains 3-hourly data of the ECHAM-HAM experiment in the paper: "Saponaro, G., Sporre, M. K., Neubauer, D., Kokkola, H., Kolmonen, P., Sogacheva, L., Arola, A., de Leeuw, G., Karset, I. H. H., Laaksonen, A., and Lohmann, U.: Evaluation of aerosol and cloud properties in three climate models using MODIS observations and its corresponding COSP simulator, as well as their application in aerosol–cloud interactions, Atmos. Chem. Phys., 20, 1607–1626, https://doi.org/10.5194/acp-20-1607-2020, 2020."

Primary raw observation input file for the Ring Laser Analysis program

This dataset is the primary input for the ring laser analysis program. It comprises a tab-delimited table, containing time information, the observed Sagnac frequency and a fairly large number of auxiliary measurements in order to compute the necessary raw data reductions.

Dataset of fungal communities observed on decomposing pig carcasses in New Jersey

This dataset contains estimated count data for fungal taxa identified using ITS metabarcoding collected from decomposing fetal pig carcasses placed in grasslands of New Jersey, USA. FungiPigDecomp_Data.csv is a file that contains the estimated count data at the level of taxonomic resolution possible for each replicate, at each stage of decomposition, across three body districts. FungiPigDecomp_Methods.docx is a summarized version of the sampling method relevant to interpreting the data. FungiPigDecomp_Descriptive.txt is a file describing the column headers in "FungiPigDecomp_Data.csv".