Skip to main content
Powered by ShareScore

Find research datasets worth reusing

Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.

5

datasets available to search

ShareScore release 0.9.0

Reset

Dataset results

5 results for “Probe requests”

Learn how ShareScore rates datasets ↗
zenodo48/100

Supplementary Materials for "Exploration of User Privacy in 802.11 Probe Requests with MAC Address Randomization Using Temporal Pattern Analysis"

<p>Supplementary Materials for &quot;Exploration of User Privacy in 802.11 Probe Requests with MAC Address Randomization Using Temporal Pattern Analysis&quot;</p> <p>This package contains an anonymized packets of 802.11 probe requests captured in in December 2021 at Universitat Jaume I . The packet capture file is in the standardized *.pcap binary format and can be opened with any packet analysis tool such as Wireshark or scapy (Python packet analysis and manipulation package).</p>

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

Labeled dataset of IEEE 802.11 probe requests

<p><strong>Introduction</strong> &nbsp;<br> &nbsp;<br> The 802.11 standard includes several management features and corresponding frame types. One of them are probe requests (PR). They are sent by mobile devices in the unassociated state to search the nearby area for existing wireless networks. The frame part of PRs consists of variable length fields called information elements (IE). IE fields represent the capabilities of a mobile device, such as data rates. &nbsp;<br> The dataset includes PRs collected in a controlled rural environment and in a semi-controlled indoor environment under different measurement scenarios. &nbsp;<br> It can be used for various use cases, e.g., analysing MAC randomization, determining the number of people in a given location at a given time or in different time periods, analysing trends in population movement (streets, shopping malls, etc.) in different time periods, etc.</p> <p>&nbsp;<br> <strong>Measurement setup</strong> &nbsp;<br> &nbsp;<br> The system for collecting PRs consists of a Raspberry Pi 4 (RPi) with an additional WiFi dongle to capture Wi-Fi signal traffic in monitoring mode. Passive PR monitoring is performed by listening to 802.11 traffic and filtering out PR packets on a single WiFi channel.<br> The following information about each PR received is collected: MAC address, Supported data rates, extended supported rates, HT capabilities, extended capabilities, data under extended tag and vendor specific tag, interworking, VHT capabilities, RSSI, SSID and timestamp when PR was received.<br> The collected data was forwarded to a remote database via a secure VPN connection. A Python script was written using the Pyshark package for data collection, preprocessing and transmission.</p> <p><br> <strong>Data preprocessing</strong></p> <p>The gateway collects PRs for each consecutive predefined scan interval (10 seconds). During this time interval, the data are preprocessed before being transmitted to the database.<br> For each detected PR in the scan interval, IEs fields are saved in the following JSON structure:<br> PR_IE_data =<br> {<br> &nbsp;&nbsp;&nbsp; &#39;DATA_RTS&#39;: {&#39;SUPP&#39;: DATA_supp , &#39;EXT&#39;: DATA_ext},<br> &nbsp;&nbsp;&nbsp; &#39;HT_CAP&#39;: DATA_htcap,<br> &nbsp;&nbsp;&nbsp; &#39;EXT_CAP&#39;: {&#39;length&#39;: DATA_len, &#39;data&#39;: DATA_extcap},<br> &nbsp;&nbsp;&nbsp; &#39;VHT_CAP&#39;: DATA_vhtcap,<br> &nbsp;&nbsp;&nbsp; &#39;INTERWORKING&#39;: DATA_inter,<br> &nbsp;&nbsp;&nbsp; &#39;EXT_TAG&#39;: {&#39;ID_1&#39;: DATA_1_ext, &#39;ID_2&#39;: DATA_2_ext ...},<br> &nbsp;&nbsp;&nbsp; &#39;VENDOR_SPEC&#39;: {VENDOR_1:{<br> &nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#39;ID_1&#39;: DATA_1_vendor1,<br> &nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#39;ID_2&#39;: DATA_2_vendor1<br> &nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ...},<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; VENDOR_2:{<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#39;ID_1&#39;: DATA_1_vendor2,<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#39;ID_2&#39;: DATA_2_vendor2<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ...}<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ...}<br> }</p> <p>&nbsp;<br> Supported data rates and extended supported rates are represented as arrays of values that encode information about the rates supported by a mobile device. The rest of the IEs data is represented in hexadecimal format. Vendor Specific Tag is structured differently than the other IEs. This field can contain multiple vendor IDs with multiple data IDs with corresponding data. Similarly, the extended tag can contain multiple data IDs with corresponding data. &nbsp;<br> Missing IE fields in the captured PR are not included in <em>PR_IE_DATA</em>.</p> <p>When a new MAC address is detected in the current scan time interval, the data from PR is stored in the following structure:</p> <p>{&#39;MAC&#39;: MAC_address, &#39;SSIDs&#39;: [ SSID ], &#39;PROBE_REQs&#39;: [PR_data] },</p> <p>where <em>PR_data</em> is structured as follows:<br> {<br> &nbsp;&nbsp;&nbsp; &#39;TIME&#39;: [ DATA_time ],<br> &nbsp;&nbsp;&nbsp; &#39;RSSI&#39;: [ DATA_rssi ],<br> &nbsp;&nbsp;&nbsp; &#39;DATA&#39;: PR_IE_data<br> }.</p> <p>This data structure allows storing only <em>TOA</em> and <em>RSSI</em> for all PRs originating from the same MAC address and containing the same <em>PR_IE_data</em>. All SSIDs from the same MAC address are also stored. &nbsp;<br> The data of the newly detected PR is compared with the already stored data of the same MAC in the current scan time interval. &nbsp;<br> If identical PR&#39;s IE data from the same MAC address is already stored, then only data for the keys <em>TIME</em> and <em>RSSI</em> are appended.<br> If no identical PR&#39;s IE data has yet been received from the same MAC address, then PR_data structure of the new PR for that MAC address is appended to <em>PROBE_REQs</em> key. &nbsp;<br> The preprocessing procedure is shown in Figure ./Figures/Preprocessing_procedure.png &nbsp;<br> At the end of each scan time interval, all processed data is sent to the database along with additional metadata about the collected data e.g. wireless gateway serial number and scan start and end timestamps. For an example of a single PR captured, see the ./Single_PR_capture_example.json file.</p> <p><br> <strong>Environments description</strong> &nbsp;<br> &nbsp;<br> We performed measurements in a controlled rural outdoor environment and in a semi-controlled indoor environment of the Jozef Stefan Institute.<br> See the Excel spreadsheet Measurement_informations.xlsx for a list of mobile devices tested. &nbsp;<br> &nbsp;<br> &nbsp;&nbsp; <strong>Indoor environment &nbsp;</strong><br> &nbsp;<br> We used 3 RPi&#39;s for the acquisition of PRs in the Jozef Stefan Institute. They were placed indoors in the hallways as shown in the ./Figures/RPi_locations_JSI.png. Measurements were performed on weekend to minimize additional uncontrolled traffic from users&#39; mobile devices. While there is some overlap in WiFi coverage between the devices at the location 2 and 3, the device at location 1 has no overlap with the other two devices.</p> <p>&nbsp;&nbsp; <strong>Rural environment outdoors</strong> &nbsp;<br> &nbsp;<br> The three RPi&#39;s used to collect PRs were placed at three different locations with non-overlapping WiFi coverage, as shown in ./Figures/RPi_locations_rural_env.png. Before starting the measurement campaign, all measured devices were turned off and the environment was checked for active WiFi devices. We did not detect any unknown active devices sending WiFi packets in the RPi&#39;s coverage area, so the deployment can be considered fully controlled.<br> All known WiFi enabled devices that were used to collect and send data to the database used a global MAC address, so they can be easily excluded in the preprocessing phase. MAC addresses of these devices can be found in the ./Measurement_informations.xlsx spreadsheet.<br> Note: The Huawei P20 device with ID 4.3 was not included in the test in this environment.</p> <p><br> <strong>Scenarios description</strong> &nbsp;<br> &nbsp;<br> We performed three different scenarios of measurements. &nbsp;<br> &nbsp;<br> &nbsp;&nbsp; <strong>Individual device measurements</strong><br> &nbsp;<br> For each device, we collected PRs for one minute with the screen on, followed by PRs collected for one minute with the screen off. In the indoor environment the WiFi interfaces of the other devices not being tested were disabled. In rural environment other devices were turned off. Start and end timestamps of the recorded data for each device can be found in the ./Measurement_informations.xlsx spreadsheet under the <em>Indoor environment of Jozef Stefan Institute</em> sheet and the <em>Rural environment</em> sheet.</p> <p>&nbsp;&nbsp; <strong>Three groups test</strong></p> <p>In this measurement scenario, the devices were divided into three groups. The first group contained devices from different manufacturers. The second group contained devices from only one manufacturer (Samsung). Half of the third group consisted of devices from the same manufacturer (Huawei), and the other half of devices from different manufacturers. The distribution of devices among the groups can be found in the ./Measurement_informations.xlsx spreadsheet. &nbsp;<br> &nbsp;<br> The same data collection procedure was used for all three groups. Data for each group were collected in both environments at three different RPis locations, as shown in ./Figures/RPi_locations_JSI.png and ./Figures/RPi_locations_rural_env.png. &nbsp;<br> At each location, PRs were collected from each group for 10 minutes with the screen on. Then all three groups switched locations and the process was repeated. Thus, the dataset contains measurements from all three RPi locations of all three groups of devices in both measurement environments. The group movements and the timestamps for the start and end of the collection of PRs at each loacation can be found in spreadsheet ./Measurement_informations.xlsx.</p> <p>&nbsp;&nbsp; <strong>One group test</strong> &nbsp;<br> &nbsp;<br> In the last measurement scenario, all devices were grouped together. In rural evironement we first collected PRs for 10 minutes while the screen was on, and then for another 10 minutes while the screen was off. In indoor environment data were collected at first location with screens on for 10 minutes. Then all devices were moved to the location of the next RPi and PRs were collected for 5 minutes with the screen on and then for another 5 minutes with the screen off.</p> <p><strong>Folder structure</strong> &nbsp;<br> &nbsp;<br> The root directory contains two files in JSON format for each of the environments where the measurements took place (Data_indoor_environment.json and Data_rural_environment.json). Both files contain collected PRs for the entire day that the measurements were taken (12:00 AM to 12:00 PM) to get a sense of the behaviour of the unknown devices in each environment. The spreadsheet ./Measurement_informations.xlsx. contains three sheets. <em>Devices description</em> contains general information about the tested devices, RPis, and the assigned group for each device. The sheets <em>Indoor environment of Jozef Stefan Institute</em> and <em>Rural environment</em> contain the corresponding timestamps for the start and end of each measurement scenario. For the scenario where the devices were divided into groups, additional information about the movements between locations is included. The location names are based on the RPi gateway ID and may differ from those on the figures showing the locations of the RPIs for each environment.<br> The ./Figures folder contains the figures already mentioned above.</p>

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

Dataset of IEEE 802.11 probe requests from an uncontrolled urban environment

<p><strong>Introduction</strong></p> <p>The 802.11 standard includes several management features and corresponding frame types. One of them are Probe Requests (PR), which are sent by mobile devices in an unassociated state to scan the nearby area for existing wireless networks. The frame part of PRs consists of variable-length fields, called Information Elements (IE), which represent the capabilities of a mobile device, such as supported data rates.</p> <p>This dataset contains PRs collected over a seven-day period by four gateway devices in an uncontrolled urban environment in the city of Catania.</p> <p>It can be used for various use cases, e.g., analyzing MAC randomization, determining the number of people in a given location at a given time or in different time periods, analyzing trends in population movement (streets, shopping malls, etc.) in different time periods, etc.</p> <p><strong>&nbsp; Related dataset</strong></p> <p>Same authors also produced the <a href="https://zenodo.org/record/7503594">Labeled dataset of IEEE 802.11 probe requests</a>&nbsp; with same data layout and recording equipment.</p> <p><br> <strong>Measurement setup</strong> &nbsp;</p> <p>The system for collecting PRs consists of a Raspberry Pi 4 (RPi) with an additional WiFi dongle to capture WiFi signal traffic in monitoring mode (gateway device).<br> Passive PR monitoring is performed by listening to 802.11 traffic and filtering out PR packets on a single WiFi channel.</p> <p>The following information about each received PR is collected:<br> &nbsp;- MAC address<br> &nbsp;- Supported data rates<br> &nbsp;- extended supported rates<br> &nbsp;- HT capabilities<br> &nbsp;- extended capabilities<br> &nbsp;- data under extended tag and vendor specific tag<br> &nbsp;- interworking<br> &nbsp;- VHT capabilities<br> &nbsp;- RSSI<br> &nbsp;- SSID<br> &nbsp;- timestamp when PR was received.</p> <p>The collected data was forwarded to a remote database via a secure VPN connection.<br> A Python script was written using the Pyshark package to collect, preprocess, and transmit the data.</p> <p><br> <strong>Data preprocessing</strong></p> <p><br> The gateway collects PRs for each successive predefined scan interval (10 seconds). During this interval, the data is preprocessed before being transmitted to the database.<br> For each detected PR in the scan interval, the IEs fields are saved in the following JSON structure:</p> <pre><code class="language-json">PR_IE_data = { 'DATA_RTS': {'SUPP': DATA_supp , 'EXT': DATA_ext}, 'HT_CAP': DATA_htcap, 'EXT_CAP': {'length': DATA_len, 'data': DATA_extcap}, 'VHT_CAP': DATA_vhtcap, 'INTERWORKING': DATA_inter, 'EXT_TAG': {'ID_1': DATA_1_ext, 'ID_2': DATA_2_ext ...}, 'VENDOR_SPEC': {VENDOR_1:{ 'ID_1': DATA_1_vendor1, 'ID_2': DATA_2_vendor1 ...}, VENDOR_2:{ 'ID_1': DATA_1_vendor2, 'ID_2': DATA_2_vendor2 ...} ...} }</code></pre> <p><br> Supported data rates and extended supported rates are represented as arrays of values that encode information about the rates supported by a mobile device. The rest of the IEs data is represented in hexadecimal format. Vendor Specific Tag is structured differently than the other IEs. This field can contain multiple vendor IDs with multiple data IDs with corresponding data. Similarly, the extended tag can contain multiple data IDs with corresponding data. &nbsp;<br> Missing IE fields in the captured PR are not included in <em>PR_IE_DATA</em>.</p> <p>When a new MAC address is detected in the current scan time interval, the data from PR is stored in the following structure:</p> <pre><code class="language-json">{'MAC': MAC_address, 'SSIDs': [ SSID ], 'PROBE_REQs': [PR_data] },</code></pre> <p>where <em>PR_data</em> is structured as follows:</p> <pre><code class="language-json">{ 'TIME': [ DATA_time ], 'RSSI': [ DATA_rssi ], 'DATA': PR_IE_data }.</code></pre> <p>&nbsp;</p> <p>This data structure allows to store only &#39;TOA&#39; and &#39;RSSI&#39; for all PRs originating from the same MAC address and containing the same &#39;PR_IE_data&#39;. All SSIDs from the same MAC address are also stored.<br> The data of the newly detected PR is compared with the already stored data of the same MAC in the current scan time interval.<br> If identical PR&#39;s IE data from the same MAC address is already stored, only data for the keys &#39;TIME&#39; and &#39;RSSI&#39; are appended.<br> If identical PR&#39;s IE data from the same MAC address has not yet been received, then the PR_data structure of the new PR for that MAC address is appended to the &#39;PROBE_REQs&#39; key.<br> The preprocessing procedure is shown in Figure ./Figures/Preprocessing_procedure.png</p> <p>At the end of each scan time interval, all processed data is sent to the database along with additional metadata about the collected data, such as the serial number of the wireless gateway and the timestamps for the start and end of the scan. For an example of a single PR capture, see the <em>Single_PR_capture_example.json</em> file.</p> <p><br> &nbsp; <strong>Folder structure</strong></p> <p>For ease of processing of the data, the dataset is divided into 7 folders, each containing a 24-hour period.<br> Each folder contains four files, each containing samples from that device.</p> <p>The folders are named after the start and end time (in UTC).<br> For example, the folder [2022-09-22T22-00-00_2022-09-23T22-00-00](2022-09-22T22-00-00_2022-09-23T22-00-00) contains samples collected between <em>23th of September 2022 00:00 local time</em>, until <em>24th of September 2022 00:00</em> local time.</p> <p>Files representing their location via mapping:<br> - 1.json -&gt; location 1<br> - 2.json -&gt; location 2<br> - 3.json -&gt; location 3<br> - 4.json -&gt; location 4</p> <p><strong>Environments description</strong> &nbsp;</p> <p>The measurements were carried out in the city of Catania, in Piazza Universit&agrave; and Piazza del Duomo<br> The gateway devices (rPIs with WiFi dongle) were set up and gathering data before the start time of this dataset.<br> As of September 23, 2022, the devices were placed in their final configuration and personally checked for correctness of installation and data status of the entire data collection system.<br> Devices were connected either to a nearby Ethernet outlet or via WiFi to the access point provided.</p> <p>Four Raspbery Pi-s were used:<br> - location 1 -&gt; Piazza del Duomo - Chierici building (balcony near Fontana dell&rsquo;Amenano)<br> - location 2 -&gt; southernmost window in the building of Via Etnea near Piazza del Duomo<br> - location 3 -&gt; nothernmost window in the building of Via Etnea near Piazza Universit&agrave;<br> - location 4 -&gt; first window top the right of the entrance of the University of Catania</p> <p>Locations were suggested by the authors and adjusted during deployment based on physical constraints (locations of electrical outlets or internet access)<br> Under ideal circumstances, the locations of the devices and their coverage area would cover both squares and the part of Via Etna between them, with a partial overlap of signal detection. The locations of the gateways are shown in Figure ./Figures/catania.png.</p> <p>&nbsp; <strong>Known dataset shortcomings</strong></p> <p>Due to technical and physical limitations, the dataset contains some identified deficiencies.</p> <p>PRs are collected and transmitted in 10-second chunks.<br> Due to the limited capabilites of the recording devices, some time (in the range of seconds) may not be accounted for between chunks if the transmission of the previous packet took too long or an unexpected error occurred.</p> <p>Every 20 minutes the service is restarted on the recording device.<br> This is a workaround for undefined behavior of the USB WiFi dongle, which can no longer respond.<br> For this reason, up to 20 seconds of data will not be recorded in each 20-minute period.</p> <p>The devices had a scheduled reboot at 4:00 each day which is shown as missing data of up to a few minutes.</p> <p>&nbsp;<strong>&nbsp;&nbsp;&nbsp; Location 1 - Piazza del Duomo - Chierici</strong></p> <p>&nbsp;The gateway device (rPi) is located on the second floor balcony and is hardwired to the Ethernet port. This device appears to function stably throughout the data collection period.<br> &nbsp;Its location is constant and is not disturbed, dataset seems to have complete coverage.</p> <p>&nbsp;&nbsp;&nbsp;&nbsp; <strong>Location 2 - Via Etnea - Piazza del Duomo</strong></p> <p>&nbsp;The device is located inside the building.<br> &nbsp;During working hours (approximately 9:00-17:00), the device was placed on the windowsill. However, the movement of the device cannot be confirmed.<br> &nbsp;As the device was moved back and forth, power outages and internet connection issues occurred.<br> &nbsp;The last three days in the record contain no PRs from this location.</p> <p>&nbsp;<strong>&nbsp;&nbsp;&nbsp; Location 3 - Via Etnea - Piazza Universit&agrave;</strong></p> <p>&nbsp;Similar to Location 2, the device is placed on the windowsill and moved around by people working in the building.<br> &nbsp;Similar behavior is also observed, e.g., it is placed on the windowsill and moved inside a thick wall&nbsp; when no people are present.<br> &nbsp;This device appears to have been collecting data throughout the whole dataset period.<br> &nbsp;<br> &nbsp;<strong>&nbsp;&nbsp;&nbsp; Location 4 - Piazza Universit&agrave;</strong></p> <p>&nbsp;This location is wirelessly connected to the access point.<br> &nbsp;The device was placed statically on a windowsill overlooking the square.<br> &nbsp;Due to physical limitations, the device had lost power several times during the deployment.<br> &nbsp;The internet connection was also interrupted sporadically.</p> <p><strong>Recognitions</strong></p> <p>The data was collected within the scope of <a href="https://www.resilocproject.eu/">Resiloc project</a> with the help of City of Catania and project partners.</p>

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

Supplementary Materials for "UJI Probes: Dataset of Wi-Fi Probe Requests"

<p>This package contains an anonymized packets of 802.11 probe requests captured throughout March of 2023 at Universitat Jaume I. The packet capture file is in the standardized *.pcap binary format and can be opened with any packet analysis tool such as Wireshark or scapy (Python packet analysis and manipulation package).<br> <br> The dataset is usable for analyzis of Wi-Fi probe requests, presence detection, occupancy estimation or signal stability analyzis.</p>

opencc-by-4.0Apr 2023View details →
zenodo40/100

Probe requests of 24 devices in a semianechoic chamber

<p>This dataset was created collecting probe requests generated by&nbsp;24 devices inside a semianechoic chamber.</p> <p>The scanning duration is around 22 minutes and for each probe request acquired, several details are reported:</p> <p>- MAC ADDRESS: for privacy reasons the id annotated in mac column is the result of hashing with SHA256 algorithm on the original mac address</p> <p>- SEQ: the sequence number of the probe request</p> <p>- TIME:&nbsp; is the unixtime of istant when the probe request where collected</p> <p>- ID_X: for each column, the X value indicates the information element ID and its value represents the length for that field</p> <p>- OUI: indicates the&nbsp;Organizationally Unique Identifier directly from the original mac address</p> <p>- VENDOR: contains the vendor extracted from the original OUI.</p>

opencc-by-4.0Jul 2020View details →

ScienceDex guides

Understand access before you commit

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

Compare curated datasets

Allen Brain Atlas

Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.

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

Annotated Behaviour and Observability Dataset (ABODe)

ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.

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

DANDI Archive for NWB datasets

DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.

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

International Brain Laboratory public data

The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.

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

OpenNeuro

OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.

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