Helsinki's goal-oriented green and recreation network map

Open data API in a single place

Provided by Helsingin kaupunkiympäristön toimiala

Get early access to Helsinki's goal-oriented green and recreation network map API!

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

Dataset information

Country of origin
Updated
Created
2022.01.03
Available languages
English
Keywords
green spaces, natur, nature, kasvillisuus, vegetation, viheralueet, luonto
Quality scoring

Dataset description

The prospective green and recreational network VISTRA includes the constituent parts of the Helsinki green and recreational network. These include the green fingers, the maritime blue palm, the green lines, the neighbourhood parks and other planned park areas as well as various routes and connections. The area of the map covers the entire land area of Helsinki. The southern sea area is not included in the map. The green fingers and recreational connections for Östersundom are prospective and are shown according to the unapproved 2016 planning situation. The map serves land use planning and the development of public areas and specifies the content of the Recreational and green network 2050 thematic map in the master plan. The map illustrates the development of the continuity of the green and recreational network. The map is based on the current situation and the projected future situation according to the land use priorities of the master plan. The purpose of the map is to serve as a starting point that will be specified in further planning, for example, when defining more precise locations of green connections or boundaries of parks in city planning. Read the reports that form the basis of the map: [the development plan for the green and recreational network of Helsinki (VISTRA part II)](https://www.hel.fi/hel2/ksv/julkaisut/aos_2016-2.pdf) (in Finnish), published in 2016, and [Green maritime Helsinki 2050 – VISTRA part I: starting points and vision](https://www.hel.fi/hel2/ksv/julkaisut/aos_2013-4.pdf) (also in Finnish), published in 2013. 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. **Previewing the data in the map.hel.fi service:** - [kartta.hel.fi](https://kartta.hel.fi/link/dzYZDM) **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: - Goal-oriented_viher_ja_recreational_network_VISTRA WFS: - Goal-oriented_viher_ja_recreational_network_VISTRA_region - Goal-oriented_viher_ja_recreational_network_VISTRA_point - Goal-oriented_viher_and_recreational_network_VISTRA_line **WFS: attributes, data types and translation:** - id/id (long): Unique identifier of the feature. - target type / feature type (string). Name of the feature type. - comment / comment (string). Any additional information related to the feature. - number / number (int): Additional information on the proposals. - name / name (string). Additional information on the proposals. - type / type (string). Additional information on the proposals. - data owner / data owner (string). Name of the data owner. - updated_to_information_service (date). Date of update of the data. - geom/geom (GeometryPropertyType). Geometry of the feature.
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