Public transport data integration
Transit agencies publish schedules and realtime data, and operate fleets, depots and stations with their own systems.
Example use case
An agency compares GTFS schedules with vehicle CAN data from battery buses to see which routes leave too little charge margin in winter.
Typical sources and transports
GTFS static and GTFS Realtime, GTFS-Fares v2 and Flex, Bus FMS via CAN J1939, C-ITS SREM/SSEM priority messages, GBFS, and BACnet/IP in depots.
What the data means
GTFS trips and stops are identifiers that change between feed versions; realtime updates are predictions with timestamps. Battery state of charge needs its vehicle and time.
Prerequisites
Before connecting public transport sources, prepare an inventory of systems and owners, interface documentation for each one, read-only credentials and approved network paths. Agree identifiers, units and time zones early, and name a person who can confirm values against the source during commissioning.
Limitations
Feed versions must be tracked. Vehicle data access depends on the bus manufacturer, and is validated per fleet.
ALLINLET reads and normalises data; it does not control equipment.
Catalogue entries for this domain
The connector catalogue lists 48 entries for this domain. A selection is shown below. Listing indicates a possible integration path, not that it is implemented, validated or installed for your environment.
- AIS (vessels)
- BACnet/IP
- Bus FMS battery profile
- C-ITS · SREM/SSEM
- CAN Bus / J1939
- CDC / external change-data pipeline
- CSV
- DATEX II
- ECMWF GRIB2
- GBFS (shared mobility)
- GTFS static · HTTPS download
- GTFS stops.txt
- GTFS-Fares v2
- GTFS-Flex
- GTFS-Pathways
- GTFS-Realtime
- iCalendar
- IEC 60870-5-104
Further reading
Catalogue listings describe possible integration paths. Implementation and validation status is confirmed for each source during project scoping; no certification, service level or price is implied by this page.
Plan your data integration
Share your devices, protocols and network constraints, and we will propose a first validated connection.