Spår-Jokern

Open data API in a single place

Provided by Helsingin kaupunkiympäristön toimiala

Get early access to Spår-Jokern API!

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

Dataset information

Country of origin
Updated
Created
2016.09.14
Available languages
English
Keywords
joukkoliikenne, pikaraitiotie, public transport, aluesuunnittelu, liikenne, traffic, suunnitelmat
Quality scoring

Dataset description

Planned Jokeri Light Rail line and stops from Itäkeskus in Helsinki to Keilaniemi in Espoo. Jokeri Light Rail is a light rail line planned to run between Itäkeskus and Keilaniemi. The geographic dataset shows the planned line and stops. In the traffic plans approved in autumn 2016, the line has in some places shifted 5-15 metres laterally. At the same time, stops may have been shifted as well. The dataset still shows the route streets and mainly the stops, but not necessarily whether the line runs on the side or in the middle of the street. The content of the data is the responsibility of the City of Helsinki Urban Environment Division/Traffic and Street Planning, and the supply of the data in the interface is the responsibility of the City of Helsinki Urban Environment Division/City Survey Services. The scale of the dataset is 1:1000 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:** - [Jokeri Light Rail areas and stops](https://kartta.hel.fi/link/dBEez1) - All Jokeri Light Rail map layers can be found on the website: [https://kartta.hel.fi/](https://kartta.hel.fi/?setlanguage=en) > Layers > Projects > Jokeri Light Rail **Coordinate system(s):** - 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:** - Jokeri railway line - RaideJokeri_stops **RaideJokeri_stops: attributes, data types and their explanation and reliability data in information services:** - id (int). Unique identifier of the feature. Reliable, comprehensively existing information. - project (string). Project name. Reliable, comprehensively existing information. - pysakki_name (string). Name of the stop in English. Reliable, comprehensively existing information. - to the paivittu_information service on (date). Information service record date (yyyy-mm-dd). Reliable, comprehensively existing information. - data owner (string). Data owner. Reliable, comprehensively existing information. - geom (GeometryPropertyType). Geometry of the feature. **RaideJokeri_railline: attributes, data types and their explanation and reliability data in information services:** - information service_id (int). Unique identifier of the feature. Reliable, comprehensively existing information. - project (string). Project name. Reliable, comprehensively existing information. - type (string). Type of feature. Reliable, comprehensively existing information. - to the paivittu_information service on (date). Information service record date (yyyy-mm-dd). Reliable, comprehensively existing information. - data owner (string). Data owner. Reliable, comprehensively existing information. - 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