Helsinki sub-universal plans

Open data API in a single place

Provided by Helsingin kaupunkiympäristön toimiala

Get early access to Helsinki sub-universal plans API!

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

Dataset information

Country of origin
Updated
Created
2017.11.28
Available languages
English
Keywords
kaavoitus, kiinteistöt, osayleiskaava, yleiskaava, kaavat, aluesuunnittelu
Quality scoring

Dataset description

A component master plan supplements or amends the master plan for the entire municipality. The master plan is a general plan of the organisation of land use and traffic that covers the whole city. The master plan guides city planning. **Component master plans of Helsinki** - East Jollas component master plan 10541 - Jätkäsaari 11350 - Central Pasila 11356 - King's oak 11640 - Sörnäistenranta and Hermanninranta 11650 - Kruunuvuorenranta component master plan 11756 - Meri-Rastila western shore component master plan 12155 - Koivusaari component master plan 12180 - Component master plan of eastern part of Pohjois-Haaga 12199 - Hernesaari component master plan 12385 The purpose of the master plan is to provide general guidance on the community structure and land use of a municipality or part of it and to coordinate operations. The master plan sets out the principles of the desired development and indicates the necessary areas for detailed city planning and other planning as well as for construction and other land use. The master plan for the whole municipality forms the basis for the urgency of planning work. The planning programme is checked annually in conjunction with the planning review. The master plan can also be drawn up in stages or by city sub-district as a so-called component master plan, which guides land use and construction in a given area. The master plan may be determined to be binding or indicative. The municipality is responsible for the preparation of the master plan. The plan is approved by the municipal council. **Previewing the data in the map.hel.fi service:** - [kartta.hel.fi](https://kartta.hel.fi/link/dB2ji7) **Coordinate systems:** - Maintained in ETRS-GK25 (EPSG:3879), can be projected to other coordinate systems. See GetCapabilities query for other possible coordinate systems. **API addresses:** - WMS API: [https://kartta.hel.fi/ws/geoserver/avoindata/wms](https://kartta.hel.fi/ws/geoserver/avoindata/wms?request=getCapabilities) - WFS API: [https://kartta.hel.fi/ws/geoserver/avoindata/wfs](https://kartta.hel.fi/ws/geoserver/avoindata/wfs?request=getCapabilities) **Layers:** WMS: - Partial master plan_10541 - Partial master plan_11350 - Partial master plan_11356 - Partial master plan_11640 - Partial master plan_11650 - Partial master plan_11756 - Partial master plan_12155 - Partial master plan_12180 - Partial master plan_12199 - Partial master plan_12385 WFS: - Master Plan Directory_area **Sub-Master Plan Directory_Region: attributes, data types and translation:** - id (int): unique identifier - target name (string) - the symbol (string): unique identifier for the plan - name (string): name for the area - state of being (int) - Date of creation (date): date, when the plan was created - Date of editing (date): date, when the plan was modified - data owner (string): owner of the data - to the advising_service on (date): date, when the data was updated the last time
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