Resource details

File name: Données en temps réel au format GTFS-RT
Format: gtfs-rt

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

2025-08-15
100%
2025-08-16
100%
2025-08-17
100%
2025-08-18
100%
2025-08-19
100%
2025-08-20
100%
2025-08-21
100%
2025-08-22
100%
2025-08-23
100%
2025-08-24
100%
2025-08-25
100%
2025-08-26
100%
2025-08-27
100%
2025-08-28
99.3%
2025-08-29
99.4%
2025-08-30
99.4%
2025-08-31
99.4%
2025-09-01
99.4%
2025-09-02
99.4%
2025-09-03
99.3%
2025-09-04
99.4%
2025-09-05
99.4%
2025-09-06
99.4%
2025-09-07
99.4%
2025-09-08
99.4%
2025-09-09
99.4%
2025-09-10
99.4%
2025-09-11
98.7%
2025-09-12
99.4%
2025-09-13
99.4%
2025-09-14
100%
Learn more
We test this resource download availability every hour by making an HTTP 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

3 errors, 3 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-13 at 09:09 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_time_update doesn't have arrival or departure E043 3 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-235012109 stop_sequence 13 doesn't have arrival or departure
  • trip_id 5-235012109 stop_sequence 14 doesn't have arrival or departure
  • trip_id 5-235012109 stop_sequence 15 doesn't have arrival or departure

Warnings

ID in one feed missing from the other W003 3 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-218497044-AUR02-_____S_ is in TripUpdates but not in VehiclePositions feed
  • trip_id 5-218431505-AUR01-_____S_ is in TripUpdates but not in VehiclePositions feed
  • trip_id 5-218497047-AUR01-_____S_ is in TripUpdates but not in VehiclePositions feed
Validate this GTFS-RT now

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
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 139 12 times (92 % of validations)
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 87 12 times (92 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 80 10 times (77 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 142 10 times (77 % 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. 55 10 times (77 % of validations)
E047 If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. 20 10 times (77 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 16 8 times (62 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-09-14 at 02:44 Europe/Paris.

service_alerts (2) vehicle_positions (0) trip_updates (0)

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Service alerts

Here is a display of service alerts contained in this feed at 2025-09-14 at 02:44 Europe/Paris.

Arrêt Lann Roz non desservi Detour

Du 1er septembre jusqu’à la fin des travaux, sur le Boulevard Anne de Bretagnel’arrêt Lann Roz ne sera pas desservi dans les deux sens.

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 2025-09-14 at 02:44 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "alert": { "cause": "CONSTRUCTION", "descriptionText": { "translation": [ { "text": "Du 1er septembre jusqu’à la fin des travaux, sur le Boulevard Anne de Bretagnel’arrêt Lann Roz ne sera pas desservi dans les deux sens." } ] }, "effect": "DETOUR", "headerText": { "translation": [ { "text": "Arrêt Lann Roz non desservi" } ] }, "informedEntity": [ { "routeId": "13" } ] }, "id": "alert:68c3ed5a72e392735dea13fb" }, { "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": "1757810650" } }