Open data

The Journey Planner (reittiopas.fi) APIs provide data related to routing, geocoding, map data and vehicle locations via a number of APIs. APIs available 

• Routing API, routing, route and timetable queries either via a GraphQL  API or a REST API
• Geocoding API, via Pelias REST API
• Map API, HSL's background map as a TMS service (Tile Map Service) and a number of public transport related point of interest (POI) layers (e.g. ticket sales points, city bike stations and Park & Ride sites) as Mapbox vectortile services.
• Real-time API, via GTFS-RT and MQTT feeds

More information : http://digitransit.fi

Public transport network data is updated daily from HSL's public transport register to the Journey Planner APIs (see below). OpenStreetMap data is also updated daily to the Journey Planner for the purposes of routing, geocoding and the background map (see below). The OpenStreetMap wiki contains a more detailed description of how the Digitransit Journey Planners utilize OpenStreetMap data.

Changes to the routing and geocoding are due to data loading procedures visible within a few (in optimal conditions two) days. In the background map these results can however, due to different cache settings, take up to a week before they are visible to users.

Data from HSL's public transport register is parsed into GTFS format daily. The data extraction includes all public transport routes that have a valid timetable. The window is three months from the moment the extraction is started. The latest GTFS package is available here.

The GTFS-RT APIs provide real-time data about service changes and disruptions, arrival time predictions and vehicle locations. More information : realtime.hsl.fi

Please note that real-time data is also available via the Journey Planner’s Real-time API

Data from OpenStreetMap is derived daily into HSL's journey planner into routing network, geocoding dataset and background maps. These data packages ini PBF-format can be found here.

OpenStreetMap wiki contains a more detailed description of how the HSL uses OpenStreetMap data.

The Origin–Destination (OD) data of city bike stations includes all journeys made by city bikes in Helsinki and Espoo. The data includes information about the origin and destination station, start and end times, distance (in meters) and duration (in seconds) of each journey.  Data is available starting from the 2016 season, either by month (csv) or for the full season (zip). The data is owned by City Bike Finland.

Monthly data (2016–2017, May–October) and (from 2018, April–October): dev.hsl.fi/citybikes/od-trips-[year]/[year]-[month].csv.  For example, "dev.hsl.fi/citybikes/od-trips-2021/2021-04.csv"

Annual data package: "dev.hsl.fi/citybikes/od-trips-[vuosi]/od-trips-[vuosi].zip". For example, "dev.hsl.fi/citybikes/od-trips-2021/od-trips-2021.zip"

HSL's bluetooth beacon REST API offers information about the beacons instaled. More information : https://hsldevcom.github.io/beacon_api/

HSL’s OpenMaaS API offers a sales interface for both single and season tickets available to all operators interested in transport services. More information : https://sales-api.hsl.fi/

Information about cancelled services is available in the Journey Planner APIs mentioned above, for example the routing API’s disruption-info and the real-time API’s service-alerts.

The Park & Ride Information System is no longer maintained by HSL.

Starting from 20.5.2024 the Park & Ride Information System (LIIPI in finnish) has expanded nationwide and it's maintained by the govermental Traffic Management Company Fintraffic.  The new service can be found at : https://parking.fintraffic.fi

Further info in finnish : https://www.fintraffic.fi/fi/fintraffic/liityntapysakoinnin-tietopalvelu-liipi

HSL's Louhin service contains data related to customer satisfaction (Asty Web) and passenger numbers on the Suomenlinna ferry (Lati Web).

The customer satisfaction survey data is updated with preliminary results about once a month in February–April and September–October.

The final results are updated into the database three times a year, whenever each survey period is completed (June, September and December). More information about the survey and the data: louhin@hsl.fi

Lati Web is updated constantly. Operators mainly enter ferry passenger numbers in the system each day. More information about the survey and the data: louhin@hsl.fi

The HSL GIS data portal provides a range of public transport related data. The available formats are Excel spreadsheet, Google KML, GeoJSON, ESRI shapefile and ArcGIS Rest API.

Data available (in Finnish):  

HSL’s stops
HSL’s stops by route
HSL’s routes
HSL’s intersections
HSL’s terminals
HSL sales points
HSL fare zones
Number of HSL bus and tram services
Number of boardings
HSL Park & Ride areas
HSL Park & Ride for cars
HSL Park & Ride for bikes
City bike stations in Helsinki and Espoo
City bike stations in Vantaa
Bicycle counts in Helsinki
Old Journey Planner POI database

The data in the GIS data portal is always a cross-section at a given point of time. The data has been gathered in particular for consultancy and research purposes and is designed to describe HSL's services, for example, the route network, in an optimal situation with as few diversions as possible.

Consequently, the extraction time is adjusted according to the public transport network status. The aim is to update the route network data at least once a year, at the end of summer service/start of autumn service in August. More regularly updated and more recent data is available via the Journey Planner and Park & Ride APIs. More information about the GIS data portal : paikkatieto@hsl.fi