Physical loss pressure layer combines all human activities that cause physical loss of seabed. The pressure is given as area lost in each cell (km2). For the polygon datasets the area was assumed to be the lost area. For line and point datasets spatial extents were calculated with buffers (below in brackets). If no buffer extent is indicated, the data was reported as polygon. The human activities used for the physical loss pressure: - Bridges (2 m) - Cables (operational; 1,5 m) - Coastal defence and flood protection (area of polygon, 50 m for lines) - Dredging (capital dredging, Area of polygon or a 25/50 m buffer for <5000 m3 / >5000m3 points) - Extraction of sand and gravel - Finfish mariculture (150 m) - Harbours (polygon with 200 m buffer) - Land claim (area of polygon, 30m buffer for lines) - Marinas and leisure harbours (200 m) - Oil platforms (25 m) - Oil terminals and refineries (200 m) - Pipelines (operational; 15 m) - Shellfish mariculture (area of polygon, 150 m points) - Watercourse modification (50 m) - Wind turbines (operational; 30m point location of turbine) The datasets were first processed separately covering the whole Baltic Sea and then merged into one uniform data layer and minimizing the effect of overlapping areas. Polygon areas were clipped with coastline to remove buffered areas that reached to land.

The dataset contains total landings of sprat for years 2011-2016 reported per ICES statistical rectangles (tonnes / ICES rectangle) under EU Joint Research Centre’s data collection framework for fisheries data. Russian data extracted from ICES annual reports.

Data set represents dredging activities around the Baltic Sea. The dataset contains information about the dredging activity and for some the type (capital, maintenance) and the year of activity as reported by HELCOM Contracting Parties in response to data request. The dredging data is missing from Denmark.

The dataset contains total landings of cod for years 2011-2016 reported per ICES statistical rectangles (tonnes / ICES rectangle) under EU Joint Research Centre’s data collection framework for fisheries data. Russian data extracted from ICES annual reports.

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.

Data shows the extent of land claim (permanent or temporary establishments of the sea) and the type of the construction. The data was made available by HELCOM Contracting Parties in response to data request. The data was received from Denmark, Finland, Sweden and Poland. The activity was declared as not relevant in Germany, Estonia, Latvia and Lithuanian. From Russia no data was reported. Attribute specification and units: Country: Country Type: Type of construction (land claim) Type_spec: More specified information about the type of land claim Year: Year of construction Estimated: Estimated year of construction from the identification information (environmental permit) given by the country in question Length: Length of the land reclamation (m) Area: Area (km2) of the land claim X_lon: Original Longitude coordinate point (for the data that has been transformed from points into lines) Y_Lat: Original latitude coordinate point (for the data that has been transformed from points into lines)

This data set on deposition sites of dredged material (areas) reported by HELCOM Contracting parties according to http://www.helcom.fi/Recommendations/Rec%2036-2.pdf for the reporting period 2011-2016. The dataset contains data reported by nationally by nominated experts by HELCOM PRESSURE group for Denmark, Germany, Estonia, Finland, Latvia, Lithuania, Poland, Russia and Sweden.

The fishing intensity map displays data provided in C-square (0.05 x 0.05 degrees) converted to 1x1 km raster 2011-2016. The value of raster cell is subsurface swept area ratio. The data does not cover Russian waters.

'Availability of deep water habitat, based on occurrence of H2S' layer describes the suitability of the bottom areas for the Baltic Sea biota, with regard to oxygen conditions of the near bottom waters. The data used to produce the layer was received from Leibniz-Institut für Ostseeforschung Warnemünde (IOW): - areas (polygons) with hydrogen sulfide (H2S) based on point measurements and modelling. Five time periods / year, for years 2011-2016 (altogether 30 layers). The polygons were converted to raster layers in a way, that for each time period (6 years, 5 time periods each year), areas with H2S got a value 0, other areas got the value 1. All layers were summed, (representing 6 years, 5 time periods each year, maximum value 30) and data was normalised. For more detailed information on the data used, please see Feistel et al. 2016.

The extraction of herring data set is based on: 1. http://metadata.helcom.fi/geonetwork/srv/eng/catalog.search#/metadata/a3b67a55-7c1e-469e-b692-58c4e7b79279 for years 2011-2016 reported per ICES statistical rectangles (tonnes / ICES rectangle). Landing values were redistributed within each ICES rectangle by the c-square fishing effort data provided by ICES (all gears, 2011-2013). Tonnes / km² was calculated and the results were converted to 1 km x 1 km grid cells. The layer was log-transformed and normalised to produce the final pressure layer on extraction of herring. Please see "lineage" section below for further details on attributes, data source, data processing, etc.