Jeu de données ouvert gtfs-rt - Horaires temps réel des lignes du réseau FORBUS pour Réseau urbain Forbus

Détails de la ressource

Nom du fichier : Horaires temps réel des lignes du réseau FORBUS

Format : gtfs-rt

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

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

❌116 erreurs, 411 avertissements

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

Erreurs

stop_times_updates not strictly sorted E002 29 erreurs

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

Exemples d'erreurs

trip_id 1c9da668-854b-4f28-b49b-53ac1542ee7e stop_sequence [1, 2, 3, 4, 5, 7, 8, 9, 10, 10] is not strictly sorted by increasing stop_sequence
trip_id 26ed67e0-d78b-4527-bd09-8c5d84318d4e stop_sequence [1, 2, 3, 4, 5, 7, 8, 9, 10, 10] is not strictly sorted by increasing stop_sequence
trip_id 42fb6533-419e-4fb5-a231-152667d73b51 stop_sequence [1, 2, 3, 4, 5, 7, 8, 9, 10, 10] is not strictly sorted by increasing stop_sequence
trip_id 4d8ad55c-f6b7-4400-9fd8-3c06e9828ecd stop_sequence [1, 2, 3, 4, 5, 7, 8, 9, 10, 10] is not strictly sorted by increasing stop_sequence
trip_id 555df099-5e0a-4bb9-9939-4c1328c633ab stop_sequence [1, 2, 3, 4, 5, 7, 8, 9, 10, 10] is not strictly sorted by increasing stop_sequence

Sequential stop_time_updates have the same stop_sequence E036 29 erreurs

Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence

Exemples d'erreurs

trip_id 1c9da668-854b-4f28-b49b-53ac1542ee7e has repeating stop_sequence 10 - stop_sequence must increase for each stop_time_update
trip_id 26ed67e0-d78b-4527-bd09-8c5d84318d4e has repeating stop_sequence 10 - stop_sequence must increase for each stop_time_update
trip_id 42fb6533-419e-4fb5-a231-152667d73b51 has repeating stop_sequence 10 - stop_sequence must increase for each stop_time_update
trip_id 4d8ad55c-f6b7-4400-9fd8-3c06e9828ecd has repeating stop_sequence 10 - stop_sequence must increase for each stop_time_update
trip_id 555df099-5e0a-4bb9-9939-4c1328c633ab has repeating stop_sequence 10 - stop_sequence must increase for each stop_time_update

Sequential stop_time_updates have the same stop_id E037 29 erreurs

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

Exemples d'erreurs

trip_id 1c9da668-854b-4f28-b49b-53ac1542ee7e has repeating stop_id 161016 at stop_sequence 10 - sequential stop_ids should be different
trip_id 26ed67e0-d78b-4527-bd09-8c5d84318d4e has repeating stop_id 161016 at stop_sequence 10 - sequential stop_ids should be different
trip_id 42fb6533-419e-4fb5-a231-152667d73b51 has repeating stop_id 161016 at stop_sequence 10 - sequential stop_ids should be different
trip_id 4d8ad55c-f6b7-4400-9fd8-3c06e9828ecd has repeating stop_id 161016 at stop_sequence 10 - sequential stop_ids should be different
trip_id 555df099-5e0a-4bb9-9939-4c1328c633ab has repeating stop_id 161016 at stop_sequence 10 - sequential stop_ids should be different

GTFS-rt stop_sequence not found in GTFS data E051 29 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 1c9da668-854b-4f28-b49b-53ac1542ee7e contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 26ed67e0-d78b-4527-bd09-8c5d84318d4e contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 42fb6533-419e-4fb5-a231-152667d73b51 contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 4d8ad55c-f6b7-4400-9fd8-3c06e9828ecd contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 555df099-5e0a-4bb9-9939-4c1328c633ab contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip

Avertissements

vehicle_id not populated W002 137 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id d81e2ee9-8481-415f-a4dd-430cb745ae0b does not have a vehicle_id
trip_id de699483-43a6-4e0b-849c-c21da008f2c9 does not have a vehicle_id
trip_id e36ad08e-03f6-4b1c-92c6-2d15278e3210 does not have a vehicle_id
trip_id e47399c3-0bb3-4e47-8a4c-d0a72f65424a does not have a vehicle_id
trip_id f32f42c9-9212-4b18-8ed1-8c88c9ff4293 does not have a vehicle_id

schedule_relationship not populated W009 274 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs

trip_id d81e2ee9-8481-415f-a4dd-430cb745ae0b stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id d81e2ee9-8481-415f-a4dd-430cb745ae0b does not have a schedule_relationship
trip_id de699483-43a6-4e0b-849c-c21da008f2c9 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id de699483-43a6-4e0b-849c-c21da008f2c9 does not have a schedule_relationship
trip_id e36ad08e-03f6-4b1c-92c6-2d15278e3210 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship

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
W008	The data in a GTFS-realtime feed should always be less than one minute old	20	20 fois (67 % des validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	238	13 fois (43 % des validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	238	13 fois (43 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	258	13 fois (43 % des validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	238	13 fois (43 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	1 304	13 fois (43 % des validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	2 608	13 fois (43 % 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.	3	2 fois (7 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 19/07/2025 à 04h07 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 19/07/2025 à 04h07 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


{
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1752890838"
  }
}