Skip to main content
Powered by ShareScore

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.

3,377

datasets available to search

ShareScore release 0.9.0

Reset

Dataset results

3,377 results for “scan”

Learn how ShareScore rates datasets ↗
zenodo44/100

3D scans of two types of railway ballast including shape analysis information

<p>This data set contains 3D scanner data of two types of railway ballast &ldquo;Calcite&rdquo; (stems from Croatia) and &ldquo;Kieselkalk&rdquo;, also known as Helvetic Siliceous Limestone, (stems from Switzerland).<br> From each type of ballast 25 stones are scanned. The files are provided in .ply format.<br> For the scanned meshes several shape descriptors are provided: elongation, flatness, sphericity, convexity index.<br> Additional to the 3D scans, both simplified and rounded versions of the meshes are included.<br> For these meshes information on three different angularity indices are available.<br> The scanned ballast types are the same, as&nbsp; previously investigated in uniaxial compression tests and direct shear tests:<br> Suhr, Bettina, &amp; Six, Klaus. (2018).<br> &quot;Compression tests and direct shear test of two types of railway ballast [Data set]&quot;<br> Zenodo. http://doi.org/10.5281/zenodo.1423742</p> <p>&nbsp;</p> <p>A detailed shape analysis of the results is conducted in:<br> Bettina Suhr, William A. Skipper, Roger Lewis, and Klaus Six<br> &quot;Shape analysis of railway ballast stones: curvature-based calculation of particle angularity&quot;<br> <em>Scientific Reports, </em><strong>2020</strong><em>, 10</em>, 6045<br> DOI: https://doi.org/10.1038/s41598-020-62827-w</p> <p>A summary of several shape descriptors can be found in:<br> B. Suhr and K. Six:<br> &quot;Simple particle shapes for DEM simulations of railway ballast --&nbsp; influence of shape descriptors on packing behaviour&quot;<br> Granular Matter, <strong>2020</strong><em>, 22</em><br> DOI: https://doi.org/10.1007/s10035-020-1009-0</p> <p><br> This data set is organised as follows:<br> 1_ScanMeshesCleaned<br> &nbsp;&nbsp;&nbsp; scanned meshes:<br> &nbsp;&nbsp;&nbsp; K_1.ply&nbsp; -&nbsp; K_25.ply Calcite (German: Kalzit)<br> &nbsp;&nbsp;&nbsp; KK_1.ply - KK_25.ply Kieselkalk<br> 2_CSE1 &nbsp;<br> &nbsp;&nbsp;&nbsp; simplifications of the scanned meshes, little simplifications, used in the detailed shape analysis<br> &nbsp;&nbsp;&nbsp; CSE1_AngInfo.csv: contains values of three different angularity indices used in the detailed shape analysis<br> 3_CSE2 &nbsp;<br> &nbsp;&nbsp;&nbsp; simplifications of the scanned meshes, more simplified, used in the detailed shape analysis<br> &nbsp;&nbsp;&nbsp; CSE2_AngInfo.csv: contains values of three different angularity indices used in the detailed shape analysis<br> 4_CSE3 &nbsp;<br> &nbsp;&nbsp;&nbsp; simplifications of the scanned meshes, even more simplified, used in the detailed shape analysis<br> &nbsp;&nbsp;&nbsp; CSE3_AngInfo.csv: contains values of three different angularity indices used in the detailed shape analysis<br> 5_CSE4 &nbsp;<br> &nbsp;&nbsp;&nbsp; simplifications of the scanned meshes, most simplified, used in the detailed shape analysis<br> &nbsp;&nbsp;&nbsp; CSE4_AngInfo.csv: contains values of three different angularity indices used in the detailed shape analysis<br> 6_RoundedMeshes<br> &nbsp;&nbsp;&nbsp; artificially rounded versions of the scanned ballast meshes, used in the detailed shape analysis<br> &nbsp;&nbsp;&nbsp; RoundedMeshes_AngInfo.csv: contains values of three different angularity indices used in the detailed shape analysis<br> 7_TestBodies &nbsp;<br> &nbsp;&nbsp;&nbsp; meshes of artificial test bodies, constructed for testing different angularity indices in the detailed shape analysis<br> &nbsp;&nbsp;&nbsp; TestBodies_AngInfo.csv: contains values of three different angularity indices used in the detailed shape analysis<br> scanMeshesInfo.csv: summary of several shape descriptors of the scanned meshes<br> README.txt &nbsp;</p> <p><br> Check the README.txt file for more information on the technical aspects of scanning.</p> <p>&nbsp;</p>

opencc-by-4.0Feb 2020View details →
zenodo44/100

York Archaeological Trust 1984.132.4148 3D Archaeological Use-wear (Incomplete Scan) Raw Measurements

<p>This dataset contains the 25&nbsp;raw measurements/scans&nbsp;taken before the mesh creation step&nbsp;for object&nbsp;1984.132.4148&nbsp;in the collections of York Archaeological Trust.</p> <p>1984.132.4148&nbsp;is a dish. Close analysis was not undertaken at time of data capture. Scanning was not complete. Holes in scan data: one small circle at the very centre of the base of the dish, and gaps in data capture under the rim.&nbsp;</p> <p>Data was captured using a Zeiss Comet L3D 2 5M at 100 FOV to enable the analysis of use-wear on archaeological objects.&nbsp;The model is scaled in millimetres.</p> <p>This dataset consists of 27,629,672 points&nbsp;- additional metadata included in associated spreadsheet.</p>

opencc-by-sa-4.0Jun 2020View details →
zenodo44/100

Scanning electron diffraction tilt series data of an aluminium-steel interface region

<p>This dataset contains scanning electron diffraction (SED) data used in the publication entitled &quot;<strong>Microstructural and mechanical characterisation of a second generation hybrid metal extrusion &amp; bonding aluminium-steel butt joint</strong>&quot;. The data denoted &ldquo;SED_HYB_...&rdquo; were recorded from an aluminium-steel interface region that includes aluminium and steel grains, an interfacial Al-Fe-Si layer, and dispersoids and some oxide particles located within the aluminium region. The nanoscale interfacial intermetallic phase layer is polycrystalline, and to increase the probability of recording data from intermetallic phase crystals oriented close to zone axes, the data were recorded in a tilt series covering 30 degrees, in steps of 1 degree. The file names give the goniometer x-tilt values in degrees, e.g. &quot; SED_HYB_TX-150.hdf5&quot; denotes an x-tilt of -15.0 degrees. SED data recorded from an Au cross-grating specimen, named &quot;SED_AuX.hdf5&quot;, and from a MoO3 specimen, named &quot;SED_MoO3.hdf5&quot;, are also included for calibration purposes.</p>

opencc-by-4.0Nov 2020View details →
zenodo44/100

Terrestrial laser scanning - RIEGL VZ-1000, individual tree point clouds and cylinder models, Belgian hedgerows and tree rows

<p>Terrestrial laser scans were acquired for 69 trees (<em>Quercus&nbsp;robur</em>: 39 trees; <em>Alnus glutinosa</em>: 19 trees; <em>Betula pendula: </em>11 trees) in hedgerows and tree rows in agricultural lands in Flanders, Belgium. We used a RIEGL VZ-1000 terrestrial laser scanner (RIEGL Laser Measurement Systems GmbH, Austria) with a beam divergence of 0.35 mrad operating in the infrared (wavelength 1550 nm) with a range up to 1000 m. We scanned leaf-off and all recorded variables are valid for overbark measurements. Individual trees were manually extracted from the co-registered point cloud in RiSCAN PRO software (provided by RIEGL). To the extracted trees, quantitative structure models (QSM) were fitted. We used the QSMs to derive branch length (m), total wood volume (m&sup3;) and merchantable wood volume (m&sup3;, using only cylinders with diameter &gt; 7 cm). From the point clouds, we extracted the tree structural features such as crown projection (m&sup2;), maximum crown diameter (m) and tree height (m). Biomass expansion factors (BEF)&nbsp;were calculated by dividing total tree volume to merchantable tree volume. We expressed the age dependency of the BEF values via non-linear regression models. See Van Den Berge et al. (2021) for further information (DOI: 10.1007/s12155-021-10250-y).</p>

opencc-by-4.0Jan 2021View details →
zenodo44/100

Fluorescent Confocal Laser Scanning Microscopy of White Blood Cells, Cancer Cell Line MCF7, and Mixtures of these Cells: A Model System for Circulating Tumor Cell Biomarker Evaluation V.1

<p>This is a confocal laser scanning microscopy data set of white blood cells (leukocytes), the cancer cell line MCF7, and mixtures of these cells acquired on a Zeiss LSM 780 microscope in the University of Colorado Anschutz Medical Campus Advanced Light Microscopy Core. Cells are fluorescently labeled for DNA with DAPI (Sigma D9542), lipids with Bodipy 495/503 (Thermo Fisher D3922), the filament protein cytokeratin (CK) with pan-cytokertain-alexa555 antibodies (Cell Signaling Technologies 3478S) and the surface membrane antigen CD45 with CD45-alexa647 antibodies (Biolegend 304020). Bodipy was excited with a continuous wave (CW) 488 nm laser, alexa555 was excited with CW 561 nm laser, and alexa647 was excited with a CW 633 nm laser. The acquiring instrument does not have a CW 405 nm source so DAPI was excited by two photon process using a Coherent Cameleon ultrafast pulsed laser tuned to 765 nm. The objective used was a Zeiss Plan-Apochromat 20x, 0.8 NA, air.</p> <p>The data consists of 4 channel 8x8 mosaic z-stacks. The Zeiss software performed stitching of the mosaics. These stitched data images are included and marked with _Stitched at the end. Those interested in performing the stitching themselves can do this with the raw data files (without the _Stitched). The jpeg images are processed from the stitched LSM images. The LSM files contain additional meta data on the experiment including power levels and acquisition settings.</p> <p>The _Stiched .lsm files will load in ImageJ (tested with V.1.49) as 4 channel 3 stack images.</p> <p>This data is a model system for evaluating the DNA/Lipids/CK/CD45 biomarker panel to identify circulating tumor cells (CTCs). The D- population of the model is the WBCs and the D+ population is the MCF7 cancer cell line. The amount of separation the biomarker panel plus analysis algorithm can produce between these populations (D+/D-) is an estimate the sensitivity and specificity of the biomarker panel plus algorithm to CTCs.</p> <p>Experiments generating the data were performed over the course of 15 days. Peripheral blood samples were collected from the Gynecological Tissue and Fluid Bank (COMIRB 07-0935 / COMIRB 05-1081)&nbsp;from consenting patients undergoing surgery at the University of Colorado Hospital. Blood samples were used the same day they were collected. Blood samples were collected from 3 patients with benign conditions, labeled WBBN#, and 3 patients with ovarian cancer, labeled WBCA#. We do not expect there to be any difference in the isolated white blood cells samples prepared from the cancer and benign patients. Samples were stored at room temperature until white blood cells were isolated. Mixed samples were prepared by passaging a MCF7 flask and mixing it with isolated white blood cells before fixation. A schedule showing the time duration between collection, processing and imaging is included as &ldquo;experimental schedule.gif&rdquo;.</p> <p>The MCF7 cancer cell line was a kind gift from Dr. Heide Ford. Genomic DNA was isolated from the MCF7 cell line after the experiment and sent for cell line authentication. The gDNA was a match to MCF7. The authentication report and data are included in this submission.</p> <p>CD45 antibodies were exhausted on day 7. New antibody was purchased and received on day 8. The day 7 images only has labels for DAPI and Bodipy. The samples prepared with the old antibodies on days 4 and 7 were relabeled and imaged with the new antibodies on days 14 and 15. This labeling was also done to confirm the pan-CK antibodies remained good since they are dim in the MCF7 cells imaged on days 12 and 13. The pan-CK on days 14 and 15 looks the same as it did on days 5 and 7 confirming the antibodies are good.</p> <p>Four of the filters containing cells were not sufficiently flat to be acquired with a 3 slice z-stack so a 5 slice z-stack was used. These files have been zipped to compress them under the 2 GB limit permitted by zenodo.org</p> <p>Further information on how these samples were prepared, processed, and analyzed can be found in our associated 2016 SPIE Photonics West BIOS conference proceeding titled, &ldquo;Quantitative image cytometry measurements of lipids, DNA, CD45 and cytokeratin for circulating tumor cell identification in a model system&rdquo;, http://dx.doi.org/10.1117/12.2222317.</p> <p>This work was supported by funding provided to the University of Colorado Cancer Center by the American Cancer Society and awarded as Institutional Research Grant Number 57-001-53, by funding provided by the Defense Advanced Research Projects Agency under grant number N66001-10-4035, and by funding provided by NIH/NCATS Colorado CTSI Grant Number TL1 TR001081. The University of Colorado Anschutz Medical Campus Advanced Light Microscopy Core is also supported in part by NIH/NCATS Colorado CTSI Grant Number UL1 TR001082. The funders had no role in the study design, data collection, analysis, or&nbsp;decision to publish.</p>

opencc-by-4.0Apr 2016View details →
zenodo44/100

Nitric oxide (NO) data set (60--160 km) from SCIAMACHY mesosphere--lower thermosphere limb scans

<p><strong>Overview</strong><br> Contains the nitric oxide (NO) number densities (in cm<sup>-3</sup>) from 60 km to 160 km retrieved from SCIAMACHY mesosphere--lower thermosphere (MLT, 50--150 km) limb scans.</p> <p>SCIAMACHY is a UV-visible-near-infrared spectrometer which flies on ESA&#39;s Envisat and was operational from 08/2002 to 04/2012 (see Burrows et al., 1995 and Bovensmann et al., 1999 and references therein). The Mesosphere--Lower Thermosphere (MLT) measurement mode was carried out from 07/2008 until the end of the mission for one day every 15 days. This data set comprises 84 days of SCIAMACHY MLT NO measurements, each<br> containing about 15 orbits.</p> <p>The NO retrieval was carried out at the Karlsruhe Institute of Technology (KIT), Karlsruhe, Germany, and is described in Bender et al., 2013. We used the SCIAMACHY geo-located atmospheric spectra (SCI_NL__1P) version 8.02 provided by ESA via their data browser at<br> https://earth.esa.int/web/guest/data-access/browse-data-products.<br> The spectra were calibrated with ESA&#39;s `SciaL1C` command line tool available for download at<br> https://earth.esa.int/web/guest/software-tools/content/-/article/scial1c-command-line-tool-4073.</p> <p>The SCIAMACHY NO data were compared to the results from ACE-FTS, MIPAS, and SMR in Bender et al., 2015, showing that all agree within the respective measurement uncertainties.</p> <p><strong>Acknowledgements</strong><br> The development of the retrieval was funded by the Helmholtz-society under the grant number VH-NG-624. The SCIAMACHY project, which was initiated by Professor Burrows in 1984, was funded by the German Aerospace&nbsp; Agency (DLR), the Netherlands Space Office NSO, formerly NIVR, and the Belgium ministry responsible for space.&nbsp; ESA funded the Envisat project. Professor Burrows of University of Bremen is the Principal Investigator. He and his&nbsp; research team comprising his colleagues in Bremen and international scientific collaborators led the scientific&nbsp; support and development of SCIAMACHY and the scientific exploitation of its&nbsp; data products.</p> <p>The SCIAMACHY instrument is developed by an industrial team headed by companies now known as Airbus SD on the German side and by Dutch Space on the Dutch side and included Belgium companies. The instrument and algorithm development is supported by the activities of the SCIAMACHY Science Advisory Group (SSAG), a team of scientists from various&nbsp; international institutions: University of&nbsp; Bremen (D), SRON (NL), SAO (USA), IASB (B), MPI Chemistry Mainz (D), KNMI (NL),&nbsp; University of Heidelberg (D), IMGA (I), CNRS-LPMA (F). Operational data processing is being performed by ESA and DLR-DFD within the ENVISAT ground&nbsp; segment. Support with respect to mission planning and operations is given by&nbsp; the SCIAMACHY Operations Support Team (SOST). The relevant work at the University of Bremen is funded by the University and State of Bremen.</p>

opencc-by-sa-4.0Jun 2017View details →
zenodo44/100

Data repository of multi-temporal high-resolution data products of ecosystem structure derived from country-wide airborne laser scanning surveys of the Netherlands

<p><span lang="EN-GB">This data repository contains a set of multi-temporal data products of ecosystem structure derived from four national ALS surveys of the Netherlands (AHN1&ndash;AHN4) (folders:<strong> 1_AHN1, 2_AHN2, 3_AHN3, and 4_AHN4</strong>). Four sets of 25 LiDAR-derived vegetation metrics representing ecosystem height, cover, and structural variability are provided at 10 m spatial resolution, providing valuable data sources for a wide range of ecological research and field beyond. A preview of all generated LiDAR metrics are also provided (folder: <strong>5_Maps</strong>). All 25 LiDAR metrics were calculated using Laserfarm workflow&nbsp; (<a href="https://laserfarm.readthedocs.io/en/latest/">https://laserfarm.readthedocs.io/en/latest/</a>) (building on the user-extendable features from the &ldquo;Laserchicken&rdquo; software: <a href="https://laserchicken.readthedocs.io/en/latest/#features">https://laserchicken.readthedocs.io/en/latest/#features</a>). All metrics are calculated with the normalized point cloud. More details on metric calculation are provided on GitHub (Laserchicken: <a href="https://github.com/eEcoLiDAR/laserchicken">https://github.com/eEcoLiDAR/laserchicken</a> and Laserfarm: <a href="https://github.com/eEcoLiDAR/Laserfarm">https://github.com/eEcoLiDAR/Laserfarm</a>), as well as on the &ldquo;Laserchicken&rdquo; documentation page (<a href="https://laserchicken.readthedocs.io/en/latest/">https://laserchicken.readthedocs.io/en/latest/</a>). We also provided masks to minimize the influence of water surfaces, buildings and roads, powerlines and NA values in the data products (folder: <strong>6_Masks</strong>).&nbsp; To supplement the generated data products, we also provided a set of raster layers that contains point/pulse density of each AHN survey and the DTM and DSM raster layers for each AHN dataset (folder: <strong>7_Auxiliary_data</strong>). To test the robustness of the LiDAR metrics, we also compared the metrics generated from different pulse densities across different habitat types (folder: <strong>8_Sensitivity_analysis</strong>). Two use cases demonstrated the utility of the presented data products: (use case 1) monitoring forest structural change across time using multi-temporal ALS data and (use case 2) comparison of vegetation structural difference within Natura 2000 sites. The used data are also provided (folder: <strong>9_Use_case</strong>). Note that all the raster layers are provided at 10 m resolution under the local Dutch coordinate system &ldquo;RD_new&rdquo; (EPSG: 28992, NAP:5709). To gain more insights of the pre-classification accuracy of the AHN datasets, we also conducted a preliminary assessment of the effect of terrain filtering on vegetation change detection across AHN datasets (i.e. AHN2&ndash;AHN4). The data used in this analysis are made available (folder: <strong>10_Ground_classification</strong>). </span></p> <p><span lang="EN-GB">An overview of all the folders in the repository:</span></p> <p><strong><span lang="EN-GB">1.&nbsp;&nbsp;&nbsp;&nbsp; </span></strong><strong><span lang="EN-GB">AHN1</span></strong></p> <p><strong><span lang="EN-GB">2.&nbsp;&nbsp;&nbsp;&nbsp; </span></strong><strong><span lang="EN-GB">AHN2</span></strong></p> <p><strong><span lang="EN-GB">3.&nbsp;&nbsp;&nbsp;&nbsp; </span></strong><strong><span lang="EN-GB">AHN3</span></strong></p> <p><strong><span lang="EN-GB">4.&nbsp;&nbsp;&nbsp;&nbsp; </span></strong><strong><span lang="EN-GB">AHN4</span></strong></p> <p><strong><span lang="EN-GB">5.&nbsp;&nbsp;&nbsp;&nbsp; </span></strong><strong><span lang="EN-GB">Maps</span></strong></p> <p><span lang="EN-GB">Those folders contain four sets of 25 LiDAR metrics at 10 m resolution generated from each AHN dataset. The file names and their corresponding LiDAR metrics can be found in Table 1. An additional folder (5_Maps) contains the maps (.pdf format) of all 25 metrics for each AHN dataset.</span></p> <p><strong><span lang="EN-GB">6. Masks</span></strong></p> <ul> <li><span lang="EN-GB">ahn3_10m_mask_building_road_water.tif</span></li> <li><span lang="EN-GB">ahn4_10m_mask_building_road_water.tif</span></li> <li><span lang="EN-GB">ahn4_10m_mask_powerline.tif</span></li> <li><span lang="NL">ahn1_10m_NA_mask.tif</span></li> <li><span lang="NL">ahn2_10m_NA_mask.tif</span></li> <li><span lang="NL">ahn3_10m_NA_mask.tif</span></li> <li><span lang="NL">a</span><span lang="NL">hn4_10m_NA_mask.tif</span></li> </ul> <p><span lang="NL">&nbsp;</span></p> <p><span lang="EN-GB">It contains two mask layers of water surfaces, buildings and roads for both AHN3 and AHN4 data products based on the Dutch cadaster data (TOP10NL) from 2018 (corresponding to AHN3) and 2021 (corresponding to AHN4) (<a href="https://www.kadaster.nl/zakelijk/producten/geo-informatie/topnl">https://www.kadaster.nl/zakelijk/producten/geo-informatie/topnl</a>). In the masks, water surfaces, buildings and roads were merged into one class with pixel value assigned to 1 and the rest has the pixel value of 0. There is also a powerline mask generated from the AHN4 dataset at 10 m resolution, where pixels containing powerlines were assigned a value of 1 and the rest as NoData. We provide those masks to minimize the inaccuracies of the data products caused by human infrastructures and water surfaces. We also provided a mask for each AHN dataset where NA value occurs &mdash; areas with no vegetation points (&ldquo;unclassified&rdquo; class in the AHN datasets). Pixels with NA value were assigned with a value of 1 and the rest as 0.</span></p> <p><strong><span lang="EN-GB">7. Auxiliary data</span></strong></p> <p><span lang="EN-GB">(1) Point_density</span></p> <ul> <li><span lang="EN-GB">ahn1_10m_point_density.tif</span></li> <li><span lang="EN-GB">ahn2_10m_point_density.tif</span></li> <li><span lang="EN-GB">ahn3_10m_point_density.tif</span></li> <li><span lang="EN-GB">ahn4_10m_point_density.tif</span></li> </ul> <p><span lang="EN-GB">(2) Pulse_density</span></p> <ul> <li><span lang="EN-GB">ahn3_10m_pulse_density.tif</span></li> <li><span lang="EN-GB">ahn4_10m_pulse_density.tif</span></li> </ul> <p><span lang="EN-GB">(3) Flighttime</span></p> <ul> <li><span lang="EN-GB">ahn3_10m_flighttime.tif</span></li> <li><span lang="EN-GB">ahn4_10m_flighttime.tif</span></li> </ul> <p><span lang="EN-GB">(4) DTM_DSM</span></p> <ul> <li><span lang="EN-GB">ahn2_10m_dtm.tif</span></li> <li><span lang="EN-GB">ahn2_10m_dsm.tif</span></li> <li><span lang="EN-GB">ahn3_10m_dtm.tif</span></li> <li><span lang="EN-GB">ahn3_10m_dsm.tif</span></li> <li><span lang="EN-GB">ahn4_10m_dtm.tif</span></li> <li><span lang="EN-GB">ahn4_10m_dsm.tif</span></li> </ul> <p><span lang="EN-GB">It contains four raster layers representing the point density of each AHN dataset, two raster layers for pulse density of the AHN3 and AHN4, two raster layers for flight timestamp of the AHN3 and AHN4, and six DTM and DSM layers for AHN2</span><span lang="EN-GB">&ndash;</span><span lang="EN-GB">AHN4. All raster layers are provide at 10 m resolution.</span></p> <p><strong><span lang="EN-GB">8. Sensitivity analysis</span></strong></p> <ul> <li><span lang="EN-GB">Dunes</span></li> <li><span lang="EN-GB">Marsh</span></li> <li><span lang="EN-GB">Grassland</span></li> <li><span lang="EN-GB">Shrubland</span></li> <li><span lang="EN-GB">Woodland</span></li> <li><span lang="EN-GB">Code</span></li> <li><span lang="EN-GB">Figure</span></li> </ul> <p><span lang="EN-GB">It contains the 25 metrics generated from point clouds with the original and down-sampled pulse densities (original pulse density of the AHN4, pulse density of the AHN3, &frac12; of the pulse density of the AHN3, and &frac14; of the pulse density of AHN3) for each habitat type (i.e. dunes, marsh, grassland, shrubland, and woodland). We also provided the code and the figures generated from this analysis.</span></p> <p><strong><span lang="EN-GB">9. Use_case</span></strong></p> <p><span lang="EN-GB">(1) Multi-temporal_AHN</span></p> <ul> <li><span lang="EN-GB">Data</span></li> <li><span lang="EN-GB">Usecase_multi-temporal_AHN.R</span></li> </ul> <p><span lang="EN-GB">It contains the input data for the use case data processing (i.e. Data folder), including the shapefile of the area (i.e. shp folder), and extracted pixel value from six selected LiDAR metrics from AHN1&ndash;AHN5 (i.e. Metrics folder), and the selected LiDAR metrics of the area (e.g. Hp95 folder), and the R code for data processing (i.e. Usecase_multi-temporal_AHN.R). </span></p> <p><span lang="EN-GB">(2) Natura2000</span></p> <ul> <li><span lang="EN-GB">Data</span></li> <li><span lang="EN-GB">Natura2000_end2021_HABITATCLASS.csv</span></li> <li><span lang="EN-GB">Natura2000_NL_habitat_grouped.csv</span></li> <li><span lang="EN-GB">Usecase_Natura2000.R</span></li> </ul> <p><span lang="EN-GB">It contains a folder of the input data used for the use case (i.e. Data folder), including the shapefile (i.e. shp folder) of the Natura 2000 sites in the Netherlands (i.e. Nature2000_NL_RDnew.shp) and the 100 random sample plots from each habitat type (e.g. woodland_points.shp), and the LiDAR metrics from AHN4 used for demonstrating the vegetation&nbsp; structure within each habitat type (i.e. AHN4_metrics folder). The table &ldquo;Natura2000_end2021_HABITATCLASS.csv&rdquo; is the original attribute table of Natura 2000 sites, including information related to the description of habitat classes (column &ldquo;DESCRIPTION&rdquo;), the code corresponding to the habitat class (column &ldquo;HABITATCODE&rdquo;), the code for the specific site (column &ldquo;SITECODE&rdquo;), and the percentage of the cover of a specific habitat class in one site (column &ldquo;PERCENTAGECOVER&rdquo;). The table &ldquo;Natura2000_NL_habitat_grouped.csv&rdquo; contains two subtabs, one (i.e. &ldquo;Habitatclass&rdquo;) is the copy of the original attribute table of Natura 2000 sites in the Netherlands, and the other one (i.e. &ldquo;Habitat_class_summary&rdquo;) is the grouped habitat type based on the dominant habitat class (i.e. class with the highest percentage cover) in each site. Different colors indicate different habitat types, corresponding to the colors in the first tab (&ldquo;Habitatclass&rdquo;) where the dominant habitat class was highlighted for each site. </span></p> <p><strong><span lang="EN-GB">10. Ground classification</span></strong></p> <ul> <li><span lang="EN-GB">Raw_point_cloud</span></li> <li><span lang="EN-GB">Computed_metrics </span></li> <li><span lang="EN-GB">Plottings_and_code</span></li> <li><span lang="EN-GB">ArcGIS_project</span></li> </ul> <p><span lang="EN-GB">It contains four subfolders: (1) The original point cloud for each sample area (AHN2&ndash;AHN4) (subfolder: Raw_point_cloud); (2) The 25 LiDAR metrics computed from the original point clouds with pre-classification of AHN and from the new terrain filtering method across AHN2&ndash;AHN4 (subfolder: Computed_metrics); (3) Generated violin plots for the comparison of vegetation change detection and the python code employed (subfolder: Plottings_and_code); (4) an ArcGIS project which the shapefiles of the study area and sample plots are provided (subfolder: ArcGIS_project).</span></p> <p><strong><span lang="EN-GB">Code availability</span></strong></p> <p><span lang="EN-GB">Jupyter Notebooks for processing AHN datasets: </span></p> <p><span lang="EN-GB"><a href="https://github.com/ShiYifang/AHN">https://github.com/ShiYifang/AHN</a></span></p> <p><span lang="EN-GB">Laserfarm workflow repository: </span></p> <p><span lang="EN-GB"><a href="https://github.com/eEcoLiDAR/Laserfarm">https://github.com/eEcoLiDAR/Laserfarm</a></span></p> <p><span lang="EN-GB">Laserchicken software repository: </span></p> <p><span lang="EN-GB"><a href="https://github.com/eEcoLiDAR/laserchicken">https://github.com/eEcoLiDAR/laserchicken</a></span></p> <p><span lang="EN-GB">Code for downloading AHN dataset: <a href="https://github.com/ShiYifang/AHN/tree/main/AHN_downloading">https://github.com/ShiYifang/AHN/tree/main/AHN_downloading</a></span></p> <p><span lang="EN-GB">Code for generating masks for AHN datasets: <a href="https://github.com/ShiYifang/AHN/tree/main/AHN_masks">https://github.com/ShiYifang/AHN/tree/main/AHN_masks</a></span></p> <p><span lang="EN-GB">Code for demonstration of ecological use cases: <a href="https://github.com/ShiYifang/AHN/tree/main/Use_case">https://github.com/ShiYifang/AHN/tree/main/Use_case</a></span></p> <p>&nbsp;</p>

opencc-by-4.0Oct 2024View details →
zenodo44/100

High-resolution, Decadal to Weekly Geomorphic Change Analysis of the Elbow River in Calgary, using Multi-temporal Lidar and Repeat Terrestrial Laser Scanning

<p>This directory contains files related to the scientific research project of Luc van Dijk at the Department of Earth, Energy, and Environment, University of Calgary. The project title is "High-resolution, Decadal to Weekly Geomorphic Change Analysis of the Elbow River in Calgary, using Multi-temporal Lidar and Repeat Terrestrial Laser Scanning". This project in the field of geomorphology was a collaboration between the University of Calgary and Utrecht University in the Netherlands. The project was completed on October 27, 2023. Below is a description of the files in this directory.</p><p>&nbsp;</p><p><strong>DisplacementVolumeDistributions_TLS.xlsx</strong></p><p>Excel file containing tabular data of the normalized sediment displacement volumes that were obtained using TLS. Each tab in the Excel file represents a period of interest in 2023. The data in this file were used to generate the 'histogram-like' figures in the report.</p><p>&nbsp;</p><p><strong>DoD_rasters.zip</strong></p><p>Folder containing the aerial lidar DEMs of Difference (DoDs) for each period of interest. The DoDs are 'waterless', i.e. the water surface is masked. The suffix of the file name before the file extension (e.g., ..._10cm.tif) indicates the maximum REM value that was used for the automated masking of the water surface extent (see report section 3.1.2). If the file name contains "large", it refers to the upstream greater area (see report section 3.1.3).</p><p>Within this folder is another folder called 'Clipped2AOIs'. This folder contains the same DoDs, but covering only the extents of the sites of interest ('AOIs' = Areas Of Interest).</p><p>&nbsp;</p><p><strong>FilteredPointClouds_TLS.zip</strong></p><p>Folder containing the processed and filtered point clouds that were acquired throughout the summer of 2023 using TLS. These point clouds have been pre-processed and filtered to remove vegetation (see report section 3.2). They are grouped in sub-folders per acquisition date. The filenames are numbered to location, i.e. 'elbow1', 'elbow2', 'elbow3' and 'elbow4'. These correspond to the sites of interest: Glenmore Dam, golf club, Sandy Beach and Riverdale, respectively.</p><p>&nbsp;</p><p><strong>PythonScripts_Discharge_Rainfall.zip</strong></p><p>Folder containing the Python scripts that were made to process the discharge and rainfall data that were sourced from Environment Canada and The City of Calgary (see report section 3.3). The scripts themselves contain descriptions of their purpose.</p><p>&nbsp;</p><p><strong>PythonScripts_DisplacementVolumeAnalysis.zip</strong></p><p>Folder containing the Python scripts that were made to process and analyze the aerial lidar DoDs and the TLS rasterized difference point clouds (M3C2 output). The 'convert2pickle' scripts converted the sizable rasters to smaller pickle files, which were easier and faster to work with. The 'chart' scripts load the data from the pickle files, analyze them and produce the 'histogram-like' figures in the report. The scripts themselves contain descriptions of their purpose.</p><p>&nbsp;</p><p><strong>RainfallDischargeData.xlsx</strong></p><p>Excel file containing the discharge and rainfall data from Environment Canada and The City of Calgary. The data came from different sources in different formats and were combined into this single table.</p><p>&nbsp;</p><p><strong>RasterizedDifferencedPointClouds_M3C2.zip</strong></p><p>Folder containing the rasterized results of the differenced TLS point clouds (M3C2 output) (see report section 3.2.4). The filenames are numbered to location, i.e. 'Elbow1', 'Elbow2', 'Elbow3' and 'Elbow4'. These correspond to the sites of interest: Glenmore Dam, golf club, Sandy Beach and Riverdale, respectively. The numeric sequence in the file name indicates the start and end date of the change analysis in a 'mm-dd' format. The suffixes '_dist', '_unc' and '_sig' refer to the three output layers of the M3C2 algorithm: distance, uncertainty and significance of change. The main files of interest are the '.tif' files. Files sharing the same name, but with different extensions (.tfw, .tif.aux.xml, .tif.xml) are supplementary/auxiliary files for the '.tif' file, generated by ArcGIS Pro.</p><p>&nbsp;</p><p><strong>ScarpsOfInterest_shapefile.zip</strong></p><p>Folder containing a polygon shapefile describing the extents and locations of the sites of interest. The main file of interest is the '.shp' file. The other files with the same name, but different extensions (.cpg, .dbf, .prj, .sbn, .sbx, .shp.xml, .shx) are supplementary/auxiliary files for the '.shp' file, generated by ArcGIS Pro.</p>

opencc-by-4.0Oct 2023View details →
zenodo44/100

Synchrotron X-ray Computed Tomography scan of a wasp

<h4>Contents:</h4><ul><li><i>bee_yazeed-20231001T170032.h5</i> - SXCT scan of a wasp performed at beamline <a href="https://www.sesame.org.jo/beamlines/beats">ID10-BEATS</a> of SESAME.</li><li><i>SESAME_wasp_yazeed.avi -</i> 3D video rendering of phase-contrast CT reconstruction of <i>bee_yazeed-20231001T170032</i>. The dataset was reconstructed using <a href="https://github.com/gianthk/alrecon/tree/master">alrecon</a>. The video was created using ORS Dragonfly.</li></ul><h4>H5 dataset information:</h4><ul><li>Raw experimental data (sinogram, flat fields and dark fields) and metadata are stored in a common .H5 file.</li><li>The HDF5 file is organized hierarchically following the <a href="https://dxfile.readthedocs.io/en/latest/">Scientific Data Exchange (DXfile)</a> community standard.</li></ul><h4>How to reconstruct:</h4><ul><li>You can use <a href="http://www.silx.org/">Silx</a> to read and explore the .H5 dataset.</li><li>The file can be read within Python using the <a href="https://dxchange.readthedocs.io/en/latest/">DXChange</a> package.</li><li>See the <a href="https://beats.readthedocs.io/reconstruction.html">ID10-BEATS beamline user guide</a> for a detailed description on how to process and reconstruct the scan.</li></ul>

opencc-by-4.0Nov 2023View details →
zenodo44/100

A Large Scale Side-Scan Sonar Dataset of Seafloor Sediments for Self-Supervised Pretraining

<p>This dataset serves as an extension to the dataset part of "A convolutional vision transformer for semantic segmentation of side-scan sonar data" published in Ocean Engineering, Volume 86, part 2, 15 October 2023,<strong> </strong>DOI: <a href="https://www.sciencedirect.com/science/article/pii/S0029801823020310">10.1016/j.oceaneng.2023.115647</a> for self-supervised pretraining.</p><p>This dataset consists of patches of side-scan sonar waterfalls collected along the coast of Catalunya during an extensive survey. The waterfalls were partitioned in batches of 384 lines to generate images of size 384 × 384 with a 192 pixel-overlap along-track and across-track. This resulted in a total of 434,164 images capturing various seafloor types including rocky bottoms, sand ripples, detrital funds, posidonia, cymocea, mud, corals, artificial reefs etc.</p><p>Additional tools for using the data for self-supervised pretraining can be found under <a href="https://github.com/DeeperSense/deepersense-seafloorscan">https://github.com/DeeperSense/deepersense-seafloorscan</a></p><p>&nbsp;</p><p><strong>Acknowledgements</strong></p><p>The data in this repository were collected by Tecnoambiente SL as part of the project DeeperSense that received funding from the European Commission. Program H2020-ICT-2020-2 ICT-47-2020. Project Number: 101016958.</p>

opencc-by-4.0Nov 2023View details →
zenodo44/100

IODP Expedition 383 Scanning electron microscope images

Microscopic images of discrete samples were acquired using a scanning electron microscope (SEM) and captured as image files. These files were uploaded along with a brief description and a record of the microscopic conditions when the image was taken.

opencc-by-4.0Jul 2021View details →
zenodo44/100

PsPM-SF: SCR, ECG, PPU and respiration measurements from a delay fear conditioning task with auditory CS (monophones/triads), performed during MRI scanning

<p>This dataset includes skin conductance response (SCR), electrocardiogram (ECG), peripheral pulse unit (PPU) and respiration measurements for 20 healthy unmedicated participants (10 females and 10 males, age range: 19 - 35 years, mean age: 24.2 +/- 4.9) participating in a classical (Pavlovian) discriminant delay fear conditioning experiment with auditory CS, during MRI scanning. Also included are CS and US information, and ratings of CS after the experiment. Simple and complex CS were simple sine tones (4 s), and triads in root position or in first inversion, respectively. US was a train of electric square pulses delivered with a constant current stimulator (Digitimer DS7A, Digitimer, Welwyn Garden City, UK) on participants&#39; dominant forearm through a pin-cathode/ring-anode configuration. After the fear conditioning task, participants were first asked to report their subjective estimate of how likely they were to receive a shock after a given CS in the future, on a visual analogue scale of 0-100. Then they were asked to rate pairs of CS sounds with respect to which of the two stimuli they liked less. NOTE: In Staib et al. 2015, this dataset is denoted as SC1F</p>

opencc-by-4.0Sep 2020View details →
zenodo44/100

IODP Expedition 378 Scanning electron microscope images

<p>Microscopic images of discrete samples were acquired using a scanning electron microscope (SEM) and captured as image files. These files were uploaded along with a brief description and a record of the microscopic conditions when the image was taken.</p>

opencc-by-4.0Feb 2022View details →
zenodo44/100

IODP Expedition 367 Scanning electron microscope images

Microscopic images of discrete samples were acquired using a scanning electron microscope (SEM) and captured as image files. These files were uploaded along with a brief description and a record of the microscopic conditions when the image was taken.

opencc-by-4.0Sep 2018View details →
zenodo44/100

Mangrove terrestrial laser scanning (TLS) point clouds and quantitative structural models (QSMs)

<p>Datasets for a publication entitled, "Terrestrial laser scanning for the estimation of above ground biomass of mangrove roots by modelling them as inverted trees."</p> <p>See the file "Data dictionary for Mangrove terrestrial laser scanning.pdf" for a description of the datasets included in the zipped folder.&nbsp;</p>

opencc-by-4.0Nov 2024View details →
zenodo44/100

NatalIA: PBF-US1 (Phantom Blind-sweeps for Fetal Ultrasound Scanning)

<p>NatalIA PBF-US1 is dataset designed to support the development of AI-based tools for detecting relevant fetal planes in ultrasound videos captured by non-trained personnel, such as midwives or nurses.</p>

opencc-by-4.0Nov 2024View details →
zenodo44/100

Virtual RHI lidar scans retrieved in high-fidelity wake vortex simulations of landing aircraft under turbulent crosswind conditions - LES Lidar Simulator (LLS)

<p>This dataset contains two types of virtual measurements of multiple pulsed lidar integrated into high-fidelity hybrid RANS-LES wake vortex simulations of a landing Airbus A340 aircraft.&nbsp;Simulations have been performed for four different atmospheric conditions, varying in crosswind and therefore turbulence in the atmosphere.</p> <p>The two lidar simulator types are:</p> <ul> <li>LLS: LES Lidar Simulator (no noise, Signal to Noise Ratio &gt;&gt; 1). The analysis is based on the Range Gate Weighting function (RWF) [based on formulations in for example [1]]. Given the assumption of no instrument noise, no spectral analysis in the frequency domain is required.</li> <li>LLSn: LES Lidar Simulator with noise (realisitic Signal to Noise Ratio). Based on formulations in [2], where non-linear low-pass spatial filters accurately model real field measurements. Both background noise and aerosol noise contained in real lidar measurements are modeled.&nbsp;</li> </ul> <p>Provided are the raw lidar scans in RHI format, with the position and strength of the wake vortices within each lidar scan given by a pressure-vorticity tracking algorithm from the wake vortex simulation (simulation truth, ST). Misidentifications have been removed from the provided dataset. In addition to the labels for each wake vortex lidar scan, also wind background scans are provided for the crosswind simulation cases. These background scans give a better understanding of the prevailing atmospheric condition within which the aircraft lands.&nbsp;</p> <p>Furthermore the evaluation of the LLS scans using the Method of Radial Velocities (RV method) [3], a state-of-the-art wake vortex characterization method for lidar scans is provided for a subset of the LLS dataset. For analysing the impact of the RWF for LLS scans, selected lidar scans are also given in a&nbsp; 'naive' fashion (lidar scans assuming point measurements are possible).</p> <p><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></p> <h3><strong>Overview</strong></h3> <p><strong>In total each dataset (LLS and LLSn) contains 8 Aircraft landing simulation with associated </strong><strong>virtual lidar RHI scans:</strong></p> <ul> <li>2x no wind</li> <li>6x crosswind (specified at height b_0)</li> <li>0.5w_0 from port direction</li> <li>0.5w_0 from starboard direction</li> <li>1.0w_0 from port direction</li> <li>1.0w_0 from starboard direction</li> <li>2.0w_0 from port direction</li> <li>2.0w_0 from starboard direction</li> </ul> <p><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></p> <h3><strong>The dataset has 13 folders:</strong></h3> <div> <p><strong>POS1_POS2_POS8_scans&nbsp; = Individual scans of various simulations as well as background wind scans (no wake vortices). </strong></p> <p>POS1_POS2: 0_0, 0_5, 1_0, 2_0 corresponds to the wind, same as POS1_POS2 below</p> <p>POS8: LLS or LLSn, corresponding to the type of lidar simulator (without or with instrument noise, respectively)</p> </div> <div>&nbsp;</div> <div>Scan naming convention: POS1_POS2_POS3_POS4_POS5_POS6_POS7.csv</div> <div>&nbsp;</div> <div>Example: 0_5_D_248_8_161.2201878198302_168.4201878198237.csv</div> <div>&nbsp;</div> <div> <ul> <li>POS1_POS2: Together they form a factor which is multiplied with the initial descend speed of the wake vortex pair, w_0. The definition for w_0 can be found in [4]. It is common for the crosswind speed to be set according to the multiples of w_0. Due to the landing of the A340 aircraft, and the logarithmic nature of the wind simulation, we set the crosswind at the b_0 altitude of the simulation. For a definition of b_0, also see [4]. For the above example, 0.5w_0 is the crosswind speed. Note that every 26 lidar positions (POS4), the direction of the crosswind changes, if there is a crosswind.</li> </ul> </div> <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - Crosswind approaches from port side: POS4: 0-25, 52-77, 104-129, 156-181, 208-233, 260-285</div> <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - Crosswind approaches from starboard side: POS4: 26-51, 78-103, 130-155, 182-207, 234-259, 286-311</div> <div> <ul> <li>POS3: Label indicating which part of the numerical simulation this scan belongs to (a full landing simulation consists of A-D). A: Hybrid RANS-LES, B,C,D: temporal LES (in order). For the above example, D indicates that the lidar scan was recorded during the last part of the simulation. W: Prior to the wake vortex simulations with crosswind, a background wind scan for each lidar position is recorded.</li> </ul> </div> <div> <ul> <li>POS4: Specifies the number of the lidar, implications are the longitudinal position along the glide path of the aircraft. In the packs of lidar positions described in the description of POS1_POS2, the last lidar position is the closest to the touchdown point of the aircraft, smaller lidar positions within this pack are further away (in order) - also see the lid_plane_info directory. Note that the lidar position also adjusts the spectrum of the elevation angles used (and thus the size of the lidar scan). For that see the associated virtual lidar scan raw data. In the above example we have lidar position 248, thus crosswind approaching from starboard and rather mid-way of the longitudinal glide path direction.</li> </ul> </div> <div> <ul> <li>POS5: Specifies the number of the scan for this lidar position (POS4) and simulation (POS1__POS2). In the above example this is scan number 8.</li> </ul> </div> <div> <ul> <li>POS6_POS7: Specifies the simulation time within which the scan was measured during the aircraft landing simulation (POS1__POS2). In the above example this is 161.2201878198302 s to 168.4201878198237 s.</li> </ul> </div> <div>The scans purely with wind, an no wake vortices are stored in an additional directory within conv_scans. The case '0_0' (no wind) does not require wind scans.&nbsp;</div> <div>&nbsp;</div> <div>Within the scan files, we have a four (LLS) or five (LLSn) columns:</div> <div> <ul> <li>t: Simulation time</li> <li>ELE: Elevation angle [deg] of the lidar beam</li> <li>R: Range from lidar [m]</li> <li>v_r: LOS velocity (radial velocity) along lidar beam</li> <li>snr: Signal to Noise Ratio&nbsp;</li> </ul> <p>&nbsp;</p> <p><strong>wind_POS8_scans = Simulated lidar scans of the background wind for LLS and LLSn.</strong></p> <p>POS8: LLS or LLSn, corresponding to the type of lidar simulator (without or with instrument noise, respectively)</p> <p>Scans simulated here are in the same format as <em>POS1_POS2_POS8_scans</em>. Wind scans for point measurement scans are found in&nbsp;<em>naive_scan_subset&nbsp;</em>- the scans with POS4 = 0 should be used if more are available.</p> <p>&nbsp;</p> <p><strong>naive_scan_subset = Simulated lidar scans simulating velocity point measurements.</strong></p> </div> <div> <p>The format is the same as for <em>POS1_POS2_POS8_scans</em>, with the difference of being sorted first by wind subdirectories and then lidar number (LID).</p> <p>&nbsp;</p> <p><strong>labels = Labels of wake vortices for the above wake vortex scans.&nbsp;</strong></p> </div> <div>We have 4 main files, where each file represents the targets for one wind strength 0.0w_0, 0.5w_0, 1.0w_0, 2.0w_0.</div> <div>Within the labels files, we have a multitude of columns with different data:</div> <div> <ul> <li>#Time: Simulation (not scan) time.</li> <li>y_uw : lateral position in simulation domain of upwind (port) vortex.</li> <li>z_uw : height position in simulation domain of upwind (port) vortex.</li> <li>y_dw : lateral position in simulation domain of downwind (starboard) vortex.</li> <li>z_dw : height position in simulation domain of downwind (starboard) vortex.</li> <li>G_515_uw: Gamma 515 Circulation strength (see additional notes) of upwind (port) vortex [m^2/s].</li> <li>G_515_dw: Gamma 515 Circulation strength (see additional notes) of downwind (starboard) vortex [m^2/s].</li> <li>cr_uw: Core radius of upwind (port) vortex (in meters).</li> <li>cr_dw: Core radius of downwind (starboard) vortex (in meters).</li> <li>uw distance from lidar [m]: Horizontal distance of upwind (port) vortex from respective lidar.</li> <li>dw distance from lidar [m]: Horizontal distance of downwind (starboard) vortex from respective lidar.</li> <li>uw height [m]: Vertical distance of upwind (port) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m).</li> <li>dw height [m]: Vertical distance of downwind (starboard) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m).</li> <li>vortex age uw [s]: Age of upwind (port) vortex (after first generated by aircraft at respective measurement plane of lidar).</li> <li>vortex age dw [s]: Age of downwind (starboard) vortex (after first generated by aircraft at respective measurement plane of lidar).</li> <li>scan: Associated scan.</li> <li>LID: Associated lidar number.</li> </ul> <p>On top of the summarizing files for each simulation, in the subdirectory&nbsp;<em>individual</em>, the label for each scan is given in a separate file.</p> <p>The above gives information on the simulation truth, furthermore the file&nbsp;<em>labels_with_rv.csv</em> can be found here, where the following extra label columns are given for a subset of scans: [in the following Conv and Naive refer to LLS scans and point measurement scans, respectively]</p> <ul> <li>wind: Strength of crosswind, same as POS1_POS2 in &nbsp;<em>POS1_POS2_scans.&nbsp;</em>The sign corresponds to the wind direction. Negative is a crosswind from the port side of the aircraft, positive is a crosswind from the starboard side of the aircraft.</li> <li>Conv RV: 1 indicates the RV method has been evaluated for LLS scans, 0 if not.</li> <li>Naive RV: 1 indicates the RV method has been evaluated for point measurement scans, 0 if not.</li> <li>conv rv G_515_uw: Gamma 515 Circulation strength (see additional notes) of upwind (port) vortex computed using the RV method on LLS scans&nbsp; [m^2/s].</li> <li>conv rv G_515_dw: Gamma 515 Circulation strength (see additional notes) of downwind (starboard) vortex computed using the RV method on LLS scans [m^2/s].</li> <li>conv rv uw distance from lidar [m]: Horizontal distance of upwind (port) vortex from respective lidar using the RV method on LLS scans.</li> <li>conv rv dw distance from lidar [m]: Horizontal distance of downwind (starboard) vortex from respective lidar using the RV method on LLS scans.</li> <li>conv rv uw height [m]: Vertical distance of upwind (port) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m) using the RV method on LLS scans.</li> <li>conv rv dw height [m]: Vertical distance of downwind (starboard) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m) using the RV method on LLS scans.</li> <li>naive rv G_515_uw: Gamma 515 Circulation strength (see additional notes) of upwind (port) vortex computed using the RV method on point measurement scans [m^2/s].</li> <li>naive rv G_515_dw: Gamma 515 Circulation strength (see additional notes) of downwind (starboard) vortex computed using the RV method on point measurement scans [m^2/s].</li> <li>naive rv uw distance from lidar [m]: Horizontal distance of upwind (port) vortex from respective lidar using the RV method on point measurement scans.</li> <li>naive rv dw distance from lidar [m]: Horizontal distance of downwind (starboard) vortex from respective lidar using the RV method on point measurement scans.</li> <li>naive rv uw height [m]: Vertical distance of upwind (port) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m) using the RV method on point measurement scans.</li> <li>naive rv dw height [m]: Vertical distance of downwind (starboard) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m) using the RV method on point measurement scans.</li> <li>uw phi [deg]: Elevation angle to the center of the upwind (port) vortex from the simulation truth.</li> <li>uw range [m]: Range from the lidar to the center of the upwind (port) vortex from the simulation truth.</li> <li>dw phi [deg]: Elevation angle to the center of the downwind (starboard) vortex from the simulation truth.</li> <li>dw range [m]: Range from the lidar to the center of the downwind (starboard) vortex from the simulation truth.</li> <li>conv rv uw phi [deg]: Elevation angle to the center of the upwind (port) vortex using the RV method on LLS scans.</li> <li>conv rv uw range [m]: Range from the lidar to the center of the upwind (port) vortex using the RV method on LLS scans.</li> <li>conv rv dw phi [deg]: Elevation angle to the center of the downwind (starboard) vortex using the RV method on LLS scans.</li> <li>conv rv dw range [m]: Range from the lidar to the center of the downwind (starboard) vortex using the RV method on LLS scans.</li> <li>naive rv uw phi [deg]: Elevation angle to the center of the upwind (port) vortex using the RV method on point measurement scans.</li> <li>naive rv uw range [m]: Range from the lidar to the center of the upwind (port) vortex using the RV method on point measurement scans.</li> <li>naive rv dw phi [deg]: Elevation angle to the center of the downwind (starboard) vortex using the RV method on point measurement scans.</li> <li>naive rv dw range [m]: Range from the lidar to the center of the downwind (starboard) vortex using the RV method on point measurement scans.</li> <li>y err conv uw [m]: Cartesian localization error (RV minus ST) in y-direction (lateral) between simulation truth and RV method of upwind (port) vortex center on LLS scans.</li> <li>y err conv dw [m]: Cartesian localization error (RV minus ST) in y-direction (lateral) between simulation truth and RV method of downwind (starboard) vortex center on LLS scans.</li> <li>z err conv uw [m]: Cartesian localization error (RV minus ST) in z-direction (vertical) between simulation truth and RV method of upwind (port) vortex center on LLS scans.</li> <li>z err conv dw [m]: Cartesian localization error (RV minus ST) in z-direction (vertical) between simulation truth and RV method of downwind (starboard) vortex center on LLS scans.</li> <li>y err naive uw [m]: Cartesian localization error (RV minus ST) in y-direction (lateral) between simulation truth and RV method of upwind (port) vortex center on point measurement scans.</li> <li>y err naive dw [m]: Cartesian localization error (RV minus ST) in y-direction (lateral) between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans.</li> <li>z err naive uw [m]: Cartesian localization error (RV minus ST) in z-direction (vertical) between simulation truth and RV method of upwind (port) vortex center on point measurement scans.</li> <li>z err naive dw [m]: Cartesian localization error (RV minus ST) in z-direction (vertical) between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans.</li> <li>D err conv uw [m]: Euclidean distance error for the Cartesian coordinates to the vortex center between simulation truth and RV method of upwind (port) vortex center on LLS scans.</li> <li>D err conv dw [m]: Euclidean distance for the Cartesian coordinates to the vortex center between simulation truth and RV method of downwind (starboard) vortex center on LLS scans.</li> <li>D err naive uw [m]: Euclidean distance error for the Cartesian coordinates to the vortex center between simulation truth and RV method of upwind (port) vortex center on point measurement scans.</li> <li>D err naive dw [m]: Euclidean distance for the Cartesian coordinates to the vortex center between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans.</li> <li>plus_minus_phi: Indicates whether a RHI lidar scan features a positive lidar scanning rate (plus), or a negative one (negative).</li> <li>conv err G_515_uw: Circulation error (RV minus ST) between simulation truth and RV method of upwind (port) on LLS scans [m^2/s].&nbsp;</li> <li>conv err G_515_dw: Circulation error (RV minus ST) between simulation truth and RV method of downwind (starboard) on LLS scans [m^2/s].&nbsp;</li> <li>naive err G_515_uw: Circulation error (RV minus ST) between simulation truth and RV method of upwind (port) on point measurement scans [m^2/s].&nbsp;</li> <li>naive err G_515_dw: Circulation error (RV minus ST) between simulation truth and RV method of downwind (starboard) on point measurement scans [m^2/s].&nbsp;</li> <li>conv err uw phi: Elevation angle error (RV minus ST) between simulation truth and RV method of upwind (port) vortex center on LLS scans&nbsp;[deg].</li> <li>conv err dw phi: Elevation angle error (RV minus ST) between simulation truth and RV method of downwind (starboard) vortex center on LLS scans [deg].</li> <li>naive err uw phi: Elevation angle error (RV minus ST) between simulation truth and RV method of upwind (port) vortex center on LLS scans [deg].</li> <li>naive err dw phi: Elevation angle error (RV minus ST) between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans [deg].</li> <li>conv err uw range: Range from lidar error (RV minus ST) between simulation truth and RV method of upwind (port) vortex center on LLS scans [m].</li> <li>conv err dw range: Range from lidar error (RV minus ST) between simulation truth and RV method of downwind (starboard) vortex center on LLS scans [m].</li> <li>naive err uw range: Range from lidar error (RV minus ST) between simulation truth and RV method of upwind (port) vortex center on point measurement scans [m].</li> <li>naive err dw range: Range from lidar error (RV minus ST) between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans [m].</li> </ul> <p><em>0_0_movement.csv</em> gives insight on the vertical movement on selected vortices in selected lidar scans of the 0_0 wind case.&nbsp;</p> <p>The following data columns exist within the file (note csv file with ; separator):</p> <ul> <li>Str_dw: Vertical movement of the downwind (starboard) vortex, 0 is neutral, -1 is downward, and 1 is upward.</li> <li>Prt_uw: Vertical movement of the upwind (port) vortex, 0 is neutral, -1 is downward, and 1 is upward.</li> <li>scan_code: Identfies associated lidar scan with POS3_POS4_POS5 as in <em>POS1_POS2_scans.</em></li> </ul> <p>&nbsp;</p> <p><strong>lid_plane_info = Additional guidance on the simulated lidars.</strong></p> <p>Each simulation case has a separate file due to minimal ground speed changes of the aircraft.&nbsp;</p> <p>The following data columns exist within each file:</p> <ul> <li>Index: Gives the lidar number corresponding to POS4 and LID.</li> <li>Plane Pos [x]: Gives the longitudinal position of the lidar with respect to the glide path of the aircraft in meters.</li> <li>time plane passed [s]: Gives the simulation time when the aircraft first passes the measurement plane (related to the previous column.</li> <li>height plane passed [m]: Aircraft altitude at the respective lidar positon.</li> <li>lateral position lidar from GP [m]: Lateral position of the lidar from the glide path of the aircraft.</li> </ul> <p><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></p> </div> <h3>Additional Notes:&nbsp;</h3> <div> <ul> <li>Gamma 515 circulation [4]: The Gamma 515 circulation is the averaged circulation of a vortex evaluated at radii 5-15m from the vortex center.&nbsp;</li> </ul> </div> <div> <div> <ul> <li>Lidar scans may contain 2 or 1 vortex. In the case of 1 vortex, the other has G_515_?? set to nan. Note that the position may still available in the labels data sets, but only vortices with available G_515_?? values should be used.</li> <li>The upwind and downwind definitions should purely be taken as names, rather than physical meaning. The names are derived from the simulation, due to mirroring and other post-processing these can be misleading however.</li> </ul> </div> </div> <div><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></div> <div> <p><strong>Funding</strong>: This dataset was generated within the mFUND&nbsp;<a href="https://bmdv.bund.de/SharedDocs/DE/Artikel/DG/mfund-projekte/kiwi.html">KIWI project</a> funded by the Federal Ministry for Digital and Transportation Germany and the DLR undertaking "Wetter und Disruptive Ereignisse".</p> <p><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></p> <p><strong>Acknowledgements:</strong></p> <p>The necessary RANS simulations were performed as part of the EU-funded AWIATOR by DLR's Institute of Aerodynamics and Flow Technology.</p> <p>We acknowledge Airbus for the allowance to use the RANS data.</p> <p>The LES was performed with the incompressible Navier-Stokes code MGLET [5] and kindly provided by the Technical University of Munich, Hydromechanics.</p> <p>The wake vortex simulations were computed on the high performance computer SuperMUC-NG by Leibniz-Rechenzentrum (LRZ).</p> </div> <div><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></div> <div>&nbsp;</div> <div><strong>References</strong>:&nbsp;</div> <div>&nbsp;</div> <div>[1] Robey, Rachel, and Julie K. Lundquist. "Behavior and mechanisms of Doppler wind lidar error in varying stability regimes."&nbsp;<em>Atmospheric Measurement Techniques</em> 15.15 (2022): 4585-4622.</div> <div>&nbsp;</div> <div>[2] Stephan, Anton, Norman Wildmann, and Igor Smalikho. "Effectiveness of the MFAS Method for Determining the Wind Velocity Vector from Windcube 200s Lidar Measurements." <em>Atmospheric and Oceanic Optics</em> 32.5 (2019): 555-563.</div> <div>&nbsp;</div> <div>[3] Smalikho, Igor., et al. "Method of radial velocities for the estimation of aircraft wake vortex parameters from data measured by coherent Doppler lidar." <em>Optics Express</em>&nbsp; &nbsp; &nbsp; 23.19 (2015): A1194-A1207.</div> <div>&nbsp;</div> <div>[4] Gerz, Thomas, Frank Holz&auml;pfel, and Denis Darracq. "Commercial aircraft wake vortices." <em>Progress in Aerospace Sciences</em> 38.3 (2002): 181-208.&nbsp;</div> <div>&nbsp;</div> <div>[5] Manhart, Michael. "A zonal grid algorithm for DNS of turbulent boundary layers."&nbsp;<em>Computers &amp; fluids</em> 33.3 (2004): 435-461.</div>

opencc-by-4.0Jul 2024View details →
zenodo44/100

Point clouds from terrestrial laser scanning from crowns of individual Scots pine trees

<p>Trees adapt to their growing conditions by regulating the sizes of their parts and their relationships. For example, removal or death of adjacent trees increases the growing space and the amount of light received by the remaining trees enabling their crowns to expand. Knowledge about the effects of silvicultural practices on crown size and shape as well as about the quality of branches affecting the shape of a crown is, however, still limited. Laser scanning (or Light detecting and ranging LiDAR) has provided new opportunities for characterizing trees in more detail in three-dimensional space. Especially terrestrial laser scanning (TLS) has increasingly been used in producing a variety of tree attributes. This data set includes 3D reconstruction of crowns of Scots pine (<em>Pinus sylvestris</em> L.) trees from sample plots with different thinning treatments. The thinning treatments include two intensities of thinning, three thinning types as well as control (i.e. no thinning treatment since the establishment). This data set can be used in developing point cloud processing algorithms for single tree crown characterization and for investigating variation in crown size and shape as well as the effects of various thinning treatments on crown size and shape of Scots pine trees grown in boreal forests.</p>

opencc-by-4.0Dec 2021View details →
zenodo44/100

Lago Argentino digital core scans and stratigraphic logs

<p>This dataset includes full resolution (20 micron per pixel) digital core scans of all lake cores collected during the 2019 GCO project coring of Lago Argentino.</p> <p>A second folder includes a stratigraphic log and description of each core, created in PSICAT.</p> <p>This dataset is uploaded alongside the submission &quot;Physical limnology and sediment dynamics of Lago&nbsp;Argentino, the world&rsquo;s largest ice-contact lake&quot; to JGR: Earth Surface.</p> <p>All analyses were conducted at the Continental Scientific Drilling Facility at the&nbsp;University of Minnesota.</p> <p>For any questions about this&nbsp;dataset, please contact vanwy048@umn.edu .</p>

opencc-by-4.0Jan 2022View details →
zenodo44/100

Scanning the horizon for invasive plant threats using a data-driven approach

<p>This repository holds the data and code for the manuscript &quot;Scanning the horizon for invasive plant threats using a data-driven approach&quot;.&nbsp;</p> <p><strong>Contents</strong></p> <ul> <li>code: descriptions below</li> <li>data: descriptions below</li> <li>intermediate-data: datasets produced by processing original data (see code) or produced through horizon scan process (descriptions below)</li> <li>fl-plants-horizon-scan.Rproj: RStudio project for running R scripts</li> </ul> <p>&nbsp;</p> <table> <thead> <tr> <th scope="col">code</th> <th scope="col">description</th> </tr> </thead> <tbody> <tr> <td>gcw_processing.R</td> <td>R script to format data downloaded from the Global Compendium of Weeds</td> </tr> <tr> <td>native_introduced_ranges.R</td> <td>R script to create map of native and introduced ranges of taxa on the final list</td> </tr> <tr> <td>random_draws_plant_families.R</td> <td>R script to evaluate over- and underrepresentation of plant families in initial and final list</td> </tr> <tr> <td>review_process_comparison.R</td> <td>R script to evaluate differences in scores before and after peer-review and consensus-building</td> </tr> <tr> <td>scores_certainty_pathways.R</td> <td>R script to create figures of scores, certainty, and pathways for final list</td> </tr> <tr> <td>risk_scores_analys.R</td> <td>R script to evaluate final risk scores</td> </tr> <tr> <td>pathways_process.R</td> <td>R script to process pathways to introduction data</td> </tr> <tr> <td>taxa_list_processing.R</td> <td>R script to create list used for rapid risk assessments from an initial list</td> </tr> </tbody> </table> <p>&nbsp;</p> <table> <thead> <tr> <th scope="col">data</th> <th scope="col">description</th> </tr> </thead> <tbody> <tr> <td>cab_list_full.csv</td> <td>list of potential invasive species to Florida generated by CABI Horizon Scan Tool on November 15, 2019</td> </tr> <tr> <td>GCW_full_list_020420.csv</td> <td>Global Compendium of Weeds downloaded on February 4, 2020</td> </tr> <tr> <td>PlantAtlasDataExport-20191211-194219.csv</td> <td>Atlas of Florida plants downloaded December 11, 2019</td> </tr> <tr> <td>Taxon_x_List_GloNAF_vanKleunenetal2018Ecology_121119.csv</td> <td>GloNAF 1.2 database downloaded December 11, 2019</td> </tr> <tr> <td>the-plant-list</td> <td>The Plant List Database downloaded August 3, 2021</td> </tr> </tbody> </table> <p>&nbsp;</p> <table> <thead> <tr> <th scope="col">intermediate-data</th> <th scope="col">description</th> </tr> </thead> <tbody> <tr> <td>federal_noxious_weed_list.csv</td> <td>manually formatted version of the USDA Federal Noxious Weed List downloaded March 16, 2020</td> </tr> <tr> <td>first_round_assessments_050120.csv</td> <td>rapid risk assessments for horizon scan pre-peer-review</td> </tr> <tr> <td>fl_prohibited_plants.csv</td> <td>manually compiled list of prohibited plants in Florida based on the Florida Noxious Weed List, Florida Prohibited Plants list, and Florida Invasive Species Council (all downloaded March 9, 2020)</td> </tr> <tr> <td>horizon_scan_plants_full_reviews_080321.csv</td> <td>rapid risk assessments for horizon scan post-peer-review and consensus-building</td> </tr> </tbody> </table> <p>&nbsp;</p>

openmit-licenseFeb 2022View details →

ScienceDex guides

Understand access before you commit

These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.

Compare curated 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.

allen-brain-atlas
neuroscienceopenDocumentation, web resources, and API references are available online.
Last verified 2026-04-30Open record

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.

abode-home-cage
behavioral-neuroscienceopenThe DataShare record exposes download links for annotations, documentation, license text, and the zipped per-snippet data directory.
Last verified 2026-04-30Open record

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.

dandi-nwb
electrophysiologyopenPublished Dandiset metadata and archive endpoints are available through the production DANDI API.
Last verified 2026-04-30Open record

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.

ibl
behavioral-neuroscienceopenPublic sessions can be searched and loaded from the IBL public data server through ONE.
Last verified 2026-04-29Open record

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.

openneuro
neuroscienceopenPublished datasets are available on demand over the internet.
Last verified 2026-04-29Open record