GTFS Schedule Display

Renders GTFS schedule data as a timetable people can read: stops down the side, trips across, times in the cells. It runs against a GTFS Core install on the same site, or against a remote one over its REST API.

Features

• A timetable page per route, at a URL pattern you control.
• Local or remote data. Run it on the site that holds the feed, or point it at another site's GTFS API — useful when the public website and the data importer are separate builds on separate release cycles.
• Timepoints only by default, with the full stop list available, so a long route does not produce an unreadable wall of numbers.
• Manual stop ordering for routes where the feed's own sequence does not match how riders read the line.
• Stop headings link through to stop pages, so a timetable is a way into the rest of the site rather than a dead end.
• Your own wording for a route with no service, your own time format, and route naming by ID or by name.

Requirements

Drupal 10.3 or 11. In local mode, GTFS Core 3.x on the same site. In remote mode, network access to a GTFS Core REST API.

Installation

composer require drupal/gtfs_schedule

Configuration

Administration › GTFS › Schedule settings (/admin/gtfs/schedule/settings). Choose local or remote, set the feed alias and agency, and set the URL pattern —
/gtfs/routes/{route_id}/schedules by default. Stop-order overrides are at /admin/gtfs/schedule/schedule-order-override.

Related modules

• GTFS Core — the entities, the importer and the API everything else reads
• GTFS Realtime — trip updates, vehicle positions and service alerts
• GTFS Display — stop, route and system displays for public screens
• GTFS Display Map — route and stop geometry on a map
• GTFS Display Map RT — live vehicles, and an embeddable map
• GTFS 511 — feed provisioning from the 511 SF Bay API
• GTFS+ — the GTFS+ extension files

Maintainers

Maintained by tbcs and jpsalter, supported by FivePaths. These modules run public transit information systems in daily service. Issues and merge requests are welcome, and so are co-maintainers.