Every time you check Citymapper, Google Maps, or Apple Maps for a bus time, a hidden supply chain of data producers, aggregators, and public bodies made that answer possible. This piece from Open Data Manchester asks the deceptively simple question: who actually pays for that? — and the answer exposes one of the more underappreciated tensions in modern civic infrastructure.

Public transit timetable data is the classic "commons" problem in a digital wrapper. Local authorities and operators generate the raw schedules. National feeds (in the UK, things like BODS — the Bus Open Data Service) aggregate and standardise them, usually funded by taxpayers. Then large commercial platforms consume that data for free and package it into apps that generate substantial revenue — without meaningfully returning value to the producers.

Why a technical audience should care:

• It's a real-world data pipeline case study. GTFS, TransXChange, SIRI, NeTEx — bus data touches nearly every hard problem in schema design, versioning, geospatial encoding, and real-time streaming. Anyone who's tried to normalise a national transit feed knows the pain.
• It's about the economics of open data. "Open" doesn't mean "free to produce." The article likely explores how sustainable open data ecosystems require funding models beyond goodwill, and what happens when the producers can't recoup costs while the consumers monetise heavily.
• It mirrors debates in open source. Substitute "npm maintainer" for "local transit authority" and the story rhymes. Corporations extract value from unpaid or underfunded infrastructure until it breaks — then act surprised when it does.
• It's a governance question dressed as a technical one. Who defines the schema? Who guarantees uptime? Who owns the API contract when a bus route changes at 4am? These are engineering decisions with political weight.

Manchester in particular is an interesting lens because Greater Manchester recently brought buses back under public control via franchising — the first English city outside London to do so. That means the data flows, ownership, and funding models are being actively re-architected in a way most cities aren't yet grappling with.

For engineers building on public data, this is essential reading: the pipes you depend on have a funding model, and if you don't know what it is, you don't actually know how reliable your dependency is.