Quarters of Helsinki

Open data API in a single place

Provided by Helsingin kaupunkiympäristön toimiala

Get early access to Quarters of Helsinki API!

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

Dataset information

Country of origin
Updated
Created
2020.01.27
Available languages
English
Keywords
käyttöoikeusalueet, maankäytön suunnittelu, aluerakenne, maankäytön ohjaus, rakennusoikeus, rakentaminen, korttelit, aluesuunnittelu, kaavayksikkö, tontit, kaavahakemisto, ajantasa-asemakaava, kaavasuunnittelu, maankäyttö, kvarter, quaters, talot, asemakaavat, kaavayksiköt, kiinteistöt, kaupunkisuunnittelu
Quality scoring

Dataset description

The Helsinki Blocks dataset is made up of [planning units] maintained by City Measurement Services (https://hri.fi/data/fi/dataset/helsingin-planning units) with the status "Valid" and the characteristics of the municipal register. Blocks are formed by combining geometries with the same block identifier. The planning unit is the smallest unit reserved for a specific purpose in the local detailed plan. The use of the data has been reclassified for data protection reasons. The material can also be downloaded in several different formats, including: JSON, KML, GIF, Tiff, GeoTiff, JPEG, PNG, CSV, Esri Shape. The available formats can always be found with the [GetCapabilities](https://kartta.hel.fi/ws/geoserver/avoindata/wfs?request=GetCapabilities) survey. Administrator: City of Helsinki, Urban Environment Division, Services and permits service entity, City surveying services **Preview of data in the map.hel.fi service:** - [kartta.hel.fi](https://kartta.hel.fi/link/dAVpee) **Coordination system(s):** - ETRS-GK25 (EPSG:3879). Maintenance coordinate system. The data can also be projected to other coordinate systems. Other possible coordinate systems can be found in the GetCapabilities document of the interface service. **Addresses for cross-border services:** - WFS interface: [https://kartta.hel.fi/ws/geoserver/avoindata/wfs](https://kartta.hel.fi/ws/geoserver/avoindata/wfs?request=getCapabilities) **Published levels:** - Helsinki_block **Helsinki_block level characteristics** - id (int): Id of the material. Reliable, comprehensive information. - block code (string): Identifier of the block. Reliable, comprehensive information. - municipality (string): Municipality. Reliable, comprehensive information. - Location (string): Location area. Reliable, comprehensive information. - group (string): The group. Reliable, comprehensive information. - area_kvyks (decimal): The total register area of the block. This may differ from the calculated area of the spatial object. Reliable, comprehensively valid information. - schematics_lkm (int): Number of planning units forming the block. Reliable, comprehensively valid information. - building rights (decimal): The building right summed up in the block. - use categories (string): Uses in the block as a list according to the generalized classification. The classification is based on the same classification as HSY's SeutuRamava. The purposes of use are not those set out in the formula, but generalised information about them. - name_finnish (string): The name of the block in Finnish. - name_Swedish (string): The name of the block in Swedish. - data owner (string): Owner of the material. - to the advising_service on (date): Date of storage of the information service (yyyy-mm-dd). - geom (gml:GeometryPropertyType): The geometry of the object.
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