Data export

← Network Pulse

A service's day as flat tables: the headline, every scheduled journey run or not, and every stop of every journey tracked. Pick the services and the days and it is built on demand — the same code the command line runs, so a correction to how a journey is matched reaches this file the day it is made.

Days

From To

Schedule held from 2026-09-13. A past day cannot be rebuilt from today's timetable, so nothing before that can be exported.

Columns This platform's columns Four grains and a dictionary. Seconds are seconds, stop codes are full ATCO, and every scheduled journey is a row whether it ran or not. Mosaiq's columns Journeys and stops in the layout of the Mosaiq extract — same names, same order, decimal minutes — so a spreadsheet built on that can be pointed at this. What cannot be filled is left empty, not nought.

Tables

Also build the Excel workbook Every table as a sheet, with the read-me and the dictionary.

Services Every service that ran The whole network for the days chosen, one row per journey whether it ran or not. Find

Loading…

Nothing picked yet.

What the figures rest on

Every scheduled journey is a row, run or not. A journey nobody reported against is not absent from the file — absent reads as nought, and nought is a claim this data cannot make.
Join on journey_key, not trip_id. The trip id is BODS's, and it is a content hash of the journey: 22.8% of one Monday's journeys were renamed by a republication a week later, so a report joined across two weeks on that column would quietly drop a quarter of them. journey_key is built from what a re-issue leaves alone — date, operator, line, direction, origin stop and aimed departure — and resolved 99.9% of a day against the timetable published a week earlier.
A line number is not a service. Stagecoach Yorkshire run two services called 21 — Barnsley to Penistone, and Rotherham to Harthill — with not one stop in common, and First run a 51 in Sheffield and another in Doncaster. Those are offered separately, because no figure describes both. Every table carries route_id and route so the rows say which. Where a number is one service, and almost all of them are, it stays a bare number.
"Did not run" is always a ceiling. A journey nobody reported on looks exactly like one that did not run, and nothing in BODS tells them apart. The four states say which is which as far as the evidence goes: TRACKED, PART TRACKED, NO DATA, and NOT WATCHED — the last being our own recording gap, not the operator's missing bus.
There is no cancellation column. BODS carries no concept of one, in any of its three feeds. In the Mosaiq layout jny_canc and jny_part_canc are written empty rather than 0, because 0 would say nothing was cancelled and this data cannot say that.
Depot is empty in the Mosaiq layout. GTFS has no depot or garage concept, so it is not held anywhere here.
The Mosaiq stops file keeps unobserved stops as rows with observations 0, where theirs holds observed stops only. Filter to 1 to match their row count exactly.
Re-badging is only flagged from 2026-09-14 12:12, when the run log behind it starts. A journey due away before then reads not recorded rather than blank, because blank has to mean we looked and saw none.