transport.data.gouv.fr transport.data.gouv.fr

Détails de la ressource

Nom du fichier : Données en temps réel des horaires aux arrêts du réseau Astrobus
Format : gtfs-rt
Télécharger

GTFS-RT (protobuff) des horaires aux arrêts

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

Disponibilité au téléchargement

05/03/2025
100%
06/03/2025
100%
07/03/2025
100%
08/03/2025
100%
09/03/2025
100%
10/03/2025
100%
11/03/2025
100%
12/03/2025
100%
13/03/2025
100%
14/03/2025
100%
15/03/2025
100%
16/03/2025
100%
17/03/2025
100%
18/03/2025
100%
19/03/2025
100%
20/03/2025
100%
21/03/2025
100%
22/03/2025
100%
23/03/2025
100%
24/03/2025
100%
25/03/2025
100%
26/03/2025
100%
27/03/2025
100%
28/03/2025
100%
29/03/2025
100%
30/03/2025
100%
31/03/2025
100%
01/04/2025
100%
02/04/2025
100%
03/04/2025
100%
04/04/2025
100%
En savoir plus
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

❌208 erreurs, 30 avertissements

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

Erreurs

stop_times_updates not strictly sorted E002 6 erreurs

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

Exemples d'erreurs
  • trip_id ATOUMOD036:ServiceJourney:5060085219852288x2:LOC stop_sequence [7, 12, 3] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD036:ServiceJourney:6556412902637568x5:LOC stop_sequence [4, 12, 2] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC stop_sequence [7, 5] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD036:ServiceJourney:6556412902637568x4:LOC stop_sequence [14, 21, 16] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD036:ServiceJourney:6556412902637568x6:LOC stop_sequence [21, 3] is not strictly sorted by increasing stop_sequence

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 3 erreurs

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Exemples d'erreurs
  • trip_id ATOUMOD036:ServiceJourney:5262133903228928x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD036:ServiceJourney:5016735846498304x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD036:ServiceJourney:5899329798668288x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 3 erreurs

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Exemples d'erreurs
  • route_id ATOUMOD036:Line:6459004587868160:LOC does not exist in the GTFS data routes.txt
  • route_id ATOUMOD036:Line:6484099108700160:LOC does not exist in the GTFS data routes.txt
  • route_id ATOUMOD036:Line:4818648599363584:LOC does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 3 erreurs

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Exemples d'erreurs
  • trip_id ATOUMOD036:ServiceJourney:5262133903228928x0:LOC stop_id FR:14574:ZE:5983181636370432:ATOUMOD036 does not exist in GTFS data stops.txt
  • trip_id ATOUMOD036:ServiceJourney:5262133903228928x0:LOC stop_id FR:14574:ZE:5374014747836416:ATOUMOD036 does not exist in GTFS data stops.txt
  • trip_id ATOUMOD036:ServiceJourney:5899329798668288x0:LOC stop_id FR:14654:ZE:5504460185927680:ATOUMOD036 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 174 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 ATOUMOD036:ServiceJourney:5060085219852288x2:LOC stop_sequence 3 arrival_time 08:58:33 (1743663513) is less than previous stop arrival_time 09:12:32 (1743664352) - times must increase between two sequential stops
  • trip_id ATOUMOD036:ServiceJourney:5060085219852288x2:LOC stop_sequence 3 arrival_time 08:58:33 (1743663513) is less than previous stop departure_time 09:12:42 (1743664362) - times must increase between two sequential stops
  • trip_id ATOUMOD036:ServiceJourney:5060085219852288x2:LOC stop_sequence 3 departure_time 08:58:49 (1743663529) is less than previous stop departure_time 09:12:42 (1743664362) - times must increase between two sequential stops
  • trip_id ATOUMOD036:ServiceJourney:5060085219852288x2:LOC stop_sequence 3 departure_time 08:58:49 (1743663529) is less than previous stop arrival_time 09:12:32 (1743664352) - times must increase between two sequential stops
  • trip_id ATOUMOD036:ServiceJourney:5060085219852288x2:LOC stop_sequence 5 arrival_time 09:04:23 (1743663863) is less than previous stop arrival_time 09:14:04 (1743664444) - times must increase between two sequential stops

trip direction_id does not match GTFS data E024 7 erreurs

GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt

Exemples d'erreurs
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:5060085219852288x2:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:6556412902637568x5:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:4792930217754624x6:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:6556412902637568x4:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 5 erreurs

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Exemples d'erreurs
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:6556412902637568x5:LOC stop_sequence 4 has stop_id FR:14366:ZE:35170002:ATOUMOD036 but GTFS stop_sequence 4 has stop_id FR:14366:ZE:678860002:ATOUMOD036 - stop_ids should be the same
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:6556412902637568x5:LOC stop_sequence 12 has stop_id FR:14366:ZE:35180002:ATOUMOD036 but GTFS stop_sequence 12 has stop_id FR:14366:ZE:33090002:ATOUMOD036 - stop_ids should be the same
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:6556412902637568x4:LOC stop_sequence 14 has stop_id FR:14366:ZE:33090002:ATOUMOD036 but GTFS stop_sequence 14 has stop_id FR:14366:ZE:310810014:ATOUMOD036 - stop_ids should be the same
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:6556412902637568x4:LOC stop_sequence 21 has stop_id FR:14366:ZE:7150003:ATOUMOD036 but GTFS stop_sequence 21 has stop_id FR:14366:ZE:3100004:ATOUMOD036 - stop_ids should be the same
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:6556412902637568x6:LOC stop_sequence 21 has stop_id FR:14366:ZE:7150003:ATOUMOD036 but GTFS stop_sequence 21 has stop_id FR:14366:ZE:3100004:ATOUMOD036 - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 7 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 ATOUMOD036:ServiceJourney:5060085219852288x2:LOC contains stop_sequence 3 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:6556412902637568x5:LOC contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:4792930217754624x6:LOC contains stop_sequence 24 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC contains stop_sequence 5 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:6556412902637568x4:LOC contains stop_sequence 16 that does not exist in GTFS stop_times.txt for this trip

Avertissements

vehicle_id not populated W002 10 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id ATOUMOD036:ServiceJourney:5060085219852288x2:LOC does not have a vehicle_id
  • trip_id ATOUMOD036:ServiceJourney:6556412902637568x5:LOC does not have a vehicle_id
  • trip_id ATOUMOD036:ServiceJourney:4792930217754624x6:LOC does not have a vehicle_id
  • trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC does not have a vehicle_id
  • trip_id ATOUMOD036:ServiceJourney:6556412902637568x4:LOC does not have a vehicle_id

schedule_relationship not populated W009 20 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs
  • trip_id ATOUMOD036:ServiceJourney:5060085219852288x2:LOC stop_sequence 7 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD036:ServiceJourney:5060085219852288x2:LOC does not have a schedule_relationship
  • trip_id ATOUMOD036:ServiceJourney:6556412902637568x5:LOC stop_sequence 4 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD036:ServiceJourney:6556412902637568x5:LOC does not have a schedule_relationship
  • trip_id ATOUMOD036:ServiceJourney:4792930217754624x6:LOC stop_sequence 24 (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
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 437 26 fois (87 % des validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 9 697 26 fois (87 % des validations)
E024 GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt 387 26 fois (87 % 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 172 26 fois (87 % des validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 269 26 fois (87 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 616 26 fois (87 % des validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 1 232 26 fois (87 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 229 20 fois (67 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 216 19 fois (63 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 796 19 fois (63 % des validations)

Contenu du flux GTFS-RT

Entités

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

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