Helsinki Heat Vulnerability Index

Open data API in a single place

Provided by Helsingin kaupunginkanslia

Get early access to Helsinki Heat Vulnerability Index API!

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

Dataset information

Country of origin
Updated
Created
2022.12.08
Available languages
English
Keywords
lämpöhaavoittuvuus, heat vulnerability, lämpöherkkyys, lämpöaltistuminen
Quality scoring

Dataset description

This analysis evaluates the Helsinki Heat Vulnerability Index. Thermal vulnerability is a combination of exposure, sensitivity and adaptability. Heat exposure refers to very high temperatures in the city area. Earth surface temperatures from satellite data over a four-year period and data from local weather stations have been used to determine how often heat waves occur. Thermal sensitivity refers to the intensity of an individual's reaction at high temperatures. This depends on individual characteristics, such as age and health problems. In the analysis, this is taken into account by the population density of the elderly in different parts of the city. Adaptability refers to a city's system-level ability to cope with the effects of thermal events. In the adaptability analysis, data on urban vegetation and humidity are collected from satellites in the summer of 2021, as these have a major impact on urban thermal resilience. The smallest variable, i.e. subdivisions, of the statistical database [Series of regions](https://https://aluesarjat.fi/) has been used in the analysis. Areas entirely at sea have been excluded from the analysis. **Coordinate system used** - ETRS-GK25 (EPSG:3879) **Vector levels** - Urban Heat Vulnerability dataset of Helsinki, Finland **Raster levels** Urban Heat Adaptivity Index Urban Heat Exposure Index Urban Heat Impact Index Urban Heat Vulnerability Index **Attributes of vector levels and their descriptions** - "ID": District IDName: District Name - "TP": Total Population - "TP-AG1": Total Population: Age Group under 1 - "TP-AG2": Total Population: Age Group 1 to 6 - "TP-AG3": Total Population: Age Group 7 to 12 - "TP-AG4": Total Population: Age Group 13 to 15 - "TP-AG5": Total Population: Age Group over 64 - "Area": District Area (km2) - "HVP": Heat Vulnerable Population - "MARK": Urban Heat Sensitivity Index - "Avg-UHVI": Average Urban Heat Vulnerability Index (From Raster) - "Avg-UHII": Average Urban Heat Impact Index (From Raster) - "Avg-UHEI": Average Urban Heat Exposure Index (From Raster) - "Avg-UHAI": Average Urban Heat Adaptivity Index (From Raster) **Raster level source** - Landsat 8 Thermal Data obtained from the months of June, July and August for the years 2018, 2019, 2020, 2021 - Sentinel 2 Vegetation and Moisture Data obtained for the day 26.07.2021 **Other sources** - [Source of Weather Data for Helsinki from Finnish Meteorological Institute](https://en.ilmatieteenlaitos.fi/) - [Source of Population and their Age-Group Distribution Data of Helsinki from Greater Helsinki Open Statistical Databases](https://stat.hel.fi/pxweb/en/Aluesarjat/Aluesarjat__vrm__vaerak__pksoa/A03S_HKI_Vakiluku_aidinkieli.px/) - [Source of Landsat 8 Data](https://earthexplorer.usgs.gov/) - [Source of Sentinel 2 Data](https://scihub.copernicus.eu/) The analysis was done by Ecoten - Urban Comfort.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

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

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks