Helsinki city plan directory map (station plan directory)

Open data API in a single place

Provided by Finnish Digital Agency / Population Register Centre

Get early access to Helsinki city plan directory map (station plan directory) API!

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

Dataset information

Country of origin
Updated
Created
2016.05.09
Available languages
Finnish
Keywords
kartat, asemakaavat, ajantasa-asemakaava, rakennusoikeus, maankäyttö, kaavasuunnittelu
Quality scoring
250

Dataset description

The detailed plans index map (detailed plans situation map) of Helsinki is a combined map of the city’s valid detailed plans. The index map describes the boundaries, numbers and dates of the detailed plans.The identifiers of the detailed plans are stored in such a way that each 1:2,000 sheet shows the number and date of the detailed plan. The data is available for download in several formats, including JSON, KML, CSV, Esri Shape and XML. Available formats can always be found under OutputFormat in the [GetCapabilities query](https://kartta.hel.fi/ws/geoserver/avoindata/wfs?request=GetCapabilities) for the service.More information and instructions in guidebook [Use](https://kartta.hel.fi/avoindata/dokumentit/Prosessi_Ty%C3%B6ohje_kyselypalveluiden_kaytto_ulkoverkko.pdf) (in Finnish). The area types in the data comprise the following area classifications: — Detailed plans; Under planning/Valid — Underground detailed plans; Under planning/Valid — Decisions of name changes; Under planning/Valid Name changes approved by the City Board (due to the Sipoo annexation) **Coordinate systems:** — Maintained in ETRS-GK25 (EPSG:3879), can be projected to other coordinate systems. See [GetCapabilities query](https://kartta.hel.fi/ws/geoserver/avoindata/wfs?request=GetCapabilities) for other possible coordinate systems. **API addresses:** WFS API: [https://kartta.hel.fi/ws/geoserver/avoindata/wfs](https://kartta.hel.fi/ws/geoserver/avoindata/wfs?request=getCapabilities) — WMS API: [https://kartta.hel.fi/ws/geoserver/avoindata/wms](https://kartta.hel.fi/ws/geoserver/avoindata/wms?request=getCapabilities) **Layers:** (Only WMS, all layers at the same time) — Formula directory_region_format_valid — Formula directory_area_format_buses — Formula directory_region_underground formula_valid — Formula directory_region_underground formula_buses — Formula Directory_area_name change path_validity — Formula Directory_region_name change formula_valid — Formula directory_reference lines — Formula directory_ID_format_valid — Formula directory_identity_format_buses — Formula directory_ID_underground formula_valid — Formula directory_identity_underground formula_buses — Formula Directory_ID_name change path_valid — Formula Directory_ID_name change formula_valid **Plans index: attributes, data types and their key and reliability attributes: the ID (int). Unique identifier of the feature. Reliable, comprehensively existing information. type (string). Type of detailed plan. Reliable, comprehensively existing information. — schematic code (string). Identification of the detailed plan. Reliable, comprehensively existing information. class (string). Class describes the status of the detailed plan. Reliable, comprehensively existing information. the starter (string). Status describes the history of the detailed plan. Reliable, comprehensively existing information. — surface area (decimal). Area covered by the detailed plan. The unit of area is square metre. Reliable, comprehensively existing information. the “string” system. The altitude system used in the detailed plan. In plans after 12/2012, the altitude system is mainly N2000, and in the older plans, it is NN. Reliable, comprehensively existing information. the location (string). Location area. Reliable, comprehensively existing information. — the date of acceptance (string). Date of approval of the detailed plan. Reliable, comprehensively existing information. — date of validity. Validity date of the detailed plan (yyyy-mm-dd). Reliable, comprehensively existing information. — date of entry into force. Date of entry into force of the detailed plan (yyyy-mm-dd). Reliable, comprehensively existing information. — confirmation date (date). Approval date of the detailed plan (yyyy-mm-dd). Reliable, comprehensively existing information. date of creation (date). Feature creation date (yyyy-mm-dd). Reliable, comprehensively existing information. — Modification Date (date). Previous editing date of the feature (yyyy-mm-dd). Reliable, comprehensively existing information. data owner (string). Owner of data. Reliable, comprehensively existing information. — updated to the information service (date). Stored in the information service, date (yyyy-mm-dd). Reliable, comprehensively existing information. — GEOM (GeometryPropertyType). Geometry of the feature.
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