Détails de la ressource
Données temps-réel du réseau RUBAN suivant la structure GTFS-RT au format Protocol Buffers.
Cette ressource fait partie du jeu de données Réseau urbain Ruban.
Disponibilité au téléchargement
En savoir plus
HEAD dont le temps de réponse doit être inférieur à 5 secondes. Si nous détectons une indisponibilité, nous effectuons un nouveau test toutes les 10 minutes, jusqu'à ce que la ressource soit à nouveau disponible.Pour les flux SIRI et SIRI Lite, nous effectuons une requête HTTP de type
GET : nous considérons une réponse avec un code 401 ou 405 comme étant disponible. En cas d'erreur 500, nous considèrerons que le flux est indisponible, sauf si il semble contenir du SOAP.Rapport de validation
❌608 erreurs, 44 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 04/12/2025 à 08h02 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
Sequential stop_time_update times are not increasing E022 271 erreurs
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Exemples d'erreurs
- trip_id 1159-38797 stop_sequence 8 arrival_time 08:08:40 (1764832120) is equal to previous stop arrival_time 08:08:40 (1764832120) - times must increase between two sequential stops
- trip_id 1159-38797 stop_sequence 8 arrival_time 08:08:40 (1764832120) is equal to previous stop departure_time 08:08:40 (1764832120) - times must increase between two sequential stops
- trip_id 1159-38797 stop_sequence 8 departure_time 08:08:40 (1764832120) is equal to previous stop departure_time 08:08:40 (1764832120) - times must increase between two sequential stops
- trip_id 1159-38797 stop_sequence 8 departure_time 08:08:40 (1764832120) is equal to previous stop arrival_time 08:08:40 (1764832120) - times must increase between two sequential stops
- trip_id 1159-38797 stop_sequence 12 arrival_time 08:11:40 (1764832300) is equal to previous stop arrival_time 08:11:40 (1764832300) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 1 erreur
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.
Exemples d'erreurs
- trip_id 922-38813 stop_sequence 14 departure_time 06:10:55 (1764825055) is less than the same stop arrival_time 06:27:04 (1764826024) - departure time must be equal to or greater than arrival time
stop_time_update doesn't have arrival or departure E043 78 erreurs
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Exemples d'erreurs
- trip_id 1141-38328 stop_sequence 4 doesn't have arrival or departure
- trip_id 1144-38245 stop_sequence 21 doesn't have arrival or departure
- trip_id 1144-38245 stop_sequence 22 doesn't have arrival or departure
- trip_id 1144-38245 stop_sequence 23 doesn't have arrival or departure
- trip_id 933-37605 stop_sequence 8 doesn't have arrival or departure
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 256 erreurs
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Exemples d'erreurs
- GTFS-rt trip_id 923-36244 stop_sequence 22 has stop_id BJPOSTE2 but GTFS stop_sequence 22 has stop_id BJGARE1 - stop_ids should be the same
- GTFS-rt trip_id 923-36244 stop_sequence 23 has stop_id BJLYCEE2 but GTFS stop_sequence 23 has stop_id BJPOSTE2 - stop_ids should be the same
- GTFS-rt trip_id 923-36244 stop_sequence 24 has stop_id BJPMICH2 but GTFS stop_sequence 24 has stop_id BJLYCEE2 - stop_ids should be the same
- GTFS-rt trip_id 923-36244 stop_sequence 25 has stop_id BJFOLAT2 but GTFS stop_sequence 25 has stop_id BJPMICH2 - stop_ids should be the same
- GTFS-rt trip_id 923-36244 stop_sequence 26 has stop_id BJEPARG1 but GTFS stop_sequence 26 has stop_id BJFOLAT2 - stop_ids should be the same
VehiclePosition and TripUpdate ID pairing mismatch E047 2 erreurs
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Exemples d'erreurs
- trip_id 42137{1141_2}-Période Scolaire Sep 2024-2025_5_LMWJV and vehicle_id 692872f0244f030d0e38bcb9 pairing in VehiclePositions does not match trip_id 42233{BJA01_2}-Période Scolaire Sep 2024-2025_5_LMWJV and vehicle_id 692872f0244f030d0e38bcb9 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 42134{1141_2}-Période Scolaire Sep 2024-2025_5_LMWJV and vehicle_id 68dba158b789cf024ede8580 pairing in VehiclePositions does not match trip_id 42239{BJA01_2}-Période Scolaire Sep 2024-2025_5_LMWJV and vehicle_id 68dba158b789cf024ede8580 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
Avertissements
ID in one feed missing from the other W003 44 erreurs
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
Exemples d'erreurs
- trip_id 1137-38326 is in TripUpdates but not in VehiclePositions feed
- trip_id 1139-38708 is in TripUpdates but not in VehiclePositions feed
- trip_id 1143-38359 is in TripUpdates but not in VehiclePositions feed
- trip_id 1142-38231 is in TripUpdates but not in VehiclePositions feed
- trip_id 924-38056 is in TripUpdates but not in VehiclePositions feed
Validations précédentes
Voici un récapitulatif des différents types d'erreurs constatés au cours des 30 derniers jours.
| Identifiant d'erreur | Description | Nombre d'erreurs | Nombre d'occurences |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 4 266 | 25 fois (83 % des 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 | 2 013 | 25 fois (83 % des 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 | 712 | 25 fois (83 % des validations) |
| E045 | If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt | 5 005 | 23 fois (77 % des 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. | 24 | 13 fois (43 % des validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 4 | 3 fois (10 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Impossible de décoder le flux GTFS-RT
Le flux GTFS-RT doit être accessible en HTTP, sans authentification et utiliser le format Protobuf.