Request ID: FOI-2095-2122 Date published: 22 December 2021
You asked
Would you please provide me with your bus speed data in .xls format for the period from 01.01.19 to date relating to the section of bus routes as follows:
Routes 236, 276, 488, 308 W15 on Homerton High Street, Homerton Road
Routes 30, 236, 276, W15 on Morning Lane
Routes 38, 242, 277 Graham Rd to Dalston Junction
Route 30 Amhurst Road to Dalston Junction
Route 76,149, 243 Old Street to Stamford Hill
We answered
TfL Ref: FOI-2095-2122
Thank you for your request received by Transport for London (TfL) on 14th December 2021 asking for bus speed data within the London Borough of Hackney. Your request has been considered in accordance with the requirements of the Freedom of Information Act and our information access policy.
Specifically you asked:
“Would you please provide me with your bus speed data in .xls format for the period from 01.01.19 to date relating to the section of bus routes as follows: Routes 236, 276, 488, 308 W15 on Homerton High Street, Homerton Road Routes 30, 236, 276, W15 on Morning Lane Routes 38, 242, 277 Graham Rd to Dalston Junction Route 30 Amhurst Road to Dalston Junction Route 76,149, 243 Old Street to Stamford Hill”.
I can confirm that we hold some of the information you require, which is provided in the attached folder. Note that our iBus database only contains two years’ worth of detailed data, and so the data provided starts from mid-December 2019. Our database contains run time data by stop segments, which is provided. The run times can be converted into bus speeds by dividing distances between stops by the run times. The files provided are:
FOI-2095-2122 routes contains distances (in miles) between each stop point.
FOI-2095-2122 MADT [route number] contains individual hourly records per route / date / stop segment:
ROUTE – route number;
SERVICEDAY – service day, which on day routes typically starts early in the morning and ends around or just after midnight;
DIRECTION – direction of travel;
DIRLONGDESC – destination point of each direction;
STOPSEQUENCE – sequential number of each stop;
SD1 – stop code of stop segment start;
SL1 – stop name of stop segment start;
SD2 – stop code of stop segment end;
SL2 – stop name of stop segment end;
SCHEDULEDDISTANCE – distance (in metres) between stops within stop segment;
HR – hour (e.g. “07” stands for a period 07:00:00 to 07:59:59);
SCH_TRIPS – number of scheduled trips within the hour;
TRIPS – number of observed trips within the hour;
MESJT – average schedule run time (in seconds) between stops SL1 and SL2;
MEAJT – average actual run time (in seconds) between stops SL1 and SL2 (includes dwell time at stop SL2 of each segment);
MADT – average actual dwell time (in seconds) at stop SL2 of each segment.
If this is not the information you are looking for, or if you are unable to access it for any reason, please do not hesitate to contact me.
Please see the attached information sheet for details of your right to appeal as well as information on copyright and what to do if you would like to re-use any of the information we have disclosed.
Yours sincerely,
David Wells FOI Case Officer FOI Case Management Team General Counsel Transport for London
