Potential spawning areas for herring (PBS EFH)

Open data API in a single place

Provided by HELCOM

Get early access to Potential spawning areas for herring (PBS EFH) API!

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

Dataset information

Updated
Created
2020.05.13
Available languages
English
Keywords
MADS, Habitats and biotopes
Quality scoring
155

Dataset description

Essential fish habitat (EFH) map on Potential spawning areas for herring was prepared in PanBalticScope project (co-founded by the European Maritime and Fisheries Fund of the European Union) http://www.panbalticscope.eu/ Herring (Clupea harengus) is widely distributed in the Baltic Sea and is common in all sub-basins. Herring feeds in the pelagic, mainly on zooplankton, and is an important prey for cod, other fish, and marine mammals. In fisheries management, herring in the Baltic Sea is sub-divided into several stocks. Herring spawns in coastal areas or offshore shallows. It has demersal eggs, which are attached to the substrate. Spawning may occur both in spring and autumn, depending on population, but spring spawning dominates today. Spawning areas of herring were identified by main habitat associations, based on existing observations of herring spawning grounds in the Baltic Sea. ‘Potential spawning areas’ were delineated based on the distribution of any of the following: modelled photic zone, photic hard bottom, charophytes, Fucus spp, Furcellaria lumbricalis, and Zostera marina, several data layers were combined due to uncertainty in the coverage of some of them, ‘High probability’ spawning areas were identified as areas where the modelled photic zone overlaps with any of the other layers. The habitat variables were identified by other existing HELCOM data layers. Stock: Herring in ICES subdivisions 22-24 (spring spawning), subdivisions 25-27, 28.2, 29 and 32, subdivision 28.1 (Gulf of Riga), subdivisions 30-31. EFH type: Spawning areas Approach: Habitat associations combined with manual corrections to eastern Gulf of Finland (Neva inlet), Curonian lagoon, Szczechin lagoon, Vistula lagoon and German waters Variables and thresholds: Distribution of Photic zone, Photic hard bottom, Charophytes, Fucus spp., Furcellaria lumbricalis, Zostera marina. The resulting data layer was corrected by removing recruitment areas in eastern Gulf of Finland (Neva inlet), Curonian lagoon, Szczechin lagoon and enhancing that of the Vistula lagoon. Quality: The data layer is mainly developed based on main habitat associations as identified from scientific literature, not actual data on herring spawning. The delineations are based on other data layers (benthic and habitat-related ecosystem components) for which mapping is not exhaustive and sampling density may vary between countries. Underlying data layers on vegetation (Fucus, Furcellaria, charophytes, Zostera) are based on inventory data and species distribution models. Information on the distribution of Furcellaria is lacking from Russia. Herring preferably spawns in shallow areas. However, the layer does not include depth as a variable, as some known spawning areas offshore would not be included if the depth restriction is used. Due to constraints in the resolution of the underlying data layer, the map also identifies areas shallower than one meter as potential spawning areas of Baltic herring. However, spawning of Baltic herring does not usually occur in such shallow depth. The map represents potential spawning areas. In addition, behavioral components and hydrographic factors influence on the actual chose of spawning site at a certain occasion. Due to these constraints, the data layer on Baltic herring spawning habitats should be considered as a rough estimation. Attribute information: Raster value representing no spawning (0), potential spawning area (0.5) and high probability spawning area (1). References - Fey, DP (2001) Differences in temperature conditions and somatic growth rate of larval and early juvenile spring spawned herring from the Vistula Lagoon, Baltic Sea manifested in the otolith size to fish size relationship. Journal of Fish Biology 58: 1257–1273 - Fey, DP, AM Lejk, P Margonski, L Szymanek, I Psuty, T Nermer, F Lempe, HV Strehlow, P Polte, D Moll, N Stybel, A Hiller, and M van Laak (2014a) Herring. An analysis of spawning ground management, ecological conditions and human impacts in Greifswald Bay, Vistula Lagoon and Hanö Bight. NMFRI, Gdynia, 177 pp. - Fey, D, A. Szkudlarek-Pawelczyk, and A. Wozniczka (2014b) Abundance and distribution of larval herring, Clupea harengus (Actinopterygii: Clupeiformes: Clupeidae) in the Pomeranian Bay, Baltic Sea as an indicator of spawning sites. Acta Ichthyologica et Piscatoria 44: 309–317 - HELCOM (2018a) HELCOM Map and Data service. Layers: mean slope and bottom currents. https://maps.helcom.fi/website/mapservice/. Accessed March 2019 - HELCOM (2018b) HELCOM Map and Data service. Layers: Seabed sediment polygon (BALANCE), Fucus distribution, Furcellaria lumbricalis distribution. https://maps.helcom.fi/website/mapservice/ Accessed 29 October 2018 - Kanstinger P, J Beher, G Grenzdörffer, C Hammer, KB Huebert, D Stepputtis, and M Peck (2018) What is left? Macrophyte meadows and Atlantic herring (Clupea harengus) spawning sites in the Greifswalder Bodden, Baltic Sea. Estuar Coast Shelf Sci 201:72-81) - Krasovskaya, N (2002) Spawning of Baltic herring in the Vistula Lagoon: Effects of environmental conditions and stock parameters. Bulletin of Sea Fish. Inst. No. 1 (155), Gdynia: 3–25 - Popiel, J (1984) On the biology of the Baltic herring. Reports of the Sea Fisheries Institute, Gdynia, vol. 19, 8-16.
Build on reliable and scalable technology
Revolgy LogoAmazon Web Services LogoGoogle Cloud Logo
FAQ

Frequently Asked Questions

Some basic informations about API Store ®.

Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.

Didn't find the API you need?

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

API Store provides access to European Open Data via scalable and reliable REST API interface.
Copyright © 2024. Made with ♥ by Apitalks