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.
315
datasets available to search
ShareScore release 0.9.0
Dataset results
315 results for “Underwater Images”
R-CAUSTIC: Rippling CAUSTICs underwater Image dataset
<p><strong>Description</strong></p><p>Rippling caustics seem to be the main factor degrading the underwater RGB image quality and affecting the image- based 3D reconstruction process in very shallow waters. These effects are adversely affecting image matching algorithms by throwing off most of them, leading to less accurate matches and causing issues in the Simultaneous Localization and Mapping (SLAM) based navigation of the Remotely Operated Vehicles (ROV) and Autonomous Underwater Vehicles (AUV) on shallow waters. Also, they are the main cause for dissimilarities in the generated textures and orthoimages. In order to fill the gap in the literature regading underwater rippling caustics imagery with real ground truth and reference images, the first real-world underwater caustics benchmark dataset which contains 1465 underwater images is presented. Together with the RGB imagery, the corresponding generated ground truth images are delivered for facilitating the training and testing of machine learning and deep learning methods for image classification. R-CAUSTIC dataset also provides the necessary data to evaluate, at least to some extent, the performance of 3D reconstruction approaches. Data were acquired using a GoPro Hero 4 Black action camera with image dimensions of 4000 x 3000 pixels, focal length of 2.77mm and pixel size of 1.55μm and a tripod. Action cameras are widely used for underwater image acquisition. The dataset was captured in near-shore underwater sites at depths varying from 0.5 to 2m. No artificial light sources were used. Due to the wind, the turbulent surface of the water created dynamic rippling caustics on the seabed. In total 1465 RGB images were collected, separated in 7 different datasets; five of them containing stereo images, one of them tri-stereo images and one consists of multi-stereo imagery acquired in 7 different camera poses.</p><p> </p><p><strong>Publication</strong></p><p>The paper is availbale in Open Access here: https://ieeexplore.ieee.org/document/10172291</p><p><strong>If you use this dataset please cite it as R-CAUSTIC</strong> [Reference].<br>[Reference]: <strong>P. Agrafiotis, K. Karantzalos and A. Georgopoulos, "Seafloor-Invariant Caustics Removal From Underwater Imagery," in </strong><i><strong>IEEE Journal of Oceanic Engineering</strong></i><strong>, vol. 48, no. 4, pp. 1300-1321, Oct. 2023, doi: 10.1109/JOE.2023.3277168.</strong></p><p>BibTeX:</p><p>@ARTICLE{10172291, author={Agrafiotis, Panagiotis and Karantzalos, Konstantinos and Georgopoulos, Andreas}, journal={IEEE Journal of Oceanic Engineering}, title={Seafloor-Invariant Caustics Removal From Underwater Imagery}, year={2023}, volume={48}, number={4}, pages={1300-1321}, doi={10.1109/JOE.2023.3277168}}</p><p> </p>
Underwater surveys of mullet schools (Mugil liza) with Adaptive Resolution Imaging Sonar
<p>This dataset is part of a research project that employs deep learning, with a density-based regression approach, to count fish in low-resolution sonar images (Tarling et al. preprint arXiv DOI: http://arxiv.org/abs/2104.14964).</p> <p>In this repository, we provide data from sonar-based underwater videos of schools of migratory mullets (<em>Mugil liza</em>) recorded at the Tesoura beach (28.495775 S, 48.759996 W), a 100-meter long beach at the inlet canal connecting the Laguna lagoon system to the Atlantic Ocean, in southern Brazil. Since the water transparency at the lagoon canal is very low (from 0.3 to 1.5m visibility; collected <em>in situ</em> with a Secchi disk), mullet schools were recorded by deploying an Adaptive Resolution Imaging Sonar, ARIS 3000 (Sound Metrics Corp, WA, USA), which uses 128 beams to project a wedge-shaped volume of acoustic energy and convert their returning echoes into a digital overhead view of the mullet schools.</p> <p>This dataset contains 500 fully annotated images that were manually marked for the location and abundance of mullet fish, and 126 raw sonar video files, representing over 100k images. The files are organized as follows:</p> <p>1) "2018-MM-DD_HHMMSS" files are mp4 videos (you may need to add the file extension ".mp4"): There are 126 ARIS files converted into MP4 videos totalling over 789MB of underwater footage captured at 3 frames/seconds. Note that file names indicate the date and time the video was recorded.</p> <p>2) ".npy" files (in Labelled_data.zip): From the video files, 500 images were selected for labelling. Images (x) were cropped to represent a 4x8.5m<sup>2</sup> area and resized to 320 x 576 pixels. Mullet fish were marked with a point annotation. Corresponding ground truth density maps (y) were generated by convolving a Gaussian kernel over the image mask, size =4 and standard deviation = 1. The labelled dataset was randomly split into a holdout partition of 350 training images, 70 validation, and 80 test. </p> <p>3) ".csv" files: log of frames selected for the labelled subset of data</p> <p>4) ".h5" file: pre-trained weights for our multi-task with uncertainty regularisation network</p> <p>To advance the development of these machine learning tools, we also make our code openly available (https://github.com/ptarling/DeepLearningFishCounting).</p>
Underwater images collected by Scuba diving in Ifaty, Madagascar - 2023-05-07
<i>This dataset was collected by Scuba diving in Ifaty, Madagascar - 2023-05-07.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 2.66 GB of MP4 files, which were trimmed into 1056 frames (at 2997/1000 fps). <br> The frames are not georeferenced. <br> 93.75% of these extracted images are useful and 6.25% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> No GPS. <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://doi.org/10.5281/zenodo.15853010" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://doi.org/10.5281/zenodo.15228535" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by Scuba diving in Nosy-Ve, Madagascar - 2023-04-30
<i>This dataset was collected by Scuba diving in Nosy-Ve, Madagascar - 2023-04-30.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 1.5 GB of JPG files, which were trimmed into 267 frames (at 4 fps). <br> The frames are georeferenced. <br> 99.63% of these extracted images are useful and 0.37% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> No GPS. <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://doi.org/10.5281/zenodo.15853010" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://doi.org/10.5281/zenodo.15228535" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Sarodrano, Madagascar - 2023-05-03
<i>This dataset was collected by an Autonomous Surface Vehicle in Sarodrano, Madagascar - 2023-05-03.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 15.07 GB of MP4 files, which were trimmed into 5136 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 59.54% of these extracted images are useful and 40.46% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 0.0 %, Q2: 0.0 %, Q5: 100.0 % <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://doi.org/10.5281/zenodo.15853010" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://doi.org/10.5281/zenodo.15228535" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Ifaty, Madagascar - 2023-05-06
<i>This dataset was collected by an Autonomous Surface Vehicle in Ifaty, Madagascar - 2023-05-06.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 17.33 GB of MP4 files, which were trimmed into 4251 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 100.0% of these extracted images are useful and 0.0% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> Base : No Base <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 0.0 %, Q2: 0.0 %, Q5: 100.0 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://www.echologger.com/products/single-frequency-echosounder-deep" target="_blank">ETC 400</a>. <br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 0.2 m and 50.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 0.422 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://doi.org/10.5281/zenodo.15853010" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://doi.org/10.5281/zenodo.15228535" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Anakao, Madagascar - 2023-05-01
<i>This dataset was collected by an Autonomous Surface Vehicle in Anakao, Madagascar - 2023-05-01.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 13.58 GB of MP4 files, which were trimmed into 2767 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 80.88% of these extracted images are useful and 19.12% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 0.0 %, Q2: 0.0 %, Q5: 100.0 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://www.echologger.com/products/single-frequency-echosounder-deep" target="_blank">ETC 400</a>. <br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 0.2 m and 50.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 0.335 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://doi.org/10.5281/zenodo.15853010" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://doi.org/10.5281/zenodo.15228535" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Ifaty, Madagascar - 2023-05-07
<i>This dataset was collected by an Autonomous Surface Vehicle in Ifaty, Madagascar - 2023-05-07.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 25.86 GB of MP4 files, which were trimmed into 5425 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 99.17% of these extracted images are useful and 0.83% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> Base : No Base <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 0.0 %, Q2: 0.0 %, Q5: 100.0 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://www.echologger.com/products/single-frequency-echosounder-deep" target="_blank">ETC 400</a>. <br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 0.2 m and 20.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 0.313 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://doi.org/10.5281/zenodo.15853010" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://doi.org/10.5281/zenodo.15228535" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Sarodrano, Madagascar - 2023-05-04
<i>This dataset was collected by an Autonomous Surface Vehicle in Sarodrano, Madagascar - 2023-05-04.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 0.0 %, Q2: 0.0 %, Q5: 100.0 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://www.echologger.com/products/single-frequency-echosounder-deep" target="_blank">ETC 400</a>. <br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 0.2 m and 35.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 0.492 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://doi.org/10.5281/zenodo.15853010" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://doi.org/10.5281/zenodo.15228535" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Sarodrano, Madagascar - 2023-05-05
<i>This dataset was collected by an Autonomous Surface Vehicle in Sarodrano, Madagascar - 2023-05-05.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 34.7 GB of MP4 files, which were trimmed into 9193 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 98.34% of these extracted images are useful and 1.66% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 0.0 %, Q2: 0.0 %, Q5: 100.0 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://www.echologger.com/products/single-frequency-echosounder-deep" target="_blank">ETC 400</a>. <br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 0.2 m and 20.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 0.463 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://doi.org/10.5281/zenodo.15853010" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://doi.org/10.5281/zenodo.15228535" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by Scuba diving in Nosy-Ve, Madagascar - 2023-04-30
<i>This dataset was collected by Scuba diving in Nosy-Ve, Madagascar - 2023-04-30.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 2.49 GB of JPG files, which were trimmed into 460 frames (at 4 fps). <br> The frames are not georeferenced. <br> 100.0% of these extracted images are useful and 0.0% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> No GPS. <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://doi.org/10.5281/zenodo.15853010" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://doi.org/10.5281/zenodo.15228535" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Sarodrano, Madagascar - 2023-05-03
<i>This dataset was collected by an Autonomous Surface Vehicle in Sarodrano, Madagascar - 2023-05-03.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 16.67 GB of MP4 files, which were trimmed into 8820 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 81.93% of these extracted images are useful and 18.07% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 0.0 %, Q2: 0.0 %, Q5: 100.0 % <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://doi.org/10.5281/zenodo.15853010" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://doi.org/10.5281/zenodo.15228535" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Sarodrano, Madagascar - 2023-05-05
<i>This dataset was collected by an Autonomous Surface Vehicle in Sarodrano, Madagascar - 2023-05-05.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 20.22 GB of MP4 files, which were trimmed into 5846 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 87.7% of these extracted images are useful and 12.3% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 0.0 %, Q2: 0.0 %, Q5: 100.0 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://www.echologger.com/products/single-frequency-echosounder-deep" target="_blank">ETC 400</a>. <br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 0.2 m and 35.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 0.352 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://doi.org/10.5281/zenodo.15853010" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://doi.org/10.5281/zenodo.15228535" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Aldabra-Gigi, Seychelles - 2022-10-23
<i>This dataset was collected by an Autonomous Surface Vehicle in Aldabra-Gigi, Seychelles - 2022-10-23.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 13.17 GB of MP4 files, which were trimmed into 5413 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 97.84% of these extracted images are useful and 2.16% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 95.29 %, Q2: 4.62 %, Q5: 0.09 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://ceruleansonar.com/products/sounder-s500" target="_blank">S500</a>. <br> We only keep the values which have a GPS correction in Q1.<br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 0.2 m and 6.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 0.083 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://github.com/SeatizenDOI/plancha-workflow/releases/tag/v1.0.3" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://github.com/SeatizenDOI/plancha-inference/releases/tag/v1.0.0" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Aldabra-Gigi, Seychelles - 2022-10-22
<i>This dataset was collected by an Autonomous Surface Vehicle in Aldabra-Gigi, Seychelles - 2022-10-22.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 20.08 GB of MP4 files, which were trimmed into 8062 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 98.76% of these extracted images are useful and 1.24% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 94.17 %, Q2: 5.18 %, Q5: 0.65 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://www.echologger.com/products/single-frequency-echosounder-deep" target="_blank">ETC 400</a>. <br> We only keep the values which have a GPS correction in Q1.<br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 0.2 m and 40.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 0.175 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://github.com/SeatizenDOI/plancha-workflow/releases/tag/v1.0.3" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://github.com/SeatizenDOI/plancha-inference/releases/tag/v1.0.0" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Aldabra-Arm06, Seychelles - 2022-10-22
<i>This dataset was collected by an Autonomous Surface Vehicle in Aldabra-Arm06, Seychelles - 2022-10-22.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 24.62 GB of MP4 files, which were trimmed into 9233 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 41.21% of these extracted images are useful and 58.79% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 96.03 %, Q2: 3.86 %, Q5: 0.11 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://ceruleansonar.com/products/sounder-s500" target="_blank">S500</a>. <br> We only keep the values which have a GPS correction in Q1.<br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 0.2 m and 40.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 1.352 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://github.com/SeatizenDOI/plancha-workflow/releases/tag/v1.0.3" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://github.com/SeatizenDOI/plancha-inference/releases/tag/v1.0.0" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Aldabra-Arm06, Seychelles - 2022-10-22
<i>This dataset was collected by an Autonomous Surface Vehicle in Aldabra-Arm06, Seychelles - 2022-10-22.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 23.38 GB of MP4 files, which were trimmed into 9125 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 87.56% of these extracted images are useful and 12.44% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 57.44 %, Q2: 42.55 %, Q5: 0.01 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://ceruleansonar.com/products/sounder-s500" target="_blank">S500</a>. <br> We only keep the values which have a GPS correction in Q1.<br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 0.2 m and 40.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 0.928 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://github.com/SeatizenDOI/plancha-workflow/releases/tag/v1.0.3" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://github.com/SeatizenDOI/plancha-inference/releases/tag/v1.0.0" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Aldabra-Dubois, Seychelles - 2022-10-23
<i>This dataset was collected by an Autonomous Surface Vehicle in Aldabra-Dubois, Seychelles - 2022-10-23.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 24.93 GB of MP4 files, which were trimmed into 12191 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 54.2% of these extracted images are useful and 45.8% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 98.28 %, Q2: 1.68 %, Q5: 0.05 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://ceruleansonar.com/products/sounder-s500" target="_blank">S500</a>. <br> We only keep the values which have a GPS correction in Q1.<br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 2.0 m and 20.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 0.465 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://github.com/SeatizenDOI/plancha-workflow/releases/tag/v1.0.3" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://github.com/SeatizenDOI/plancha-inference/releases/tag/v1.0.0" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Aldabra-Arm01, Seychelles - 2022-10-24
<i>This dataset was collected by an Autonomous Surface Vehicle in Aldabra-Arm01, Seychelles - 2022-10-24.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 24.82 GB of MP4 files, which were trimmed into 8638 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 97.42% of these extracted images are useful and 2.58% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 68.72 %, Q2: 30.93 %, Q5: 0.34 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://www.echologger.com/products/single-frequency-echosounder-deep" target="_blank">ETC 400</a>. <br> We only keep the values which have a GPS correction in Q1.<br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 0.2 m and 15.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 0.451 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://github.com/SeatizenDOI/plancha-workflow/releases/tag/v1.0.3" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://github.com/SeatizenDOI/plancha-inference/releases/tag/v1.0.0" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <br>
Underwater images collected by an Autonomous Surface Vehicle in Aldabra-Arm06, Seychelles - 2022-10-22
<i>This dataset was collected by an Autonomous Surface Vehicle in Aldabra-Arm06, Seychelles - 2022-10-22.</i> <br> <br><br>Underwater or aerial images collected by scientists or citizens can have a wide variety of use for science, management, or conservation. These images can be annotated and shared to train IA models which can in turn predict the objects on the images. We provide a set of tools (hardware and software) to collect marine data, predict species or habitat, and provide maps.<br><br> This dataset is part of larger collection referencing numerous underwater and aerial images <a href="https://doi.org/10.5281/zenodo.11125847" target="_blank">Seatizen Altas</a>. Methods, tools and scientific objectives are also described in a dedicated data paper.<br> <h2>Image acquisition</h2> This session has 21.06 GB of MP4 files, which were trimmed into 7993 frames (at 2997/1000 fps). <br> The frames are georeferenced. <br> 51.06% of these extracted images are useful and 48.94% are useless, according to predictions made by <a href="jacques-v0.1.0_model-20240513_v20.0" target="_blank">Jacques model</a>. <br> Multilabel predictions have been made on useful frames using <a href="https://huggingface.co/lombardata/DinoVdeau-large-2024_04_03-with_data_aug_batch-size32_epochs150_freeze" target="_blank">DinoVd'eau</a> model. <br> <h2> GPS information: </h2> The data was processed with a PPK workflow to achieve centimeter-level GPS accuracy. <br> Base : Files coming from rtk a GPS-fixed station or any static positioning instrument which can provide with correction frames. <br> Device GPS : Emlid Reach M2 <br> Quality of our data - Q1: 75.76 %, Q2: 24.12 %, Q5: 0.12 % <br> <h2> Bathymetry </h2> The data are collected using a single-beam echosounder <a href="https://www.echologger.com/products/single-frequency-echosounder-deep" target="_blank">ETC 400</a>. <br> We only keep the values which have a GPS correction in Q1.<br> We keep the points that are the waypoints.<br> We keep the raw data where depth was estimated between 0.2 m and 30.0 m deep. <br> The data are first referenced against the WGS84 ellipsoid. <br> At the end of processing, the data are projected into a homogeneous grid to create a raster and a shapefiles. <br> The size of the grid cells is 1.259 m. <br> The raster and shapefiles are generated by linear interpolation. The 3D reconstruction algorithm is ballpivot. <br> <h2> Generic folder structure </h2> YYYYMMDD_COUNTRYCODE-optionalplace_device_session-number <br> ├── DCIM : folder to store videos and photos depending on the media collected. <br> ├── GPS : folder to store any positioning related file. If any kind of correction is possible on files (e.g. Post-Processed Kinematic thanks to rinex data) then the distinction between device data and base data is made. If, on the other hand, only device position data are present and the files cannot be corrected by post-processing techniques (e.g. gpx files), then the distinction between base and device is not made and the files are placed directly at the root of the GPS folder. <br> │ ├── BASE : files coming from rtk station or any static positioning instrument. <br> │ └── DEVICE : files coming from the device. <br> ├── METADATA : folder with general information files about the session. <br> ├── PROCESSED_DATA : contain all the folders needed to store the results of the data processing of the current session. <br> │ ├── BATHY : output folder for bathymetry raw data extracted from mission logs. <br> │ ├── FRAMES : output folder for georeferenced frames extracted from DCIM videos. <br> │ ├── IA : destination folder for image recognition predictions. <br> │ └── PHOTOGRAMMETRY : destination folder for reconstructed models in photogrammetry. <br> └── SENSORS : folder to store files coming from other sources (bathymetry data from the echosounder, log file from the autopilot, mission plan etc.). <br> <h2> Software </h2> All the raw data was processed using our <a href="https://github.com/SeatizenDOI/plancha-workflow/releases/tag/v1.0.3" target="_blank">worflow</a>. <br>All predictions were generated by our <a href="https://github.com/SeatizenDOI/plancha-inference/releases/tag/v1.0.0" target="_blank">inference pipeline</a>. <br>You can find all the necessary scripts to download this data in this <a href="https://github.com/SeatizenDOI/zenodo-tools" target="_blank">repository</a>. <br>Enjoy your data with <a href="https://github.com/SeatizenDOI" target="_blank">SeatizenDOI</a>! <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.