Published June 24, 2026 | Version v6.1

Global monthly tuna, tuna-like and shark catch (levels 1-2) and fishing effort (level 0) datasets (1950-2024) at 1° and 5° spatial resolution

  • 1. ROR icon Institut de Recherche pour le Développement
  • 2. ROR icon Marine Biodiversity Exploitation and Conservation
  • 3. EDMO icon Marine Biodiversity, Exploitation and Conservation (Sète)
  • 1. Indian Ocean Tuna Commission
  • 2. International Commission for the Conservation of Atlantic Tunas
  • 3. Western and Central Pacific Fisheries Commission
  • 4. Inter-American Tropical Tuna Commission
  • 5. Commission for the Conservation of Southern Bluefin Tuna

Description

Global Tuna Atlas (GTA) - Dataset Description

This Zenodo record contains the complete collection of datasets required to reproduce the Global Tuna Atlas (GTA) processing workflow, together with the Docker image used to generate the processed products. The archive contains both the original public datasets collected from the five tuna Regional Fisheries Management Organizations (t-RFMOs) - CCSBT, IATTC, ICCAT, IOTC and WCPFC - and the processed catch and effort datasets generated by the GTA workflow, covering the period 1950-2024 on 1° or 5° spatial grids with monthly temporal resolution.

Lower levels of processing have been officially endorsed by FIRMS and are also published on Zenodo (see FIRMS Global Tuna Atlas datasets, DOI: 10.5281/zenodo.5745958). FIRMS datasets currently deal only with catches and Level 0 data - a global dataset kept as close as possible to what is published on t-RFMO websites — including a lower spatio-temporal resolution version giving the best estimates of total (nominal) catches per year and per ocean.

Data structure

All Global Tuna Atlas datasets comply with a common data format aligned with the CWP Reference Harmonization standard (FAO CWP RH), described in a JSON schema available on GitHub. Catch data are stratified by: month, species, gear_type, fishing_fleet, fishing_mode, geographic_identifier, measurement_unit, measurement (catch), measurement_type (landings or retained catches), and measurement_processing_level (original samples or processed data). A descriptive label column is added for each coded field.

Included datasets

Raw input data (all_raw_data_GTA.zip)

Contains all datasets required to reproduce the workflow from the original public sources: catch and effort datasets from CCSBT, IATTC, ICCAT, IOTC and WCPFC; nominal catch datasets; species, gear, fleet and measurement codelists; conversion factors; spatial reference datasets; mapping tables; workflow configuration files; and all auxiliary resources used by the processing workflow. These files are the exact inputs used to generate every processed GTA product.

Nominal dataset

Annual catches aggregated by ocean and species. This is the official reference dataset used throughout the workflow and the target against which georeferenced catches are raised.

Level 0 catch dataset (IRD Level 0)

The harmonized global georeferenced catch dataset. Original t-RFMO reporting is preserved as closely as possible while field names, codelists and metadata are converted to the common CWP-based data model.

Level 1 catch dataset (IRD Level 1)

Extends Level 0 by harmonizing catch measurement units. Catches reported in numbers are converted to weight (tons) using official IOTC conversion factors, or historical conversion factors developed by Alain Fonteneau (IRD) for the other t-RFMOs. Only the five major species with reliable conversion factors are retained: yellowfin tuna, skipjack tuna, bigeye tuna, albacore, southern bluefin tuna, and swordfish.

Level 2 catch dataset (IRD Level 2)

IRD Level 2 denotes the series of processing steps applied by IRD to convert and raise the georeferenced catch data (Level 1) to match nominal dataset values. It is not a final, static product but a processing level focused on this raising/conversion step. Although some steps mirror those used in the FIRMS Level 0 product (DOI: 10.5281/zenodo.5745958), the entire workflow was rerun to integrate early adjustments to IATTC shark and billfish data prior to final aggregation.

This dataset compiles monthly global catch data for tuna, tuna-like species and sharks from 1950 through 2023, stratified according to the latest CWP standards update: month, species, gear_type (reporting fishing_gear), fishing_fleet (reporting country), fishing_mode (type of school used), geographic_identifier (1° or 5° grid cell), measurement_unit (weight or number), measurement (catch), measurement_type (landings or retained catches), and measurement_processing_level (original samples or processed data), with a label column added to each coded field for descriptive metadata.

Exception - coarser strata for month and geographic_identifier because catches are raised to match nominal data at the strata level judged most probable when an exact match isn't available, a significant share of records end up aggregated at a resolution coarser than a single month or a 1°/5° grid cell — in some cases geographic_identifier covers a much larger area, up to a large portion of an entire ocean. This is a direct consequence of the raising procedure, not a data-quality artifact, but it means the nominal spatio-temporal resolution advertised for Level 2 does not hold uniformly across all records. Notable treatments:

  • Catches and numbers are raised to nominal only for exactly matching strata, or otherwise to the strata judged most probable to correspond, since every georeferenced catch stratum should match a nominal catch.
  • IATTC purse seine data are distributed as three separate files (tuna, billfish, shark) because tuna is reported by both observers and logbooks, while shark and billfish are observer-only; shark and billfish catches are therefore raised to the fishing effort reported in the tuna dataset (new in v4; previously done at FIRMS Level 0).
  • Catches reported in numbers of fish are converted to weight based on nominal data (since v5).
  • Strata where tonnage catches were raised to match nominal data have had their corresponding number-of-fish values removed (since v5).
  • In some strata nominal data exceeds georeferenced data; this likely reflects differences in aggregation methods and warrants further review with data providers.

Intended use: this dataset improves understanding of fish counts at Level 0 and the extent of georeferenced coverage. It is not suitable for precisely georeferencing catches by country or fleet, and should not be used for studies of fishing-zone legality or quota management — it offers a georeferenced footprint approximating reported biomass, but substantial locational uncertainty remains.

Notable difference from the previous version: missing IATTC data at the 5° resolution have been added.

Level 0 effort dataset (IRD Level 0)

Preserves all publicly available georeferenced fishing effort observations from the five t-RFMOs, processed with the same workflow as the catch data but with different parametrization. Effort is reported in 23 measurement units; only a small number of mappings between similar t-RFMO units have been established (see fdi-mappings). Remaining units are kept unconverted to preserve semantic richness, since each reflects different operational aspects depending on gear, fleet behavior and reporting RFMO. No higher processing level is currently distributed for effort; further aggregation is left to end-users based on their scientific goals.

Known duplication: for ICCAT, and for WCPFC purse-seine data, the same effort may be reported multiple times under different units, since no official conversion between them exists (e.g., Hours.FAD and Hours.FSC may partially inform Hours.STD). For WCPFC, SETS records are associated with a fishing_mode while DAYS records are not, so duplicates do not always share the same fishing_mode. Limited harmonization (e.g., NET-days vs. Nets) has not yet been implemented but may be considered in future releases.

Reproducibility

  • Docker image (gta-workflow.tar.gz): complete software environment to reproduce the workflow from raw inputs without installing R or additional dependencies.
  • GitHub repository: firms-gta/geoflow-tunaatlas (DOI: 10.5281/zenodo.14039665), with full code, materials and documentation on the impact of each processing step.
  • Shiny app: ghcr.io/firms-gta/tunaatlas_pie_map_shiny_cwp_database:latest, a Docker-based visualization tool for exploring catch data in CWP format.
  • R package: bastienird/CWP.dataset, for manipulating CWP-standard data and generating structured plots and reports.

Contact

For a customized version of the Global Tuna Atlas with specific filters or adjustments for particular research questions, please contact the maintainers directly.

Notes

Global Tuna Atlas (GTA) Workflow – Docker Distribution

Overview

This Zenodo record provides everything required to reproduce the Global Tuna Atlas (GTA) workflow without installing R or its dependencies.

The archive contains:

  • gta-workflow.tar.gz – Docker image containing the complete GTA workflow.

  • all_raw_data_GTA.zip – Input datasets required by the workflow.

  • README.md – This document.

Requirements

Before running the workflow, make sure you have:

  • Docker installed (Docker Engine 24 or newer recommended)

  • Approximately 30 GB of available disk space

  • Internet connection only for downloading this Zenodo record (the workflow itself can be run offline)

1. Create a working directory

mkdir -p ~/gta_run/downloads
mkdir -p ~/gta_run/data/GTA_2026
mkdir -p ~/gta_run/jobs

2. Download the files

If you downloaded the files directly from the Zenodo record using your web browser, place them in:

~/gta_run/downloads/

Alternatively, they can be downloaded directly from Zenodo using wget:

cd ~/gta_run/downloads

wget -O gta-workflow.tar.gz \
  "https://zenodo.org/records/20834708/files/gta-workflow.tar.gz?download=1"

wget -O all_raw_data_GTA.zip \
  "https://zenodo.org/records/20834708/files/all_raw_data_GTA.zip?download=1"

3. Load the Docker image

cd ~/gta_run/downloads

docker load < gta-workflow.tar.gz

This imports the Docker image into your local Docker installation.

4. Extract the raw data

cd ~/gta_run/downloads

unzip all_raw_data_GTA.zip -d ~/gta_run/data/GTA_2026

The archive contains a top-level folder named all_raw_data_GTA. Move its content directly into GTA_2026, because the workflow expects the raw files at the top level of the mounted data directory:

mv ~/gta_run/data/GTA_2026/all_raw_data_GTA/* ~/gta_run/data/GTA_2026/
rmdir ~/gta_run/data/GTA_2026/all_raw_data_GTA

After extraction, files such as the following should be directly available in:

~/gta_run/data/GTA_2026/

For example:

~/gta_run/data/GTA_2026/iotc_nominal_catch_firms_level0_2026-04-13.csv

If you get a Permission denied error during extraction, reset ownership of the working directory:

sudo chown -R $USER:$USER ~/gta_run

Then run the extraction commands again.

5. Run the workflow

docker run --rm \
  --network none \
  -v ~/gta_run/data/GTA_2026:/home/rstudio/geoflow-tunaatlas/data/GTA_2026 \
  -v ~/gta_run/jobs:/home/rstudio/geoflow-tunaatlas/jobs \
  -e GTA_STEPS=nominal,level0,effort,rawdata,level1,level2 \
  -e GTA_DATA_SOURCE=volume_dir \
  -e GTA_DATA_PATH=/home/rstudio/geoflow-tunaatlas/data/GTA_2026 \
  -e GTA_SUMMARISE_INVALID_RAW=false \
  -e GTA_BOOTSTRAP_RESTORE_RENV=false \
gta-workflow:latest

The --network none option disables network access during execution, ensuring the workflow uses only the provided input data and resources already contained in the Docker image.

Output

Workflow outputs, reports and logs are written to:

~/gta_run/jobs

Reproducibility

This Docker image contains:

  • the GTA workflow;

  • the complete R environment;

  • all required R packages;

  • all required system libraries;

  • cached external mappings required by the workflow.

Running the image with the supplied input datasets should reproduce the workflow in a consistent software environment.

Citation

If you use this workflow or its outputs, please cite this Zenodo record together with any associated publication describing the Global Tuna Atlas methodology.

Files

Report__level2.pdf

Files (4.2 GB)

Name Size
md5:901f645ffc2e2c7db7197ddf9102530e
194.7 MB Preview Download
md5:d4798ba82d37f7c41b09aa49ced3f179
391.1 MB Preview Download
md5:96f38f4139177733e1f7ee4309781bc6
308.8 MB Preview Download
md5:916464aa10733e20dea791257d1ba15a
625.0 MB Preview Download
md5:dbf99a1589f221b3cf9092d9df8df9a9
331.1 MB Preview Download
md5:7144138f1d2ac4387adcc8334b9e4528
2.3 GB Download
md5:acc950c0601795e750be17234bbbeda9
10.4 MB Preview Download
md5:8dee05e5811089f622abc0eee1d27677
8.0 MB Preview Download
md5:86d0ef05ed06f86674b34b8391e76ee0
9.3 MB Preview Download

Additional details

Related works

Is described by
Computational notebook: 10.5281/zenodo.14025108 (DOI)
Requires
Workflow: 10.5281/zenodo.21109008 (DOI)

Funding

European Commission
Blue-Cloud 2026 - A federated European FAIR and Open Research Ecosystem for oceans, seas, coastal and inland waters 101094227
European Commission
Blue Cloud - Blue-Cloud: Piloting innovative services for Marine Research & the Blue Economy 862409

Software

Repository URL
https://github.com/firms-gta/geoflow-tunaatlas
Programming language
R , Dockerfile
Development Status
Active