CE12009 Northwest Herring Acoustic Survey

Open data API in a single place

Provided by Marine Institute

Get early access to CE12009 Northwest Herring Acoustic Survey API!

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

Dataset information

Country of origin
Updated
2026.04.07 15:08
Created
2017.11.27
Available languages
English
Keywords
environment
Quality scoring

Dataset description

This survey was conducted by the Marine Institute on-board the RV Celtic Explorer in summer 2012 as part of the North West Herring Acoustic Survey. The aim of an acoustic survey is to determine the relative abundance of the target species. This information is then used to determine catch rates and management advice for the following year. The northwest and west coast (ICES Divisions VIaS and VIIb) herring acoustic survey programme was first established in 1994. The summer 2012 survey represents the fifth in the new time series. The survey was coordinated through the ICES Working Group of International Pelagic Surveys (WGIPS). Combined survey data on herring distribution, abundance and age are used to provide a measure of the relative abundance of herring within the Malin shelf stock complex. Survey data on stock numbers at age are submitted to the ICES Herring Assessment Working Group (HAWG) and used in the annual stock assessment process. The northwest and west coast (ICES Divisions VIaS and VIIb) herring stock is composed of two spawning components, autumn and winter spawners. Spawning covers a large geographical area and extends over a 4-month period from late September through to late March. Traditionally, fishing effort has been concentrated on spawning and pre-spawning aggregations. The autumn spawning component, which mostly occurs within VIIb and VIaS, feeds along the shelf break area to the west of the spawning grounds. The winter spawning component is found further north in VIaS. In VIaS, summer distribution extends from close inshore to the shelf break. Components of the winter spawning fish are known to undertake northward feeding migration into VIaN before returning in the winter to spawn along the Irish coast. This survey focused on the northwest and west coast of Ireland and the west coast of Scotland. The survey track started in the region south of the Hebrides and worked progressively southwards after surveying the Minches region. A systematic parallel transect design was adopted for the majority of the survey, with a randomised start point. Transects were positioned running perpendicular to the lines of bathymetry where possible The acoustic data were collected using the Simrad ER60 scientific echosounder. For biological sampling, a single pelagic midwater trawl was used. 29 trawls were carried out. All components of the catch from the trawl hauls were sorted and weighed; fish and other taxa were identified to species level. Oceanographic stations were carried out during the survey at predetermined locations along the track. Not all stations were sampled due to weather conditions. Data on temperature, depth and salinity (CTD) were collected. The aim of the acoustic survey is to determine the relative abundance of the target species, herring. This information is then used to determine catch rates and management advice for the following year. Other objectives include collecting physical oceanography data
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