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

❌136 erreurs, 351 avertissements

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

Erreurs

stop_times_updates not strictly sorted E002 34 erreurs

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

Exemples d'erreurs

trip_id 58695777 stop_sequence [1, 2, 3, 4, 5, 7, 8, 8] is not strictly sorted by increasing stop_sequence
trip_id 58695778 stop_sequence [1, 2, 3, 4, 5, 7, 8, 8] is not strictly sorted by increasing stop_sequence
trip_id 58695779 stop_sequence [1, 2, 3, 4, 5, 7, 8, 8] is not strictly sorted by increasing stop_sequence
trip_id 58695780 stop_sequence [1, 2, 3, 4, 5, 7, 8, 8] is not strictly sorted by increasing stop_sequence
trip_id 58695781 stop_sequence [1, 2, 3, 4, 5, 7, 8, 8] is not strictly sorted by increasing stop_sequence

Sequential stop_time_updates have the same stop_sequence E036 34 erreurs

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

Exemples d'erreurs

trip_id 58695777 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
trip_id 58695778 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
trip_id 58695779 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
trip_id 58695780 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
trip_id 58695781 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update

Sequential stop_time_updates have the same stop_id E037 34 erreurs

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

Exemples d'erreurs

trip_id 58695777 has repeating stop_id 160908 at stop_sequence 8 - sequential stop_ids should be different
trip_id 58695778 has repeating stop_id 160908 at stop_sequence 8 - sequential stop_ids should be different
trip_id 58695779 has repeating stop_id 160908 at stop_sequence 8 - sequential stop_ids should be different
trip_id 58695780 has repeating stop_id 160908 at stop_sequence 8 - sequential stop_ids should be different
trip_id 58695781 has repeating stop_id 160908 at stop_sequence 8 - sequential stop_ids should be different

GTFS-rt stop_sequence not found in GTFS data E051 34 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 58695777 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 58695778 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 58695779 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 58695780 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 58695781 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip

Avertissements

vehicle_id not populated W002 117 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id 2d263b0c-608f-43ba-8ebe-bf98d3d57c7c does not have a vehicle_id
trip_id 0bfcfb9d-851a-483b-997c-bdfad65c294e does not have a vehicle_id
trip_id 1e6a06ac-6fa4-479b-ad78-726045a68681 does not have a vehicle_id
trip_id 30c0b014-73aa-4a80-af0b-dcef7183fbcf does not have a vehicle_id
trip_id 540177df-8339-463d-8c0e-1788d711d1e8 does not have a vehicle_id

schedule_relationship not populated W009 234 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs

trip_id 2d263b0c-608f-43ba-8ebe-bf98d3d57c7c stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 2d263b0c-608f-43ba-8ebe-bf98d3d57c7c does not have a schedule_relationship
trip_id 0bfcfb9d-851a-483b-997c-bdfad65c294e stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 0bfcfb9d-851a-483b-997c-bdfad65c294e does not have a schedule_relationship
trip_id 1e6a06ac-6fa4-479b-ad78-726045a68681 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
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	2 098	21 fois (70 % des validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	4 196	21 fois (70 % des validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	597	20 fois (67 % des validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	597	20 fois (67 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	615	20 fois (67 % des validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	597	20 fois (67 % des validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	14	14 fois (47 % 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.	10	7 fois (23 % des validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	2	2 fois (7 % des validations)

Contenu du flux GTFS-RT

Entités

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


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