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.
1,721
datasets available to search
ShareScore release 0.9.0
Dataset results
1,721 results for “network data”
GIS data - Model přirozené komunikační sítě pro území ČR | GIS data - Model of Natural Path Network for the Czech Republic
<p>GeoTIFF layer (8 x 8 m) containing a model of natural routes through the landscape of the Czech Republic. For a detailed description of layers, see https://doi.org/10.5281/zenodo.3367296</p>
Stream network for the SAFE Project derived from SRTM data
<b>Description: </b><p>This zipfile contains linear geometries showing a channel network across the SAFE Project landscape. The network was calculated using the GRASS hydrology tool <code>r.stream.extract</code> from SRTM elevation data and the resulting flow accumulation predictions (see <a href="https://zenodo.org/record/3490488">https://zenodo.org/record/3490488</a> and <a href="https://zenodo.org/record/3490687">https://zenodo.org/record/3490687</a>).<br><br>Note that these networks are derived entirely from remotely sensed data, but do form a single interconnected network across the wider SAFE landscape. Other stream network data are available () but the provenance of these are not well known and they only cover part of the SAFE network.<br><br>Details of the geoprocessing can be found here: <a href="https://www.safeproject.net/dokuwiki/safe_gis/stream_networks">https://www.safeproject.net/dokuwiki/safe_gis/stream_networks</a>.</p><p><b>Project: </b>This dataset was collected as part of the following SAFE research project: <a href="https://www.safeproject.net/projects/project_view/1"><b>SAFE CORE DATA</b></a></p><p><b>XML metadata: </b>GEMINI compliant metadata for this dataset is available <a href="https://www.safeproject.net/datasets/xml_metadata?id=3492009">here</a></p><p><b>Files: </b>This dataset consists of 2 files: SAFE_SRTM_Stream_network_metadata.xlsx, SRTM_Channels_network.zip</p><p><b>SAFE_SRTM_Stream_network_metadata.xlsx</b></p><p>This file only contains metadata for the files below</p><p><b>SRTM_Channels_network.zip</b></p><p>Description: Shapefile containing 54413 calculated segments forming a channel network across the wider SAFE landscape.</p><p>This file contains 1 data tables:</p><ol><li><p></p><p><b>Feature properties</b> (described in worksheet Properties)</p><p>Description: Field descriptions for shapefile properties</p><p>Number of fields: 17</p><p>Number of data rows: Unavailable (table metadata description only).</p><p>Fields: </p><ul><li><b>cat</b>: Identity of segment (Field type: id)</li><li><b>type_cd</b>: Segment type (see also type) (Field type: numeric)</li><li><b>ID</b>: Identity of segment (Field type: id)</li><li><b>length</b>: Length of network segment (Field type: numeric)</li><li><b>n_ponts</b>: Number of points in segment (Field type: numeric)</li><li><b>sourceX</b>: X coordinate of source point of segment (Field type: numeric)</li><li><b>sourceY</b>: Y coordinate of source point of segment (Field type: numeric)</li><li><b>sinkX</b>: X coordinate of sink point of segment (Field type: numeric)</li><li><b>sinkY</b>: Y coordinate of sink point of segment (Field type: numeric)</li><li><b>type</b>: Segment type - is the segment a source or outflow segment (connected at one end only, type_cd = 0) or internal (connected at both ends, type_cd=1) (Field type: categorical)</li><li><b>snkChnn</b>: Identity of sink channel for this segment (Field type: id)</li><li><b>srcChnn</b>: Identities of source channels for this segment (Field type: id)</li><li><b>nSourcs</b>: Count of source channels (Field type: numeric)</li><li><b>sorcElv</b>: Elevation of start point of segment (Field type: numeric)</li><li><b>sinkElv</b>: Elevation of sink point of segment (Field type: numeric)</li><li><b>sorcFlw</b>: Incoming flow at segment source (Field type: numeric)</li><li><b>sinkFlw</b>: Outgoing flow at segment sink (Field type: numeric)</li></ul><p></p></li></ol><p><b>Date range: </b>2010-10-01 to 2019-10-01</p><p><b>Latitudinal extent: </b>4.0223 to 5.9761</p><p><b>Longitudinal extent: </b>116.0242 to 117.9758</p>
Alternative stream network data for the SAFE Project
<b>Description: </b><p>This zipfile contains three shapefiles of linear geometries showing channel networks across the SAFE landscape.<br></p><ul><br><li>RIVERS_UTM.shp: From Igor Lysenko's SAFE pack, this is a river network with two areas, covering Maliau and the area around the SAFE experimental region. The network density is much higher in Maliau than SAFE and the channel network around SAFE is not complete. This is projected in UTM50N WGS84.</li><br><li>LFEriver_SL.shp: This is provided (by Sarah Luke?) through Clare Wilkinson's GIS files and adds a critical missing stream for the Logged Forest Edge (LFE) catchment. This is projected in UTM50N WGS84.</li><br><li>all_rivers.shp: This is provided through Clare Wilkinson's GIS files and provides streams for a single region covering Danum and the SAFE experimental region but not sampled watersheds in Oil Palm plantations to the south of SAFE. The original file is missing projection information (no .prj file) but other files in the same dataset are projected in RSO Timbalai 1948 and using this projection fits with the context of other data. The version uploaded onto Zenodo has been reprojected into UTM50N WGS84.</li><br></ul><br><br>Although the files are not consistent, they do contain channels and channel data that are referenced in some studies. The provenance of these files are unknown, although the following suggests that they may be traced using GPS or from imagery:<br><ul><br><li>Incomplete coverage within the regions they cover.</li><br><li>Treatment of larger rivers, changing from a single line feature showing the stream centreline (?) to double lines showing the river banks.</li><br><li>Variation in network density: the western edge of all_rivers.shp shows a vertical band about 4 km wide of higher stream density than the rest of the region; RIVERS_UTM.shp shows marked differences in stream density between SAFE and Maliau.</li><br></ul><p></p><p><b>Project: </b>This dataset was collected as part of the following SAFE research project: <a href="https://www.safeproject.net/projects/project_view/1"><b>SAFE CORE DATA</b></a></p><p><b>XML metadata: </b>GEMINI compliant metadata for this dataset is available <a href="https://www.safeproject.net/datasets/xml_metadata?id=3492064">here</a></p><p><b>Files: </b>This dataset consists of 2 files: SAFE_Alternative_Stream_network_metadata.xlsx, Preexisting_SAFE_river_files.zip</p><p><b>SAFE_Alternative_Stream_network_metadata.xlsx</b></p><p>This file only contains metadata for the files below</p><p><b>Preexisting_SAFE_river_files.zip</b></p><p>Description: Contains three shapefiles of channel networks.</p><p>This file contains 3 data tables:</p><ol><li><p></p><p><b>Feature properties</b> (described in worksheet LFEriver_SL)</p><p>Description: Field descriptions for shapefile properties</p><p>Number of fields: 1</p><p>Number of data rows: Unavailable (table metadata description only).</p><p>Fields: </p><ul><li><b>Id</b>: Identity of river (Field type: id)</li></ul><p></p></li><li><p></p><p><b>Feature properties</b> (described in worksheet RIVERS_UTM)</p><p>Description: Field descriptions for shapefile properties</p><p>Number of fields: 1</p><p>Number of data rows: Unavailable (table metadata description only).</p><p>Fields: </p><ul><li><b>NAME</b>: Local name of segment (Field type: comments)</li></ul><p></p></li><li><p></p><p><b>Feature properties</b> (described in worksheet all_river_UTM50N_WGS84)</p><p>Description: Field descriptions for shapefile properties</p><p>Number of fields: 10</p><p>Number of data rows: Unavailable (table metadata description only).</p><p>Fields: </p><ul><li><b>FNODE_</b>: Unknown (Field type: numeric)</li><li><b>TNODE_</b>: Unknown (Field type: numeric)</li><li><b>LPOLY_</b>: Unknown (Field type: numeric)</li><li><b>RPOLY_</b>: Unknown (Field type: numeric)</li><li><b>LENGTH_MET</b>: Length of channel segment in metres (Field type: numeric)</li><li><b>RIV_YSC_</b>: Unknown (Field type: numeric)</li><li><b>RIV_YSC_ID</b>: Unknown (Field type: numeric)</li><li><b>CODE</b>: Unknown (Field type: numeric)</li><li><b>NAME</b>: Local name of segment (Field type: comments)</li><li><b>AREA</b>: Local area of segment (Field type: comments)</li></ul><p></p></li></ol><p><b>Date range: </b>2010-10-01 to 2019-10-01</p><p><b>Latitudinal extent: </b>4.0223 to 5.9761</p><p><b>Longitudinal extent: </b>116.0242 to 117.9758</p>
Data set of manuscript entitled "Spatiotemporal evolution of long- and short-term slow slip events in the Tokai region, central Japan, estimated from a very dense GNSS network during 2013–2016" submitted to the Journal of Geophysical Research: Solid Earth
<p>This data set was used for manuscript entitled “Spatiotemporal evolution of long- and short-term slow slip events in the Tokai region, central Japan, estimated from a very dense Global Navigation Satellite Systems (GNSS) network during 2013–2016” submitted to the Journal of Geophysical Research: Solid Earth. This data set includes 1 figure file, 1 station list and 26 numerical data files. Figure and numerical data are locations of GNSS stations and GNSS time series used in our submitted manuscript, respectively.</p> <p>Figure file maned “location_of_station.png” shows locations of GNSS stations used in our submitted manuscript. Blue dots denote a continuous GNSS network named GEONET was installed by the Geospatial Information Authority of Japan, and red triangles denote continuous GNSS stations constructed by the Japanese University Consortium for GPS Researchers (JUNCO) and operated by the Earthquake Research Institute at the University of Tokyo and allied universities.</p> <p>The coordinates of JUNCO station are collected in a file named “site_junco.bl”. Description of each column is as follows:</p> <p>1. Column 1: Longitude in degree.</p> <p>2. Column 2: Latitude in degree.</p> <p>3. Column 3: Station name.</p> <p>Numerical data is GNSS time series, corresponds to the corrected time series in our submitted manuscript, observed for the period between 1 January 2013 and 31 January 2016. A complete description of data set is found in our submitted manuscript. Description of each column is as follows:</p> <p> </p> <p>1. Column 1: Days since 31 December 2012.</p> <p>2. Column 2: East displacement in cm</p> <p>3. Column 3: North displacement in cm</p> <p>4. Column 4: Vertical displacement in cm</p> <p>5. Column 5: Standard deviation of east displacement in cm</p> <p>6. Column 6: Standard deviation of north displacement in cm</p> <p>7. Column 7: Standard deviation of vertical displacement in cm</p> <p> </p> <p>The numerical data in this data set includes only the 26 JUNCO stations data. Numerical data files are named by the regularity of the combination of the 4 characters station name and extension “.dat”.</p>
Data for the prediction of chatter vibrations in robotic milling of aluminium parts based on previous experiences using neural network
<p>This data has been used for the validation of the software developed by DFKI in collaboration with IDEKO for the prediction of stability in robotic milling of aluminium parts, in the framework of COROMA research project funded by the European Union. www.coroma-project.eu</p> <p>The source of information is stability lobes obtained from FRFs obtained mixing by receptance coupling experimental FRFs of the robot, spindle and toolholder with FRFs of the tool obtained analitycally using beams theory. Real machinings have not been done since they would be very time consuming. Once the stability lobes where available random sampling has been done in the lobes between certain boundaries of axial depth of cut and spindle speed to represent machining with different conditions.</p> <p>The information contained here includes:</p> <p>- Data sets for different conditions, with tools of different diameters and different number of cutting teeth. (in the naming of the folder D represents diameter, Z represents number of teeth).</p> <p>- Most of the data sets also include figures with the milling stability lobe charts for different radial depths of cut and different diameters and number of teeth. In these figures the random sampling representing machining tests has been marked with a black X.</p> <p>- There are also versions of the data sets with different number of samples (20 or 40) in order to test the prediction algorithm with a different number of information.</p> <p>- In the data sets an extended version has been created, representing the know-how of the operator that if a machining is unstable all the machinings with higher axial depth of cut will be unstable, and if a machining is stable all the machinings with lower axial depth of cut will be stable.</p> <p>- Companion documents in PDF format in order to provide more detailed information on the datasets and results.</p> <p>Keywords: Milling, machining, vibration, chatter, stability, prediction, neural network, robot, robotic, AI, artificial intelligence.</p> <p>www.ideko.es<br> www.dfki.de</p> <p>Asier Barrios<br> IDEKO research centre<br> Arriaga Kalea, 2<br> Elgoibar 20870, Spain<br> Phone: +34 943748000<br> abarrios@ideko.es</p> <p>October 2019</p>
Data for "Corruption Risk in Contracting Markets: A Network Science Perspective"
<p>EU public procurement data, scored for corruption risk. Includes deduped issuers and winners. Includes data dictionary. For more information contact: johanneswachs@gmail.com</p>
Data for: Redshift Prediction with Images for Cosmology using a Bayesian Convolutional Neural Network with Conformal Predictions
<p>These files contain the predictions from the CNN and BCNN model from the paper titled: "Redshift Prediction with Images for Cosmology using a Bayesian Convolutional Neural Network with Conformal Predictions" (Jones et al. 2024). These files will allow reproduction of the performance metrics described in the paper.</p> <p> </p> <p>full_prediction_set_CNN.csv - predictions for the redshift using the CNN model of the entire dataset<br>cnn_evaluation.csv - predictions from just the evaluation dataset that was not used in training</p> <p>Columns are:</p> <p>photoz - predicted photoz from the model<br>specz - spectroscopic redshift<br>objectid - object ID from HSC PDR2 data release (Aihara et al. 2019)</p> <p><br>full_prediction_set_BCNN.csv - predictions for the redshift using the BCNN model of the entire dataset<br>bcnn_evaluation.csv - predictions from just the evaluation dataset that was not used in training</p> <p>Columns are:</p> <p>photoz - predicted photoz from the model<br>specz - spectroscopic redshift<br>objectid - object ID from HSC PDR2 data release (Aihara et al. 2019)<br>photoz_uncertainty - uncertainty in the predicted photoz</p>
Part 2 of real-time testing data for: "Identifying data sources and physical strategies used by neural networks to predict TC rapid intensification"
<p>Each file in the dataset contains machine-learning-ready data for one unique tropical cyclone (TC) from the real-time testing dataset. "Machine-learning-ready" means that all data-processing methods described in the journal paper have already been applied. This includes cropping satellite images to make them TC-centered; rotating satellite images to align them with TC motion (TC motion is always towards the +x-direction, or in the direction of increasing column number); flipping satellite images in the southern hemisphere upside-down; and normalizing data via the two-step procedure.</p> <p>The file name gives you the unique identifier of the TC -- e.g., "learning_examples_2010AL01.nc.gz" contains data for storm 2010AL01, or the first North Atlantic storm of the 2010 season. Each file can be read with the method `example_io.read_file` in the ml4tc Python library (https://zenodo.org/doi/10.5281/zenodo.10268620). However, since `example_io.read_file` is a lightweight wrapper for `xarray.open_dataset`, you can equivalently just use `xarray.open_dataset`. Variables in the table are listed below (the same printout produced by `print(xarray_table)`):</p> <p>Dimensions: (<br> satellite_valid_time_unix_sec: 289,<br> satellite_grid_row: 380,<br> satellite_grid_column: 540,<br> satellite_predictor_name_gridded: 1,<br> satellite_predictor_name_ungridded: 16,<br> ships_valid_time_unix_sec: 19,<br> ships_storm_object_index: 19,<br> ships_forecast_hour: 23,<br> ships_intensity_threshold_m_s01: 21,<br> ships_lag_time_hours: 5,<br> ships_predictor_name_lagged: 17,<br> ships_predictor_name_forecast: 129)<br>Coordinates:<br> * satellite_grid_row (satellite_grid_row) int32 2kB ...<br> * satellite_grid_column (satellite_grid_column) int32 2kB ...<br> * satellite_valid_time_unix_sec (satellite_valid_time_unix_sec) int32 1kB ...<br> * ships_lag_time_hours (ships_lag_time_hours) float64 40B ...<br> * ships_intensity_threshold_m_s01 (ships_intensity_threshold_m_s01) float64 168B ...<br> * ships_forecast_hour (ships_forecast_hour) int32 92B ...<br> * satellite_predictor_name_gridded (satellite_predictor_name_gridded) object 8B ...<br> * satellite_predictor_name_ungridded (satellite_predictor_name_ungridded) object 128B ...<br> * ships_valid_time_unix_sec (ships_valid_time_unix_sec) int32 76B ...<br> * ships_predictor_name_lagged (ships_predictor_name_lagged) object 136B ...<br> * ships_predictor_name_forecast (ships_predictor_name_forecast) object 1kB ...<br>Dimensions without coordinates: ships_storm_object_index<br>Data variables:<br> satellite_number (satellite_valid_time_unix_sec) int32 1kB ...<br> satellite_band_number (satellite_valid_time_unix_sec) int32 1kB ...<br> satellite_band_wavelength_micrometres (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_longitude_deg_e (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_cyclone_id_string (satellite_valid_time_unix_sec) |S8 2kB ...<br> satellite_storm_type_string (satellite_valid_time_unix_sec) |S2 578B ...<br> satellite_storm_name (satellite_valid_time_unix_sec) |S10 3kB ...<br> satellite_storm_latitude_deg_n (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_longitude_deg_e (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_intensity_number (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_u_motion_m_s01 (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_v_motion_m_s01 (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_predictors_gridded (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column, satellite_predictor_name_gridded) float64 474MB ...<br> satellite_grid_latitude_deg_n (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column) float64 474MB ...<br> satellite_grid_longitude_deg_e (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column) float64 474MB ...<br> satellite_predictors_ungridded (satellite_valid_time_unix_sec, satellite_predictor_name_ungridded) float64 37kB ...<br> ships_storm_intensity_m_s01 (ships_valid_time_unix_sec) float64 152B ...<br> ships_storm_type_enum (ships_storm_object_index, ships_forecast_hour) int32 2kB ...<br> ships_forecast_latitude_deg_n (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_forecast_longitude_deg_e (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_v_wind_200mb_0to500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_vorticity_850mb_0to1000km_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_vortex_latitude_deg_n (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_vortex_longitude_deg_e (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_850mb_0to600km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_max_tangential_wind_850mb_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_1000mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_850mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_500mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_300mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_srh_1000to700mb_200to800km_j_kg01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_srh_1000to500mb_200to800km_j_kg01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_threshold_exceedance_num_6hour_periods (ships_storm_object_index, ships_intensity_threshold_m_s01) int32 2kB ...<br> ships_v_motion_observed_m_s01 (ships_storm_object_index) float64 152B ...<br> ships_v_motion_1000to100mb_flow_m_s01 (ships_storm_object_index) float64 152B ...<br> ships_v_motion_optimal_flow_m_s01 (ships_storm_object_index) float64 152B ...<br> ships_cyclone_id_string (ships_storm_object_index) object 152B ...<br> ships_storm_latitude_deg_n (ships_storm_object_index) float64 152B ...<br> ships_storm_longitude_deg_e (ships_storm_object_index) float64 152B ...<br> ships_predictors_lagged (ships_valid_time_unix_sec, ships_lag_time_hours, ships_predictor_name_lagged) float64 13kB ...<br> ships_predictors_forecast (ships_valid_time_unix_sec, ships_forecast_hour, ships_predictor_name_forecast) float64 451kB ...</p> <p>Variable names are meant to be as self-explanatory as possible. Potentially confusing ones are listed below.</p> <ul> <li>The dimension ships_storm_object_index is redundant with the dimension ships_valid_time_unix_sec and can be ignored.</li> <li>ships_forecast_hour ranges up to values that we do not actually use in the paper. Keep in mind that our max forecast hour used in machine learning is 24.</li> <li>The dimension ships_intensity_threshold_m_s01 (and any variable including this dimension) can be ignored.</li> <li>ships_lag_time_hours corresponds to lag times for the SHIPS satellite-based predictors. The only lag time we use in machine learning is "NaN", which is a stand-in for the best available of all lag times. See the discussion of the "priority list" in the paper for more details.</li> <li>Most of the data variables can be ignored, unless you're doing a deep dive into storm properties. The important variables are satellite_predictors_gridded (full satellite images), ships_predictors_lagged (satellite-based SHIPS predictors), and ships_predictors_forecast (environmental and storm-history-based SHIPS predictors). These variables are all discussed in the paper.</li> <li>Every variable name (including elements of the coordinate lists ships_predictor_name_lagged and ships_predictor_name_forecast) includes units at the end. For example, "m_s01" = metres per second; "deg_n" = degrees north; "deg_e" = degrees east; "j_kg01" = Joules per kilogram; ...; etc.</li> </ul>
Real-time testing data for: "Identifying data sources and physical strategies used by neural networks to predict TC rapid intensification"
<p>Each file in the dataset contains machine-learning-ready data for one unique tropical cyclone (TC) from the real-time testing dataset. "Machine-learning-ready" means that all data-processing methods described in the journal paper have already been applied. This includes cropping satellite images to make them TC-centered; rotating satellite images to align them with TC motion (TC motion is always towards the +x-direction, or in the direction of increasing column number); flipping satellite images in the southern hemisphere upside-down; and normalizing data via the two-step procedure.</p> <p>The file name gives you the unique identifier of the TC -- e.g., "learning_examples_2010AL01.nc.gz" contains data for storm 2010AL01, or the first North Atlantic storm of the 2010 season. Each file can be read with the method `example_io.read_file` in the ml4tc Python library (https://zenodo.org/doi/10.5281/zenodo.10268620). However, since `example_io.read_file` is a lightweight wrapper for `xarray.open_dataset`, you can equivalently just use `xarray.open_dataset`. Variables in the table are listed below (the same printout produced by `print(xarray_table)`):</p> <p>Dimensions: (<br> satellite_valid_time_unix_sec: 289,<br> satellite_grid_row: 380,<br> satellite_grid_column: 540,<br> satellite_predictor_name_gridded: 1,<br> satellite_predictor_name_ungridded: 16,<br> ships_valid_time_unix_sec: 19,<br> ships_storm_object_index: 19,<br> ships_forecast_hour: 23,<br> ships_intensity_threshold_m_s01: 21,<br> ships_lag_time_hours: 5,<br> ships_predictor_name_lagged: 17,<br> ships_predictor_name_forecast: 129)<br>Coordinates:<br> * satellite_grid_row (satellite_grid_row) int32 2kB ...<br> * satellite_grid_column (satellite_grid_column) int32 2kB ...<br> * satellite_valid_time_unix_sec (satellite_valid_time_unix_sec) int32 1kB ...<br> * ships_lag_time_hours (ships_lag_time_hours) float64 40B ...<br> * ships_intensity_threshold_m_s01 (ships_intensity_threshold_m_s01) float64 168B ...<br> * ships_forecast_hour (ships_forecast_hour) int32 92B ...<br> * satellite_predictor_name_gridded (satellite_predictor_name_gridded) object 8B ...<br> * satellite_predictor_name_ungridded (satellite_predictor_name_ungridded) object 128B ...<br> * ships_valid_time_unix_sec (ships_valid_time_unix_sec) int32 76B ...<br> * ships_predictor_name_lagged (ships_predictor_name_lagged) object 136B ...<br> * ships_predictor_name_forecast (ships_predictor_name_forecast) object 1kB ...<br>Dimensions without coordinates: ships_storm_object_index<br>Data variables:<br> satellite_number (satellite_valid_time_unix_sec) int32 1kB ...<br> satellite_band_number (satellite_valid_time_unix_sec) int32 1kB ...<br> satellite_band_wavelength_micrometres (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_longitude_deg_e (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_cyclone_id_string (satellite_valid_time_unix_sec) |S8 2kB ...<br> satellite_storm_type_string (satellite_valid_time_unix_sec) |S2 578B ...<br> satellite_storm_name (satellite_valid_time_unix_sec) |S10 3kB ...<br> satellite_storm_latitude_deg_n (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_longitude_deg_e (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_intensity_number (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_u_motion_m_s01 (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_v_motion_m_s01 (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_predictors_gridded (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column, satellite_predictor_name_gridded) float64 474MB ...<br> satellite_grid_latitude_deg_n (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column) float64 474MB ...<br> satellite_grid_longitude_deg_e (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column) float64 474MB ...<br> satellite_predictors_ungridded (satellite_valid_time_unix_sec, satellite_predictor_name_ungridded) float64 37kB ...<br> ships_storm_intensity_m_s01 (ships_valid_time_unix_sec) float64 152B ...<br> ships_storm_type_enum (ships_storm_object_index, ships_forecast_hour) int32 2kB ...<br> ships_forecast_latitude_deg_n (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_forecast_longitude_deg_e (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_v_wind_200mb_0to500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_vorticity_850mb_0to1000km_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_vortex_latitude_deg_n (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_vortex_longitude_deg_e (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_850mb_0to600km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_max_tangential_wind_850mb_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_1000mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_850mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_500mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_300mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_srh_1000to700mb_200to800km_j_kg01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_srh_1000to500mb_200to800km_j_kg01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_threshold_exceedance_num_6hour_periods (ships_storm_object_index, ships_intensity_threshold_m_s01) int32 2kB ...<br> ships_v_motion_observed_m_s01 (ships_storm_object_index) float64 152B ...<br> ships_v_motion_1000to100mb_flow_m_s01 (ships_storm_object_index) float64 152B ...<br> ships_v_motion_optimal_flow_m_s01 (ships_storm_object_index) float64 152B ...<br> ships_cyclone_id_string (ships_storm_object_index) object 152B ...<br> ships_storm_latitude_deg_n (ships_storm_object_index) float64 152B ...<br> ships_storm_longitude_deg_e (ships_storm_object_index) float64 152B ...<br> ships_predictors_lagged (ships_valid_time_unix_sec, ships_lag_time_hours, ships_predictor_name_lagged) float64 13kB ...<br> ships_predictors_forecast (ships_valid_time_unix_sec, ships_forecast_hour, ships_predictor_name_forecast) float64 451kB ...</p> <p>Variable names are meant to be as self-explanatory as possible. Potentially confusing ones are listed below.</p> <ul> <li>The dimension ships_storm_object_index is redundant with the dimension ships_valid_time_unix_sec and can be ignored.</li> <li>ships_forecast_hour ranges up to values that we do not actually use in the paper. Keep in mind that our max forecast hour used in machine learning is 24.</li> <li>The dimension ships_intensity_threshold_m_s01 (and any variable including this dimension) can be ignored.</li> <li>ships_lag_time_hours corresponds to lag times for the SHIPS satellite-based predictors. The only lag time we use in machine learning is "NaN", which is a stand-in for the best available of all lag times. See the discussion of the "priority list" in the paper for more details.</li> <li>Most of the data variables can be ignored, unless you're doing a deep dive into storm properties. The important variables are satellite_predictors_gridded (full satellite images), ships_predictors_lagged (satellite-based SHIPS predictors), and ships_predictors_forecast (environmental and storm-history-based SHIPS predictors). These variables are all discussed in the paper.</li> <li>Every variable name (including elements of the coordinate lists ships_predictor_name_lagged and ships_predictor_name_forecast) includes units at the end. For example, "m_s01" = metres per second; "deg_n" = degrees north; "deg_e" = degrees east; "j_kg01" = Joules per kilogram; ...; etc.</li> </ul>
Aerosol products presented in "ALICENET – an Italian network of automated lidar ceilometers for four-dimensional aerosol monitoring: infrastructure, data processing, and applications"
<p>ALICENET output products on aerosol optical and physical properties and vertical layering presented in “Bellini, A., Diémoz, H., Di Liberto, L., Gobbi, G. P., Bracci, A., Pasqualini, F., and Barnaba, F.: Alicenet – An Italian network of Automated Lidar-Ceilometers for 4D aerosol monitoring: infrastructure, data processing, and applications, AMT, https://doi.org/10.5194/egusphere-2024-730, 2024”.</p> <p>The aod*.txt files include the following information:</p> <p>- date: date in UTC<br>- AOD_ALICENET: AOD as retrieved by ALICENET at 1064 nm<br>- AOD_AERONET/SKYNET: AOD measured by a co-located photometer from AERONET/SKYNET (level 2) at 1020 nm<br>- AE: Angstrom Exponent from AERONET/SKYNET (level 2)</p> <p>The contiunous.aerosol.layer.rome.txt file includes the following information:</p> <p>- date: date in CET<br>- continuous_aerosol_layer: Continous Aerosol Layer heights as retrieved by ALICENET</p> <p>The mixed.aerosol.layer.rome.txt file includes the following information:</p> <p>- date: date in CET<br>- mixed_aerosol_layer: Mixed Aerosol Layer heights as retrieved by ALICENET</p> <p>This work received partial financial support from the EC H2020 Project RI-URBANS (GA No 101036245), and benefited from work done within the Action PROBE (CA18235), supported by COST (European Cooperation in Science and Technology).</p>
Supporting data ocean model GMD submission: From Weather Data to River Runoff: Leveraging Spatiotemporal Convolutional Networks for Comprehensive Discharge Forecasting
<p>Ocean model salinity data used for the comparison of the ConvLSTM river runoff model and the original E-HYPE based model simulations.</p>
Experimental online quantum dots charge autotuning using neural networks - Output data
<p>Outputs of the model training and the online autotuning experiments presented in the paper: "Experimental online quantum dots charge autotuning using neural networks".</p> <p>Each folder in the zipped files represent a run that includes:</p> <ul> <li>log file</li> <li>plots / images</li> <li>run settings</li> <li>performance results</li> <li>pytorch model parameters</li> </ul> <p>See README.txt for more information about the file strucutre.</p>
Network files and Python code used in "Designing a sector-coupled European energy system robust to 60 years of historical weather data"
<p><strong>Description</strong></p> <p>This repository contains data presented in the paper <a href="https://www.nature.com/articles/s41467-024-54853-3" target="_blank" rel="noopener">Designing a sector-coupled European energy system robust to 60 years of historical weather data</a>. It contains the derived metrics (.csv) files from a:</p> <ol> <li>joint capacity and dispatch optimization with weather years (design years) from 1960 to 2021 as input</li> <li>dispatch optimization of the 62 capacity layouts using weather years (operational years) different from the design year.</li> </ol> <p>All results from (1) are found in "Capacity_optimization.zip" and results from (2) are found in "Dispatch_optimization.zip".</p> <p>The resulting network files (both from the capacity and dispatch optimization) are located <a href="https://anon.erda.au.dk/cgi-sid/ls.py?share_id=DuGvDWlkeI">here</a>.</p> <p>We also provide the Python code used to derive the metrics and to create the visualizations included in the paper. This is located in "Jupyter_notebooks". The Jupyter notebooks refer to Python scripts located <a href="https://github.com/ebbekyhl/multi-weather-year-assessment">here</a>.</p> <p><strong>Revisions:</strong></p> <p>This version includes the following additions compared to the previous versions: </p> <ul> <li>Timeseries of nodal loads for all years</li> <li>Timeseries of nodal heat pump Coefficient of Performance (COP) </li> <li>Nodal capacity and hourly capacity factors </li> </ul>
Aggregation of recount3 RNA-seq data improves inference of consensus and tissue-specific gene co-expression networks
<p>Data and Inferred Networks accompanying the manuscript entitled - “Aggregation of recount3 RNA-seq data improves the inference of consensus and context-specific gene co-expression networks” </p> <p>Authors: Prashanthi Ravichandran, Princy Parsana, Rebecca Keener, Kaspar Hansen, Alexis Battle </p> <p>Affiliations: Johns Hopkins University School of Medicine, Johns Hopkins University Department of Computer Science, Johns Hopkins University Bloomberg School of Public Health</p> <p>Description: </p> <p>This folder includes data produced in the analysis contained in the manuscript and inferred consensus and context-specific networks from graphical lasso and WGCNA with varying numbers of edges. Contents include:</p> <ul> <li> <p>all_metadata.rds: File including meta-data columns of study accession ID, sample ID, assigned tissue category, cancer status and disease status obtained through manual curation for the 95,484 RNA-seq samples used in the study. </p> </li> <li> <p>all_counts.rds: log2 transformed RPKM normalized read counts for 5999 genes and 95,484 RNA-seq samples which was utilized for dimensionality reduction and data exploration </p> </li> <li> <p>precision_matrices.zip: Zipped folder including networks inferred by graphical lasso for different experiments presented in the paper using weighted covariance aggregation following PC correction.</p> </li> <ul> <li> <p>The networks can be found as follows. First, select the folder corresponding to the network of interest - for example, Blood, this will then include two or more folders which indicate the data aggregation utilized, select the folder corresponding appropriate level of data aggregation - either all samples/ GTEx for blood-specific networks, this includes precision matrices inferred across a range of penalization parameters. To view the precision matrix inferred for a particular value of the penalization parameter X, select the file labeled lambda_X.rds</p> </li> <li> <p>For select networks, we have included the computed centrality measures which can be accessed at centrality_X.rds for a particular value of the penalization parameter X. </p> </li> <li> <p>We have also included .rds files that list the hub genes from the consensus networks inferred from non-cancerous samples at “normal_hubs.rds”, and the consensus networks inferred from cancerous samples at “cancer_hubs.rds”</p> </li> <li> <p>The file “context_specific_selected_networks.csv” includes the networks that were selected for downstream biological interpretation based on the scale-free criterion which is also summarized in the Supplementary Tables. </p> </li> </ul> <li> <p>WGCNA.zip: A zipped folder containing gene modules inferred from WGCNA for sequentially aggregated GTEx, SRA, and blood studies. Select the data aggregated, and the number of studies based on folder names. For example, blood networks inferred from 20 studies can be accessed at blood/consensus/net_20. The individual networks correspond to distinct cut heights, and include information on the cut height used, the genes that the network was inferred over merged module labels, and merged module colors. </p> </li> </ul>
Support data for article "The concept of optimal planning of a linearly oriented segment of the 5G network"
<p>Support data for article</p> <p>V. Kovtun, K. Grochla, E. Zaitseva, and V. Levashenko, “The concept of optimal planning of a linearly oriented segment of the 5G network,” PLOS ONE, vol. 19, no. 4. Public Library of Science (PLoS), p. e0299000, Apr. 17, 2024. doi: 10.1371/journal.pone.0299000.</p> <p>This research is part of the project No. 2022/45/P/ST7/03450 co-funded by the National Science Centre and the European Union Framework Programme for Research and Innovation Horizon 2020 under the Marie Skłodowska-Curie grant agreement No. 945339.</p>
Support data for article "The concept of network resource control of a 5G cluster focused on the smart city's critical infrastructure needs"
<p>Support data for article:</p> <div>V. Kovtun, K. Grochla, and K. Połys, “The concept of network resource control of a 5G cluster focused on the smart city’s critical infrastructure needs,” Alexandria Engineering Journal, vol. 94. Elsevier BV, pp. 248–256, May 2024. doi: 10.1016/j.aej.2024.03.038.</div> <p>This research is part of the project No. 2022/45/P/ST7/03450 co-funded by the National Science Centre and the European Union Framework Programme for Research and Innovation Horizon 2020 under the Marie Skłodowska-Curie grant agreement No. 945339.</p>
Supplementary Data and Software for "Robust NLoS Localization in 5G mmWave Networks: Data-based Methods and Performance"
<p>The file includes supplementary data for "Robust NLoS Localization in 5G mmWave Networks: Data-based Methods and Performance". If you would like to re-use the software provided please cite the following two items.</p> <p>R. Klus, J. Talvitie, J. Equi, G. Fodor, J. Torsner, and M. Valkama, “Robust NLoS Localization in 5G mmWave Networks: Data-based Methods and<br>Performance,” IEEE Transactions on Vehicular Technology, 2024.</p> <p>R Klus et al. (2024). Supplementary materials for “Robust NLoS Localization in 5G mmWave Networks: Data-based Methods and Performance”. version v1, 25.06.2024, [Online]. Available: https://doi.org/10.5281/zenodo.12204892</p> <p>If you have any questions about this package, please do not hesitate to contact Roman Klus (roman.klus@tuni.fi).</p>
Data set from the 6G-SANDBOX platforms benchmarking and assessment for different documented trial networks - Oulu facility
<p>This data set covers core network and end-to-end measurements at the Oulu facility, part of the 6G-SANDBOX infrastructure.</p>
Data set from the 6G-SANDBOX platforms benchmarking and assessment for different documented trial networks - Malaga facility
<p>This data set covers core network and end-to-end measurements at the Malaga facility, part of the 6G-SANDBOX infrastructure.</p>
Data set from the 6G-SANDBOX platforms benchmarking and assessment for different documented trial networks - Berlin facility
<p>This data set covers core network and end-to-end measurements at the Berlin facility, part of the 6G-SANDBOX infrastructure.</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.