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.
14
datasets available to search
ShareScore release 0.9.0
Dataset results
14 results for “World Cup”
Real-world grasp data of a dual-arm Yumi robot with a parallel gripper and suction cup end-effectors
<p>The attached txt file contains indexes to a cleaner subset of the data issued in the first version.</p> <p>Note: <br>Version 1 contains samples with failure cases due to environment constraints, which work well for the platform used in GraspAgent 1.0 (https://doi.org/10.1109/LRA.2024.3502066). However, this can degrade the performance if used on another platform with different constraints. To solve this, version 2 reports a subset of the raw data, excluding the failure modes due to environmental causes. </p>
FIFA World Cups 2010, 2014 and 2018 matches' information datasets
<p>Data from FIFA World Cups 2010 (South Africa), 2014 (Brazil) and 2018 (Russia) collected from the FIFA website from the section of each match's facts. The original data were pdf files, which were cleaned and organized.</p> <p>The data was collected for the analysis of competition networks in soccer matches, where the high and low performance teams were studied.</p> <p>The zip file contains 3 folders of each world cup. Each folder contains the following files:</p> <p>- Players performance measures: input_worldcup.csv. This file contains information from 'fulltime statistics' and 'teams statistics' original files, complete for each match played in the world cup. More detailed player statistics is only complete for the teams that were champion, runner-up, and the teams that accumulated the less points and goals-against in their respective world cup.</p> <p>- The description of each column can be found in data_dictionary_worldcup.csv.</p> <p>- The list of countries that participated in the world cup with its abbreviation is found in countries_abbreviations_worldcup.csv.</p> <p>- The result of each match is found in tags_worldcup.csv</p> <p>- The players position information is the tactical line-up for World Cup 2010 and initial actual formation for World Cups 2014 and 2018. This information was manually set as a best approximation of position for the starting 11 players and a receiving shots nodes 'XS' - special for the visualization developed. The x-axis is between 0.5 and 6 and y-axis is flipped and between 0 and 6.</p> <p>- Folder of ball passing distributions for each match and team. The name of each file contains the match number and the team's ball passing distribution. The column names are the players numbers who received the ball. Rows represent 'from' and the columns 'to'. Each value are the number of passes between players.</p>
1998 World Cup Website Access Logs
<p><strong>Description:</strong></p> <p>The access logs, as well as the accompanying description, are directly taken from [1] and include traffic of the 1998 World Cup website on three days as follows. The log files have the following naming format "wc_dayX_Y.gz"</p> <p>where:</p> <ul> <li>X is an integer that represents the day the access log was collected</li> <li>Y is an integer that represents the subinterval for a particular day</li> </ul> <p>This collection includes <em>three</em> log files containing the access traffic on three different days as listed below:</p> <pre><a>wc_day25_1.gz</a> May 20, 1998 -> TR1 <a>wc_day9_1.gz</a> May 4, 1998 -> TR2 <a>wc_day28_1.gz</a> May 23, 1998 -> TR3</pre> <p><strong>Format</strong></p> <p>The access logs from the 1998 World Cup Web site were originally in the Common Log Format. In order to reduce both the size of the logs and the analysis time the access logs were converted to a binary format (big endian = network order). Each entry in the binary log is a fixed size and represents a single request to the site. The format of a request in the binary log looks like:</p> <pre>struct request { uint32_t timestamp; uint32_t clientID; uint32_t objectID; uint32_t size; uint8_t method; uint8_t status; uint8_t type; uint8_t server; };</pre> <p>The fields of the request structure contain the following information:</p> <p><em>timestamp </em>- the time of the request, stored as the number of seconds since the Epoch. The timestamp has been converted to GMT to allow for portability. During the World Cup the local time was 2 hours ahead of GMT (+0200). In order to determine the local time, each timestamp must be adjusted by this amount.</p> <p><em>clientID </em>- a unique integer identifier for the client that issued the request (this may be a proxy); due to privacy concerns these mappings cannot be released; note that each clientID maps to exactly one IP address, and the mappings are preserved across the entire data set - that is if IP address 0.0.0.0 mapped to clientID X on day Y then any request in any of the data sets containing clientID X also came from IP address 0.0.0.0</p> <p><em>objectID</em> - a unique integer identifier for the requested URL; these mappings are also 1-to-1 and are preserved across the entire data set</p> <p><em>size</em> - the number of bytes in the response</p> <p><em>method</em> - the method contained in the client's request (e.g., GET).</p> <p><em>status</em> - this field contains two pieces of information; the 2 highest order bits contain the HTTP version indicated in the client's request (e.g., HTTP/1.0); the remaining 6 bits indicate the response status code (e.g., 200 OK).</p> <p><em>type</em> - the type of file requested (e.g., HTML, IMAGE, etc), generally based on the file extension (.html), or the presence of a parameter list (e.g., '?' indicates a DYNAMIC request). If the url ends with '/', it is considered a DIRECTORY.</p> <p><em>server</em> - indicates which server handled the request. The upper 3 bits indicate which region the server was at (e.g., SANTA CLARA, PLANO, HERNDON, PARIS); the remaining bits indicate which server at the site handled the request. All 8 bits can also be used to determine a unique server.</p> <p><strong>Reference</strong></p> <p>[1]<strong> </strong>M. Arlitt and T. Jin, "1998 World Cup Web Site Access Logs", August 1998. </p>
Monte Carlo simulation of the 2018 World Cup
<p>Generated using </p> <pre> </pre> <p><a href="https://doi.org/10.5281/zenodo.1284221">https://doi.org/10.5281/zenodo.1284221</a></p> <p> </p> <p> </p>
Potential Injury Incidents At the FIFA World Cup Qatar 2022
ClinicalTrials.gov study NCT05629182. IPD Sharing: UNDECIDED. Countries: 1. Publications: 0.
Injury and Illness Surveillance At the FIFA World Cup Qatar 2022TM
ClinicalTrials.gov study NCT05629156. IPD Sharing: NO. Countries: 1. Publications: 0.
Physical activities of players during the 2018 Soccer World Cup
<p>Physical activities of players during the 2018 Soccer World Cup</p>
Data from: Attractiveness is positively related to World Cup performance in male, but not female, biathletes
Open the record for dataset details and reuse information.
Impact of the Qatar 2022 FIFA World Cup on PED Use and Misuse Patterns
ClinicalTrials.gov study NCT05818215. IPD Sharing: YES. Countries: 1. Publications: 0.
Everglade Stem, World Cup and World Liner Post Market Clinical Follow-up
ClinicalTrials.gov study NCT06153940. IPD Sharing: NO. Countries: 1. Publications: 0.
Video Review of the Frequency and Assessment of Head Impacts During the FIFA World Cup 2022TM
ClinicalTrials.gov study NCT05629169. IPD Sharing: NO. Countries: 1. Publications: 0.
Injury and Illness Surveillance at FIFA U-17 & U-20 Women's World Cups.
ClinicalTrials.gov study NCT05488639. IPD Sharing: NO. Countries: 1. Publications: 0.
Spartan Stem, World Cup and World Liner Post Market Clinical Follow-up Study
ClinicalTrials.gov study NCT06172569. IPD Sharing: NO. Countries: 1. Publications: 0.
CSIO-World Cup Wertungsturnier
<u>Source</u>: Europeana <br><u>4DCity URL</u>: <a href="https://4dcity.org/imgupload/1652096303.5195.jpg">https://4dcity.org/imgupload/1652096303.5195.jpg</a> <br><u>Original Image URL</u>: <a href="https://api.europeana.eu/thumbnail/v2/url.json?uri=https%3A%2F%2Fwww.stadtmuseum.leipzig.de%2FDE-MUS-853418%2Fmedien%2FwmMedium%3DSM009535&type=IMAGE">https://api.europeana.eu/thumbnail/v2/url.json?uri=https%3A%2F%2Fwww.stadtmuseum.leipzig.de%2FDE-MUS-853418%2Fmedien%2FwmMedium%3DSM009535&type=IMAGE</a> <br><br><u>Image-Metadata:</u><br>Filename: 1652096303.5195.jpg<br>Image Dimensions: 224x350<br>Megapixels: 0.08 MP<br>Filesize: 38.83 KB<br>
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.