Find research datasets worth reusing

opencc-by-4.0Apr 2017View details →

Laboratory dataset on Self-Heating Behavior and Ignition of Shale Rock

The file attached contains a complete set of experimental data from shale rock self-heating ignition cubic basket experiments. The experiments were carried out in a thermostatically controlled oven with thermocouples for measuring the ambient and shale sample temperatures. The data is divided in two parts, one for coarse particles and one for fine particle experiments. The data reported includes the dates of experiments, volume of shale basket being tested, oven ambient temperature, fuel mass of shale, bulk density of the shale, residue mass after the experiment, percentage of residue in respect to initial mass, and if the sample ignited or not. This data is in support of the journal paper: F. Restuccia, N. Ptak, G. Rein, Self-Heating Behavior and Ignition of Shale Rock, Combustion and Flame, Vol 176, 2017, pp 213-219. doi: 10.1016/j.combustflame.2016.09.025.

opencc-by-4.0Apr 2024View details →

Data, plotting scripts, and figures for "A physics-based ignition model with detailed chemical kinetics for live fuel burning studies"

This repository contains the data, plotting scripts, and figures associated with the paper "A physics-based ignition model with detailed chemical kinetics for live fuel burning studies" by Diba Behnoudfar and Kyle E. Niemeyer. See the README file for additional details.

opencc-by-4.0Oct 2024View details →

Distribution and Characteristics of Lightning-Ignited Wildfires in Boreal Forests - the BoLtFire database

This repository holds a dataset of lightning-ignited wildfires across the boreal biome. The BoLtFire dataset covers the period 2012 to 2022 and encompasses 6,902 fires - 4,201 in Eurasia and 2,701 in North America. The layers included in this dataset are: FireID, StartDate, EndDate, FireYdear, AreaHa (burned area), ClassSize, BiomeName, EcoBiome, EcoName, EcoID, Realm, LCDN (Land cover number), LCName (land cover name), Country, Continent, HoldoverD (days), HoldoverRD (holdover rounded), IgnLat (Ignition location Latitude), IgnLong (Ignition Location Longitude), DisPol (Distance of the ignition location to the fire perimeter if it is located outside the polygon), and PerCheck (designates if the ignition location is within the fire perimeter or oustide the perimeter).   The datasets are available per continent (North America, Europe, and Asia) as shapefiles. The spatial reference system is Global LANd Cover mapping and Estimation (GLANCE) Grids - Version 01 CRS.   *Please note: Versions 1 and 2 are missing LIW from Canada between 2021-2022.

opencc-by-4.0Jul 2023View details →

Estimating the silica content and loss-on-ignition in the North American Soil Geochemical Landscapes datasets: a recursive inversion approach

Abstract: A novel method of estimating the silica (SiO2) and loss-on-ignition (LOI) concentrations for the North American Soil Geochemical Landscapes (NASGL) project datasets is proposed. Combining the precision of the geochemical determinations with the completeness of the mineralogical NASGL data, we suggest a ‘reverse normative’ or inversion approach to calculate first the minimum SiO2, water (H2O) and carbon dioxide (CO2) concentrations in weight percent (wt%) in these samples. These can be used in a first step to compute minimum and maximum estimates for SiO2. In a recursive step, a ‘consensus’ SiO2 is then established as the average between the two aforementioned estimates, trimmed as necessary to yield a total composition (major oxides converted from reported Al, Ca, Fe, K, Mg, Mn, Na, P, S, and Ti elemental concentrations + ‘consensus’ SiO2 + reported trace element concentrations converted to wt% + ‘normative’ H2O + ‘normative’ CO2) of no more than 100 wt%. Any remaining compositional gap between 100 wt% and this sum is considered ‘other’ LOI and likely includes H2O and CO2 from the reported ‘amorphous’ phase (of unknown geochemical or mineralogical composition) as well as other volatile components present in soil. We validate the technique against a separate dataset from Australia where geochemical (including all major oxides) and mineralogical data exist on the same samples. The correlation between predicted and observed SiO2 is linear, strong (R2 = 0.91) and homoscedastic. We also compare the estimated NASGL SiO2 concentrations with another publicly available continental-scale survey over the conterminous USA, the ‘Shacklette and Boerngen’ dataset. This comparison shows the new data to be a reasonable representation of SiO2 values measured on the ground over the same study area. We recommend the approach of combining geochemical and mineralogical information to estimate missing SiO2 and LOI by the recursive inversion approach in datasets elsewhere, with the caveat to validate results. Datasets: The original geochemical and mineralogical data for soils of the conterminous United States (A and C horizon datasets) were downloaded from <a href="https://mrdata.usgs.gov/ds-801/">https://mrdata.usgs.gov/ds-801/</a>. The ‘Shacklette and Boerngen’ dataset was downloaded from <a href="https://mrdata.usgs.gov/ussoils/">https://mrdata.usgs.gov/ussoils/</a>. A worked example for the five selected samples of Figure 5 is available as a Microsoft Excel spreadsheet (NALG_Ch_oxides_with_estimated_SiO2_LOI_worked example.xlsx) on Zenodo.org. The new datasets including sample identification, coordinates, converted major oxide concentrations, and the concentration estimates for SiO2 and LOI in wt% for the A and C horizon datasets from the North American Soil Geochemical Landscapes (NASGL) project are available as comma separated value files (NALG_Ah_oxides_with_estimated_SiO2_LOI.csv and NALG_Ch_oxides_with_estimated_SiO2_LOI.csv) on Zenodo.org.

opencc-by-4.0Apr 2024View details →

Dataset for the publication: Potential of alcohol fuels in active and passive pre-chamber applications in a passenger car spark-ignition engine

<div> The dataset covers the research data of the publication "Potential of alcohol fuels in active and passive pre-chamber applications in a passenger car spark-ignition engine" in International Journal of Engine Research (DOI: 10.1177/14680874211053168). </div>

opencc-by-4.0Jan 2022View details →

Ignition and combustion characteristics of n-butanol and FPBO/n-butanol blends with addition of ignition improver

This is the dataset for the paper "Ignition and combustion characteristics of n-butanol and FPBO/n-butanol blends with addition of ignition improver." This research is supported by the European Union’s Horizon 2020 Research and Innovation programme (SmartCHP project, Grant Agreement No. 815259). In this study, the ignition and combustion characteristics of fast pyrolysis bio-oil (FPBO) are investigated in a combustion research unit (CRU), which mainly consists of a constant-volume combustion chamber. To fuel CRU with FPBO, n-butanol and 2-ethylhexyl nitrate (EHN) are used to improve the atomization and ignition properties of the fuel blends, respectively. In the first part of this study, an appropriate proportion of EHN additive into n-butanol is determined based on the balance between the ignition improvement and the amount of EHN addition. Then, the effects of FPBO content in FPBO/n-butanol blends with the same EHN addition are investigated. The effects of chamber wall temperature on the combustion are also studied.

opencc-by-4.0Jul 2024View details →

Re-igniting Windrush Folk stories and songs to improve African-Caribbean mental health disparities in the London Boroughs of Lewisham & Greenwich

This cross-disciplinary intergenerational project created a network of experts from multiple fields, aiming to achieve several key objectives. Using A-C Folk Songs and Art methods, it provided support to hub spaces, including training, remuneration for services and connecting them to therapists. The project also embeded culturally relevant narrative therapy techniques in community settings to support proactive positive mental health, whilst ensuring community organisations had access to affordable meeting spaces. Finally, it created opportunities for intergenerational connection, fostering a more cohesive and supportive community environment. A-C communities are 40% more likely than white-British people to come into contact with mental health services and be detained under the Mental Health Act, reflecting a stark historical pattern of structural racism and its ensuing health inequalities within the mental health system (Vige, 2019). Access to mental healthcare services are limited as a result of institutional, cultural and socio- economic exclusion factors related to BME groups (Memon, et al., 2016).  The field of clinical psychology often 'assumes a deficit-based-approach' to the mental health of those minoritised by society (Renkly & Bertolini, 2018). This model is problematic with those from A-C groups because it places emphasis on the individual rather than systems of oppression and ignores the ways cultural traditions and communities create supporting mechanisms for mental health.  Our approach offers an alternative model. This project uses an augmented generative co-design framework base on Bird et al (2021) where a narrative enquiry (Pinnegar, & Daynes, 2007) is used to engage participants in conversations on folk songs and how these can be utilised to support mental health of the local A-C community.  Through a series of workshops we brought together storytellers, A-C elders and young adults 18-85 to gather traditional stories as well as to create new ones. This supported our understanding of both folk stories and song routes and the lessons learnt within them. We used these stories as analogies to map out the socio-cultural ways in which mental health is discussed in African-Caribbean communities, capturing these conversations via film which, after each session, is edited and re-shared in the next session to create a focus for future conversations.  During the project we have co-produced a toolkit including: film, workshop plans and thematic analysis of findings.  Our work will feed into at least 2 publications which connect the 10 NHS 75 projects (article and policy document) and we plan on publishing at least 2 further works; 1 on methodological insight and the other on research findings. Our work has been shared at the International symposium (1st July 2024 University of Greenwich) linked to mental Health and the Climate crisis, opening possible future avenues of work with international organisations as well as with the Caribbean Association.

opencc-by-4.0Sep 2018View details →

Laboratory Dataset on Self-ignition of Biochar samples

The file attached contains a complete set of experimental data from biochar self-heating ignition of cubic basket experiments for a range of feedstock materials (Softwood, Wheat pellets and rice husks) produced in a kiln reactor at temperatures ranging between 350 and 800  °C. The experiments are all oven-basket experiments, and were carried out in a thermostatically controlled oven with thermocouples for measuring the ambient and sample temperatures. The data reported includes the dates of experiments, volume of samples being tested, oven ambient temperature, reactor production temperature, bulk density of the sample and if the sample ignited or not. There are 3 worksheets included, one per feedstock type. This data is in support of the journal paper: F. Restuccia, O. Masek, R. M. Hadden, G. Rein, Quantifying self-heating ignition of biochar as a function of feedstock and the pyrolysis reactor temperature, Fuel  236 (2019), pp 201-213 <a href="https://doi.org/10.1016/j.fuel.2018.08.141">https://doi.org/10.1016/j.fuel.2018.08.141</a>.

edi40/100

Arctic LTER 1991: Percent moisture, bulk density, percent loss on ignition and percent organic carbon were measured for peat collected from soils in the Imnavait Creek watershed.

Percent moisture, bulk density, percent loss on ignition and percent organic carbon were measured for peat collected from soils in the Imnavait Creek watershed.

openOpenDec 2015View details →

opencc-byFeb 2020View details →

Petrol Lamp with Electric Igniter

This lamp was produced in Germany around 1950. Around that time, the technique of batteries developed a lot, and batteries could now be used in the mine lamps as well. The firestone igniters in the mineworkers' lamps got replaced by electric igniters, fed by a battery. This lamp only has a single mesh cap. In the later versions of this lamp, a second mesh cap was placed around this one, to make it stronger. Creator: Aniek van den Brandt Source: Objaverse 1.0 / Sketchfab

opencc-byFeb 2020View details →

Petrol lamp with a firestone igniter

* Origin: Germany * Producer: Friemann & Wolf GmbH * Date: 1910 * Height: 30,5 cm * Diameter: 10 cm This petrol lamp is also known as one of the safety lamps. That is because the elements of the lamp protect the flame inside it well enough to carry the lamp around the mines in the presence of flammable gases there. Using a wire gauze around the flame was designed to cool down the lamp, and the glass casing below further protected the igniter. The glass casing can be removed. Compared to the petrol lamp with a chatter igniter, a firestone igniter was an improvement. A firestone was stroked to the gear to create a spark of fire. This system was more effective than the chatter igniter because the firestones lasted for longer. Besides that, they sparked better than the chatters. Although this lamp prevented the explosions in the mines, unlike the earlier lamps with the open flame, it still was heavy to carry around and could not be attached to the helmet. Created by: Anna Bashuk Source: Objaverse 1.0 / Sketchfab

dryad36/100

Discrete fire events, their severity, and their ignitions, as derived from MODIS MCD 14ML active-fire detection data for Indonesia, 2002-2019

1. PUBLICATION CORRESPONDING TO THESE DATA Sloan, Sean*; Locatelli, Bruno; Andela, Niels; Cattau, Megan E.; Gaveau, David; Tacconi, Luca. 2022 'Declining Severe Fire Activity on Managed Lands in Equatorial Asia'. Communications Earth & Environment. DOI: 10.1038/s43247-022-00522-6. *Corresponding author email: sean.sloan@viu.ca 2. ABSTRACT OF THE DATA The GIS data and corresponding attribute data described here pertain to discrete fire events, their severity, and their ignitions, as derived on the basis of daily MODIS Collection 6 MCD14ML active-fire detections (AFDs). Data on fire events and their ignitions are provided separately, as two data files. These data files on fire events and ignitions may however be linked to each other by the data user. Fire-event severity is quantified per fire event and reported in the data file for fire events. A fire event is a cluster of MODIS Collection 6 MCD14ML active-fire detections (AFDs) wherein each AFD has a spatial (<=1-km) and temporal (<=4-day) proximity to another AFD in the same fire event, inferring thus a relational co-occurrence amongst AFDs in time and space. In other words, a fire event is considered a likely occasion of burning wherein all constituent AFDs are related to each other in time and space, either directly (as for proximate AFDs) or indirectly (as in the case of a large area of fire activity that spread progressively over time and space from an initial source). Each fire event has a designated ignition AFD, being the AFD of the fire event with the earliest detection date. A given fire event can have more than one ignition AFD if the ignitions all share same earliest detection date. The ignition AFD(s) is the nominal initial source of the burning described by the corresponding fire event. All other, non-ignition AFDs of a fire event are deemed its 'propagation' AFDs, since these AFDs follow from the ignitions, temporally and spatially. See Figure 4 in the publication by Sloan et al. for an illustration of the geography of fire events and their ignition AFDs. Fire events and their ignitions were derived from standard science-quality MODIS Collection 6 MCD 14ML AFD data, commonly referred to as fire 'hotspot' data. Data were detected by both the Terra and Aqua satellite sensors daily for Indonesia between July 2002 and December 2019. Information on these input data are provide by the two citations below. The publication of Sloan et al. provides methodological details on how the MODIS Collection 6 MCD 14ML AFD data were processed into discrete fire events and ignitions. EarthData. MODIS Collection 6 Active-Fire Detections standard scientific data (MCD14ML), NASA EarthData, https://earthdata.nasa.gov/firms (2019). Giglio, L., Schroeder, W. & Justice, C. O. The Collection 6 MODIS active fire detection algorithm and fire products. Remote Sensing of Environment 178, 31-41, (2016). 3. DATA FILES Two data files are distributed here – one for discrete fire events, and another for the ignition AFDs of each fire event. The data files are provided in a GIS-compatible format, and also as a generic text format, as described below. 3.1 GIS VERSION Data files in GIS-compatible format are provided as 'feature classes' within an ArcGIS file geodatabase 'Sloan_MODIS_FireEvents_Ignitions_2002_2019.gdb'. These data files can be viewed and manipulated using either ArcGIS Desktop or ArcGIS Pro software. There is one feature class for fire events, and another file for ignitions. Sloan_MODIS_FireEvents_Ignitions_2002_2019.gdb\nfire4_all_spatial_fire_2002_2019_joins_sp_LC This file pertains to fire events. All AFDs of a given fire event are included, without differentiation as to whether the AFDs are ignition AFDs or other (propagation) AFDs. Fire events are assigned unique ID values and basic attribute data. Sloan_MODIS_FireEvents_Ignitions_2002_2019.gdb\nfire4_all_spatial_fire_2002_2019_igs_sp_LC This file pertains to ignitions. Only ignition AFDs are included for a given fire event. Fire events corresponding to the ignitions are assigned unique ID values and basic attribute data. 3.2 CSV TEXT VERSION Both data files are also supplied as comma-separated value (CSV) text files for viewing and manipulation in non-GIS software, such as Excel, text editors, or any statistical software. The text files can also be read into various GIS software. CSV-formatted files have the same file name and attribute fields as the corresponding GIS-formatted data files. These CSV-formatted data files (as well as the GIS-formatted data files) include attribute data on the latitude and the longitude of each AFD. Attribute field names are included as the first row of values in a CSV file. No 'text qualifiers' like quotations (" ") or inverted commas ('') are used to designate text/string values within the CSV file. Text values appear directly between commas in the CSV data file, e.g., …,Kalimantan_Southern,… . Note two points of caution for working with these CSV data: i) Microsoft Excel may be used for a partial view of the data file nfire4_all_spatial_fire_2002_2019_joins_sp_LC.csv, but it is not recommended for working with this data file. This is because the number of records/rows in this csv file slightly exceeds that maximum that may be read by Excel, which is just over 1 million. This limitation does not apply to the other csv file, however. ii) The GIS-formatted data files employ 'null values' in their attribute tables, and so the corresponding 'values' in the CSV-formatted data files are similarly null. For null values, no value whatsoever is ascribed, not even 0. In the syntax of a CSV file (apparent upon opening the file in any text editor like Microsoft Notepad), a null value is denoted by two consecutive commas without any value, text, or space between them. If a CSV file were opened in Excel, a cell assigned a null value would be blank, not 0 or otherwise. This denotes the correct transcription of the GIS-formatted data. This feature will not impede the correct reading of these CSV data by whatever software. Users are made aware of this feature merely to ensure the proper input of these data into whatever software. 4. DATA STRUCTURE / GEOGRAPHY The GIS-formatted data files are 'point data', i.e., they map the geography of AFDs as individual 'points', in keeping with how these MODIS MCD14ML AFD data were originally structured. For the GIS-formatted data files, each record/row in its corresponding attribute tables corresponds geographically to single AFD 'point', regardless of whether that AFD belongs to a fire event comprised of many AFDs. In the parlance of GIS files, the files depict 'single-part' point features. The unique ID field [nfireID2] serves to denote the fire event to which a given AFD belongs. Similarly, for the CSV-formatted data files, each record/row of values corresponds to a single AFD. There are 1,232,377 records for the data file 'nfire4_all_spatial_fire_2002_2019_joins_sp_LC'. There are 720795 records for the data file 'nfire4_all_spatial_fire_2002_2019_igs_sp_LC'. 5. ATTRIBUTE FIELDS In the data files, while some attribute fields pertain to the individual AFD as the unit of observation (e.g., the land-cover class coincident with the AFD), other attribute fields correspond to the larger 'fire event' to which the individual AFD belongs (e.g., the total duration of fire activity for the fire event). Accordingly, for certain attribute fields pertaining to the fire event as a whole, their values will appear 'duplicated' in the data file amongst those individual AFDs (records) that constitute the fire event in question. Whether a given attribute field pertains to the individual AFD or to its constituent fire event is denoted below for each field. Each AFD is assigned a unique ID field denoting its constituent fire event, [nfireID2]. This field is consistent between both data files, so that attribute data for a given fire event may be 'matched' to attribute data for its corresponding ignition AFD(s), and vice versa, on the basis of the common value of the field [nfireID2]. Note that many attributes below are as originally defined/measured by the input MCD 14ML data, or are derived directly thereof. 5.1 DATASET nfire4_all_spatial_fire_2002_2019_joins_sp_LC <table class="MsoTableGrid"> <tbody> <tr> <td> Field Name </td> <td> Geography of Attribute Value </td> <td> Definition </td> </tr> <tr> <td> OID </td> <td> AFD </td> <td> Object ID value. Unique values for each AFD (record) in the GIS-formatted data file when viewed in ArcGIS. Field values are -1 in the CSV-formatted data file. </td> </tr> <tr> <td> Peat </td> <td> AFD </td> <td> Denotes whether the AFD occurs on peatlands (value=1) as defined in Sloan et al. </td> </tr> <tr> <td> MIN_CONFIDE </td> <td> Fire Event </td> <td> The minimum detection confidence of all AFDs in the fire event, where confidence ranges from 1-100%. </td> </tr> <tr> <td> MAX_CONFIDE </td> <td> Fire Event </td> <td> The maximum detection confidence of all AFDs in the fire event, where confidence ranges from 1-100%. </td> </tr> <tr> <td> MEAN_CONFIDE </td> <td> Fire Event </td> <td> The mean detection confidence of all AFDs in the fire event, where confidence ranges from 1-100%. </td> </tr> <tr> <td> STD_CONFIDE </td> <td> Fire Event </td> <td> The standard deviation of detection confidence of all AFDs in the fire event, where confidence ranges from 1-100%. </td> </tr> <tr> <td> SUM_FRP </td> <td> Fire Event </td> <td> The sum total of all fire-radiative power (FRP) measures for all AFDs in the fire event. Units are megawatts. </td> </tr> <tr> <td> MEAN_FRP </td> <td> Fire Event </td> <td> The mean of all fire-radiative power (FRP) measures for all AFDs in the fire event. Units are megawatts. </td> </tr> <tr> <td> MIN_FRP </td> <td> Fire Event </td> <td> The minimum of all fire-radiative power (FRP) measures for all AFDs in the fire event. Units are megawatts. </td> </tr> <tr> <td> MAX_FRP </td> <td> Fire Event </td> <td> The maximum of all fire-radiative power (FRP) measures for all AFDs in the fire event. Units are megawatts. </td> </tr> <tr> <td> MEAN_LATITUD </td> <td> Fire Event </td> <td> The mean latitude of all AFDs in the fire event. </td> </tr> <tr> <td> MEAN_LONGITU </td> <td> Fire Event </td> <td> The mean longitude of all AFDs in the fire event. </td> </tr> <tr> <td> MIN_ACQ_DAT </td> <td> Fire Event </td> <td> The minimum acquisition date of all AFDs in the fire event (i.e., the ignition AFD detection date). </td> </tr> <tr> <td> MAX_ACQ_DAT </td> <td> Fire Event </td> <td> The maximum acquisition date of all AFDs in the fire event (i.e., the ignition AFD detection date). </td> </tr> <tr> <td> MIN_acq_yer </td> <td> Fire Event </td> <td> The year in which the earliest AFD of the fire event was detected. </td> </tr> <tr> <td> MIN_acq_mnt </td> <td> Fire Event </td> <td> The month in which the earliest AFD of the fire event (i.e., ignition AFD) was detected. Months are coded numerically, e.g., 1=January, 12=December. </td> </tr> <tr> <td> MAX_acq_mnt </td> <td> Fire Event </td> <td> The month in which the latest AFD of the fire event was detected. Months are coded numerically, e.g., 1=January, 12=December. </td> </tr> <tr> <td> MIN_yday </td> <td> Fire Event </td> <td> The detection day of year of the earliest AFD of the fire event, i.e., ignition AFD. Day of year is denoted numerically, where 1=January 1 and 365=December 31. </td> </tr> <tr> <td> MAX_yday </td> <td> Fire Event </td> <td> The detection day of year of the latest AFD of the fire event, i.e., ignition AFD. Day of year is denoted numerically, where 1=January 1 and 365=December 31. </td> </tr> <tr> <td> RANGE_yday </td> <td> Fire Event </td> <td> The number of days of duration of the fire event, defined as [MAX_yday]-[MIN_yday] </td> </tr> <tr> <td> FIRST_subst_r </td> <td> AFD </td> <td> Text labels denoting the Indonesian island/region of data processing, e.g., Kalimantan, Papua. </td> </tr> <tr> <td> AF_Count </td> <td> Fire Event </td> <td> Number of AFDs in the fire event. </td> </tr> <tr> <td> nfireID2 </td> <td> Fire Event </td> <td> The unique ID of the fire event to which the AFD belongs. </td> </tr> <tr> <td> Island </td> <td> AFD </td> <td> Numerical values coding for major Indonesian islands/region: 1000000=Sumatra; 2000000=Kalimantan; 3000000=Sulawesi; 4000000=Papua. </td> </tr> <tr> <td> FRP_Days </td> <td> Fire Event </td> <td> The severity of the fire event, as defined by Sloan et al., equal to [Sum_FRP] * ([Range_yday]+1). </td> </tr> <tr> <td> IG_Count </td> <td> Fire Event </td> <td> Number of ignition AFDs in the fire event </td> </tr> <tr> <td> CCI_LC2002 </td> <td> </td> <td> The land-cover class coincident with the AFD. The class is coded by a numerical value as per the left-most column in the table in Section 5.3. The class is that observed for the calendar year in which the AFD occurred, where the year #### is denoted in the field name 'CCI_LC####'. The land-cover data source is as described in Section 5.3. </td> </tr> <tr> <td> CCI_LC2003 </td> <td> </td> </tr> <tr> <td> CCI_LC2004 </td> <td> </td> </tr> <tr> <td> CCI_LC2005 </td> <td> </td> </tr> <tr> <td> CCI_LC2006 </td> <td> </td> </tr> <tr> <td> CCI_LC2007 </td> <td> </td> </tr> <tr> <td> CCI_LC2008 </td> <td> </td> </tr> <tr> <td> CCI_LC2009 </td> <td> </td> </tr> <tr> <td> CCI_LC2010 </td> <td> </td> </tr> <tr> <td> CCI_LC2011 </td> <td> </td> </tr> <tr> <td> CCI_LC2012 </td> <td> </td> </tr> <tr> <td> CCI_LC2013 </td> <td> </td> </tr> <tr> <td> CCI_LC2014 </td> <td> </td> </tr> <tr> <td> CCI_LC2015 </td> <td> </td> </tr> <tr> <td> CCI_LC2016 </td> <td> </td> </tr> <tr> <td> CCI_LC2017 </td> <td> </td> </tr> <tr> <td> CCI_LC2018 </td> <td> </td> </tr> <tr> <td> CCI_LC2019 </td> <td> </td> </tr> <tr> <td> Region </td> <td> AFD </td> <td> Text labels denote whether the AFD occurs within one of the two focal regions of Sloan et al.: Southern Kalimantan, or Central South Sumatra. </td> </tr> <tr> <td> POINT_X </td> <td> AFD </td> <td> Longitude, given as decimal degrees with WGS84 datum. </td> </tr> <tr> <td> POINT_Y </td> <td> AFD </td> <td> Latitude, given as decimal degrees with WGS84 datum. </td> </tr> <tr> <td> POINT_Z </td> <td> -- </td> <td> Ignore. </td> </tr> <tr> <td> POINT_M </td> <td> -- </td> <td> Ignore. </td> </tr> </tbody> </table> 5.2 DATASET nfire4_all_spatial_fire_2002_2019_igs_sp_LC <table class="MsoTableGrid"> <tbody> <tr> <td> Field Name </td> <td> Geography of Attribute Value </td> <td> Definition </td> </tr> <tr> <td> OID </td> <td> AFD </td> <td> Object ID value. Unique values for each AFD (record) in the GIS-formatted data file when viewed in ArcGIS. Field values are -1 in the CSV-formatted data file. </td> </tr> <tr> <td> IG_Count </td> <td> Fire Event </td> <td> Number of ignition AFDs in the fire event. </td> </tr> <tr> <td> MIN_acq_yer </td> <td> Fire Event </td> <td> The year in which the earliest AFD of the fire event was detected. </td> </tr> <tr> <td> MIN_acq_mnt </td> <td> Fire Event </td> <td> The month in which the earliest AFD of the fire event (i.e., ignition AFD) was detected. Months are coded numerically, e.g., 1=January, 12=December. </td> </tr> <tr> <td> FIRST_subst_r </td> <td> AFD </td> <td> Text labels denoting the Indonesian island/region of data processing, e.g., Kalimantan, Papua. </td> </tr> <tr> <td> MIN_yday </td> <td> Fire Event </td> <td> The detection day of year of the earliest AFD of the fire event, i.e., ignition AFD. Day of year is denoted numerically, where 1=January 1 and 365=December 31. </td> </tr> <tr> <td> nfireID2 </td> <td> Fire Event </td> <td> The unique ID of the fire event to which the AFD belongs. </td> </tr> <tr> <td> CCI_LC2002 </td> <td> AFD </td> <td> The land-cover class coincident with the AFD. The class is coded by a numerical value as per the left-most column in the table in Section 5.3. The class is that observed for the calendar year in which the AFD occurred, where the year #### is denoted in the field name 'CCI_LC####'. The land-cover data source is as described in Section 5.3. </td> </tr> <tr> <td> CCI_LC2003 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2004 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2005 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2006 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2007 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2008 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2009 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2010 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2011 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2012 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2013 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2014 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2015 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2016 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2017 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2018 </td> <td> AFD </td> </tr> <tr> <td> CCI_LC2019 </td> <td> AFD </td> </tr> <tr> <td> Region </td> <td> AFD </td> <td> Text labels denote whether the AFD occurs within one of the two focal regions of Sloan et al.: Southern Kalimantan, or Central South Sumatra. </td> </tr> <tr> <td> Peat </td> <td> AFD </td> <td> Denotes whether the AFD occurs on peatlands (value=1) as defined in Sloan et al. </td> </tr> <tr> <td> POINT_X </td> <td> AFD </td> <td> Longitude, given as decimal degrees with WGS84 datum. </td> </tr> <tr> <td> POINT_Y </td> <td> AFD </td> <td> Latitude, given as decimal degrees with WGS84 datum. </td> </tr> <tr> <td> POINT_Z </td> <td> -- </td> <td> Ignore. </td> </tr> <tr> <td> POINT_M </td> <td> -- </td> <td> Ignore. </td> </tr> </tbody> </table> 5.3. LAND-COVER ATTRIBUTE DATA As noted in Section 5.1 and Section 5.2, the nominal values of the attribute fields 'CCI_LC####' correspond to column 1 of the table below. These hierarchical values, and their corresponding land-cover classes labels in column 2 of the table, pertain to the land-cover classification of the Copernicus Climate Change Initiative Land-Cover Product of the European Space Agency. This classification has an annual temporal resolution and 300-meter spatial resolution. Pertinent citations for these land-cover data are below: ESA. Annual land-cover product, 1992 to 2019/present, based on MERIS 300-m and ancillary SPOT, AVHRR, Sentinel-3 and PROB-V satellite data. European Space Agency (ESA) European Centre for Medium-Range Weather Forecasts (ECMFW) Copernicus Climate Change Service (C3S) Climate Change Initiative (CCI), <a href="https://cds.climate.copernicus.eu/cdsapp#!/dataset/satellite-land-cover?tab=overview">https://cds.climate.copernicus.eu/cdsapp#!/dataset/satellite-land-cover?tab=overview</a>; <a href="http://maps.elie.ucl.ac.be/CCI/viewer/download.php">http://maps.elie.ucl.ac.be/CCI/viewer/download.php</a>; <a href="http://www.esa-landcover-cci.org/">http://www.esa-landcover-cci.org/</a> (2020). Pérez-Hoyos, A., Rembold, F., Kerdiles, H. & Gallego, J. Comparison of global land cover datasets for cropland monitoring. Remote Sensing 9, (2017). Columns 3 and 4 in the table below illustrate how the original land-cover classes of the Copernicus Climate Change Initiative Land-Cover Product were reclassified for analysis in Sloan et al. <table class="MsoNormalTable"> <tbody> <tr> <td> 1. CCI-LC Class Value </td> <td> 2. CCI-LC Class Label </td> <td> 3. New Class Value for Sloan et al. </td> <td> 4. New Class Label for Sloan et al. </td> </tr> <tr> <td> 0 </td> <td> No Data </td> <td> 0 </td> <td> No Data </td> </tr> <tr> <td> 10 </td> <td> Cropland, rainfed </td> <td> 1 </td> <td> Cleared/Cultivated </td> </tr> <tr> <td> 11 </td> <td> Herbaceous cover </td> <td> 1 </td> <td> Cleared/Cultivated </td> </tr> <tr> <td> 12 </td> <td> Tree or shrub cover </td> <td> 1 </td> <td> Cleared/Cultivated </td> </tr> <tr> <td> 20 </td> <td> Cropland, irrigated or post‐flooding </td> <td> 1 </td> <td> Cleared/Cultivated </td> </tr> <tr> <td> 30 </td> <td> Mosaic cropland (>50%) / natural vegetation (tree, shrub, herbaceous cover) (<50%) </td> <td> 2 </td> <td> Mosaic Cropland </td> </tr> <tr> <td> 40 </td> <td> Mosaic natural vegetation (tree, shrub, herbaceous cover) (>50%) / cropland (<50%) </td> <td> 3 </td> <td> Mosaic Natural Veg </td> </tr> <tr> <td> 50 </td> <td> Tree cover, broadleaved, evergreen, closed to open (>15%) </td> <td> 4 </td> <td> Forest </td> </tr> <tr> <td> 60 </td> <td> Tree cover, broadleaved, deciduous, closed to open (>15%) </td> <td> 4 </td> <td> Forest </td> </tr> <tr> <td> 61 </td> <td> Tree cover, broadleaved, deciduous, closed (>40%) </td> <td> 4 </td> <td> Forest </td> </tr> <tr> <td> 62 </td> <td> Tree cover, broadleaved, deciduous, open (15‐40%) </td> <td> 4 </td> <td> Forest </td> </tr> <tr> <td> 70 </td> <td> Tree cover, needleleaved, evergreen, closed to open (>15%) </td> <td> 4 </td> <td> Forest </td> </tr> <tr> <td> 71 </td> <td> Tree cover, needleleaved, evergreen, closed (>40%) </td> <td> 4 </td> <td> Forest </td> </tr> <tr> <td> 72 </td> <td> Tree cover, needleleaved, evergreen, open (15‐40%) </td> <td> 4 </td> <td> Forest </td> </tr> <tr> <td> 80 </td> <td> Tree cover, needleleaved, deciduous, closed to open (>15%) </td> <td> 4 </td> <td> Forest </td> </tr> <tr> <td> 81 </td> <td> Tree cover, needleleaved, deciduous, closed (>40%) </td> <td> 4 </td> <td> Forest </td> </tr> <tr> <td> 82 </td> <td> Tree cover, needleleaved, deciduous, open (15‐40%) </td> <td> 4 </td> <td> Forest </td> </tr> <tr> <td> 90 </td> <td> Tree cover, mixed leaf type (broadleaved and needleleaved) </td> <td> 4 </td> <td> Forest </td> </tr> <tr> <td> 100 </td> <td> Mosaic tree and shrub (>50%) / herbaceous cover (<50%) </td> <td> 5 </td> <td> Mosaic Shrubland </td> </tr> <tr> <td> 110 </td> <td> Mosaic herbaceous cover (>50%) / tree and shrub (<50%) </td> <td> 5 </td> <td> Mosaic Shrubland </td> </tr> <tr> <td> 120 </td> <td> Shrubland </td> <td> 6 </td> <td> Low/Sparse Vegetation </td> </tr> <tr> <td> 121 </td> <td> Evergreen shrubland </td> <td> 6 </td> <td> Low/Sparse Vegetation </td> </tr> <tr> <td> 122 </td> <td> Deciduous shrubland </td> <td> 6 </td> <td> Low/Sparse Vegetation </td> </tr> <tr> <td> 130 </td> <td> Grassland </td> <td> 6 </td> <td> Low/Sparse Vegetation </td> </tr> <tr> <td> 140 </td> <td> Lichens and mosses </td> <td> 6 </td> <td> Low/Sparse Vegetation </td> </tr> <tr> <td> 150 </td> <td> Sparse vegetation (tree, shrub, herbaceous cover) (<15%) </td> <td> 6 </td> <td> Low/Sparse Vegetation </td> </tr> <tr> <td> 151 </td> <td> Sparse tree (<15%) </td> <td> 6 </td> <td> Low/Sparse Vegetation </td> </tr> <tr> <td> 152 </td> <td> Sparse shrub (<15%) </td> <td> 6 </td> <td> Low/Sparse Vegetation </td> </tr> <tr> <td> 153 </td> <td> Sparse herbaceous cover (<15%) </td> <td> 6 </td> <td> Low/Sparse Vegetation </td> </tr> <tr> <td> 160 </td> <td> Tree cover, flooded, fresh or brakish water </td> <td> 7 </td> <td> Flooded Vegetation </td> </tr> <tr> <td> 170 </td> <td> Tree cover, flooded, saline water </td> <td> 7 </td> <td> Flooded Vegetation </td> </tr> <tr> <td> 180 </td> <td> Shrub or herbaceous cover, flooded, fresh/saline/brakish water </td> <td> 7 </td> <td> Flooded Vegetation </td> </tr> <tr> <td> 190 </td> <td> Urban areas </td> <td> 8 </td> <td> Other </td> </tr> <tr> <td> 200 </td> <td> Bare areas </td> <td> 8 </td> <td> Other </td> </tr> <tr> <td> 201 </td> <td> Consolidated bare areas </td> <td> 8 </td> <td> Other </td> </tr> <tr> <td> 202 </td> <td> Unconsolidated bare areas </td> <td> 8 </td> <td> Other </td> </tr> <tr> <td> 210 </td> <td> Water bodies </td> <td> 8 </td> <td> Other </td> </tr> </tbody> </table>

opencc-zeroAug 2022View details →

opencc-by-nc-nd-1.0Jun 2024View details →

DNS dataset for modelling homogeneous ignition processes of clustering solid particle clouds in isotropic turbulence

<h2>Abstract</h2> This dataset is being published to enable the development of models for igniting and combusting solid particles in isotropic turbulence using flamelet tabulated chemistry. This dataset is generated using the forced homogeneous isotropic turbulence in order to investigate the effect of active turbulent forces on the ignition of particles, and it is used as the supplementary material for the manuscript "Modeling homogeneous ignition processes of clustering solid particle clouds in isotropic turbulence", which was accepted for publication in the special issue of Fuel Journal for the proceeding of the 4th international Oxyflame workshop. The particles are chosen to have near unity Stokes numbers, which promote particle clustering to study the ignition phenomenon for particle clusters, which is common during ignition and combustion of particle clouds in large industrial solid fuel-powered burners. Since the ignition process of clustering solid particle clouds is transient, different time instances during the ignition process are presented to facilitate the modelling effort for the transient ignition behaviour of the particles. The dataset consists of gas-phase data, particle data and the most important routines required to process the dataset.    This database is a valuable resource for users developing solid fuel ignition and combustion in turbulent conditions.  It should be noted that this dataset is a reduced version of the full dataset in order to size limitations in the sharing platforms. More information and full dataset can be provided upon request. For more information, contact: p.farmand@itv.rwth-aachen.de <h2>Technical details</h2> The data provided in this dataset contains gas phase data, particle data, and some post-processing scripts for visualization of the data. The data is generated in forced homogeneous isotropic turbulence (HIT) with an initial preferential concentration of the particles in a hot atmosphere to study the impact of particle clustering on ignition. Simulations were performed within a region with the physical size of 12.8mm * 12.8mm * 12.8mm with periodic boundary conditions in all directions. The domain size is discretized with a three-dimensional cartesian mesh with a resolution of Δx = 50 μm. A forced isotropic turbulent field with Re_λ=30 and the Kolmogorov length scale η =100 microns has been chosen. The dispersed phase consists of 10,000 particles of Colombian coal with D_p= 20 microns and T0=300K and with an apparent density of 700kg/m3. Non-reactive particles are first randomly distributed in the box filled with air with 20% oxygen and an initial gas temperature of T = 1500K, which is relevant to practical PCC applications. These conditions lead to an initial Stokes number of around 5, for which a clustering behaviour in particle cloud motion is expected. The employed forced isotropic turbulence ensures maintaining the same turbulence statistics during non-reactive and reactive simulations, as summarised in the following table: <table> <tbody> <tr> <td> time [ms] </td> <td> Re_λ </td> <td> Re_Turb </td> <td> η[m] </td> <td> l_t[m] </td> <td> t_η[ms] </td> <td> t_l[ms] </td> <td> St </td> </tr> <tr> <td>0</td> <td>30.7</td> <td>141.8</td> <td>1.04e-4</td> <td>4.27e-3</td> <td>4.47e-2</td> <td>5.33e-1</td> <td>6.199</td> </tr> <tr> <td>0.46</td> <td>30.9</td> <td>143.9</td> <td>9.94e-5</td> <td>4.13e-3</td> <td>4.16e-2</td> <td>4.99e-1</td> <td>6.207</td> </tr> <tr> <td>0.5</td> <td>30.5</td> <td>140.1</td> <td>9.96e-5</td> <td>4.06e-3</td> <td>4.27e-2</td> <td>5.05e-1</td> <td>6.333</td> </tr> <tr> <td>0.55</td> <td>29.4</td> <td>129.8</td> <td>1.01e-4</td> <td>3.88e-3</td> <td>4.34e-2</td> <td>4.94e-1</td> <td>6.032</td> </tr> <tr> <td>0.6</td> <td>28.5</td> <td>122.1</td> <td>1.02e-4</td> <td>3.76e-3</td> <td>4.46e-2</td> <td>4.92e-1</td> <td>5.775</td> </tr> <tr> <td>0.65</td> <td>27.7</td> <td>115.2</td> <td>1.04e-4</td> <td>3.66e-3</td> <td>4.48e-2</td> <td>4.81e-1</td> <td>5.365</td> </tr> </tbody> </table> η and t_η are the respective Kolmogorov length and time scales, and l_t and t_l correspond to the integral length and time scales.   <h3>Gas phase and particle data:</h3> The gas phase data has HDF5 formation, which contains selected scalars relevant to model developments. Since the ignition process is a transient process, two different time instances, t=0.5ms with the maximum number of ignited regions during the ignition process and t=0.65ms at the end of the ignition process, are chosen. Before starting the reactive simulations, a non-reactive simulation for 20.5ms was performed to form the particle clusters, and then the reactive simulation was started. Therefore, the data.out_2.100E-02.h5 corresponds to t = 0.5ms and data.out_2.115E-02.h5 corresponds to t = 0.65ms. Each HDF5 dataset has the following structure: Group Flow: <ul> <li>U, V, W</li> </ul> Group scalar:  <ul> <li>CO, CO2, H2O, C2H2, O2, N2, OH, progress variable (PV), temperature(T), enthalpy(h), heat capacity (Cp), density(RHO), pressure(P), mixture fraction(Z), dissipation rate, heat conductivity</li> </ul> Group C_dot: <ul> <li>Molar production rate of CO, CO2, O2, OH</li> </ul> Group ST: <ul> <li>Mass fraction rate of OH</li> </ul> Group var (data required for subfilter analysis and PDF modelling): <ul> <li>RHO * h</li> <li>RHO * h * h</li> <li>RHO * PV</li> <li>RHO * PV * PV</li> <li>RHO * RHO</li> <li>RHO * RHO * RHO</li> <li>RHO * T</li> <li>RHO * T * T</li> <li>RHO * Z</li> <li>RHO * Z * Z</li> </ul> These gas phase data can be used to study the Eulerian field, which is impacted by the particles through the source terms, which are obtained from the Lagrangian framework. For the particle data, two CSV files containing information about each particle's position and temperature are provided.  In each CSV file, which corresponds to the same time instance as the gas phase data, this structure can be found: <ul> <li>Points_0, Points_1, Points_2: particle position x,y,z</li> <li>coal_defaultT: particle temperature</li> </ul> <h3>Scripts:</h3> Different scripts are provided for a reader to enable the first-time use of the data, such as visualising the gas phase quantities, calculating the conditional mean and statistical analysis, and clustering analysis for the particles. Here is a brief information regarding the scripts: <ul> <li>hdf5_2D_Con_Mean_Plots.m: This script can be used for loading the HDF5 file and visualising the field, joint PDF, and joint correlation of different quantities with respect to different parameters. This script requires another module to calculate the conditional mean of the data.</li> <li>Compute_ConditionalMean_histograms_2D.m: This module calculates the conditional average of a 2D array.</li> <li>clustering_voronoi_3D.m: This script can analyse the particle data and calculate the clustering limit based on the Voronoi algorithm. It can also filter the clustered particles and separate different clusters using the nearest neighbour and DB-SCAN methods.</li> </ul>

opencc-by-4.0Jan 2018View details →

Human-related ignitions increase the number of large wildfires across U.S. ecoregions

This data was used in the analysis in the article "Human-related ignitions increase the number of large wildfires across U.S. ecoregions" by R. Chelsea Nagy, Emily Fusco, Bethany Bradley, John T. Abatzoglou, and Jennifer Balch. This article was accepted for publication in the journal Fire on 22 January 2018.

opencc-by-4.0Mar 2019View details →

Carbon Shell or Core Ignitions in White Dwarfs Accreting from Helium Stars

MESA inlists and run_star_extras associated with <a href="https://ui.adsabs.harvard.edu/?#abs/2016ApJ...821...28B">Brooks et al. (2016)</a>. MESA version 7624. Publication DOI: <a href="https://doi.org/10.3847/0004-637X/821/1/28">10.3847/0004-637X/821/1/28</a>

opencc-by-3.0-usOct 2023View details →

Ignition Delay Test with Spray & Combustion Vessel

Ignition delay test results of different fuels (RON60, RON70, RON80, RON90, and biofuel blends) under different engine operating conditions with a multi-hole injector. These results were used to better understand the spray and combustion characteristics and validate the CFD real fuel model (https://doi.org/10.5281/zenodo.8432075). This work was part of the DOE funded project (DE-EE0008478; Co-optimized Mixed-Mode Engine and Fuel Demonstrator for Improved Fuel Economy while Meeting Emissions Requirements; https://doi.org/10.2172/1887341).