Helsinki Master Plan 2002

Open data API in a single place

Provided by Finnish Digital Agency / Population Register Centre

Get early access to 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.29
Available languages
Finnish
Keywords
yleiskaava, kiinteistöt, kaavoitus, aluesuunnittelu, kaavat
Quality scoring
250

Dataset description

The General Plan 2002 is a general plan for the organisation of land use and transport by the City of Helsinki, which covers the entire city. The master plan is drawn up in Helsinki every ten years and it guides the town planning. The master plan may be supplemented or modified by a sub-general plan for a smaller area. Helsinki’s current master plan (Yleiskaava 2002) entered into force on 19 January 2007, with the exception of the Malmi Airport area. In addition, Helsinki’s underground master plan (2009) and a number of sub-general plans are in force in the city area. The purpose of the master plan is to guide the municipal structure and land use of a municipality or part thereof in general and to coordinate operations. The master plan sets out the principles of the intended development and identifies the necessary areas as the basis for detailed planning and other planning, construction and other land use. The master plan for the whole municipality is the basis for the order of urgency of planning work. The planning plan is reviewed annually in conjunction with the zoning review. The master plan can also be drawn up in phases or sub-regions as a ‘sub-general plan’ to guide land use and construction in a specific area. The 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 final on 19 January 2007, with the exception of Malmi Airport area. The first land use master plan for Helsinki was drawn up by the city plan architect **Bertel Jung** in 1911. Helsinki’s next master plan was the 1918 “Pro Helsingfors*” plan prepared by Eliel Saarinen** and Bertel Jung. In 1932, a general plan was adopted, which was a general plan. A master plan similar to the current one originated in the 1960 Master Plan, which was the first master plan covering the whole 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 by a sub-general plan for the inner city adopted in 1976. The 1992 master plan consisted of three parts: the development picture, the actual master plan and the plan for the implementation of the master plan. (See http://www.yleiskaava.fi/2012/vuosisadan_yleiskaavat/). The scale of the data is 1:40 000. ** Coordinate system(s):** — ETRS-GK25 (EPSG:3879). Maintenance coordinates. The data can also be projected in other coordinate systems. Other possible coordinate systems can be found in the GetCapabilities document of the interface service. **Interface service address:** — 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 — General Plan_2002_Swedish
Build on reliable and scalable technology
Revolgy LogoAmazon Web Services LogoGoogle Cloud Logo
FAQ

Frequently Asked Questions

Some basic informations about API Store ®.

Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.

Didn't find the API you need?

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

API Store provides access to European Open Data via scalable and reliable REST API interface.
Copyright © 2024. Made with ♥ by Apitalks