Tampereen herkät vesistöt (viherkerroin)

KUVAUS Herkät vesistöt, joiden rajaus on luotu Viherkertoimen käyttöä varten. Viherkerroinmenetelmä on ekologinen suunnittelutyökalu tonttien viherpinta-alan arviointiin, minkä avulla etsitään vaihtoehtoisia ratkaisutapoja kaupunkivihreän lisäämiseen sekä hulevesien hallintaan. Määritellyillä alueilla huleveden laadulliseen hallintaan on kiinnitettävä erityistä huomiota. Aineisto perustuu hulevesiohjelmassa määritettyihin osavaluma-alueisiin, joiden avulla aineisto on rajattu. Aineisto on päivitetty 12/2023 vastaamaan uuden hulevesiohjelman valuma-alueita. Hulevesiohjelmaan liittyvän aineiston lisäksi rajausta on arvioitu asiantuntijoiden toimesta. KATTAVUUS Koko kaupunki PÄIVITYS Aineisto on laadittu viherkertoimen käyttöön ja päivittyy tiedon tarkentuessa. YLLÄPITOSOVELLUS Aineisto on tallennettu PostgreSQL-tietokantaan ja ylläpidetään QGIS-ympäristössä. KOORDINAATISTOJÄRJESTELMÄ Aineisto tallennetaan ETRS-GK24 (EPSG:3878) tasokoordinaattijärjestelmässä. GEOMETRIA Aluemainen SAATAVUUS Aineisto on saatavilla WFS- ja WMS2-rajapinnoilta. JULKISUUS, TIETOSUOJA. Avoin aineisto. VASTUUTAHO Ympäristönsuojeluyksikkö (ymparistonsuojelu@tampere.fi) KENTÄT vesisto: vesistöalueen nimi

Shipping accidents

This dataset contains the ship accidents in the Baltic Sea during the period 1989 to end of 2023. It is constructed from the annual data collected by HELCOM Contracting Parties on ship accidents in the Baltic Sea and starting from 2019 from EMSA EMCIP Database extraction (for those Contracting Parties that are member of the EU). The accident data has been compiled by the HELCOM Secretariat and EMSA. According to the decision of the HELCOM SEA 2/2001 shipping accident data compilation will include only so-called conventional ships according to the Regulation 5, Annex I of MARPOL 73/78 - any oil tanker of 150 GT and above and any other ships of 400 GT and above which are engaged in voyages to ports or offshore terminals under the jurisdiction of other Parties to the Convention. According to the agreed procedure all accidents (including but not limited to grounding, collision with other vessel or contact with fixed structures (offshore installations, wrecks, etc.), disabled vessel (e.g. machinery and/or structure failure), fire, explosions, etc.), which took place in territorial seas or EEZ of the Contracting Party irrespectively if there was pollution or not, are reported. The dataset contains the following information: Unique_ID = An unique identifier consisting of 4 digit running number and the year of the accident Country Year Date = Date (dd/mm/yyyy) Time = Time of the accident (hh:mm) Location = Location of the accident (open sea / port / port approach, from 2019 -> open sea / port) Acc_Type = Type of accident Colli_Type = Type of collision / contact (with vessel / object) Acc_Detail = More information on the accident CauseDetai = Details on the accident cause Assistance = Assistance after the accident Offence = Offence against Rule Damage = Damage to the ship HumanEleme = Occurrence / Reason of human error IceCondit = Ice conditions CrewIceTra = Crew trained for ice conditions Pollution = Pollution (Yes/No) Pollu_m3 = Pollution in m3 Pollu_t = Pollution in tonnes Pollu_Type = Type of pollution RespAction = Response actions after the accident Cargo_Type = Type of cargo Ship1_Name = Ship 1 identification (Not published after 2018) Sh1_Categ = Ship 1 type (according to AIS category) Sh1_Type = Ship 1 more detail ship type category Sh1_Hull = Ship 1 hull construction Sh1Size_gt = Ship 1 GT Sh1Sizedwt = Ship 1 DWT Sh1Draug_m = Ship 1 draught in meters / category Cause_Sh1 = Cause of accidents from ship 1 Pilot_Sh1 = Presence of pilot on ship 1 Ship2_Name = Ship 2 identification (Not published after 2018) Sh2_Categ = Ship 2 type (according to AIS category) Sh2_Type = Ship 2 more detail ship type category Sh2_Hull = Ship 2 hull construction Sh2Size_gt = Ship 2 GT Sh2Sizedwt = Ship 2 DWT Sh2Draug_m = Ship 2 draught in meters / category Cause_Sh2 = Cause of accidents from ship 2 Pilot_Sh2 = Presence of pilot on ship 2 Add_Info = Additional information Latitude = Latitude (decimal degrees) Longitude = Longitude (decimal degrees) For more information about shipping accidents in the Baltic Sea, see the HELCOM annual reports: https://helcom.fi/helcom-at-work/publications/ https://helcom.fi/media/publications/HELCOM-report-on-Shipping-accidents-in-the-Baltic-Sea-2019-211207-FINAL.pdf

Baltic Sea Impact Index (BSII)

The Baltic Sea Impact Index is an assessment component that describes the potential cumulative burden on the environment in different parts of the Baltic Sea. The BSII is based on georeferenced datasets of human activities (36 datasets), pressures (18 datasets) and ecosystem components (36 datasets), and on sensitivity estimates of ecosystem components (so-called sensitivity scores) that combine the pressure and ecosystem component layers, created in <a href="http://www.helcom.fi/helcom-at-work/projects/holas-ii" target="_blank">HOLAS II</a> project. Cumulative impacts are calculated for each assessment unit (1 km2 grid cells) by summing all pressures occurring in the unit for each ecosystem component. Highest impacts are found from the cells where both are abundant, but high impacts can be caused also by a single pressure if there are diverse and sensitive habitats in the grid cell. All data sets and methodologies used in the index calculations are approved by all HELCOM Contracting Parties in review and acceptance processes. This data set covers the time period 2011-2016. Please scroll down to "Lineage" and visit <a href="http://stateofthebalticsea.helcom.fi/cumulative-impacts/" target="_blank">State of the Baltic Sea website</a> for more info.

Isotope data of Finnish bedrock

The database consists of three components: "Published age determination”, ”Published Sm-Nd isotope data" and "Pb isotope data on galena". The "Published age determination" database is based on age determinations, which comprise predominantly U-Pb zircon data produced at the Geological Survey of Finland since 1960’s. For igneous rocks the age register contains radiometric ages mostly interpreted as primary ages. The information given consists of location data, rock type, method, mineral analyzed, age results, comments and references. "Published Sm-Nd isotope data" comprise Sm-Nd data procuded at GTK since 1981, which mostly are used to constrain the origin of crust. "Pb isotope data on galena" gives results produced at GTK since 1970's, and include also previously unpublished data.

EMODnet Seabed substrate 1:1 000 000 – Europe

The EMODnet (European Marine Observation and Data network) Geology project (http://www.emodnet-geology.eu/) collects and harmonizes marine geological data from the European sea areas to support decisionmaking and sustainable marine spatial planning. The partnership includes 39 marine organizations from 30 countries. The partners, mainly from the marine departments of the geological surveys of Europe (through the Association of European Geological Surveys- EuroGeoSurveys), have assembled marine geological information at a scale of 1:1 000 000 from all European sea areas (e.g. the White Sea, Baltic Sea, Barents Sea, the Iberian Coast, and the Mediterranean Sea within EU waters). This data includes the EMODnet seabed substrate map at a scale of 1:1 000 000 from the European marine areas. Traditionally, European countries have conducted their marine geological surveys according to their own national standards and classified substrates on the grounds of their national classification schemes. These national classifications are harmonized into a shared EMODnet schema using Folk's sediment triangle with a hierarchy of 16, 7 and 5 substrate classes. The data describes the seabed substrate from the uppermost 30 cm of the sediment column. In cases, the data has been generalized into a target scale (1:1 000 000). The smallest cartographic unit within the data is 4 km2. Further information about the EMODnetGeology project is available on the portal (http://www.emodnet-geology.eu/).

Integrated biodiversity status assessment - fish 2018

This dataset represents the Integrated biodiversity status assessment for fish used in State of the Baltic Sea – Second HELCOM holistic assessment 2011-2016. Status is shown in five categories based on the integrated assessment scores obtained in the BEAT tool. Biological Quality ratios (BQR) above 0.6 correspond to good status. The assessment is based on core indicators of coastal fish in coastal areas, and on internationally assessed commercial fish in the open sea. The open sea assessment includes fishing mortality and spawning stock biomass as an average over 2011–2016. Open sea results are given by ICES subdivisions, and are not shown where they overlap with coastal areas. Coastal areas results are given in HELCOM Assessment unit Scale 3 (Division of the Baltic Sea into 17 sub-basins and further division into coastal and off-shore areas) Attribute information: "COUNTRY" = name of the country / opensea "Name" = Name of the coastal assessment unit, scale 3 (empty for ICES open sea units) "HELCOM_ID" = ID of the HELCOM scale 3 assessment unit (empty for ICES open sea units) "EcoystemC" = Ecosystem component analyzed "BQR" = Biological Quality Ratio "Conf" = Confidence (0-1, higher values mean higher confidence) "Total_indi" = Number of HELCOM core indicators included (coastal assessment units) "F__of_area = % of area assessed "D1C2" = MSFD descriptor 1 criteria 2 "Number_of" = Number of open sea species included "Confidence" = Confidence of the assessment "BQR_Demer" = Demersal Biological Quality Ratio "F_spec_Deme" = Number of demersal species included "Conf_Demer" = Confidence for demersal species "BQR_Pelagi" = Pelagic Biological Quality Ratio "F_specPela" = Number of pelagic species included "Conf_Pelag" = Confidence for pelagic species "ICES_SD" = ICES Subdivision number "STATUS" = Integrated status category (0-0.2 = not good (lowest score), 0.2-0.4 = not good (lower score), 0.4-0.6 = not good (low score), 0.6-0.8 = good (high score, 0.8-1.0 = good (highest score))

Air Traffic Network

Air traffic network-product is a link-knot routing dataset compliant with INSPIRE requirements. It includes f.ex. flight routes and aerodromes. Data shall not be used for operational flight activities or flight planning. INSPIRE Air Traffic Network-product includes spatial information of air traffic network in accordance with the INSPIRE Directive. The data has been retrieved from the EAD database maintained by Eurocontrol. Information is updated regularly but is not constantly up to date. Data can be used for purposes that are in accordance with the INSPIRE Directive, but shall not be used for operational flight activities or flight planning. ANS Finland www.ais.fi –site provides information for operational flight activities or flight planning Available layers Aerodrome Node: Node located at the aerodrome reference point of an airport/heliport, which is used to represent it in a simplified way.DEFINITION Aerodrome Reference Point (ARP): The designated geographical location of an aerodrome, located near the initial or planned geometric centre of the aerodrome and normally remaining where originally established [AIXM3.3].DEFINITION Airport/heliport: A defined area on land or water (including any buildings, installations and equipment) intended to be used either wholly or in part for the arrival, departure and surface movement of aircraft/helicopters [AIXM5.0]. Air Route Link: A portion of a route to be flown usually without an intermediate stop, as defined by two consecutive significant points Air Space Area: A defined volume in the air, described as horizontal projection with vertical limits. Designated Point: A geographical location not marked by the site of a radio navigation aid, used in defining an ATS route, the flight path of an aircraft or for other navigation or ATS purposes. Instrument Approach Procedure: A series of predetermined manoeuvres by reference to flight instruments with specified protection from obstacles from the initial approach fix, or where applicable, from the beginning of a defined arrival route to a point from which a landing can be completed and thereafter, if a landing is not completed, to a position at which holding or en route obstacle clearance criteria apply. Navaid: One or more Navaid Equipments providing navigation services.DEFINITION Navaid equipment: A physical navaid equipment like VOR, DME, localizer, TACAN or etc. Procedure Link: A series of predetermined manoeuvres with specified protection from obstacles. Runway Area: A defined rectangular area on a land aerodrome/heliport prepared for the landing and take-off of aircraft. Runway Centerline Point: An operationally significant position on the center line of a runway direction. Standard Instrument Arrival: A designated instrument flight rule (IFR) arrival route linking a significant point, normally on an ATS route, with a point from which a published instrument approach procedure can be commenced. Standard Instrument Departure: A designated instrument flight rule (IFR) departure route linking the aerodrome or a specific runway of the aerodrome with a specified significant point, normally on a designated ATS route, at which the en-route phase of a flight commences. Surface Composition: Runway surface material CTR (Not INSPIRE): A control zone (CTR) is a block of Controlled Airspace extending from the surface of the earth to a specified upper limit.

HELCOM MPAs

This dataset contains borders of the HELCOM MPAs (former Baltic Sea Protected Areas (BSPAs). The dataset has been compiled from data submitted by HELCOM Contracting Parties. It includes the borders of designated HELCOM MPAs stored in the http://mpas.helcom.fi. The designation is based on the HELCOM Recommendation 15/5 (1994). The dataset displays all designated or managed MPAs as officially reported to HELCOM by the respective Contracting Party. The latest related HELCOM publication based on MPA related data is http://www.helcom.fi/Lists/Publications/BSEP148.pdf The dataset contains the following information: MPA_ID: Unique ID of the MPA as used in HELCOM Marine Protected Areas database Name: Name of the MPA Country: Country where MPA is located Site_link: Direct link to site's fact sheet in the http://mpas.helcom.fi where additional information is available MPA_status: Management status of the MPA Date_est: Establishment date of the MPA Year_est: Establishment year of the MPA

EMODnet Seabed substrate 1:45 000 – Europe

The EMODnet (European Marine Observation and Data network) Geology project collects and harmonizes marine geological data from the European sea areas to support decision making and sustainable marine spatial planning. The partnership includes 39 marine organizations from 30 countries. The partners, mainly from the marine departments of the geological surveys of Europe (through the Association of European Geological Surveys-EuroGeoSurveys), have assembled marine geological information at various scales from all European sea areas (e.g. the White Sea, Baltic Sea, Barents Sea, the Iberian Coast, and the Mediterranean Sea within EU waters). This dataset includes EMODnet seabed substrate maps at a scale of 1:45 000 from the European marine areas. Traditionally, European countries have conducted their marine geological surveys according to their own national standards and classified substrates on the grounds of their national classification schemes. These national classifications are harmonised into a shared EMODnet schema using Folk's sediment triangle with a hierarchy of 16, 7 and 5 substrate classes. The data describes the seabed substrate from the uppermost 30 cm of the sediment column. Further information about the EMODnet Geology project is available on the portal (http://www.emodnet-geology.eu/).

Potential cumulative impacts on benthic habitats

Potential cumulative impacts on benthic habitats is based on the same method than <a href="http://metadata.helcom.fi/geonetwork/srv/eng/catalog.search#/metadata/9477be37-94a9-4201-824a-f079bc27d097" target="_blank">Baltic Sea Impact Index</a>, but is focused on physical pressures and benthic habitats. The dataset was created based on separate analysis for potential cumulative impacts on only the benthic habitats, as these are particularly affected by physical pressures. In this case the evaluation was based on pressure layers representing <a href="http://metadata.helcom.fi/geonetwork/srv/eng/catalog.search#/metadata/ea0ef0fa-0517-40a9-866a-ce22b8948c88" target="_blank">physical loss</a> and <a href="http://metadata.helcom.fi/geonetwork/srv/eng/catalog.search#/metadata/05e325f3-bc30-44a0-8f0b-995464011c82" target="_blank">physical disturbance</a>, combined with information on the distribution of eight broad benthic habitat types and five habitat-forming species (<a href="http://metadata.helcom.fi/geonetwork/srv/eng/catalog.search#/metadata/363cb353-46da-43f4-9906-7324738fe2c3" target="_blank">Furcellaria lumbricalis</a>, <a href="http://metadata.helcom.fi/geonetwork/srv/eng/catalog.search#/metadata/f9cc7b2c-4080-4b19-8c38-cac87955cb91" target="_blank">Mytilus edulis</a>, <a href="http://metadata.helcom.fi/geonetwork/srv/eng/catalog.search#/metadata/264ed572-403c-43bd-9707-345de8b9503c" target="_blank"> Fucus sp.</a>, <a href="http://metadata.helcom.fi/geonetwork/srv/eng/catalog.search#/metadata/822ddece-d96a-4036-9ad8-c4b599776eca" target="_blank">Charophytes</a> and <a href="http://metadata.helcom.fi/geonetwork/srv/eng/catalog.search#/metadata/ca327bb1-d3cb-46c2-8316-f5f62f889090" target="_blank">Zostera marina</a>). The potential cumulative impacts has been estimated based on currently best available data, but spatial and temporal gaps may occur in underlying datasets. Please scroll down to "Lineage" and visit <a href="http://stateofthebalticsea.helcom.fi/cumulative-impacts/" target="_blank">State of the Baltic Sea website</a> for more info.