Détails de la ressource
Flux GTFS RT du réseau Aléop Pays de la Loire : Horaires temps réel
Cette ressource fait partie du jeu de données Réseaux interurbains Aléop - Pays de la Loire.
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
❌1 123 erreurs, 138 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 03/04/2025 à 09h12 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 108 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 FR:ServiceJourney::SN859502FERRE_3996269 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id FR:ServiceJourney::SN858407FERRE_4008403 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id FR:ServiceJourney::SN858408FERRE_4008406 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id FR:ServiceJourney::SN858307FERRE_4000925 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id FR:ServiceJourney::SN464081ROUTIER_4006849 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 108 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id T1 does not exist in the GTFS data routes.txt
- route_id 01b does not exist in the GTFS data routes.txt
- route_id 01b does not exist in the GTFS data routes.txt
- route_id 02 does not exist in the GTFS data routes.txt
- route_id 25 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 869 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id FR:ServiceJourney::SN859502FERRE_3996269 stop_id SNCF:87481002 does not exist in GTFS data stops.txt
- trip_id FR:ServiceJourney::SN859502FERRE_3996269 stop_id SNCF:87590331 does not exist in GTFS data stops.txt
- trip_id FR:ServiceJourney::SN859502FERRE_3996269 stop_id SNCF:87590349 does not exist in GTFS data stops.txt
- trip_id FR:ServiceJourney::SN859502FERRE_3996269 stop_id SNCF:87590356 does not exist in GTFS data stops.txt
- trip_id FR:ServiceJourney::SN859502FERRE_3996269 stop_id SNCF:87481564 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 37 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 312|23438934:T35|9:10:00 stop_sequence 12 arrival_time 09:22:10 (1743664930) is equal to previous stop arrival_time 09:22:10 (1743664930) - times must increase between two sequential stops
- trip_id 312|23438934:T35|9:10:00 stop_sequence 12 arrival_time 09:22:10 (1743664930) is equal to previous stop departure_time 09:22:10 (1743664930) - times must increase between two sequential stops
- trip_id 312|23438934:T35|9:10:00 stop_sequence 12 departure_time 09:22:10 (1743664930) is equal to previous stop departure_time 09:22:10 (1743664930) - times must increase between two sequential stops
- trip_id 312|23438934:T35|9:10:00 stop_sequence 12 departure_time 09:22:10 (1743664930) is equal to previous stop arrival_time 09:22:10 (1743664930) - times must increase between two sequential stops
- trip_id 312|23457316:T7|8:58:00 stop_sequence 15 arrival_time 09:16:10 (1743664570) is equal to previous stop arrival_time 09:16:10 (1743664570) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 1 erreur
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.
Exemples d'erreurs
- trip_id FR:ServiceJourney::SN857505FERRE_4008129 stop_sequence 4 departure_time 08:11:00 (1743660660) is less than the same stop arrival_time 08:15:00 (1743660900) - departure time must be equal to or greater than arrival time
Avertissements
vehicle_id not populated W002 138 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 300|25889906:T11|10:15:00 does not have a vehicle_id
- trip_id 300|25889906:T21|13:00:00 does not have a vehicle_id
- trip_id 300|25889905:T12|7:08:00 does not have a vehicle_id
- trip_id 300|25889905:T19|7:30:00 does not have a vehicle_id
- trip_id 300|25889905:T36|9:58:00 does not have a vehicle_id
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 | 4 466 | 30 fois (100 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 3 822 | 28 fois (93 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 3 755 | 28 fois (93 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 30 606 | 28 fois (93 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 817 | 26 fois (87 % 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. | 59 | 22 fois (73 % 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 | 2 fois (7 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 04/04/2025 à 00h51 Europe/Paris.
trip_updates (1) vehicle_positions (0) service_alerts (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 04/04/2025 à 00h51 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"entity": [
{
"id": "RT|FR:ServiceJourney::SN464012ROUTIER_4006854|464012",
"trip_update": {
"stop_time_update": [
{
"departure": {
"delay": 0,
"time": "1743727620",
"uncertainty": 60
},
"stop_id": "SNCF:87396002",
"stop_sequence": 0
},
{
"arrival": {
"delay": 0,
"time": "1743730620",
"uncertainty": 60
},
"departure": {
"delay": 0,
"time": "1743730620",
"uncertainty": 60
},
"stop_id": "SNCF:87396325",
"stop_sequence": 1
},
{
"arrival": {
"delay": 0,
"time": "1743732300",
"uncertainty": 60
},
"stop_id": "SNCF:87394296",
"stop_sequence": 2
}
],
"timestamp": "1743720683",
"trip": {
"direction_id": 0,
"route_id": "23",
"schedule_relationship": "SCHEDULED",
"start_date": "20250404",
"trip_id": "FR:ServiceJourney::SN464012ROUTIER_4006854"
}
}
}
],
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743720683"
}
}