Resource details
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- VehiclePosition
- TripUpdate
- ServiceAlert
This resource file is part of the dataset Réseau urbain Glazgo.
Download availability
Learn more
HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.For SIRI and SIRI Lite feeds, we perform a
GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.Validation details
❌6 errors, 7 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-17 at 08:13 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 2 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 5-251723777 stop_sequence 14 arrival_time 07:37:50 (1773729470) is less than previous stop arrival_time 08:35:50 (1773732950) - times must increase between two sequential stops
- trip_id 5-251723777 stop_sequence 14 arrival_time 07:37:50 (1773729470) is less than previous stop departure_time 08:35:50 (1773732950) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 4 errors
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Sample errors
- trip_id 5-235012123 stop_sequence 1 doesn't have arrival or departure
- trip_id 5-235012123 stop_sequence 2 doesn't have arrival or departure
- trip_id 5-235012123 stop_sequence 3 doesn't have arrival or departure
- trip_id 5-235012123 stop_sequence 4 doesn't have arrival or departure
Warnings
ID in one feed missing from the other W003 7 errors
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Sample errors
- trip_id 5-235077650 is in TripUpdates but not in VehiclePositions feed
- trip_id 5-218497052 is in TripUpdates but not in VehiclePositions feed
- trip_id 5-251723778 is in TripUpdates but not in VehiclePositions feed
- trip_id 5-235012123 is in TripUpdates but not in VehiclePositions feed
- trip_id 5-235012116 is in TripUpdates but not in VehiclePositions feed
Previous validations
Here is a recap of all the error types encountered over the last 30 days.
| Error ID | Description | Errors count | Number of occurences |
|---|---|---|---|
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 123 | 22 times (73 % of validations) |
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 129 | 18 times (60 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 34 | 13 times (43 % of validations) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 4 | 4 times (13 % of validations) |
| E025 | Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. | 2 | 2 times (7 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-03-17 at 23:49 Europe/Paris.
service_alerts (1) vehicle_positions (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsService alerts
Here is a display of service alerts contained in this feed at 2026-03-17 at 23:49 Europe/Paris.
Déviation hebdomadaire (Marché du lundi) Detour
Tous les lundis de 7h à 15h, en raison du marché Direction Pluneret : les arrêts Foch, Notre-Dame et Hôtel de Ville ne seront pasdesservis. Direction Brec’h : les arrêts Barré et Les Augustines ne seront pas desservis.
Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-03-17 at 23:49 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"alert": {
"cause": "DEMONSTRATION",
"descriptionText": {
"translation": [
{
"text": "Tous les lundis de 7h à 15h, en raison du marché\n\nDirection Pluneret : les arrêts Foch, Notre-Dame et Hôtel de Ville ne seront pasdesservis.\n\nDirection Brec’h : les arrêts Barré et Les Augustines ne seront pas desservis."
}
]
},
"effect": "DETOUR",
"headerText": {
"translation": [
{
"text": "Déviation hebdomadaire (Marché du lundi)"
}
]
},
"informedEntity": [
{
"routeId": "14"
}
]
},
"id": "alert:68c3eebc46b07dd6232d9b96"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1773787744"
}
}