Every rider screen, straight from your GTFS feeds.
gtfs.media turns the GTFS and GTFS‑Realtime feeds you already publish into live departure displays, vehicle maps, timetables, and clean JSON APIs. Open source at the core — run it yourself, or let us run it for you.
In plain language
Transit agencies publish their timetables in a standard file. It is called GTFS.
This software reads that file. It turns it into things riders can use: screens at stops, maps that show where the buses are, and timetables.
The software is free. Anyone can use it or change it.
We can also run all of it for you.
One platform, three layers
A structured data core, a realtime pipeline, and rider-facing surfaces — each usable on its own.
Data platform
Import any GTFS feed into structured, fieldable, editable content — routes, stops, trips, calendars, shapes — and re-import updates without losing your own additions.
For developers →Live displays
Departure boards for stops, routes, or your whole system — offline-resilient and compatible with old hardware.
Displays →Realtime maps
Embeddable maps with live vehicle positions, realtime predictions, and customizable cartography.
Maps →Who it’s for
Transit agency staff
Add feeds, create displays, post alerts and overrides, and watch fleet health — all from web forms. If your website already runs Drupal, none of this is new technology.
For agenciesDevelopers
Entities, fields, Views, config sync — the Drupal you already know, applied to transit, with a versioned JSON API for everything else.
For developersImport. Ingest. Serve.
-
Import your GTFS
Point the importer at your published GTFS file. Every file becomes structured content you can browse, extend, and translate. Re-run it against new versions and your manual edits survive.
-
Ingest realtime
Trip updates, vehicle positions, and service alerts are pulled from your GTFS‑Realtime endpoints on a schedule you set, decoded from Protobuf, and normalized into a clean JSON API.
-
Serve every surface
Departure displays, live maps, timetables, and embeds — all polling the same APIs your own apps can use. One source of truth, everywhere riders look.
Screens from a production deployment
A custom platform pylon: departures, alerts, and route info — multilingual by default. Displays →
A light-rail line, live: every train with its heading, every stop tappable for predictions. Realtime maps →
Proven in production at multiple major U.S. transit agencies — powering public departure displays, embeddable live maps, and rider-facing APIs.
GTFS · GTFS‑RT · 24/7Run it yourself, or let us run it for you.
Open-source
The entire platform is a suite of GPL‑2.0+ modules for Drupal 10 and 11. Install them on your own infrastructure, extend them with the same hooks we use, and keep full ownership of your data.
- Eight modules, from data core to live maps
- Standard Drupal — your web team already knows it
- Your servers, your data — nothing in the stack is proprietary
Managed by gtfs.media
We host, monitor, and operate the platform for your agency — from feed onboarding to display fleets in the field.
- Feed onboarding — static and realtime, validated and synced
- Custom skins & integrations for your brand and hardware
- Whole websites — agency sites built with transit native; the platform is free with a build
Works with
The specifications the suite implements, the feed sources it has already run against, and the software underneath. Any publisher of GTFS and GTFS‑Realtime works; these are the ones we have worked with.
Put your feed to work.
Tell us about your agency, your screens, and your data — we'll show you what gtfs.media can do with them.