Tourist traffic stops and parking places in Helsinki

Open data API in a single place

Provided by Helsingin kaupunkiympäristön toimiala

Get early access to Tourist traffic stops and parking places in Helsinki API!

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

Dataset information

Country of origin
Updated
Created
2019.01.23
Available languages
English
Keywords
matkailuliikenne, parking, pysäköintipaikat, traffic, pysäkit, parkering, trafik, parkplatser, parking spaces, bus stops, liikenne, pysäköinti
Quality scoring

Dataset description

The data includes the decided tourist traffic stops and parking places in the inner city area. The traffic signs must be checked for permitted parking spaces. 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 can be found in [WFS search guide](https://kartta.hel.fi/avoindata/dokumentit/Prosessi_Tyoohje_kyselypalvelut_kaytto_ulkoverkko.pdf) (in Finnish). **Previewing the data in the map.hel.fi service:** - [kartta.hel.fi](https://kartta.hel.fi/link/dB1xsT) **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:** - Tourist traffic_stops_point - Tourist Traffic_Places_Point **Attributes of the Matkailuliikenne_pysakit_piste layer:** - id (int): Unique identifier of the feature. - p_number (string): Unique number of the stop. - p_name (string): Name of the stop. - additional information (string): Any additional information about the stop. - time (string): Time limit for parking or stopping. - season (string): Period of validity of the stop. - p_name_en (string): Name of the stop in English. - lisati_eng (string): Any additional information about the stop in English. - p_name_ven (string): Name of the stop in Russian. - lisati_ven (string): Any additional information about the stop in Russian. - Time_ven (string): Time limit for parking or stopping in Russian. - data owner (string): Data owner. - to the advising_service on (date): Information service record date (yyyy-mm-dd). - geom (GeometryPropertyType): Geometry of the feature. **Attributes of the Matkailuliikenne_pysakointipaikat_piste layer:** - id (int): Identification of the feature. - letter p_string: Unique letter of the parking place. - p_name (string): Name of the parking place. - additional information (string): Any additional information about the parking place. - time (string): Information about the time limit at the parking place. - season (string): Period of validity of the parking place. - p_name_en (string): Name of the stop in English. - lisati_en (string): Any additional information about the parking place in English. - time_en (string): Information about the time limit at the parking place in English. - p_name_ven (string): Name of the stop in Russian. - lisati_ven (string): Any additional information about the parking place in Russian. - Time_ven (string): Information about the time limit at the parking place in Russian. - data owner (string): Data owner. - to the advising_service on (date): Information service record date (yyyy-mm-dd). - 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