Mapped Into Compliance: How Transit Agencies Use Data to Overstate the Networks They Actually Operate
Mapped Into Compliance: How Transit Agencies Use Transit Data to Overstate the Networks They Actually Operate
When a city publishes its transit map, it is making an implicit promise. Every colored line, every labeled stop, every published schedule represents a commitment to the public that a bus or train will appear at a given location within a reasonable window of time. For millions of American commuters, that promise is broken with remarkable regularity—and the data increasingly makes it impossible to ignore.
The General Transit Feed Specification, commonly known as GTFS, is the open data standard that powers the trip planners, mobile applications, and mapping tools that riders depend on every day. Developed originally by Google in partnership with TriMet in Portland, Oregon, GTFS has become the de facto language of public transit data in the United States. It is also, in a growing number of cities, a vehicle for institutional misrepresentation.
What the Feed Says Versus What the Bus Does
GTFS data is divided into two formats: static and real-time. The static feed contains scheduled routes, stop locations, and timetables. The real-time feed, where it exists, reports the actual position of vehicles and their predicted arrival times. When analysts and researchers compare the two, the results are frequently alarming.
In numerous metropolitan areas, routes listed in static GTFS feeds have not operated for months or, in some cases, years. Service suspensions initiated during the COVID-19 pandemic were never formally removed from published schedules. Seasonal service adjustments were logged as temporary but never restored. Frequency reductions that gutted the utility of certain corridors were buried in supplementary notices that never made it into the primary feed.
The practical result is that a commuter using Google Maps, Apple Maps, or a city's own transit application may be directed toward a bus that has not run since 2021. The app shows a departure. The stop shows a schedule. The bus does not come.
The Anatomy of a Coverage Claim
To understand how this happens systematically, it helps to examine how agencies construct and maintain their public-facing data. GTFS feeds are typically managed by small teams within agency IT or planning departments. Updating the feed requires deliberate action—removing routes, adjusting frequencies, flagging suspensions. When agencies face budget shortfalls, staff reductions, or operational crises, feed maintenance is rarely the highest priority.
The incentive structure compounds the problem. Transit agencies in the United States frequently report service coverage statistics to federal and state funders as part of grant compliance and performance reviews. Coverage is typically measured in terms of the percentage of a city's population living within a defined distance—often a quarter mile—of a transit stop. If routes remain in the feed even when service has been suspended, those stops continue to count toward coverage calculations.
This is not a minor accounting quirk. It is a mechanism by which agencies can report strong coverage numbers to oversight bodies while delivering substantially diminished service to the public. In cities where federal funding is tied to performance benchmarks, the pressure to maintain favorable statistics in official data is not trivial.
Case Patterns: Where the Gaps Are Deepest
Researchers and transit advocates who have conducted systematic GTFS audits have identified recurring patterns in where data-to-reality gaps tend to be most severe.
Peripheral corridors in mid-sized cities are disproportionately affected. These are routes that serve lower-density residential areas, often predominantly low-income or working-class neighborhoods, where ridership numbers are modest and political visibility is limited. When agencies quietly suspend service on these routes, the communities affected are less likely to generate the organized public response that might force a correction.
Cross-town routes—those that do not pass through a central downtown hub—are another common site of phantom service. Because these routes are structurally less visible in agency planning priorities, reductions and suspensions are less likely to be flagged in public communications. Riders who depend on them for access to employment, healthcare, or essential services may discover the problem only when they arrive at a stop and wait in vain.
Night and weekend schedules are particularly prone to discrepancy. Agencies that have reduced off-peak service often leave daytime schedules intact in their published feeds, creating an illusion of comprehensive coverage that dissolves at the hours when shift workers, service industry employees, and caregivers most need reliable transit.
The Real-Time Data Gap
A partial remedy exists in the form of GTFS-RT, the real-time extension of the standard. When properly implemented, real-time feeds allow applications to reflect actual vehicle positions and alert riders to cancellations and delays before they reach a stop. The problem is that real-time feed adoption remains uneven across the country.
Many smaller and mid-sized agencies either lack the technical infrastructure to publish real-time data or publish feeds of inconsistent quality. Vehicles drop off the feed for extended periods. Cancellations are not flagged. Trip planners fall back to static schedule data and present it as current. Riders receive no indication that the information they are acting on is unreliable.
Even in cities with robust real-time infrastructure, the gap between what the feed reports and what riders experience can be substantial. Vehicle tracking data can show a bus moving along a route while that bus is in fact operating a deadhead trip—traveling without passengers between a garage and its assigned starting point. Without careful data validation, these movements can register as service when no service is being provided.
Toward Accountability in Transit Data
Addressing this problem requires action at multiple levels. At the agency level, the most immediate step is implementing systematic audits of published GTFS feeds against operational records. Routes that are not operating should be removed or flagged as suspended. Frequency changes should be reflected in published schedules within a defined timeframe after implementation.
At the federal level, the Federal Transit Administration has authority to require data accuracy as a condition of funding. Currently, performance reporting requirements focus heavily on ridership, on-time performance, and safety metrics. Data integrity—the accuracy of published schedules relative to actual operations—is not a standard compliance category. Incorporating it into oversight frameworks would create a meaningful incentive for agencies to keep their feeds current.
Third-party validation offers another avenue. Several nonprofit organizations and academic research groups have developed tools for comparing GTFS static data against real-time feeds and rider-reported experiences. Making the outputs of these tools publicly accessible, and linking them to agency performance dashboards, would give commuters, journalists, and elected officials a clearer picture of where service claims diverge from service delivery.
The Map Is Not the Territory
There is a long-standing principle in systems thinking that the representation of a thing is not the thing itself. Transit maps, however sophisticated and data-rich they have become, are representations. They describe a network as agencies wish it to be perceived, not necessarily as it functions.
For the commuter standing at a stop in a peripheral neighborhood at 7:30 in the evening, waiting for a bus that the app says is coming in four minutes, the distinction between the map and the territory is not an abstraction. It is a material condition that shapes decisions about employment, housing, healthcare, and daily life.
Fixing the data will not fix the underlying service gaps. But it would, at minimum, give riders accurate information about the network they actually have access to—rather than the one their city claims to provide.
