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.
787
datasets available to search
ShareScore release 0.9.0
Dataset results
787 results for “radar”
Radar-derived rainfall event characteristics and ERA5 parameters
<p>Contains interpolated time series of areal radar variables from 01/01/2010 to 31/12/2020 for 15 operational radars (refer to radar_codes.txt) for specific sites, dataset of clustered rainfall events over all radar sites, and mean ERA5 variables over event duration for each event. Rainfall events were identified only using data within a 100km radius of the radar, with gaps of one timestep interpolated over using the arithmetic mean of value on either side of the gap, and using an areal mean rain rate threshold of 0.1 mm/h. Created using Level 2 rain rate and Steiner classification data from the Australian Unified Radar Archive (AURA) and ERA5 reanalysis data, both of which are available through NCI. </p>
EISCAT Svalbard radar Common Program data from February 26 to February 28 2023, which is processed by GUISDAP
<p>This is two-dimensional (time and altitude) ionospheric parameter data that contains electron density, electron temperature and ion temperature. It is estimated based on EISCAT Svalbard radar measurement implemeted as common program from February 26 to Feburuary 28, 2023 (https://portal.eiscat.se/) and processed by a software for incoherent scatter radar analysis, GUISDAP (https://gitlab.com/eiscat/guisdap9). The more detailed descriptions can be found as metadata in the uploaded netCDF file.</p>
Radar measurements for the article "Dynamic differential reflectivity calibration using vertical profiles in rain and snow"
<p><strong>Dataset documentation</strong></p> <p>The archives in hdf5 format provided at this link contain the datasets used in the manuscript <em>Dynamic differential reflectivity calibration using vertical profiles in rain and snow</em>, submitted to <em>Remote Sensing</em> (MDPI) by Alfonso Ferrone and Alexis Berne in 2020.</p> <p> </p> <p><strong>File content</strong></p> <p>Each file is structured as a table, with each column referring to a specific variable and each row containing a different realization (in space or time). The set of available variables is campaign dependent, and the possibilities are:</p> <ul> <li> <p><strong>idx</strong>, and integer index that starts at 1 for the first scan of the dataset and increases by 1 for every successive scan;</p> </li> <li> <p><strong>t</strong>, the timestamp of the scan, in seconds since seconds since Jan 01, 1970;</p> </li> <li> <p><strong>r</strong> or <strong>rg</strong> (depending on the file), the distance from the radar in meters;</p> </li> <li> <p><strong>az</strong>, the azimuth angle in degrees;</p> </li> <li> <p><strong>el</strong>, the elevation angle in degrees;</p> </li> <li> <p><strong>zdr</strong>, the uncalibrated differential reflectivity, in dB;</p> </li> <li> <p><strong>zh</strong>, the horizontal reflectivity, in dBZ;</p> </li> <li> <p><strong>rhovh</strong> or <strong>rho</strong>, the co-polar correlation coefficient, unitless;</p> </li> <li> <p><strong>snr_h</strong> or <strong>snr</strong>, the signal to noise ratio for the horizontal channel in dB;</p> </li> <li> <p><strong>snrv</strong>, the signal to noise ratio for the vertical channel, in dB,</p> </li> <li> <p><strong>ngates</strong>, the number of unique range gates.</p> </li> </ul> <p>For the comparison of the data collected by MXPol and DX50 during the PAYERNE campaign, two auxiliary variables were added to the archives:</p> <ul> <li> <p><strong>x</strong> the horizontal distance from the current radar, computed on a line passing through the location of two radars;</p> </li> <li> <p><strong>z</strong> the vertical distance from the current radar.</p> </li> </ul> <p> </p> <p><strong>Usage</strong></p> <p>The dataset are provided in the the Hierarchical Data Format version 5 (HDF5), an open source file format, supported by several programming language.</p> <p>They archives were created using the <em>vaex</em> library for Python 3:</p> <p>https://github.com/vaexio/vaex</p> <p>The function <em>vaex.open</em> from the same library can be used for accessing the archives and converting them to <em>vaex.DataFrame</em>.</p> <p> </p> <p><strong>Campaign-specific information</strong></p> <p>Some of the parameters associated to the variables included in the archives may change depending on the campaign. The following subsection provide a summary of these information.</p> <p> </p> <p><strong>dataframe_HYMEX_2013_from_20130907-040344_to_20131105-175944.hdf5</strong></p> <p>Contains PPI scans at 90° elevation for the HYMEX campaign.</p> <p>Location information:</p> <ul> <li> <p>Latitude: 44.61° N</p> </li> <li> <p>Longitude: 4.55° E</p> </li> <li> <p>Altitude: 604 m.a.s.l.</p> </li> </ul> <p>Technical information:</p> <ul> <li> <p>Radar Frequency: 9.41 GHz</p> </li> <li> <p>Theoretical 3 dB angular beamwidth of the antenna: 1.45°</p> </li> </ul> <p>Scan setup:</p> <ul> <li> <p>Range resolution: 75 m</p> </li> <li> <p>Range to the first gate: 204.3 m</p> </li> </ul> <p>Processsing parameters:</p> <ul> <li> <p>Clutter filtering: OFF</p> </li> <li> <p>Minimum rhohv: 0.6</p> </li> <li> <p>Attenuation correction: Z-PHI method</p> </li> <li> <p>Note on reflectivity calibration: The original manufacturer calibration constant was 7.56 dBZ. The value used here derives from comparison with disdrometers during the HYMEX campaign.</p> </li> </ul> <p> </p> <p><strong>dataframe_PAYERNE_2014_from_20140321-160016_to_20140519-085808.hdf5</strong></p> <p>Contains PPI scans at 90° elevation performed by MXPol during the PAYERNE campaign.</p> <p>Location information:</p> <ul> <li> <p>Latitude: 46.81° N</p> </li> <li> <p>Longitude: 6.94° E</p> </li> <li> <p>Altitude: 496 m.a.s.l.</p> </li> </ul> <p>Technical information:</p> <ul> <li> <p>Radar Frequency: 9.41 GHz</p> </li> <li> <p>Theoretical 3 dB angular beamwidth of the antenna: 1.45°</p> </li> </ul> <p>Scan setup:</p> <ul> <li> <p>Range resolution: 75 m</p> </li> <li> <p>Range to the first gate: 204.3 m</p> </li> </ul> <p>Processsing parameters:</p> <ul> <li> <p>Clutter filtering: OFF</p> </li> <li> <p>Minimum rhohv: 0.6</p> </li> <li> <p>Attenuation correction: None</p> </li> </ul> <p> </p> <p><strong>dataframe_DAVOS_2014_from_20140704-090224_to_20141231-105720.hdf5</strong></p> <p>Contains PPI scans at 90° elevation for the DAVOS campaign.</p> <p>Location information:</p> <ul> <li> <p>Latitude: 46.82° N</p> </li> <li> <p>Longitude: 9.82° E</p> </li> <li> <p>Altitude: 2220 m.a.s.l.</p> </li> </ul> <p>Technical information:</p> <ul> <li> <p>Radar Frequency: 9.41 GHz</p> </li> <li> <p>Theoretical 3 dB angular beamwidth of the antenna: 1.45°</p> </li> </ul> <p>Scan setup:</p> <ul> <li> <p>Range resolution: 75 m</p> </li> <li> <p>Range to the first gate: 204.3 m</p> </li> </ul> <p>Processsing parameters:</p> <ul> <li> <p>Clutter filtering: OFF</p> </li> <li> <p>Minimum rhohv: 0.6</p> </li> <li> <p>Attenuation correction: None</p> </li> </ul> <p> </p> <p><strong>dataframe_APRES3_from_20151207-123944_to_20160129-125856.hdf5</strong></p> <p>Contains PPI scans at 90° elevation for the APRES3 campaign.</p> <p>Location information:</p> <ul> <li> <p>Latitude: 66.66 S</p> </li> <li> <p>Longitude: 140.00 E</p> </li> <li> <p>Altitude: 40 m.a.s.l.</p> </li> </ul> <p>Technical information:</p> <ul> <li> <p>Radar Frequency: 9.41 GHz</p> </li> <li> <p>Theoretical 3 dB angular beamwidth of the antenna: 1.45°</p> </li> </ul> <p>Scan setup:</p> <ul> <li> <p>Range resolution: 75 m</p> </li> <li> <p>Range to the first gate: 354.3 m</p> </li> </ul> <p>Processsing parameters:</p> <ul> <li> <p>Clutter filtering: OFF</p> </li> <li> <p>Minimum rhohv: 0.6</p> </li> <li> <p>Attenuation correction: None</p> </li> </ul> <p> </p> <p><strong>dataframe_VALAIS_2016_from_20161104-154312_to_20170306-195912.hdf5</strong></p> <p>Contains PPI scans at 90° elevation for the VALAIS campaign.</p> <p>Location information:</p> <ul> <li> <p>Latitude: 46.12 N</p> </li> <li> <p>Longitude: 7.10 E</p> </li> <li> <p>Altitude: 460 m.a.s.l.</p> </li> </ul> <p>Technical information:</p> <ul> <li> <p>Radar Frequency: 9.41 GHz</p> </li> <li> <p>Theoretical 3 dB angular beamwidth of the antenna: 1.27°</p> </li> </ul> <p>Scan setup:</p> <ul> <li> <p>Range resolution: 30 m</p> </li> <li> <p>Range to the first gate: 226.95 m</p> </li> </ul> <p>Processsing parameters:</p> <ul> <li> <p>Clutter filtering: OFF</p> </li> <li> <p>Minimum rhohv: 0.6</p> </li> <li> <p>Attenuation correction: None</p> </li> </ul> <p> </p> <p><strong>dataframe_DX50_from_20140501-020000_to_20140524-015752.hdf5</strong></p> <p>Contains PPI scans at 90° elevation performed by DX50 during the PAYERNE campaign.</p> <p>Location information:</p> <ul> <li> <p>Latitude: 46.84° N</p> </li> <li> <p>Longitude: 6.92° E</p> </li> <li> <p>Altitude: 450 m.a.s.l.</p> </li> </ul> <p>Technical information:</p> <ul> <li> <p>Radar Frequency: 9.459 GHz</p> </li> <li> <p>Theoretical 3 dB angular beamwidth of the antenna: 1.273°</p> </li> </ul> <p>Scan setup:</p> <ul> <li> <p>Range resolution: 75 m</p> </li> <li> <p>Range to the first gate: 0.0 m</p> </li> </ul> <p>Processsing parameters:</p> <ul> <li> <p>Clutter filtering: OFF</p> </li> <li> <p>Minimum rhohv: 0.0</p> </li> <li> <p>Attenuation correction: None</p> </li> </ul> <p> </p> <p><strong>dataframe_DX50_RHI_201405.hdf5</strong></p> <p>Contains RHI scans from DX50 the PAYERNE campaign.</p> <p>The remaining information equal to the ones listed for <em>dataframe_DX50_from_20140501-020000_to_20140524-015752.hdf5</em>.</p> <p> </p> <p><strong>dataframe_MXPol_RHI_201405.hdf5</strong></p> <p>Contains RHI scans from MXPol the PAYERNE campaign.</p> <p>The remaining information is equal to the ones listed for <em>dataframe_PAYERNE_2014_from_20140321-160016_to_20140519-085808.hdf5</em>.</p>
STREAM - Sub-THz Radar sensing of the Environment for future Autonomous Marine platforms: Multi-Perspective Sensing - Maritime Environment - Side-looking Perspective
<p>This dataset contains the files corresponding to which results have been included in the journal paper titled 'High-Resolution Multi-Modal Sensing of Distributed Radar Network'. The full description of the conducted trials and data structure is mentioned in the attached PDF document.</p> <p>The trials were conducted at the Gosport Marina, Portsmouth, UK with a sea state of approximately 3 according to the Douglas Scale.</p> <p>The experiments were performed with automotive radars operating in the 79 GHz band to investigate the Doppler and imaging capabilities of these radars. A multi-sensory suite distributed around Valkyrie VI was mounted in front, corner, side and backward-looking orientations.</p> <p>This dataset contains data from the side-looking orientation, where the installation angle of radar is 90 degrees respective to the platform velocity vector.</p> <p><strong>Radar Data:</strong></p> <p>The radar data is stored in the file 'GM2_Out1_240522_160925.h5'. The methodology to process the data in MATLAB is presented in the attached pdf. document.</p> <p><strong>Inertial Measurement Unit:</strong></p> <p>Three xSens 680G IMU were mounted on the roof, front and back of the boat. They have been included in the corresponding zip folders.</p> <p>PC3_Corner_RLG: IMU at the corner of the boat.</p> <p>PC4_Forward_RLG: IMU at the roof of the boat.</p> <p>PC5_Backward_RLG: IMU at the back of the boat.</p> <p>The IMU data is converted to .txt files that can be directly loaded into MATLAB.</p> <p><strong>Timestamped Velocity:</strong></p> <p>The file 'Corner_160925.mat' contains the time-stamped velocity for each radar frame. Here, the integration interval is 128 ms with 512 radar chirps.</p> <p>The file 'CommonFramesCornner_160925.mat' contains the timestamped velocity for the frames that are synchronised with the frames of front-looking radar.</p> <p>(The dataset for the front-looking radar is stored in another repository with DOI: 10.5281/zenodo.14215115)</p> <p><strong>Camera:</strong></p> <p>Each radar also has a camera for ground truth. The time-stamped camera frames for each radar frame are stored in 'CommonFramesCornner_160925.mat'.</p> <p>Processed camera frames and video of the scene are available in: 'GM2_Corner_240522_160925_CameraFrames.zip'.</p> <p> </p> <p>For more information, please contact:</p> <p>Anum Pirkani: a.a.a.pirkani@bham.ac.uk, anum.apirkani@gmail.com</p> <p>Marina Gashinova: m.s.gashinova@bham.ac.uk</p>
STREAM - Sub-THz Radar sensing of the Environment for future Autonomous Marine platforms: Multi-Perspective Sensing - Maritime Environment - Front-looking Perspective
<p>This dataset contains the files corresponding to which results have been included in the journal paper titled 'High-Resolution Multi-Modal Sensing of Distributed Radar Network'. The full description of the conducted trials and data structure is mentioned in the attached PDF document.</p> <p>The trials were conducted at the Gosport Marina, Portsmouth, UK with a sea state of approximately 3 according to the Douglas Scale.</p> <p>The experiments were performed with automotive radars operating in the 79 GHz band to investigate the Doppler and imaging capabilities of these radars. A multi-sensory suite distributed around Valkyrie VI was mounted in front, corner, side and backward-looking orientations.</p> <p>This dataset contains data from the front-looking orientation, where the installation angle of radar is 0 degrees respective to the platform velocity vector.</p> <p><strong>Radar Data:</strong></p> <p>The radar data is stored in the file 'GM2_Lab_240522_160943.h5'. The methodology to process the data in MATLAB is presented in the attached pdf. document.</p> <p><strong>Inertial Measurement Unit:</strong></p> <p>Three xSens 680G IMU were mounted on the roof, front and back of the boat. They have been included in the corresponding zip folders.</p> <p>PC3_Corner_RLG: IMU at the corner of the boat.</p> <p>PC4_Forward_RLG: IMU at the roof of the boat.</p> <p>PC5_Backward_RLG: IMU at the back of the boat.</p> <p>The IMU data is converted to .txt files that can be directly loaded into MATLAB.</p> <p><strong>Timestamped Velocity:</strong></p> <p>The file 'Front_160943.mat' contains the time-stamped velocity for each radar frame. Here, the integration interval is 128 ms with 512 radar chirps.</p> <p>The file 'CommonFramesFront_160943.mat' contains the timestamped velocity for the frames that are synchronised with the frames of side-looking radar.</p> <p>(The dataset for the side-looking radar is stored in another repository with DOI: 10.5281/zenodo.14174138)</p> <p><strong>Camera:</strong></p> <p>Each radar also has a camera for ground truth. The time-stamped camera frames for each radar frame are stored in 'CommonFramesFront_160943.mat'.</p> <p>Processed camera frames and video of the scene are available in: 'GM2_Front_240522_160943_CameraFrames.zip'.</p> <p> </p> <p>For more information, please contact:</p> <p>Anum Pirkani: a.a.a.pirkani@bham.ac.uk, anum.apirkani@gmail.com</p> <p>Marina Gashinova: m.s.gashinova@bham.ac.uk</p>
Supplementary material for 'Revealing patterns of nocturnal migration using the European weather radar network'
<p>This package contains data, filters and visualizations from <a href="https://doi.org/10.1111/ecog.04003">Nilsson and Dokter et al. (2019)</a>.</p> <p><strong>Files</strong></p> <p><strong>radar_metadata.csv</strong>: Metadata for the 84 European radars considered for this study. Includes radar code (<code>odim_code</code> = <code>country</code> + <code>odim_code_3char</code> and alternative radar code <code>vp_radar</code>), radar site location (<code>location</code>, <code>latitude</code>, <code>longitude</code>), radar site elevation (<code>site_altitude_asl</code> in meters above sea level) and radar altitude range used in this study (<code>min_height_cut_asl</code> and <code>max_height_cut_asl</code> in meters above sea level).</p> <p><strong>vp.zip</strong>: Vertical profiles of birds (vp) data, processed from the radar volume data following procedures described by Dokter et al. (2011), using the vol2bird algorithm in the R package bioRad. Zip file includes vp data for the 84 European radars considered for this study from September 19 to October 9, 2016 (21 days). This time period is characterized by strong passerine migration throughout Europe. Files are organized in radar (= <code>odim_code</code>), date and hour directories and follow the <a href="https://github.com/adokter/vol2bird/wiki/ODIM-bird-profile-format-specification">ODIM bird profile format specification</a>. Data can be read with the <a href="https://github.com/adokter/bioRad/">R package bioRad</a>.</p> <p><strong>vp_processing_settings.yaml</strong>: Data selection setting for this study, based on data quality criteria. File lists for each radar the altitudes to include (<code>include_heights</code>), time periods to exclude (<code>exclude_datetimes</code>) and reasons for exclusion (comments). 70 of the 84 radars were retained after filtering.</p> <p><strong>vp_processed_70_radars_20160919_20161009.csv</strong>: Processed vp data for 70 radars. Is the result of processing <code>vp.zip</code> with <code>vp_processing_settings.yaml</code> and <code>radar_metadata.csv</code> using <a href="https://doi.org/10.5281/zenodo.1173544">vp-processing</a> (Desmet & Nilsson 2018). Note: includes all timestamps: day and night & those marked for exclusion (marked in <code>exclusion_reason</code>). This data file forms the basis for analysis in the study.</p> <p>Headers are:</p> <ul> <li><code>radar_id</code>: odim_code of the radar</li> <li><code>datetime</code>: timestamp</li> <li><code>HGHT</code>: lower altitude of altitude bin (m above sea level)</li> <li><code>u</code>: bird ground speed towards east (m/s)</li> <li><code>v</code>: bird ground speed towards north (m/s)</li> <li><code>dens</code>: bird density (birds/km3)</li> <li><code>dd</code>: bird flight direction (degrees from north)</li> <li><code>ff</code>: bird ground speed (m/s)</li> <li><code>DBZH</code>: reflectivity factor (dBZ) in horizontal polarisation</li> <li><code>mtr</code>: migration traffic rate (birds/km/h)</li> <li><code>day_night</code>: timestamp occurs during <code>day</code> or <code>night</code> (based on sunrise/sunset)</li> <li><code>date_of_sunset</code>: date at sunset, with night timestamps between midnight and sunrise belonging to the previous date</li> <li><code>exclusion_reason</code>: reason timestamp is excluded in vp_processing_settings.yaml (if applicable). Excluded timestamps have <code>NA</code> values for <code>u</code>, <code>v</code>, <code>dens</code>, <code>dd</code>, <code>ff</code>, <code>DBZH</code>, and <code>mtr</code>.</li> </ul> <p><strong>vp_flowviz.csv:</strong> Input data for visualizations. Is the result of processing <code>vp_processed_70_radars_20160919_20161009.csv</code> using <code>vp-to-flowviz.Rmd</code> in <a href="https://doi.org/10.5281/zenodo.1173544">vp-processing</a> (Desmet & Nilsson 2018). Aggregates data in hourly bins for 200-2000m (<code>altitude_band</code> = 1) and above (<code>altitude_band</code> = 2). Only altitude band 1 is used in visualizations.</p> <p><strong>flowviz.mov:</strong> Screencast of <code>vp_flowviz.csv</code> visualized with <a href="https://doi.org/10.5281/zenodo.57472">Bird migration flow visualization v2</a> (Desmet et al. 2016, Shamoun-Baranes et al. 2016). The visualization extrapolates the migration over the entire sampling range (cropped in the screencast due to technical limitations and thus excluding the Bulgarian radar), not taking topography or water bodies into account, and shows the ground speed (length of arrows) and direction of migration over time. Note that density is not shown: low density movements can therefore appear as strong as high density movements when ground speeds are similar.</p> <p><strong>cartoviz.mov:</strong> Screencast of <code>vp_flowviz.csv</code> visualized as an interactive map with <a href="https://carto.com">CARTO</a>. Visualization shows migration density (size of circles) and mean direction (colour) over time. The interactive map is available at <a href="https://inbo.carto.com/u/lifewatch/builder/8685140f-8d8c-4d06-9e1e-25d051d43748/embed">https://inbo.carto.com/u/lifewatch/builder/8685140f-8d8c-4d06-9e1e-25d051d43748/embed</a>.</p>
Climatology of rainfall from Atlantic hurricanes in the USA from radar data
<p>Atlantic Tropical Cyclone Rainfall Climatology in the USA<br> Data sources (see references): NEXRAD level III data, hourly precipitation; IBtracs best track data; University of Colorado extended best track data<br> Available as NetCDF files and Matlab structure</p> <p>Classification as TC precipitation criteria: within radius of outermost closed isobar of a TC at a given time</p> <p>Scope: 100km radius around corresponding radar station</p> <p>Dealing with radar outages: up to 2h gap - interpolation of precipitation, larger gaps - rescaling of frequency with fraction of available data (see formulas)</p> <p>Available variables per radar station:</p> <ul> <li>Location: name [ ], coordinates [°N, °W]</li> <li>Grid: lat [°N], lon [°E]</li> <li>Frequency rescaling: re_freq [ ]</li> </ul> <p>Available variables per event:</p> <ul> <li>Storm identifiers: name [ ], year [a]</li> <li>Storm total precipitation <ul> <li>Area distribution: Ptot [kg/m<sup>2</sup>], gridded (0.1x0.1°)</li> <li>Area average: Ptot_av [kg/m<sup>2</sup>]</li> <li>Area maximum within 0.5x0.5°: Ptot_max [kg/m<sup>2</sup>]</li> </ul> </li> <li>Annual exceedance frequency: f(Ptot_max) [a^-1]</li> </ul> <p>Relevant formulas:</p> <p>re_freq = total duration of storm exposure / duration of viable measurements<br> f (Ptot_max) = (number of events exceeding Ptot_max / length of observation) * re_freq</p> <p>Matlab structure:</p> <ul> <li>Level 1: TCP_climatology</li> <li>Level 2: station variables -> station_event_data leads to event variables</li> <li>Level 3: event variables -> Ptot leads to spatially gridded precipitation</li> <li>Level 4: Ptot-grid</li> </ul>
Radar and Lidar scattering lookup tables for atmospheric hydrometeors using a T-Matrix method and a Mie theory
<h2>Overview</h2> <p>The database includes text files containing the scattering amplitude matrices for single spherical/nonspherical particles for radar and lidar. They are the lookup tables used for calculating radar and lidar observables in the Cloud-Resolving Radar Simulator (Oue et al. 2020). The radar scattering properties were calculated for several hydrometeor categories using a T-matrix method proposed by Mishchenko (2000) accounting for incident angles, scattering direction (forward and backward), polarimetry (horizontally (H) and vertically (V) polarized waves), particle aspect ratio, phase (liquid or ice), bulk density, temperature, particle size, and radar frequency. The lidar scattering properties at a vertical incidence were calculated for spherical liquid or ice particles using the BHMIE Mie code (Bohrean and Hyffman,1998) accounting for lidar wavelength, temperature, and bulk density. The hydrometeor categories are commonly used for cloud resolving models employing bulk microphysical schemes (e.g., cloud, rain, ice cloud, snow aggregates, and graupel). Detailed descriptions are also available in the CR-SIM user guide (https://github.com/marikooue/CR-SIM/releases/tag/crsim-v3.34).</p> <h2>Data structure</h2> <p>The data files are arranged and zipped every hydrometeor types. The names of the tar-zipped directories under the top directory LLUT3 represents the hydrometer type.<br>For lidar scattering, the following directories are included:<br>ceilo: Ceilometer lidar backscatter properties at a wavelength of 905 nm<br>mpl: Micropulse lidar (MPL) backscatter properties at wavelengths of 353 and 532 nm</p> <p>For radar scattering, the following hydrometer types are included:<br>cloud: Radar scattering for liquid cloud droplets (spherical shape)<br>raina: Radar scattering for raindrops with the aspect ratio model proposed by Andsager et al. (1999)<br>rainb: Radar scattering for raindrops with the aspect ratio model proposed by Brandes et al (2002)<br>ice_ar0.90: Radar scattering for cloud ice with an aspect ratio of 0.9<br>ice_ar0.20: Radar scattering for cloud ice with an aspect ratio of 0.2<br>smallice: Radar scattering for spherical cloud ice particles<br>snow_ar0.60: Radar scattering for snowflakes with an aspect ratio of 0.6<br>graupel_ar0.60: Radar scattering for graupel particles with an aspect ratio of 0.6<br>graupel_ar0.80: Radar scattering for graupel particles with an aspect ratio of 0.8<br>graupel: Radar scattering for spherical graupel particles<br>gh_ryzh: Radar scattering for graupel particles with the graupel aspect ratio model proposed by Ryzhkov et al (2011)<br>unrimedice_ar0.40: Radar scattering for unrimed ice particles with an aspect ratio of 0.4<br>unrimedice_ar0.60: Radar scattering for unrimed ice particles with an aspect ratio of 0.6<br>unrimedice_ar0.80: Radar scattering for unrimed ice particles with an aspect ratio of 0.8<br>unrimedice: Radar scattering for spherical unrimed ice particles<br>partrimedice_ar0.40: Radar scattering for partially rimed ice particles with an aspect ratio of 0.4<br>partrimedice_ar0.60: Radar scattering for partially rimed ice particles with an aspect ratio of 0.6<br>partrimedice_ar0.80: Radar scattering for partially rimed ice particles with an aspect ratio of 0.8<br>partrimedice: Radar scattering for partially rimed spherical ice particles </p> <h2>The file name convention </h2> <p>For lidar scattering data, each file name has the following format:<br>[hydrometeor type]_[instrument name]_ [wavelength in nm]_[phase ID]_d[bulk density in kg m-3].dat<br>The hydrometeor type shows: 1) ‘cld’ for liquid cloud droplets, and 2) ‘ice’ for ice particles. The phase ID shows: 1) ‘p25’ for ceilometer liquid cloud, 2) ‘p20’ for MPL lidar liquid cloud, and 3) ‘m30’ for MPL lidar ice. </p> <p>For radar scattering data, each file name has the following format.<br>[hydrometeor type]_fr[frequency in GHz]GHz_t[temperature in K]_rho[bulk density in kg m-3]_el[elevation angle in degree].dat<br>The hydrometeor type follows the directory name presented above.</p> <h2>Format of the data files</h2> <p>Line 1: Wavelength in mm<br>Line 2: Temperature in K<br>Line 3: Refractive index (real and imaginary)<br>Line 4: Number of radii calculated and number of elevation angles<br>Line 6: Incident angle and scattered angle in degrees<br>Line 7: Radius in mm and aspect ratio<br>Line 8: Forward scattering amplitude for co-polarization VV and HH (complex number)<br>Line 9: Backward scattering amplitude for co- and cross polarizations VV, VH, HV, HH (complex number) <br>Line 10 to the end of file: Repeat Line 7 to Line 9 with different radii until the maximum radius.</p>
Simultaneous lidar and radar measurements for aeroso-cloud interaction studies
<p>Optical and microphysical aerosol and cloud properties derived from lidar and radar for aeroso-cloud interaction studies.</p>
Meteor observations and wind estimates from the northern Germany SIMONe radar network on November 5, 2018
<p>This dataset includes meteor observations and wind estimates taken as part of the SIMONe 2018 campaign in northern Germany on November 5, 2018. The files are in netCDF-4 format and follow CF conventions (https://cfconventions.org/). We recommend loading the data using the xarray Python package.</p> <p>The SIMONe 2018 campaign ran from November 2, 2018 through November 9, 2018 in northern Germany. The radar network consisted of two pulsed transmitters in Juliusruh and Collm and a five-element interferometric MIMO-CW transmitter located in Kühlungsborn. Monostatic receiver stations co-located with the pulsed transmitters and six additional receiver stations located in Mechelsdorf, Breege, Neustrelitz, Guderup, Salzwedel, and Bornim were used to form a total of two monostatic and ten bistatic links. The data from these individual links were then processed to detect specular meteor echoes and estimate their parameters, including Doppler shift. The Doppler shifts, imposed by movement of the meteor trail due to the neutral winds, were then used to estimate the 4-D wind field. More details about the campaign can be found in Vierinen et al. (2019). Details for the wind field estimation can be found in Volz et al. (submitted).</p>
Gridded depth and accumulation products from dated airborne radar stratigraphy over West Antarctica during the mid-Holocene, v.1.0.0
<p>This dataset comprises of codes (written in MATLAB) and gridded files (exported as GeoTIFF) presented in Bodart et al. (2023; The Crysophere; <a href="https://doi.org/10.5194/tc-2022-199">https://doi.org/10.5194/tc-2022-199</a>). A summary of the key findings from this study is provided as follows:</p> <p>"Using a spatially extensive IRH over Pine Island Glacier, Thwaites Glacier, and Institute and Möller Ice Streams (covering a total of 610 000 km2 or 30% of the WAIS), and a local layer approximation model, we infer mid-Holocene accumulation rates over the slow-flowing parts of these catchments for the past ~4700 years. By comparing our results with modern climate reanalysis models (1979 – 2019) and observational syntheses (1651 – 2010), we estimate that accumulation rates over the Amundsen-Weddell-Ross divide were on average 18% higher during the mid-Holocene than modern rates. However, no significant spatial changes in the accumulation pattern were observed."</p> <p>This dataset contains a series of files (5x .m files, 10x .tif files). The numbering of the figures in the description below refers to the order of the figures in the associated paper.</p> <ul> <li><strong> 5x MATLAB files:</strong> <ul> <li><strong>Calculate_accumulation_rates.m</strong>: calculates accumulation rates for the mid-Holocene-to-present, as well as uncertainties associated with the age and model structural uncertainty;</li> <li><strong>Calculate_D_parameter.m</strong>: calculates the D parameter (and associated L_path, L_H and L_b) to assess the feasability of the LLA over our grid;</li> <li><strong>Calculate_longitudinal_strain_rates.m</strong>: calculates the longitudinal strain rates over our grid from modern ice-flow velocities;</li> <li><strong>Calculate_vertical_strain_rates.m</strong>: calculates vertical strain rates for the mid-Holocene-to-present part of the ice column from accumulation estimates;</li> <li><strong>Resample_IRH_data.m</strong>: Re-samples the along-track IRH data into evenly distributed 500-m points for speeding up the gridding and calculations of accumulation rates;<br> </li> </ul> </li> <li><strong>10x GeoTIFF files:</strong> <ul> <li><strong>Holocene_IRH_depth_Fig2a.tif: </strong>Figure 2a;</li> <li><strong>Holocene_accumulation_rates_Fig3a.tif:</strong> Figure 3a;</li> <li><strong>Difference_Holocene_accumulation_RACMO2_Fig3c.tif:</strong> Figure 3c;</li> <li><strong>Relative_difference_Holocene_accumulation_RACMO2_Fig4.tif:</strong> Figure 4;</li> <li><strong>D_parameter_FigS1d.tif:</strong> Figure S1d;</li> <li><strong>Holocene_vertical_strain_rates_FigS2a.tif: </strong>Figure S2a;</li> <li><strong>Longitudinal_strain_rates_FigS2b.tif:</strong> Figure S2b;</li> <li><strong>Holocene_accumulation_lower_uncertainty_FigS4a.tif:</strong> Figure S4a;</li> <li><strong>Holocene_accumulation_upper_uncertainty_FigS4b.tif:</strong> Figure S4b;</li> <li><strong>Holocene_accumulation_relative_uncertainty_FigS4c.tif: </strong>Figure S4c;</li> </ul> </li> </ul> <p>Please also cite the associated paper when using this dataset.</p> <p>Any questions, please direct them to the corresponding author, Julien Bodart (julien.bodart@ed.ac.uk).</p>
Arctic sea ice radar freeboard from ERS-1, ERS-2, Envisat and CryoSat-2
<p>This dataset presents a radar freeboard time series from 1993 to 2021 for Arctic sea ice. Envisat, ERS-2 and ERS-1 radar freeboards have been estimated using CryoSat-2 as a reference, they are "SAR-like" estimations as they have been calibrated on CS-2 SAR TFMRA50 radar freeboard. </p>
Radar-derived storm characteristics and convective diagnostics associated with hourly maximum measured wind gusts around Australia
<p>The data in this record describes various characteristics associated with hourly measured surface wind gusts across various locations in Australia, with these characteristics and data sources described below.</p> <p>This record provides all data used in the preparation of Brown et al. (2023a), except for lightning data that can be obtained from the <a href="https://wwlln.net/">World Wide Lightning Location Network archive</a></p> <p><strong>Record contents</strong></p> <ul> <li><em>gust_observations.zip</em><br> Within this zip archive, a <em>.csv</em> file is provided for wind gust observations, along with associated storm statistics from radar, and convective diagnostics from a global reanalysis. These data are provided for each of the 20 radar domains listed in Brown et al. (2023a). The <em>.csv</em> files follow the structure: <em>gust_observations_x.csv, </em>where <em>x </em>is the identification number for each radar from the <a href="https://www.openradar.io/operational-network">Australian Unified Radar Archive</a>.<br> </li> <li><em>station_details.csv</em><br> This file provides details on the automatic weather stations that measure the wind gusts, with station identifiers (column=Station_id) consistent between <em>station_details.csv </em>and<em> gust_observations_x.csv</em>.<br> </li> <li><em>Table1.pdf</em> <br> Descriptions of convective diagnostics from reanalysis, that are provided in <em>gust_observations_x.csv</em>. This table has been extracted from the supplementary information of Brown et al. (2023a), and references in this table can be found therein.<br> </li> <li><em>radar_details.pdf</em> <br> Taken from Table 1 from Brown et al. (2023a), showing the details of radars used here for storm statistics in <em>gust_observations_x.csv</em>.<br> </li> <li><em>Fig1.jpeg</em><br> Taken from from Brown et al. (2023a), showing a map of the radar domains used here for storm statistics in <em>gust_observations_x.csv</em>.</li> </ul> <p><strong>Wind gust data</strong></p> <p>Measured wind gusts here represent a 3-second average wind speed, at a height of 10 m above ground level. We also provide some derived quantities from the gust data (see table below). Gust data is provided by the <a href="http://www.bom.gov.au/climate/data/stations/">Australian Bureau of Meteorology</a>, from 204 automatic weather stations (<em>station_details.csv)</em>, chosen to be within 100 km of a weather radar with sufficient archived data. These data are originally provided by the Bureau of Meteorology at 1-minute frequency, representing a maximum over a 1-minute interval, but are resampled in this record to hourly frequency, for comparisons with other hourly data below (see Brown et al. (2023a) for details of this resampling). Note that any reuse of this data should properly acknowledge the Australian Bureau of Meteorology.</p> <p><strong>Radar data</strong></p> <p>Radar data is obtained by the <a href="https://www.openradar.io/">Australian Unified Radar Archive</a> (AURA), produced from operational weather radar within the Australian Bureau of Meteorology network. The level1b data used here is available from the AURA dataset on the Australian NCI under a CC4-BY-NC licence from <a href="https://dx.doi.org/10.25914/5f4c85732ee80">https://dx.doi.org/10.25914/5f4c85732ee80</a>. Various properties derived from radar reflectivity and Doppler velocity data is reported here in association with the wind gust observations. These properties are only reported if there is a storm object within 10 km and 10 minutes of the gust location (see Brown et al. (2023a) for storm object definition). Radar properties are described in the table below.</p> <p><strong>Environmental data</strong></p> <p>Various convective diagnostics are associated with wind gust observations, representing the convective environment and large-scale wind profile. These diagnostics are derived from a combination of pressure-level and surface-level ERA5 data (Hersbach et al. 2020), which is provided at hourly intervals on a 0.25-degree latitude-longitude grid, hosted on the Australian NCI (<a href="http://dx.doi.org/10.25914/5fb115b82e2ba">http:// dx.doi.org/10.25914/5fb115b82e2ba</a>). Details on these convective diagnostics are provided in Brown et al. (2023a), and<strong> </strong>in <em>Table1.pdf</em> as provided in this record.</p> <p><strong>Column descriptions</strong></p> <p>The following table provides descriptions of columns of <em>gust_observations_x.csv</em></p> <table> <thead> <tr> <th scope="col">Column name</th> <th scope="col">Description</th> </tr> </thead> <tbody> <tr> <td>dt_utc</td> <td>Time of the measured wind gust, from the automatic weather station data (YYYY-MM-DD HH:MM:SS UTC)</td> </tr> <tr> <td>Station_id</td> <td>Identification number of the weather station that measured the gust. See <em>station_details.csv </em>for details of each station</td> </tr> <tr> <td>Wind_gust_observed</td> <td>The measured wind gust speed (m/s)</td> </tr> <tr> <td>Peak_to_mean_wind_gust_ratio</td> <td>Ratio of the measured wind gust to the 4-hour mean at that station (with the window centred on the gust time)</td> </tr> <tr> <td>SCW</td> <td>Is the measured gust a severe convective wind event?<br> 0: Gust is either less than 25 m/s, does not have a storm object within 10 km, or has a peak-to-mean wind gust ratio less than 2.<br> 1: Gust is greater than 25 m/s, has a storm object within 10 km, and has a peak-to-mean wind gust ratio greater than 2.</td> </tr> <tr> <td>Radar_id</td> <td>Radar identification number (see <em>radar_details.pdf)</em></td> </tr> <tr> <td>Storm_speed</td> <td>Translational speed of the parent storm object (m/s). Only defined if Storm_in10km=1</td> </tr> <tr> <td>Storm_angle</td> <td>Angle of parent storm object movement. In units of degrees from N. Only defined if Storm_in10km=1</td> </tr> <tr> <td>Parent_storm_class</td> <td>The type of parent storm associated with a gust. Only defined if Storm_in10km=1. Possible types are:<br> "Non-linear"<br> "Linear"<br> "Cellular"<br> "Cell cluster"<br> "Supercellular"<br> "Embedded supercell"<br> See Brown et al. (2023a) for classification details</td> </tr> <tr> <td>Storm_in10km</td> <td>Is there a radar-derived storm object within 10 km of the gust, observed no more than 10 minutes prior to the gust?<br> 0: No<br> 1: Yes<br> See Brown et al. (2023a) for a definition of "storm object"</td> </tr> <tr> <td>Major_axis_length</td> <td>The length of the major axis of an ellipse fitted to the parent storm object (km). Only defined if Storm_in10km=1</td> </tr> <tr> <td>Minor_axis_length</td> <td>The length of the minor axis of an ellipse fitted to the parent storm object (km). Only defined if Storm_in10km=1</td> </tr> <tr> <td>Local_reflectivity_maxima</td> <td>Number of local reflectivity maxima within the parent storm object. Only defined if Storm_in10km=1</td> </tr> <tr> <td>Maximum_storm_altitude</td> <td>The maximum height of the parent storm radar reflectivity object (km). Only defined if Storm_in10km=1</td> </tr> <tr> <td>Azimuthal_shear</td> <td>Azimuthal shear of the parent storm object derived from radar data (s<sup>-1 </sup>x 1000). Only defined if Storm_in10km=1. See Brown et al (2023a) for a discussion of azimuthal shear and processing applied to this quantity here.</td> </tr> <tr> <td>ERA5_time</td> <td>Time of the ERA5 environmental data that is associated with the measured gust, corresponding to the closest previous hour (YYYY-MM-DD HH:MM:SS UTC).</td> </tr> <tr> <td>ERA5_latitude</td> <td>Location of closest ERA5 (land) grid point to measured gust, in degrees of latitude</td> </tr> <tr> <td>ERA5_longitude</td> <td>Location of closest ERA5 (land) grid point to measured gust, in degrees of longitude</td> </tr> <tr> <td>Environmental_cluster</td> <td>Event type, based on statistical clustering of environmental data (Brown et al. 2023b)<br> 0: Strong background wind cluster<br> 1: Steep lapse rate cluster<br> 2: High moisture cluster</td> </tr> <tr> <td>Umean06</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>Umean01</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>U10</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>WindGust10</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>S06</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>EBWD</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>Umeanwindinf</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>SRHE</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>SRH06</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>DMI</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>LR_subcloud</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>LR_freezing</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>LR03</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>LR13</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>WMSI</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>BDSD</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>ConvGust_wet</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>ConvGust_dry</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>GUSTEX</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>DmgWind</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>DmgWind_fixed</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>DCAPE</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>WMPI</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>WINDEX</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>DowndraftTemp</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>ThetaeDiff</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>TEI</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>WNDG</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>DCP</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>SCP</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>SCP_fixed</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>SHERB</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>SHERBE</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>SWEAT</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>MUCS6</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>MLCS6</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>EffCS6</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>T_Totals</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>K_Index</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>Eff_CAPE</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>Eff_LCL</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>MLCAPE</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>ML_LCL</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>MUCAPE</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>MU_LCL</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>Qmean01</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> <tr> <td>Qmean06</td> <td>Convective diagnostic derived from ERA5 data. See Table1.pdf</td> </tr> </tbody> </table> <p><strong>References</strong></p> <p>Brown, A., Dowdy, A., Lane, T. P., & Hitchcock, S. (2023b). Types of Severe Convective Wind Events in Eastern Australia. <em>Monthly Weather Review</em>, <em>151</em>(2), 419–448. https://doi.org/10.1175/MWR-D-22-0096.1</p> <p>Brown, A., A. Dowdy, T. P. Lane, & Hitchcock, S. (2023a). Long-term observational characteristics of different severe convective wind types around Australia. <em>Wea. Forecasting</em>, <a href="https://doi.org/10.1175/WAF-D-23-0069.1">https://doi.org/10.1175/WAF-D-23-0069.1</a>, in press.</p> <p>Hersbach, H., Bell, B., Berrisford, P., Hirahara, S., Horányi, A., Muñoz‐Sabater, J., et al. (2020). The ERA5 Global Reanalysis. <em>Quarterly Journal of the Royal Meteorological Society</em>, qj.3803. https://doi.org/10.1002/qj.3803</p>
Radar rainfall event characteristics
<p>Datasets of radar-derived rainfall events and their characteristics between 01/01/2010 and 31/12/2020 for the Brisbane (Mt Stapylton), Sydney (Terrey Hills), and Melbourne (Laverton) radars. Rainfall events were identified only using data within a 100km radius of the radar, with gaps of one timestep interpolated over using the arithmetic mean of value on either side of the gap, and using an areal mean rain rate threshold of 0.1 mm/h. Created using Level 2 rain rate and Steiner classification data from the Australian Unified Radar Archive (AURA), which is available on NCI. Datasets are in csv format.</p>
TAASRAD19 Radar Sequences 2010-2019 HDF5
<p>TAASRAD19 (Trentino-Alto Adige/Südtirol Radar 2019) is a high-resolution radar reflectivity dataset collected by the Civil Protection weather radar of the Trentino South Tyrol Region, in the Italian Alps.<br> The dataset includes 894,916 scans of precipitation from more than 9 years of data, offering a novel resource to develop and benchmark analog ensemble models and machine learning solutions for precipitation nowcasting. Data are expressed as 2D images, considering the maximum reflectivity on the vertical section and 5 minutes sampling rate, covering an area of 240km of diameter at 500m horizontal resolution. The TAASRAD19 distribution also includes a curated set of 1,732 sequences, for a total of 362,233 radar images, labeled with precipitation type tags assigned by expert meteorologists. We validated TAASRAD19 as a benchmark for nowcasting using deep learning model to forecast reflectivity and a procedure based on the UMAP dimensionality reduction method for interactive exploration.<br> Software methods for data pre-processing, model training and inference, and a pre-trained model are<br> publicly available at https://github.com/MPBA/TAASRAD19 for replication and reproducibility.</p>
Airborne Radar Quality Control with Machine Learning
<p>This repository contains the radar data collected by ELDORA required to train and test the random forest model discussed in "Airborne radar quality control with machine learning" by Alexander DesRosiers and Michael M. Bell at the Colorado State University Department of Atmospheric Science. The model used in the manuscript is also contained in a '.pkl' file. Upon publication, a link to the paper will be provided here. Finer points of the methodology were discussed in the manuscript and the python script (make_radarQC_rf_model.py) is commented to guide users through the process of creating the model.</p>
Dataset for: A revised and expanded deep radiostratigraphy of the Greenland Ice Sheet from airborne radar sounding surveys between 1993–2019
<p>Version 5 changes the variable names in the NetCDF file so that are more readable by xarray.</p> <p>The NetCDF v4 file (Greenland_radiostratigraphy_v2.nc) contains both the gridded depths of synthetic isochrones (i.e., at ages of interest that were not necessarily directly observed) and the age at regular normalized depths (10–80%) in the ice sheet.</p> <p>For each campaign that was traced, there is an HDF5-compliant .mat MATLAB file (Greenland_radiostratigraphy_v2_X_Y, where X is the year the campaign was flown and Y is the aircraft that was used) that contains the original traced and dated reflections for each traced segment in that campaign. If using Python instead of MATLAB, the mat73 package and its loadmat function can be used to load these files. An example Jupyter notebook is included that illustrates how to access the full contents of .mat file using Python and this package. There is also a zipped (.zip) archive for each campaign that contains GeoPackage (.gpkg) files for each traced segment of that campaign. Because of format restrictions, these GeoPackages only include the traced reflections' depths, with the ages in the metadata. </p> <p> </p>
Aircraft Marshaling Signals Dataset of FMCW Radar and Event-Based Camera for Sensor Fusion
<p><strong>Dataset Introduction</strong></p><p>The advent of neural networks capable of learning salient features from variance in the radar data has expanded the breadth of radar applications, often as an alternative sensor or a complementary modality to camera vision. Gesture recognition for command control is arguably the most commonly explored application. Nevertheless, more suitable benchmarking datasets than currently available are needed to assess and compare the merits of the different proposed solutions and explore a broader range of scenarios than simple hand-gesturing a few centimeters away from a radar transmitter/receiver. Most current publicly available radar datasets used in gesture recognition provide limited diversity, do not provide access to raw ADC data, and are not significantly challenging. To address these shortcomings, we created and make available a new dataset that combines FMCW radar and dynamic vision camera of 10 aircraft marshalling signals (whole body) at several distances and angles from the sensors, recorded from 13 people. The two modalities are hardware synchronized using the radar's PRI signal. Moreover, in the supporting publication we propose a sparse encoding of the time domain (ADC) signals that achieve a dramatic data rate reduction (>76%) while retaining the efficacy of the downstream FFT processing (<2% accuracy loss on recognition tasks), and can be used to create an sparse event-based representation of the radar data. In this way the dataset can be used as a two-modality neuromorphic dataset.</p><p><strong>Synchronization of the two modalities</strong></p><p>The PRI pulses from the radar have been hard-wired to the event stream of the DVS sensor, and timestamped using the DVS clock. Based on this signal the DVS event stream has been segmented such that groups of events (time-bins) of the DVS are mapped with individual radar pulses (chirps).</p><p><strong>Data storage</strong></p><p>DVS events (x,y coords and timestamps) are stored in structured arrays, and one such structured array object is associated with the data of a radar transmission (pulse/chirp). A radar transmission is a vector of 512 ADC levels that correspond to sampling points of chirping signal (FMCW radar) that lasts about ~1.3ms. Every 192 radar transmissions are stacked in a matrix called a radar frame (each transmission is a row in that matrix). A data capture (recording) consisting of some thousands of continuous radar transmissions is therefore segmented in a number of radar frames. Finally radar frames and the corresponding DVS structured arrays are stored in separate containers in a custom-made multi-container file format (extension .rad). We provide a (rad file) parser for extracting the data out of these files. There is one file per capture of continuous gesture recording of about 10s.</p><p>Note the number of 192 transmissions per radar frame is an ad-hoc segmentation that suits the purpose of obtaining sufficient signal resolution in a 2D FFT typical in radar signal processing, for the range resolution of the specific radar. It also served the purpose of fast streaming storing of the data during capture. For extracting individual data points for the dataset however, one can pool together (concat) all the radar frames from a single capture file and re-segment them according to liking. The data loader that we provide offers this, with a default of re-segmenting every 769 transmissions (about 1s of gesturing).</p><p><strong>Data captures directory organization (</strong><a href="https://zenodo.org/api/records/10359770/draft/files/radar8Ghz-DVS-marshaling_signals_20220901_publication_anonymized.7z/content">radar8Ghz-DVS-marshaling_signals_20220901_publication_anonymized.7z</a><strong>)</strong></p><p>The dataset captures (recordings) are organized in a common directory structure which encompasses additional metadata information about the captures.</p><p>dataset_dir/<stage>/<room>/<person>-<gesture>-<distance>/ofxRadar8Ghz_yyyy-mm-dd_HH-MM-SS.rad</p><p>Identifiers</p><ul><li>stage [train, test].</li><li>room: [conference_room, foyer, open_space].</li><li>subject: [0-9]. Note that 0 stands for no person, and 1 for an unlabeled, random person (only present in test).</li><li>gesture: ['none', 'emergency_stop', 'move_ahead', 'move_back_v1', 'move_back_v2', 'slow_down' 'start_engines', 'stop_engines', 'straight_ahead', 'turn_left', 'turn_right'].</li><li>distance: ['xxx', '100', '150', '200', '250', '300', '350', '400', '450'] (in cm). Note that xxx is used for none gestures when there is no person present in front of the radar (i.e. background samples), or when a person is walking in front of the radar with varying distances but performing no gesture.</li></ul><p>The test data captures contain both subjects that appear in the train data as well as previously <i>unseen</i> subjects. Similarly the test data contain captures from the spaces that train data were recorded at, as well as from a new <i>unseen</i> open space.</p><p><strong>Files List</strong></p><p><a href="https://zenodo.org/api/records/10359770/draft/files/radar8Ghz-DVS-marshaling_signals_20220901_publication_anonymized.7z/content">radar8Ghz-DVS-marshaling_signals_20220901_publication_anonymized.7z</a></p><p>This is the actual archive bundle with the data captures (recordings).</p><p><a href="https://zenodo.org/api/records/10359770/draft/files/rad_file_parser_2.py/content">rad_file_parser_2.py</a></p><p>Parser for individual .rad files, which contain capture data.</p><p><a href="https://zenodo.org/api/records/10359770/draft/files/loader.py/content">loader.py</a></p><p>A convenience PyTorch Dataset loader (partly Tonic compatible). You practically only need this to quick-start if you don't want to delve too much into code reading. When you init a DvsRadarAircraftMarshallingSignals class object it automatically downloads the dataset archive and the .rad file parser, unpacks the archive, and imports the .rad parser to load the data. One can then <i>request from it </i>a training set, a validation set and a test set as torch.Datasets to work with<i>.</i> </p><p><a href="https://zenodo.org/api/records/10359770/draft/files/aircraft_marshalling_signals_howto.ipynb/content">aircraft_marshalling_signals_howto.ipynb</a></p><p>Jupyter notebook for exemplary basic use of loader.py</p><p><strong>Contact</strong></p><p>For further information or questions try contacting first M. Sifalakis or F. Corradi.</p><p> </p>
A new repository of electrical resistivity tomography and ground penetrating radar data from summer 2022 near Ny-Ålesund, Svalbard.
<p>We present the geophysical data set acquired in summer 2022 close to Ny-Ålesund (Western Svalbard, Brøggerhalvøya peninsula, Norway) as part of the project ICEtoFLUX (MUR/PRA2021 project-0027). The data set is composed of Electrical Resistivity Tomography (ERT) and GroundPenetrating Radar (GPR) surveys, which are well-known geophysical techniques for the characterization of glacial and hydrological processes and features. 18 ERT profiles and 10 GPR lines were acquired, for a total surveyed length of 9.3 km. The data have been organized in a consistent repository that includes both raw and processed (filtered) data. Some representative examples of 2D models of the subsurface are provided, that is, 2D sections of electrical resistivity (from ERT) and 2D radargrams (from GPR). These examples can support the identification of the active layer and the occurrence of spatial variation of soil conditions at depth. The aim of the investigation is to characterize the role of groundwater flow in correspondence of the active layer as well as through and/or below the permafrost. The data set is of major relevance because scant attention has been paid to the publication of geophysical data from the Ny-Ålesund area so far. Moreover, these geophysical data can foster multidisciplinary scientific collaborations in the fields of hydrology, glaciology, climate, geology, geomorphology, etc. To a large extent, the data set can provide new insight into the hydrological dynamics and polar and climate changes studies on the Ny-Ålesund area. </p>
STREAM - Sub-THz Radar sensing of the Environment for future Autonomous Marine platforms: Multi-Perspective Sensing - Automotive Environment
<p>This dataset contains the files corresponding to which results have been included in the journal paper. The full description of the conducted trials and data structure is mentioned in the attached PDF document.</p> <p>The trials were conducted at the University of Birmingham using distributed radar sensors installed on the mobile laboratory. The data will be used to develop algorithms to extract the information needed for high-resolution multi-modal and multi-perspective sensing.</p> <p>The experiments were performed with automotive radars operating in the 79 GHz band to investigate the Doppler and imaging capabilities of these radars.</p> <p>This report describes the measurement scenarios and data structure of INRAS Radarlog (76 GHz – 81 GHz) used for the data collection campaign.</p> <p>Contact: a.a.a.pirkani@bham.ac.uk, anum.apirkani@gmail.com, or m.s.gashinova@bham.ac.uk</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.