Jeu de données ouvert gtfs-rt - Trip Update pour Réseau urbain Citéa

Détails de la ressource

Nom du fichier : Trip Update

Format : gtfs-rt

Cette ressource fait partie du jeu de données Réseau urbain Citéa.

Disponibilité au téléchargement

Nous testons la disponibilité de cette ressource au téléchargement toutes les heures, en effectuant une requête HTTP de type 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

❌298 erreurs, 191 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 27/09/2025 à 09h00 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

stop_times_updates not strictly sorted E002 23 erreurs

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Exemples d'erreurs

trip_id SH_3074854 stop_sequence [3, 1] is not strictly sorted by increasing stop_sequence
trip_id SH_3074900 stop_sequence [28, 1] is not strictly sorted by increasing stop_sequence
trip_id SH_3074901 stop_sequence [28, 1] is not strictly sorted by increasing stop_sequence
trip_id SH_3074898 stop_sequence [28, 1] is not strictly sorted by increasing stop_sequence
trip_id SH_3074899 stop_sequence [28, 1] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 258 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 SH_3074854 stop_sequence 1 departure_time 09:46:00 (1758959160) is less than previous stop departure_time 09:48:02 (1758959282) - times must increase between two sequential stops
trip_id SH_3074854 stop_sequence 1 departure_time 09:46:00 (1758959160) is less than previous stop arrival_time 09:48:02 (1758959282) - times must increase between two sequential stops
trip_id SH_3074854 stop_sequence 2 arrival_time 09:46:56 (1758959216) is less than previous stop arrival_time 09:48:02 (1758959282) - times must increase between two sequential stops
trip_id SH_3074854 stop_sequence 2 departure_time 09:46:56 (1758959216) is less than previous stop arrival_time 09:48:02 (1758959282) - times must increase between two sequential stops
trip_id SH_3074854 stop_sequence 7 arrival_time 09:49:33 (1758959373) is less than previous stop arrival_time 09:51:19 (1758959479) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_id E037 4 erreurs

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Exemples d'erreurs

trip_id SH_3075480 has repeating stop_id 0:AURO - sequential stop_ids should be different
trip_id SH_3075478 has repeating stop_id 0:AURO - sequential stop_ids should be different
trip_id SH_3075479 has repeating stop_id 0:AURO - sequential stop_ids should be different
trip_id SH_3074779 has repeating stop_id 0:_CIM 2 - sequential stop_ids should be different

GTFS-rt stop_sequence not found in GTFS data E051 13 erreurs

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Exemples d'erreurs

GTFS-rt trip_id SH_3074854 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id SH_3074900 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id SH_3074901 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id SH_3074898 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id SH_3074899 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 121 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs

trip_id SH_3074854 does not have a timestamp
trip_id SH_3074026 does not have a timestamp
trip_id SH_3074024 does not have a timestamp
trip_id SH_3074025 does not have a timestamp
trip_id SH_3074022 does not have a timestamp

vehicle_id not populated W002 70 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id SH_3074854 does not have a vehicle_id
trip_id SH_3074026 does not have a vehicle_id
trip_id SH_3074024 does not have a vehicle_id
trip_id SH_3074025 does not have a vehicle_id
trip_id SH_3074900 does not have a vehicle_id

Valider ce GTFS-RT maintenant

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.	9 706	31 fois (100 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	236	31 fois (100 % des validations)
W001	Timestamps should be populated for all elements	4 580	31 fois (100 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	2 648	31 fois (100 % des validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	610	21 fois (68 % des validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	379	21 fois (68 % des validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	1 790	10 fois (32 % 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.	2	2 fois (6 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 28/09/2025 à 05h45 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

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 28/09/2025 à 05h45 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


{
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1759031153"
  }
}