City of Helsinki Master Plan 2002

Open data API in a single place

Provided by Helsingin kaupunkiympäristön toimiala

Get early access to City of Helsinki Master Plan 2002 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
kaavat, aluesuunnittelu, master plan, general plan, kaavoitus, kiinteistöt, planning, yleiskaava
Quality scoring

Dataset description

The General Plan 2002 is a general plan for the land use and traffic organisation of the City of Helsinki, covering the entire city. The master plan is drawn up in Helsinki approximately every ten years and it guides town planning. The master plan may be supplemented or amended by a sub-master plan drawn up for a smaller area. The current master plan for Helsinki (General Plan 2002) entered into force on 19 January 2007, with the exception of the area of Malmi Airport. In addition, the Helsinki Underground Master Plan (2009) and a number of sub-master plans are in force in the city area. The purpose of the master plan is to steer the community structure and land use of the municipality or part of it in general and to coordinate activities. The master plan sets out the principles of the desired development and designates the necessary areas as the basis for detailed planning and other planning as well as construction and other land use. The master plan for the entire municipality is the basis for the order of urgency of planning work. The zoning plan is reviewed annually in connection with the zoning review. A master plan can also be drawn up in stages or by sub-areas as a so-called sub-master plan to guide land use and construction in a specific area. A master plan may be prescribed as binding or indicative. The municipality is responsible for drawing up the master plan. The plan is approved by the municipal council. Helsinki's current General Plan 2002 became legally valid on 19 January 2007, with the exception of the area of Malmi Airport. The first land use master plan for Helsinki was drawn up by the town plan architect **Bertel Jung** in 1911. Helsinki's next master plan plan was the *Pro Helsingfors* plan from 1918, drawn up in collaboration between **Eliel Saarinen** and Bertel Jung. In 1932, a master plan was adopted, which was a master plan-level plan. The current master plan originated from the 1960 master plan, which was the first master plan to cover the entire city after the wars. Its preparation began in 1953. The next master plan proposal was published in April 1970, and the master plan was supplemented with a partial master plan for the inner city approved in 1976. The 1992 master plan consisted of three parts: the development picture, the master plan itself and the plan for the implementation of the master plan. The scale of the data is 1:40,000. **Preview of data in the map.hel.fi service:** - [General](https://kartta.hel.fi/link/dC1oyq) - [General information in Swedish](https://kartta.hel.fi/link/dC6ide) **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. **Address of the interface service:** - WMS interface: [https://kartta.hel.fi/ws/geoserver/avoindata/wms](https://kartta.hel.fi/ws/geoserver/avoindata/wms?request=getCapabilities) **Published levels:** - General plan_2002 - Master Plan_2002_Swedish
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