As a complete SAEIV solution, PYSAE has various connectors for displaying real-time data from your network, including GTFS-RT. This standardised format makes it easy to transmit real-time data to third-party tools.
The benefits of a GTFS-RT connector
The GTFS-RT (or GTFS-realtime) format is increasingly used for transport networks. It simplifies the integration of planning and movement information for your flows, while transmitting this information to your passengers via an application or display.
The GTFS-RT connector is ideal for integrating real-time data and providing accurate, up-to-date information to your passengers.
Access point
The GTFS-RT connector for your group can be accessed at the following address (this includes all services):
https://pysae.com/api/v2/groups/[group_id]/gtfs-rt
group_id is the identifier of your group in Pysae.
We offer aliases if you need an address for each service:
https://pysae.com/api/v2/groups/[group_id]/gtfs-rt/trip-update
https://pysae.com/api/v2/groups/[group_id]/gtfs-rt/vehicle-position
https://pysae.com/api/v2/groups/[group_id]/gtfs-rt/alert
Here is an example of a flow in operation:
Please note that the result of a GTFS-RT request is a binary file. It cannot be read directly by a text editor.
Exchange protocol
Transport
The transport protocol used is HTTPS.
Format
In accordance with the GTFS-RT standard, data is returned in the form of a ProtocolBuffer, the description and .proto files of which can be found here :
Services offered
The following services are offered:
TripUpdate
VehiclePosition
Alert
TripUpdate service
The following table details the content of the TripUpdate service:
Title | Type | Availability on Pysae | Comment |
trip | TripDescriptor | Yes | Race concerned |
vehicle | VehicleDescriptor | Yes | Vehicle concerned |
stop_time_update | StopTimeUpdate | Yes | Lap time update |
VehiclePosition
The following table details the contents of the VehiclePosition service:
Title | Type | Availability on Pysae | Comment |
trip | TripDescriptor | Yes | Race concerned |
vehicle | VehicleDescriptor | Yes | Vehicle concerned |
position | Position | Yes | Vehicle position |
current-status | VehicleStopStatus | Yes | Vehicle status in relation to next stop |
congestion_level | CongestionLevel | No | Traffic difficulties |
_occupancy_status_ | OccupancyStatus | No | Occupancy rate |
Alert
The table below details the contents of the Alert service:
Title | Type | Availability on Pysae | Comment |
active_period | TimeRange | Yes | Period of application |
informed_entity | EntitySelector | Yes | Element concerned (run, stop, line) |
header_text | TranslatedString | Yes | Alert header |
description_text | TranslatedString | Yes | Alert description |
cause | Cause | Yes | Cause of disruption |
effect | Effect | Yes | Effect of the disturbance |
url | TranslatedString | No | Translation of message |