From 1 - 10 / 78
  • This pressure dataset is derived from three human activities datasets - Urban land use (on land) - Recreational boating and sports (updated layer for 2018 version, please see separate http://metadata.helcom.fi/geonetwork/srv/eng/catalog.search#/metadata/8c30e828-1340-4162-b7f9-254586ae32b6) - Bathing sites These data are described in more detail in separate fact sheets. Urban land use data was first converted to 1 km grid cells and expanded with 1 km. Thus, coastal urban areas extended also to the sea. These areas were given value 1 and other sea areas, value 0. Bathing sites (points) were converted to 1km grid and given value 1, rest of the sea areas were given value 0. Normalized recreational boating data was converted to 1 km grid cells. These three layers were summed to produce the layer (values from 0 to 3), after that the layer was normalized. Hunting and recreational fishing data were excluded from human disturbance layer, as they are mostly reported per country and would have resulted in overestimation of the actual pressure.

  • Introduction of radionuclides is based on HELCOM MORS Discharge data from 2011 to 2014. The isotopes taken into account were: Cesium-137, Strontium-90, and Cobalt-60. The decay-corrected annual average of the sum of the radionuclide discharges (in Bq) were calculated for the pressure. 10 km buffer with linear decreasing function was used to represent the impact distance from the nuclear power plant outlets.

  • Estuaries (according to Habitats Directive Annex I) are coastal inlets that are strongly influenced by freshwater. The distribution map is based on data submission by HELCOM contracting parties. Most of the submitted data is based on modelling, GIS analysis and/or aerial photos. Data coverage, accuracy and the methods in obtaining the data vary between countries.

  • Distribution of eelgrass based on data submission by HELCOM contracting parties. Mainly pointwise occurrences of eelgrass were submitted, originally gathered in national mapping and monitoring campaigns, or for scientific research. Polygon data from Puck Bay (Poland) was digitized based on Polish Marine Atlas and Orlowo cliff area was added based on expert knowledge. From Estonian waters, a predictive model was used (200m resolution), that was converted to presence/absence using minimized difference threshold (MDT) criteria. All data (points, polygon and the raster presenting predicted presence of eelgrass in the Estonian waters) were generalized to 5km x 5km grid cells.

  • Broad-scale habitat maps for the Baltic Sea have been produced in the EUSeaMap project in 2016. For German and Estonian marine areas, national (more accurate) datasets were used. German data included both substrate and light information (division into infralittoral/circalittoral). Estonian data included only substrate and the division into light regimes was obtained from the EuSeaMap data. Here, the habitat class “infralittoral mixed substrate” includes classes “mixed sediment” of the original data, in the infralittoral zone. The original polygon maps have been converted to 1 km x 1km grid. The scale of the substrate data used in broad-scale habitat maps varies from 1:250 000 to 1:1M (data from EMODnet Geology). Coarser resolution data has been used in areas, where 1: 250 000 substrate data has not been available. Due to different scales used, the habitat classes may show different sized patterns in different areas.

  • Springtime Chl-a concentration is here used as a proxy for productive surface waters. In the Baltic Sea Impact Index (BSII), areas with high springtime phytoplankton production will be given higher importance, as they are considered important areas for the Baltic Sea food web. In the current map, mean of springtime maximum weekly values (weeks 12-22, years 2003-2011) Chl-a concentration of the surface waters has been used, derived from satellite data (MERIS). Years 2003-2011 have been used, as there is no MERIS data available for years 2012-2016. The data for eastern Baltic Sea is provided by the Finnish Environment Institute (~300m resolution). Outside this high resolution data, MERIS-data downloaded from JRC-database has been used (~4 km resolution, to calculate average of maximum monthly values for April or May for 2003-2011). Both datasets were converted to 1 km x 1 km grid cells.

  • Distribution of Fucus sp. based on data submission by HELCOM contracting parties. Mainly pointwise occurrences of Fucus were submitted, originally gathered in national mapping and monitoring campaigns, or for scientific research purposes. From Estonian waters, a predictive model was used (200m resolution), that was converted to presence/absence using minimized difference threshold (MDT) criteria. All data (Fucus points and the raster presenting predicted presence of Fucus) were generalized to 5km x 5km grid cells.

  • Potential effect of continuous noise to mobile species assesses the cumulative potential effect of continuous noise on mobile species and their presence in the HELCOM area. The evaluation is based on the pressure layer on input of continuous noise, combined with information on the distribution of 15 mobile species and their habitats. The thematic analyses on the potential effect of continuous noise to mobile species is calculated for each assessment unit (1 km2 grid cells) and the data set covers the time period 2016-2021. Spatial Pressure and Impact Assessment (SPIA) is the framework for assessing spatial and cumulative pressures and impacts in HOLAS 3, and this analyses present a thematic assessment including only a certain subset of layers. The framework also includes results for the Baltic Sea Impact Index (full cumulative impact assessment), Baltic Sea Pressure Index (full cumulative pressure assessment), and other thematic assessments where a subset of pressure and ecosystem layers are used. For more info please - visit the HOLAS 3 website (http://stateofthebalticsea.helcom.fi/) - download the report thematic assessment of spatial distribution of pressures and impacts 2016-2021 (https://helcom.fi/post_type_publ/holas3_spa) - or check out the HELCOM SPIA online tool to make calculations for any desired combination of pressures and ecosystem layers (https://maps.helcom.fi/website/bsii/). Please scroll down to "Lineage" for a more detailed description of the methodology.

  • Broad-scale habitat maps for the Baltic Sea have been produced in the EUSeaMap project in 2016. For German and Estonian marine areas, national (more accurate) datasets were used. German data included both substrate and light information (division into infralittoral/circalittoral). Estonian data included only substrate and the division into light regimes was obtained from the EuSeaMap data. Here, the habitat class “infralittoral mud” includes classes “Fine mud”, “Mud to sandy mud” and “Sandy mud” of the original data, in the infralittoral zone. The original polygon maps have been converted to 1 km x 1km grid. The scale of the substrate data used in broad-scale habitat maps varies from 1:250 000 to 1:1M (data from EMODnet Geology). Coarser resolution data has been used in areas, where 1: 250 000 substrate data has not been available. Due to different scales used, the habitat classes may show different sized patterns in different areas.

  • Baltic International Trawl Survey (BITS) data (2011-2016) from ICES DATRAS database was used as a base to create a map of cod relative abundance (quarter 1 data, CPUE values per ICES subdivision). Cod = 30cm was included. For ICES rectangles surveyed by BITS, values shown are the mean CPUE per ICES subdivision based on BITS data, average for 2011-2016. For ICES rectangles not surveyed by BITS, values are calculated as: MAX-value x Weighting factor. The weighting factor is specific to each ICES rectangle, calculated as the ratio between the commercial landings in that rectangle and the commercial landings in the ICES rectangle with highest landings (based on averages for 2011-2016). MAX-value = CPUE according to BITS in the ICES rectangle with highest landings. ICES rectangles outside the BITS survey area with no reported cod landings were given the value 0. Values were first log transformed and then normalized.