explore | Grilled Cheese

The NTD records only nine transit cyberattacks since 2014, though FTA says dozens likely occurred. A physical-assets reading of “infrastructure” helped screen digital incidents out.
https://its-feed.com/articles/ntd-cybersecurity-reporting/
#TransitData #Cybersecurity

GTFS ownership has moved to MobilityData on paper, while the repository and contributor agreement still point to Google. Also this month: shapes.txt is now conditionally required.
https://its-feed.com/articles/roundup-2026-10/
#GTFS #TransitData

A zero exit status from the canonical GTFS validator means it produced a report, not that the feed is clean. Compliance requires checking report.json for ERROR notices.
https://its-feed.com/articles/what-the-gtfs-validator-checks/
#GTFS #TransitData

Not all transit data updates at the same speed. ⏱️

From security waits to ground stops, school bus data and ER waits each source follows its own refresh cycle.

AVL locates the vehicle; CAD compares that position with the schedule and gives dispatchers something to act on. In 61 bus feeds surveyed, position and vehicle ID appeared in every feed.
https://its-feed.com/articles/what-a-cad-avl-system-does/
#TransitData #CADAVL

Average wait and average when delayed tell two very different stories.

TODS adds what rider-facing GTFS leaves out: pull-outs, deadheads, crew runs, and vehicle assignments. Its ten optional files offer a standard handoff from scheduling systems to CAD/AVL.
https://its-feed.com/articles/transit-operational-data-standard/
#TransitData #OpenStandards

GTFS-Realtime shows where a bus is now; TIDES preserves the service-day record. Its 11 tables link AVL, passenger counts, and fare transactions to scheduled and performed trips.
https://its-feed.com/articles/tides-transit-data-specification/
#TransitData #OpenStandards