Détails de la ressource
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
En savoir plus
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
❌135 erreurs, 18 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 13/09/2025 à 09h05 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:5981979217494016x0:LOC stop_sequence [9, 19, 5, 11, 18, 23, 12, 10, 25, 6, 16, 8, 3, 17, 15, 4, 7, 20, 14, 22, 13, 21, 24, 1, 2] is not strictly sorted by increasing stop_sequence
- trip_id ATOUMOD036:ServiceJourney:4827457917026304x0:LOC stop_sequence [6, 5, 7, 2, 1, 8, 11, 4, 9, 3] is not strictly sorted by increasing stop_sequence
- trip_id ATOUMOD036:ServiceJourney:4777455203123200x1:LOC stop_sequence [9, 8, 10, 11] is not strictly sorted by increasing stop_sequence
- trip_id ATOUMOD036:ServiceJourney:5521543422541824x2:LOC stop_sequence [11, 4, 2, 14, 13, 10, 9, 3, 1, 12] is not strictly sorted by increasing stop_sequence
- trip_id ATOUMOD036:ServiceJourney:6527488952893440x3:LOC stop_sequence [17, 10, 16, 24, 3, 9, 14, 2, 18, 7, 25, 15, 13, 4, 21, 23, 6, 11, 20, 22, 8, 12] 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 6 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:5981979217494016x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ATOUMOD036:ServiceJourney:4827457917026304x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ATOUMOD036:ServiceJourney:4777455203123200x1:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ATOUMOD036:ServiceJourney:5521543422541824x2:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ATOUMOD036:ServiceJourney:6527488952893440x3:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt stop_id does not exist in GTFS data E011 1 erreur
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id ATOUMOD036:ServiceJourney:5981979217494016x0:LOC stop_id FR:14478:ZE:4507111473020928:ATOUMOD036 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 122 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:5981979217494016x0:LOC stop_sequence 5 arrival_time 09:02:30 (1757746950) is less than previous stop arrival_time 09:34:07 (1757748847) - times must increase between two sequential stops
- trip_id ATOUMOD036:ServiceJourney:5981979217494016x0:LOC stop_sequence 5 arrival_time 09:02:30 (1757746950) is less than previous stop departure_time 09:34:17 (1757748857) - times must increase between two sequential stops
- trip_id ATOUMOD036:ServiceJourney:5981979217494016x0:LOC stop_sequence 5 departure_time 09:02:34 (1757746954) is less than previous stop departure_time 09:34:17 (1757748857) - times must increase between two sequential stops
- trip_id ATOUMOD036:ServiceJourney:5981979217494016x0:LOC stop_sequence 5 departure_time 09:02:34 (1757746954) is less than previous stop arrival_time 09:34:07 (1757748847) - times must increase between two sequential stops
- trip_id ATOUMOD036:ServiceJourney:5981979217494016x0:LOC stop_sequence 12 arrival_time 09:22:24 (1757748144) is less than previous stop arrival_time 09:38:40 (1757749120) - times must increase between two sequential stops
Avertissements
vehicle_id not populated W002 6 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id ATOUMOD036:ServiceJourney:5981979217494016x0:LOC does not have a vehicle_id
- trip_id ATOUMOD036:ServiceJourney:4827457917026304x0:LOC does not have a vehicle_id
- trip_id ATOUMOD036:ServiceJourney:4777455203123200x1:LOC does not have a vehicle_id
- trip_id ATOUMOD036:ServiceJourney:5521543422541824x2:LOC does not have a vehicle_id
- trip_id ATOUMOD036:ServiceJourney:6527488952893440x3:LOC does not have a vehicle_id
schedule_relationship not populated W009 12 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id ATOUMOD036:ServiceJourney:5981979217494016x0:LOC stop_sequence 9 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:5981979217494016x0:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:4827457917026304x0:LOC stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:4827457917026304x0:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:4777455203123200x1:LOC stop_sequence 9 (and potentially more for this trip) does not have a schedule_relationship
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 | 60 | 22 fois (71 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 2 196 | 22 fois (71 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 119 | 22 fois (71 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 238 | 22 fois (71 % des validations) |
| E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 103 | 18 fois (58 % 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 | 42 | 18 fois (58 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 73 | 18 fois (58 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 16 | 4 fois (13 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3 | 3 fois (10 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 14/09/2025 à 08h02 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updatesFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 14/09/2025 à 08h02 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1757829758"
}
}