Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
2,235
datasets available to search
ShareScore release 0.9.0
Dataset results
2,235 results for “Engine”
Supervised land cover classification using Google Earth Engine in Córdoba, Argentina, 2018-2020
Land cover information is critical to scientific, economic, and public policy-making. There is a high demand for accurate and timely land cover information that affects the accuracy of all subsequent applications. The availability of Google Earth Engine (GEE), which derives temporal aggregation methods from time-series images (i.e., the use of metrics such as mean or median), has also enabled optimization of computation time, such as managing large amounts of data to obtain more accurate results. Our objective was to obtain a land cover map for the northwest of the province of Córdoba, Argentina. The study was carried out in rural communities that belong to the departments of Cruz del Eje and Ischilín, northwest of Córdoba, and have different degrees of intervention in the land cover. Sentinel 2 Level 2A images were acquired for the study area. Images available from January 1, 2018, to December 31, 2020, were sampled. To create a thematic map, the median value was calculated for the sample of images from the selected time interval. Finally, the Normalized Difference Vegetation Index (NDVI) was calculated and added to the total bands of the median image. Training polygons were placed there considering the visual features in the median image. The Random Forest algorithm was used as the classification method. To verify the quality of the classified map, a list of 97,753 verification pixels was obtained. In addition, a confusion matrix was created to collect the conflicts that arise between categories, and the precision and kappa coefficient was calculated to define the quality of the map obtained. Image acquisition, preprocessing, and analysis were performed on the Google Earth Engine platform. Thematic maps with eight classes were obtained, with a total area of 719880 ha. The confusion matrix showed an overall precision of 99.26% and a corrected kappa index of 0.99, the classes were correctly classified by the algorithm.
Augmented emission maps: 1968 cc 55 kW Euro 6 diesel engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 1968 cc 55 kW Euro 6 diesel engine that has been applied in the Volkswagen Caddy.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI 10.5281/zenodo refers to a meta-data document that provides the full description of the standardized emission map.</p>
Detecting Changes in the Caenorhabditis elegans Intestinal Environment Using an Engineered Bacterial Biosensor
<p>Data for the figures in the manuscript <br> <a href="https://pubs.acs.org/doi/10.1021/acssynbio.9b00166">https://pubs.acs.org/doi/10.1021/acssynbio.9b00166</a></p> <p>Abstract:<br> <em>Caenorhabditis elegans</em> has become a key model organism within biology. In particular, the transparent gut, rapid growing time, and ability to create a defined gut microbiota make it an ideal candidate organism for understanding and engineering the host microbiota. Here we present the development of an experimental model that can be used to characterize whole-cell bacterial biosensors <em>in vivo</em>. A dual-plasmid sensor system responding to isopropyl β-d-1-thiogalactopyranoside was developed and fully characterized <em>in vitro</em>. Subsequently, we show that the sensor was capable of detecting and reporting on changes in the intestinal environment of <em>C. elegans</em> after introducing an exogenous inducer into the environment. The protocols presented here may be used to aid the rational design of engineered bacterial circuits, primarily for diagnostic applications. In addition, the model system may serve to reduce the use of current animal models and aid in the exploration of complex questions within general nematode and host–microbe biology.</p>
Release Engineering Posts
<p>Release engineers are continuously required to de-liver high-quality software products to the end-user. As a result, modern software companies are proposing new changes in their delivery process that adapt to new technologies such as continuous deployment and Infrastructure-as-Code. However, developers and release engineers still find these practices challenging, and resort to question and answer websites such as StackOverflow to find answers. This paper presents the results of our empirical study on release engineering questions in StackOverflow, to understand the modern release engineering topics of interest and their difficulty. Using topic modeling techniques, we find that (i)developers discuss on a broader range of38release engineering topics covering all the six phases of modern release engineering,(ii) the topics Merge Conflict, Branching & Remote Upstream are more popular, while topics Code review, Web deployment,MobileApp Debugging & Deployment, Continuous Deployment are less popular yet more complicated, (iii) - Particularly, the release engineering topic “security” is both popular and difficult according to data collected from StackOverflow</p>
The Daily Life of Software Engineers during the COVID-19 Pandemic -- Replication Package
<p>Following the onset of the COVID-19 pandemic and subsequent lockdowns, software engineers' daily life was disrupted and abruptly forced into remote working from home. This change deeply impacted typical working routines, affecting both well-being and productivity. Moreover, this pandemic will have long-lasting effects in the software industry, with several tech companies allowing their employees to work from home indefinitely if they wish to do so. Therefore, it is crucial to analyze and understand how a typical working day looks like when working from home and how individual activities affect software developers' well-being and productivity. We performed a two-wave longitudinal study involving almost 200 globally carefully selected software professionals, inferring daily activities with perceived well-being, productivity, and other relevant psychological and social variables. Results suggest that the time software engineers spent doing specific activities from home was similar when working in the office. (e.g., coding > emails > code review > networking). However, we also found some meaningful mean differences. The amount of time developers spent on each activity was unrelated to their well-being, perceived productivity, and other variables. We conclude that working remotely is not per se a challenge for organizations or developers.</p>
Uncovering the Triplet Ground State of Triangular Graphene Nanoflakes Engineered with Atomic Precision on a Metal Surface
<p>OPEN DATA related to the research publication:</p> <p>J. Li, S. Sanz, J. Castro-Esteban, M. Vilas-Varela, N. Friedrich, T. Frederiksen, D. Peña, and J. I. Pascual, <em>Uncovering the triplet ground state of triangular graphene nanoflakes engineered with atomic precision on a metal surface</em>, Phys. Rev. Lett. <strong>124</strong>, 177201 (2020) [arXiv:1912.08298]</p> <p>Abstract: Graphene can develop large magnetic moments in custom-crafted open-shell nanostructures such as triangulene, a triangular piece of graphene with zigzag edges. Current methods of engineering graphene nanosystems on surfaces succeeded in producing atomically precise open-shell structures, but demonstration of their net spin remains elusive to date. Here, we fabricate triangulenelike graphene systems and demonstrate that they possess a spin S=1 ground state. Scanning tunneling spectroscopy identifies the fingerprint of an underscreened S=1 Kondo state on these flakes at low temperatures, signaling the dominant ferromagnetic interactions between two spins. Combined with simulations based on the meanfield Hubbard model, we show that this S=1 π paramagnetism is robust and can be turned into an S=1/2 state by additional H atoms attached to the radical sites. Our results demonstrate that π paramagnetism of high-spin graphene flakes can survive on surfaces, opening the door to study the quantum behavior of interacting π spins in graphene systems.</p>
Augmented emission maps: 998 cc 74 kW Euro 6dT petrol engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 998 cc 74 kW Euro 6dT petrol engine that has been applied in the Ford Fiesta, Ecosport, Transit Courier.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 1969 cc 140 kW Euro 6dT diesel engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 1969 cc 140 kW Euro 6dT diesel engine that has been applied in the Volvo XC40, V60, XC60, V90, and S90.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 1950 cc 110 kW Euro 6c diesel engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 1950 cc 110 kW Euro 6c diesel engine that has been applied in the Mercedes E200D.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 1596 cc 74 kW Euro 3 petrol engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 1596 cc 74 kW Euro 3 petrol engine that has been applied in the Ford.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 2191 cc 110 kW Euro 6b diesel engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 2191 cc 110 kW Euro 6b diesel engine that has been applied in the Mazda.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 1242 cc 48 kW Euro 4 petrol engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 1242 cc 48 kW Euro 4 petrol engine that has been applied in the Fiat Punto, Doblo.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 1560 cc 73 kW Euro 6b diesel engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 1560 cc 73 kW Euro 6b diesel engine that has been applied in the - Peugeot Partner, 208, and 2008, Citroen C4 Cactus, Berlingo, C3, and DS3.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 1968 cc 100 kW Euro 5b diesel engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 1968 cc 100 kW Euro 5b diesel engine that has been applied in the Volkswagen Crafter, Passat, Sharan, and Tiguan, Audi A3, Q3, A4, A5, and A6, Seat Alhambra.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 2993 cc 190 kW Euro 6b diesel engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 2993 cc 190 kW Euro 56b diesel engine that has been applied in the BMW.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 1499 cc 96 kW Euro 6dT diesel engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 1499 cc 96 kW Euro 6dT diesel engine that has been applied in the Peugeot 308, 3008, 508, 5008, and Partner, Opel Grandland X and Combo, Citroen Berlingo, C4 Spacetourer, and C5 Aircross, DS 7 Crossback.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 1199 cc 55 kW Euro 4 petrol engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 1199 cc 55 kW Euro 4 petrol engine that has been applied in the Opel Corsa, Agila, and Astra.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 1587 cc 80 kW Euro 3 petrol engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 1587 cc 80 kW Euro 3 petrol engine that has been applied in the Citroen Berlingo, C2, C3, C3 Pluriel, C4, and Xsara. Peugeot 206, 307, and Partner.<br> NB: this is only the PSA cars. The Volvos have alliance code VOLV and have a different engine.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 1124 cc 44 kW Euro 3 petrol engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 11124 cc 44 kW Euro 3 petrol engine that has been applied in the Peugeot 106, 206, and Partner. Citroen Saxo, C2, C3, and Berlingo.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
Augmented emission maps: 1997 cc 100 kW Euro 3 petrol engine
<p>In order to enable the sharing of data the emission data for vehicles is standardized. The data exchange format contains all data that is applicable for a specific engine taxonomy code.</p> <p>This specific data set refers to the 1997 cc 100 kW Euro 3 petrol engine that has been applied in the Citroen C4, C5, C8, Xsara, and Xsara Picasso. Peugeot 206, 307, 406, 407, 607, 806, 807, and Expert.</p> <p>The standardized emission map has a “.map.txt” extension and is also human readable. The files starts with metadata which contains information about:</p> <ul> <li>the engine taxonomy code,</li> <li>total driven kilometers over which the data was gathered,</li> <li>total time in hours over which the data was gathered,</li> <li>the number of vehicles which were tested to create the emission map,</li> <li>the DOI (Digital Object Identifier) reference,</li> <li>Which emission maps are available in the file.</li> </ul> <p>The DOI <a href="http://doi.org/10.5281/zenodo.4268034">http://doi.org/10.5281/zenodo.4268034</a> refers to a updated meta-data document that provides the full description of the standardized emission map.</p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.