SubPipe: A Submarine Pipeline Inspection Dataset for Segmentation and Visual-inertial Localization

Open data API in a single place

Provided by Zenodo

Get early access to SubPipe: A Submarine Pipeline Inspection Dataset for Segmentation and Visual-inertial Localization API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2024.07.05 00:00
Created
2024.01.01
Available languages
English
Keywords
underwater dataset, pipeline, object detection, RGB and grayscale camera, side-scan sonar, SLAM, semantic segmentation
Quality scoring

Dataset description

Abstract This paper presents SubPipe, an underwater dataset for SLAM, object detection, and image segmentation. SubPipe has been recorded using a lightweight autonomous underwater vehicle (LAUV), operated by OceanScan MST, and carrying a sensor suite including two cameras, a side-scan sonar, and an inertial navigation system, among other sensors. The AUV has been deployed in a pipeline inspection environment with a submarine pipe partially covered by sand. The AUV's pose ground truth is estimated from the navigation sensors. The side-scan sonar and RGB images include object detection and segmentation annotations, respectively. State-of-the-art segmentation, object detection, and SLAM methods are benchmarked on SubPipe to demonstrate the dataset's challenges and opportunities for leveraging computer vision algorithms.To the authors' knowledge, this is the first annotated underwater dataset providing a real pipeline inspection scenario. The dataset and experiments are publicly available online. On Zenodo we provide three versions for SubPipe. One is the full version (SubPipe.zip, ~80GB unzipped) and two subsamples: SubPipeMini.zip, ~12GB unzipped and SubPipeMini2.zip, ~16GB unzipped. Both subsamples are only parts of the entire dataset (SubPipe.zip). SubPipeMini is a subset, containing semantic segmentation data, and it has interesting camera data of the underwater pipeline. On the other hand, SubPipeMini2 is mainly focused on underwater side-scan sonar images of the seabed including ground truth object detection bounding boxes of the pipeline. For (re-)using/publishing SubPipe, please include the following copyright text: SubPipe is a public dataset of a submarine outfall pipeline, property of Oceanscan-MST. This dataset was acquired with a Light Autonomous Underwater Vehicle by Oceanscan-MST, within the scope of Challenge Camp 1 of the H2020 REMARO project. More information about OceanScan-MST can be found at this link. Cam0 — GoPro Hero 10 Camera parameters: Resolution: 1520×2704 fx = 1612.36 fy = 1622.56 cx = 1365.43 cy = 741.27 k1,k2, p1, p2 = [−0.247, 0.0869, −0.006, 0.001] Side-scan Sonars Each sonar image was created after 20 “ping” (after every 20 new lines) which corresponds to approx. ~1 image / second. Regarding the object detection annotations, we provide both COCO and YOLO formats for each annotation. A single COCO annotation file is provided per each chunk and per each frequency (low frequency vs. high frequency), whereas the YOLO annotations are provided for each SSS image file. Metadata about the side-scan sonar images contained in this dataset: Images for object detection   # Low Frequency (LF):   5000 LF image size: 2500 × 500 # High Frequency (HF):   5030 HF Image size 5000 × 500 Total number of images: 10030 Annotations   # Low Frequency:   3163 # High Frequency:   3172 Total number of annotations:   6335
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks