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
❌245 erreurs, 28 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 02/12/2025 à 08h15 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
Sequential stop_time_update times are not increasing E022 172 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 922-38813 stop_sequence 1 arrival_time 05:50:49 (1764651049) is less than previous stop arrival_time 06:18:42 (1764652722) - times must increase between two sequential stops
- trip_id 922-38813 stop_sequence 1 departure_time 05:51:31 (1764651091) is less than previous stop arrival_time 06:18:42 (1764652722) - times must increase between two sequential stops
- trip_id 1140-38695 stop_sequence 27 arrival_time 08:11:10 (1764659470) is equal to previous stop arrival_time 08:11:10 (1764659470) - times must increase between two sequential stops
- trip_id 1140-38695 stop_sequence 27 arrival_time 08:11:10 (1764659470) is equal to previous stop departure_time 08:11:10 (1764659470) - times must increase between two sequential stops
- trip_id 1140-38695 stop_sequence 27 departure_time 08:11:10 (1764659470) is equal to previous stop departure_time 08:11:10 (1764659470) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 2 erreurs
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 0 departure_time 05:50:01 (1764651001) is less than the same stop arrival_time 06:18:42 (1764652722) - departure time must be equal to or greater than arrival time
- trip_id 1138-38751 stop_sequence 13 departure_time 07:48:11 (1764658091) is less than the same stop arrival_time 07:56:17 (1764658577) - departure time must be equal to or greater than arrival time
stop_time_update doesn't have arrival or departure E043 71 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 923-38054 stop_sequence 15 doesn't have arrival or departure
- trip_id 1143-38327 stop_sequence 4 doesn't have arrival or departure
- trip_id 925-36332 stop_sequence 9 doesn't have arrival or departure
- trip_id 1138-38751 stop_sequence 15 doesn't have arrival or departure
- trip_id 934-37606 stop_sequence 8 doesn't have arrival or departure
Avertissements
ID in one feed missing from the other W003 28 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 927-38827 is in TripUpdates but not in VehiclePositions feed
- trip_id 1140-38709 is in TripUpdates but not in VehiclePositions feed
- trip_id 1139-38708 is in TripUpdates but not in VehiclePositions feed
- trip_id 1141-38316 is in TripUpdates but not in VehiclePositions feed
- trip_id 933-37605 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 152 | 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 | 1 890 | 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 | 702 | 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 120 | 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 | 12 fois (40 % des 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. | 2 | 1 fois (3 % des validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 1 | 1 fois (3 % 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
Entités
Entités présentes dans ce flux le 02/12/2025 à 21h57 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updates vehicle_positionsFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 02/12/2025 à 21h57 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764709075"
}
}