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

❌36 erreurs, 85 avertissements

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

Erreurs

stop_times_updates not strictly sorted E002 9 erreurs

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

Exemples d'erreurs

trip_id 58695790 stop_sequence [1, 2, 3, 4, 5, 7, 8, 8] is not strictly sorted by increasing stop_sequence
trip_id 58695791 stop_sequence [1, 2, 3, 4, 5, 7, 8, 8] is not strictly sorted by increasing stop_sequence
trip_id 58695792 stop_sequence [1, 2, 3, 4, 5, 7, 8, 9, 10, 10] is not strictly sorted by increasing stop_sequence
trip_id c65c6150-2f70-4693-a73a-d41ea6e56c24 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 11] is not strictly sorted by increasing stop_sequence
trip_id dfa876ea-70fa-4e4e-90a8-fe18fcdc954f stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 11] is not strictly sorted by increasing stop_sequence

Sequential stop_time_updates have the same stop_sequence E036 9 erreurs

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

Exemples d'erreurs

trip_id 58695790 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
trip_id 58695791 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
trip_id 58695792 has repeating stop_sequence 10 - stop_sequence must increase for each stop_time_update
trip_id c65c6150-2f70-4693-a73a-d41ea6e56c24 has repeating stop_sequence 11 - stop_sequence must increase for each stop_time_update
trip_id dfa876ea-70fa-4e4e-90a8-fe18fcdc954f has repeating stop_sequence 11 - stop_sequence must increase for each stop_time_update

Sequential stop_time_updates have the same stop_id E037 9 erreurs

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

Exemples d'erreurs

trip_id 58695790 has repeating stop_id 160908 at stop_sequence 8 - sequential stop_ids should be different
trip_id 58695791 has repeating stop_id 160908 at stop_sequence 8 - sequential stop_ids should be different
trip_id 58695792 has repeating stop_id 161016 at stop_sequence 10 - sequential stop_ids should be different
trip_id c65c6150-2f70-4693-a73a-d41ea6e56c24 has repeating stop_id 160884 at stop_sequence 11 - sequential stop_ids should be different
trip_id dfa876ea-70fa-4e4e-90a8-fe18fcdc954f has repeating stop_id 160884 at stop_sequence 11 - sequential stop_ids should be different

GTFS-rt stop_sequence not found in GTFS data E051 9 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 58695790 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 58695791 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 58695792 contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id c65c6150-2f70-4693-a73a-d41ea6e56c24 contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id dfa876ea-70fa-4e4e-90a8-fe18fcdc954f contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip

Avertissements

vehicle_id not populated W002 28 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id 78c3a9cc-4319-4d3e-b8a0-8e8bb047cae2 does not have a vehicle_id
trip_id 58695789 does not have a vehicle_id
trip_id 58695790 does not have a vehicle_id
trip_id 58695791 does not have a vehicle_id
trip_id 58695792 does not have a vehicle_id

Header timestamp is older than 65 seconds W008 1 erreur

The data in a GTFS-realtime feed should always be less than one minute old

Exemples d'erreurs

header.timestamp is 919 min 11 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 56 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs

trip_id 78c3a9cc-4319-4d3e-b8a0-8e8bb047cae2 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 78c3a9cc-4319-4d3e-b8a0-8e8bb047cae2 does not have a schedule_relationship
trip_id 58695789 stop_sequence 8 (and potentially more for this trip) does not have a schedule_relationship
trip_id 58695789 does not have a schedule_relationship
trip_id 58695790 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
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	679	24 fois (80 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	2 677	24 fois (80 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	535	22 fois (73 % des validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	494	16 fois (53 % 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.	28	16 fois (53 % des validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	494	16 fois (53 % des validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	3 436	16 fois (53 % des validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	2 356	10 fois (33 % des validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	38	8 fois (27 % des validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	1 229	8 fois (27 % 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	4 063	8 fois (27 % des validations)
W001	Timestamps should be populated for all elements	1 108	8 fois (27 % des validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	8	8 fois (27 % des validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	12	6 fois (20 % 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	6	6 fois (20 % des validations)
E023	For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip	2	2 fois (7 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 24/04/2025 à 00h23 Europe/Paris.

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

Le champ timestamp contient une valeur ancienne par rapport à la date courante : l'écart est de 24 218 secondes. Essayez de mettre à jour le flux toutes les 30 secondes au plus.

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 24/04/2025 à 00h23 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


{
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1745446998"
  }
}