This dataset contains actual (non-normalized) riverine flow as well as actual atmospheric and waterborne inputs of nitrogen and phosphorus. In addition the dataset includes the normalized total nutrient inputs (atmospheric + waterborne) of nitrogen and phosphorus into the Baltic Sea. The data are used in the HELCOM core indicator on Inputs of nutrients (nitrogen and phosphorus) to the sub-basins 1995-2020 (https://indicators.helcom.fi/indicator/inputs-of-nutrients/). The river input data is based on reported riverine monitoring data as reported in HELCOM PLC data collection. Data on waterborne inputs, water flow and retention are reported by Contracting Parties to the PLC-Water database. The data are verified and quality assured using the PLC water database (https://nest.su.se/helcom_plc/) verification tools and national expert quality assurance. Atmospheric input data for all Baltic Sea sub-basins are available for the period 1990-2020. Atmospheric transport and deposition of nitrogen compounds are used for modelling atmospheric deposition to the Baltic Sea based on official emission data reported by EMEP Contracting Parties and expert estimates. Atmospheric input and source allocation budgets of nitrogen (oxidized, reduced and total) to the Baltic Sea basins and catchments were computed using the latest version of EMEP MSC-W model. Input of nutrients (N=Nitrogen, P=Phospohus) units are tonnes per year per HELCOM PLC Subbasin. Area delineation of HELCOM PLC subbasins can be accessed from https://maps.helcom.fi/website/mapservice/?datasetID=1456f8a5-72a2-4327-8894-31287086ebb5 Subbasin acronyms stand for: BOB: Bothnian Bay BOS: Bothnian Sea (including ARC = Archipelago Sea) BAP: Baltic Proper GUF: Gulf of Finalnd GUR: Gulf og Riga DS: Danish Straits (= WEB + SOU) (= Western Baltic + Sound) KAT: Kattegat BAS: The Baltic Sea

The data set includes the water flow and nutrient inputs (total nitrogen and phosphorous) of monitored river catchments and unmonitored areas as well as the nutrient inputs from point sources (municipal, industrial and aquaculture) that are directly discharging into the sea. The water flow and nutrient input data is available as actual (non-normalized) and flow normalized. The data covers the whole Baltic Sea drainage area and the years 1995-2022. Together the riverine and point source inputs provide the total land-based load of nutrients into the Baltic Sea. The data consists of several excel spreadsheets providing background info and actual load values. The spatial delineation of these catchments can be accessed through the metadata record for PLC Assessment data river catchments (https://metadata.helcom.fi/geonetwork/srv/eng/catalog.search#/metadata/d7b5404a-b3e1-4fe6-be35-a12055736783). The tabular and the spatial data includes the catchments that have a full time series of data for 1995-2022, and the nutrient load of rivers with incomplete time series are added to the adjacent unmonitored areas. The non-normalized data is used in the HELCOM Baltic Sea Environmental Fact Sheet (BSEFS) on Waterborne nitrogen and phosphorus inputs and water flow to the Baltic Sea that is published annually (https://helcom.fi/baltic-sea-trends/environment-fact-sheets/eutrophication/). The normalized data is used for the inputs of nutrients core indicator (https://indicators.helcom.fi/indicator/inputs-of-nutrients/) as well as the NIC assessment (https://helcom.fi/baltic-sea-action-plan/nutrient-reduction-scheme/national-nutrient-input-ceilings/). The assessment data set is based on the reporting by HELCOM Contracting Parties within the Pollution Load Compilation framework (PLC). The assessment dataset is produced by the Baltic Nest Institute (BNI), Stockholm University together with the Danish Centre for Environment and Energy (DCE), Aarhus University from the original reported data. For a more detailed description of the spreadsheets and included data, please scroll down to lineage.

This online application serves as a joint regional tool to identify low risk routes for IMO Ballast Water Convention exemptions (A-4) for HELCOM and OSPAR marine areas. Data are provided following the port survey protocol described in the HELCOM/OSPAR Joint Harmonised Procedure. https://helcom.fi/wp-content/uploads/2021/01/HELCOM-OSPAR-Joint-Harmonized-Procedure-for-BWMC-A-4-exemptions_2020.pdf The database contains environmental data recorded from OSPAR and HELCOM ports as well as species observations and applies World Register of Marine Species (WoRMS) taxonomy. The data model used is based on Darwin Core format, with required extensions added. The database can be searched, viewed and downloaded using a specific web application. The whole database can be downloaded as a zipped ESRI File geodatabase. The HELCOM/OSPAR Ballast Water Exemptions Decision Support Tool was further developed in the EU INTERREG Baltic Sea Region project COMPLETE, following work developed with funding through the HELCOM ALIENS 2 and 3 and BALSAM projects by the HELCOM Secretariat and Germany (BSH/Brockmann consult). The data contained in the database are resulting from various sources and contains also historical legacy data from old projects. Main sources are listed below: - HELCOM and OSPAR countries national projects - HELCOM ALIENS 2 - HELCOM ALIENS 3 - HELCOM BALSAM

The aim of HELCOM Biodiversity database is to collate all available species observation data made available by HELCOM Contracting Parties. The database contains +1M species observations and applies World Register of Marine Species (WoRMS) taxonomy. The data model used is based on Darwin Core format, with required extensions added. Species observations are mostly pointwise observations, but also gridded observations are included for some species. The database can be searched, viewed and downloaded using a specific web application. The whole database can be downloaded as a zipped ESRI File geodatabase. Disclaimer: Data in the database is stemming from various sources. While there has been considerable quality assurance efforts, the accuracy of data can not be quaranteed. Note that HELCOM Contracting Parties report open sea observations on zoobenthos, zooplanton and phytoplantkon to ICES Dome database and those observations are not included in HELCOM Biodiversity database. Biodiversity database attribute description is available below: attrribute; type (description): origin_of_data_collection; Text (Origin of data call / data collection project from which the observation has been obtained) aphiaID; Number (WoRMS AphiaID or species which is used to retrieve taxonomy information from WoRMS webservice) scientific_name; Text (Scientific name of the species as reported in source data) taxonomical_status; Text (Taxonomical status of Scientific name according to WoRMS) accepted_name; Text (Accepted name of the AphiaID according to WoRMS) species_group; Text (Species group of the AphiaID) synonyms; Text (Synonyms of AphiaID according to WoRMS) data_source; Text (Data provider organization) subunit; Text (Further explanation about any subunits or groups of the institution that are responsible for the data submission.) field_number; Text (unique identifier, number or text or combination, created at collection time to identify each observation, e.g. sample numbers) count_value; Number: Number of individuals: Count value (integer) count_unit; Text: Unit of count value count_estimate; Codelist: Total, Modelled, Maximum, Minimum, C-POD, Null. If not available, use Null count_method; Text. Count method as free text decimal_latitude; Number (Latitude coordinate of observation location in WGS84 decimal degrees, 6 decimals) decimal_longitude; Number (Longitude coordinate of observation location in WGS84 decimal degrees, 6 decimals) coordinate_uncertainty; Number (The horizontal distance (in meters) from the given decimal_latitude and decimal_longitude describing the smallest circle containing the whole of the Location. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Zero is not a valid value for this term. polygon_id_1x1km; ID of the polygon to which observations are within (EEA grid) polygon_id_2x2km; ID of the polygon to which observations are within (EEA grid) polygon_id_5x5km; ID of the polygon to which observations are within (EEA grid) polygon_id_10x10km; ID of the polygon to which observations are within (EEA grid) data_generalization; Text (Codelist: no data generalization, data aggregation as grid (1x1km), data aggregation as grid (2x2km), data aggregation as grid (5x5km), data aggregation as grid (10x10km), Other, please specify in the "Notes" section) year_collected; Number (Year as in YYYY) month_collected; Number (Month as in MM) day_collected; Number (Day as in DD) start_day_collected; Number (Year as in YYYY, used if not a date for sampling but rather a time frame exists. Starting year for that sampling period) start_month_collected; Number (Month as in MM, used if not a date for sampling but rather a time frame exists. Starting month for that sampling period) start_day_collected; Number (Day as in DD, used if not a date for sampling but rather a time frame exists. Starting day for that sampling period) end_year_collected; Number (Year as in YYYY, used if not a date for sampling but rather a time frame exists. Last year for that sampling period) end_month_collected; Number (Month as in MM, used if not a date for sampling but rather a time frame exists. Last month for that sampling period) end_day_collected; Number (Day as in DD, used if not a date for sampling but rather a time frame exists. Last day for that sampling period) notes; Text (Any other information) citation; Text. If specific citation should be used for observation, it should be described here restriction; Yes/No (No, if no restrictions on use. Yes, if any information restricted for this observation, that cannot be shared freely) restriction_description; Free text (If Restriction=Yes, then describe the reason and type of restriction) information_withheld; Text (Codelist: no information withheld, Location information aggregated, Location information aggregated and more detailed information can be asked from the Institution, Other, please specify in the "Notes" section