North Sea Cod and Plaice Tagging Data for Climate Impact Studies
Updated 9d ago
1files
Available on 2 platforms
Sign in to view source links and access this dataset
Description
Tagging data for 22,573 North Sea cod (1961-2015) and 53,489 plaice (1957-2005) includes information on fish location, maturation, sea surface temperature, length, weight, and tagging/recapture times. The dataset was generated for the EU H2020 Pandora project and includes both conventional marker-ID tags and, for cod from 1999 onward, electronic Data Storage Tags (DSTs). It supports analysis of how environmental factors like temperature affect fish fertility and population dynamics.
Use Cases
Modeling changes in cod or plaice fertility based on recorded sea surface temperature (SST)
Analyzing population dynamics and movement patterns using tagging and recapture location data
Studying growth and maturation trends across decades using length and weight measurements
Comparing fish behavior and data quality between conventional marker tags and electronic Data Storage Tags (DSTs)
Strengths
Contains a large sample size with 22,573 cod and 53,489 plaice individual records
Covers a long temporal range, with data collected from 1957 to 2015
Includes multiple measurement types such as location, SST, length, weight, and maturation status
Limitations
Column names and specific data schema are not provided in any source description
Key metadata such as license, author, and precise row count are consistently listed as unknown or null across all platforms
The dataset's freshness is uncertain as the last update date (2026-06-11) appears to be a future placeholder
Provenance
Source
Marine Environmental Data & Information Network (MEDIN), generated for the EU H2020 Pandora project
Collection Method
Fish were tagged and released using conventional marker-ID tags and, for cod from 1999, electronic Data Storage Tags (DSTs)
Time Range
1957 to 2015
Freshness
2026-06-11 08:12:39.220666
Geography
North Sea
The listed last update date is in the future (2026), suggesting it may be an administrative placeholder rather than a true timestamp.