omnitravel / gtfs

1.x-dev 2026-11-10 00:14 UTC

Requires

• php: >=8.2
• ext-pdo: *
• omnisense/omnitravel: ^1.0@dev
• symfony/http-client: ^6.4|^7.0|^8.0

Requires (Dev)

• phpstan/phpstan: ^2.1
• phpunit/phpunit: ^11.0

Suggests

• ext-pdo_mysql: A store in MySQL or MariaDB
• ext-pdo_sqlite: A store in an SQLite file
• ext-zip: Reads a feed's archive with ZipArchive (PharData reads it otherwise)

MIT

• Marco Meyer

• real-time
• sqlite
• transit
• protobuf
• timetable
• gtfs-realtime
• gtfs
• framework-agnostic
• public-transport
• departures
• omnitravel

Published on Packagist.org on 2026-11-10 00:35 UTC

README

omnisense/omnitravel's GTFS, under any PHP host: any network that publishes a static GTFS feed, imported into a store of its own (an SQLite file or MySQL, through PDO), and its GTFS-Realtime feeds laid over it.

• the network (NetworkInterface): the stops near a point, nearest first, with the lines calling there; stops by name, accents ignored; the lines in the feed's order with their colours; a line's stops in order, per direction; the operators;
• a stop's timetable (TimetablesInterface): its next departures and arrivals - a station's from all its platforms - from the feed's calendars, past midnight included (a trip at 25:10), with the delays, cancellations and skipped stops of the network's trip updates when it publishes them;
• vehicles (TrackingInterface): the positions of its vehicle feed, each with its line;
• service alerts (alerts()): the GTFS-Realtime alerts in force that concern a board's lines and stops, their texts by language;
• estimated vehicles (estimatedVehicles()): where a line's vehicles are from their times - real time where it is known - along their shapes, for networks that send no positions;
• SIRI Lite, for networks that publish SIRI rather than GTFS-Realtime (Île-de-France Mobilités' PRIM, Strasbourg's CTS): StopMonitoring laid over the timetable, GeneralMessage as alerts.

use Omnitravel\Gtfs\{Feed, GtfsFactory, Importer};
use Omnitravel\Model\{Coordinates, DepartureQuery};

$factory = new GtfsFactory($httpClient);                     // the client reads the real-time feeds only
(new Importer($factory->store('sqlite:/var/gtfs/gtfs.sqlite')))->import(new Feed('/tmp/irigo.zip'), 'angers');

$angers = $factory->create([
    'feed' => 'angers',
    'dsn' => 'sqlite:/var/gtfs/gtfs.sqlite',
    'trip_updates_url' => 'https://ara-api.enroute.mobi/irigo/gtfs/trip-updates',
    'attribution' => 'Irigo - Angers Loire Métropole, ODbL',
]);
$stop = $angers->nearby(new Coordinates(47.4712, -0.5518), 300)[0];
foreach ($angers->departures(new DepartureQuery($stop->id, limit: 5)) as $departure) {
    printf("%s %s %s%s\n", $departure->time()->format('H:i'), $departure->line?->name, $departure->headsign, $departure->isLate() ? ' (late)' : '');
}

Nothing but PHP's PDO (with pdo_sqlite or pdo_mysql) and zlib: an archive is read with ZipArchive where PHP has the zip extension, by the package's own Zip otherwise, and GTFS-Realtime's Protocol Buffers by its own WireReader - no generated classes, no protobuf extension.

The manual: docs/index.md. MIT.