The dataset shows number of unique cyclists, count of bike trips (regardless of unique riders) both from different directions, total number of bike trips regardless of the direction they are taking, time taken to complete bike trips from different directions and other cycling statistics. These ranges were extractetd using peak riding seasons with AM hours counts between 7am and 10am and PM Hours count between 4pm and 8pm. These time frames were built from Strava's internal analysis that shows the typical patterns and travel areas. The street network used is within Glasgow boundary although it might stretch to streets in neighbouring local authorities. The figures were normalized so that the values fall between 0 and 1. A Data Dictionary file is attached which contains all the field names and their respective meanings. The data points used to heat the map were between 2013-01-01 to 2013-12-31 Data licensed from Strava, Inc Licence: None strava-opendata.zip - https://dataservices.open.glasgow.gov.uk/Download/Organisation/4cd61d96-69cc-4114-a7da-54a218863c0a/Dataset/03f86c25-f7d2-457f-ae08-b356ac41d60f/File/4e1925c5-73b5-443c-99c7-b0e5ae0ace50/Version/ea9809d4-29d7-4472-8f57-351b17416582

Dataset consists of the data produced by nine cyclists. Data were directly exported from their Strava or Garmin Connect accounts. Data format of sport s activities could be written in GPX or TCX form, which are basically the XML formats adapted to specific purposes. From each dataset, many following information can be obtained: GPS location, elevation, duration, distance, average and maximal heart rate, while some workouts include also data obtained from power meters.

Introduction

This travel time matrix records travel times and travel distances for routes between all centroids (N = 13132) of a 250 × 250 m grid over the populated areas in the Helsinki metropolitan area by walking, cycling, public transportation, and private car. If applicable, the routes have been calculated for different times of the day (rush hour, midday, off-peak), and assuming different physical abilities (such as walking and cycling speeds), see details below.

The grid follows the geometric properties and enumeration of the versatile Yhdyskuntarakenteen seurantajärjestelmä (YKR) grid used in applications across many domains in Finland, and covers the municipalities of Helsinki, Espoo, Kauniainen, and Vantaa in the Finnish capital region.

Data formats

The data is available in multiple different formats that cater to different requirements, such as different software environments. All data formats share a common set of columns (see below), and can be used interchangeably.

Helsinki_Travel_Time_Matrix_2023.csv.zst: comma-separated values (CSV) of all data columns, without geometries. This data set contains all routes in one file, and can be filtered by origin or destination according to the analysis at hand. The data records can also be joined to the geometries as available below. The file is compressed using the Zstandard algorithm, that many data science libraries, for instance, pandas, support transparently, directly, and automatically.

Helsinki_Travel_Time_Matrix_2023_travel_times.gpkg.zip: an OGC GeoPackage standard file containing all data columns and the geometries that relate to the destination grid cell. The data set is delivered as a ZIP archive, which many GIS systems and libraries, e.g., GDAL/OGR, QGIS, or geopandas, support natively.

Helsinki_Travel_Matrix_2023_travel_times.csv.zip: a set of 13132 comma-separated value files containing the routes to one destination grid cell each. The files contain all data columns, no geometry, and can be joined to the geometries as available below. Filenames of the individual files within the ZIP archive follow the pattern Helsinki_Travel_Time_Matrix_2023_travel_times_to_5787545.csv where 5787545 is replaced by the to_id by which the rows in the file are grouped. Use the from_id column to join with the geometries from one of the files below.

Geometry, only:

Helsinki_Travel_Time_Matrix_2023_grid.gpkg.zip: an OGC GeoPackage standard file containing the geometries and IDs of the grid used in the analysis. This file can be joined both to the from_id and to_id columns of the data files. The data set is delivered as a ZIP archive, which many GIS systems and libraries, e.g., GDAL/OGR, QGIS, or geopandas, support natively.

Helsinki_Travel_Time_Matrix_2023_grid.shp.zip: an ESRI Shapefile archive containing the geometries and IDs of the grid used in the analysis. This file can be joined both to the from_id and to_id columns of the data files.

Table structure

from_id: ID number of the origin grid cell to_id: ID number of the destination grid cell walk_avg: Travel time in minutes from origin to destination by walking at an average speed walk_slo: Travel time in minutes from origin to destination by walking slowly bike_avg: Travel time in minutes from origin to destination by cycling at an average speedbike_fst: Travel time in minutes from origin to destination by cycling fastbike_slo: Travel time in minutes from origin to destination by cycling slowlypt_r_avg: Travel time in minutes from origin to destination by public transportation in rush hour traffic, walking at an average speed pt_r_slo: Travel time in minutes from origin to destination by public transportation in rush hour traffic, walking at a slower speed pt_m_avg: Travel time in minutes from origin to destination by public transportation in midday traffic, walking at an average speed pt_m_slo: Travel time in minutes from origin to destination by public transportation in midday traffic, walking at a slower speed pt_n_avg: Travel time in minutes from origin to destination by public transportation in nighttime traffic, walking at an average speed pt_n_slo: Travel time in minutes from origin to destination by public transportation in nighttime traffic, walking at a lower speed car_r: Travel time in minutes from origin to destination by private car in rush hour traffic car_m: Travel time in minutes from origin to destination by private car in midday traffic car_n: Travel time in minutes from origin to destination by private car in nighttime traffic walk_d: Distance from origin to destination, in meters, on foot

Data for 2013, 2015, and 2018

At the Digital Geography Lab, we started computing travel time matrices in 2013. Our methodology has changed in between the iterations, and naturally, there are systematic differences between the iterations' results. Not all input data sets are available to recompute the historical matrices with new methods, however, we were able to repeat the 2018 calculation using the same methods as the 2023 data set, please find the results below, in the same format.

For the travel time matrices for 2013 and 2015, as well as for 2018 using an older methodology, please refer to DOI:10.5281/zenodo.3247563.

Methodology

Computations were carried out for Wednesday, 15 February, 2023, and Monday, 29 January, 2018, respectively. 'Rush hour' refers to an 1-hour window between 8 and 9 am, 'midday' to 12 noon to 1 pm, and 'nighttime' to 2-3 am.

All routes have been calculated using r5py, a Python library making use of the R5 engine by Conveyal, with modifications to consider local characteristics of the Helsinki use case and to inform the computation models from local real-world data sets. In particular, we made the following modifications:

Walking

Walking speeds, and in turn walking times, are based on the findings of Willberg et al., 2023, in which we measured walking speeds of people of different age groups in varying road surface conditions in Helsinki. Specifically, we chose to use the average measured walking speed in summer conditions for walk_avg (as well as the respective pt_*_walk_avg), and the slowest quintile of all measured walker across all conditions for walk_slo (and the respective pt_*_walk_slo).

Cycling

Cycling speeds are derived from two input data sets. First, we averaged cycling speeds per network segment from Strava data, and computed a ratio between the speed ridden in each segment and the overall average speed. We then use these ratios to compute fast, slow, and average cycling speeds for each segment, based on the mean overall Strava speed, the mean speeds cycled in the Helsinki City Bike bike-share system, and the mean between the two.

Further, in line with the values observed by Jäppinen (2012), we add a flat 30 seconds each for unlocking and locking the bicycle at the origin and destination.

Public Transport

We used public transport schedules in General Transit Feed Specification (GTFS) format published by the Helsinki Regional Transport Authority, and adjusted the walking speeds (for connections between vehicles, as well as for access and egress to and from public transport stops) using the same methods as described above for walking.

Private motorcar

To represent road speeds actually driven in the Helsinki metropolitan region, we used floating car data of a representative sample of the roads in the region to derive the differences between the speed limit and the driven speed on different road classes, and by speed limit, see Perola (2023) for a detailed description of the methodology. Because these per-segment speeds factor in potential waiting times at road crossings, we eliminated turn penalties from R5.

Our modifications were carried out in two ways: some changes can be controlled by preparing input data sets in a certain way, or by setting model parameters outside of R5 or r5py. Other modifications required more profound changes to the source code of the R5 engine.

You can find a fully patched fork of the R5 engine in the Digital Geography Lab's GitHub repositories at github.com/DigitalGeographyLab/r5. The code that handles input data mangling and model parameter estimations is kept together with the logic to read input parameters and to collate output data, in the repository at github.com/DigitalGeographyLab/Helsinki-Travel-Time-Matrices.

Introduction

This travel time matrix records travel times and travel distances for routes between all centroids (N = 13231) of a 250 × 250 m grid over the populated areas in the Helsinki metropolitan area by walking, cycling, public transportation, and private car. If applicable, the routes have been calculated for different times of the day (rush hour, midday, off-peak), and assuming different physical abilities (such as walking and cycling speeds), see details below.

The grid follows the geometric properties and enumeration of the versatile Yhdyskuntarakenteen seurantajärjestelmä (YKR) grid used in applications across many domains in Finland, and covers the municipalities of Helsinki, Espoo, Kauniainen, and Vantaa in the Finnish capital region.

Data formats

The data is available in multiple different formats that cater to different requirements, such as different software environments. All data formats share a common set of columns (see below), and can be used interchangeably.

• `Helsinki_Travel_Time_Matrix_2023.csv.zst`: comma-separated values (CSV) of all data columns, without geometries. This data set contains all routes in one file, and can be filtered by origin or destination according to the analysis at hand. The data records can also be joined to the geometries as available below. The file is compressed using the Zstandard algorithm, that many data science libraries, for instance, pandas, support transparently, directly, and automatically.
• `Helsinki_Travel_Time_Matrix_2023_travel_times.gpkg.zip`: an OGC GeoPackage standard file containing all data columns and the geometries that relate to the destination grid cell. The data set is delivered as a ZIP archive, which many GIS systems and libraries, e.g., GDAL/OGR, QGIS, or geopandas, support natively.
• `Helsinki_Travel_Matrix_2023_travel_times.csv.zip`: a set of 13231 comma-separated value files containing the routes to one destination grid cell each. The files contain all data columns, no geometry, and can be joined to the geometries as available below. Filenames of the individual files within the ZIP archive follow the pattern `Helsinki_Travel_Time_Matrix_2023_travel_times_to_5787545.csv` where `5787545` is replaced by the `to_id` by which the rows in the file are grouped. Use the `from_id` column to join with the geometries from one of the files below.

Geometry, only:

• `Helsinki_Travel_Time_Matrix_2023_grid.gpkg.zip`: an OGC GeoPackage standard file containing the geometries and IDs of the grid used in the analysis. This file can be joined both to the `from_id` and `to_id` columns of the data files. The data set is delivered as a ZIP archive, which many GIS systems and libraries, e.g., GDAL/OGR, QGIS, or geopandas, support natively.
• `Helsinki_Travel_Time_Matrix_2023_grid.shp.zip`: an ESRI Shapefile archive containing the geometries and IDs of the grid used in the analysis. This file can be joined both to the `from_id` and `to_id` columns of the data files.

Table structure

from_id

to_id

walk_avg

walk_slo

bike_avg

bike_fst

bike_slo

pt_r_avg

pt_r_slo

pt_m_avg

pt_m_slo

pt_n_avg

pt_n_slo

car_r

car_m

car_n

walk_d

Data for 2013, 2015, and 2018

At the Digital Geography Lab, we started computing travel time matrices in 2013. Our methodology has changed in between the iterations, and naturally, there are systematic differences between the iterations’ results. Not all input data sets are available to recompute the historical matrices with new methods, however, we were able to repeat the 2018 calculation using the same methods as the 2023 data set, please find the results below, in the same format.

For the travel time matrices for 2013 and 2015, as well as for 2018 using an older methodology, please refer to DOI:10.5281/zenodo.3247563.

Methodology

Computations were carried out for Wednesday, 15 February, 2023, and Monday, 29 January, 2018, respectively. ‘Rush hour’ refers to an 1-hour window between 8 and 9 am, ‘midday’ to 12 noon to 1 pm, and ‘nighttime’ to 2-3 am.

All routes have been calculated using r5py, a Python library making use of the R⁵ engine by Conveyal, with modifications to consider local characteristics of the Helsinki use case and to inform the computation models from local real-world data sets. In particular, we made the following modifications:

Walking

Walking speeds, and in turn walking times, are based on the findings of Willberg et al., 2023, in which we measured walking speeds of people of different age groups in varying road surface conditions in Helsinki. Specifically, we chose to use the average measured walking speed in summer conditions for `walk_avg` (as well as the respective `pt_*_walk_avg`), and the slowest quintile of all measured walker across all conditions for `walk_slo` (and the respective `pt_*_walk_slo`).

Cycling

Cycling speeds are derived from two input data sets. First, we averaged cycling speeds per network segment from Strava data, and computed a ratio between the speed ridden in each segment and the overall average speed. We then use these ratios to compute fast, slow, and average cycling speeds for each segment, based on the mean overall Strava speed, the mean speeds cycled in the Helsinki City Bike bike-share system, and the mean between the two.

Further, in line with the values observed by Jäppinen (2012), we add a flat 30 seconds each for unlocking and locking the bicycle at the origin and destination.

Public Transport

We used public transport schedules in General Transit Feed Specification (GTFS) format published by