Détails de la ressource
Horaires temps-réel du réseau Envia
Cette ressource fait partie du jeu de données Réseau urbain Envia.
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
❌241 erreurs, 29 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 20/12/2024 à 08h05 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 4 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 1-1006698497 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-594739201-A50_5-LM_JV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-186777601-711-LM_JV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-857866253 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 2 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id 60 does not exist in the GTFS data routes.txt
- route_id 51 does not exist in the GTFS data routes.txt
Sequential stop_time_update times are not increasing E022 231 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 1-637599788 stop_sequence 17 arrival_time 08:05:13 (1734678313) is equal to previous stop departure_time 08:05:13 (1734678313) - times must increase between two sequential stops
- trip_id 1-637599788 stop_sequence 17 departure_time 08:05:13 (1734678313) is equal to previous stop departure_time 08:05:13 (1734678313) - times must increase between two sequential stops
- trip_id 1-637730821 stop_sequence 20 arrival_time 08:08:51 (1734678531) is equal to previous stop arrival_time 08:08:51 (1734678531) - times must increase between two sequential stops
- trip_id 1-637730821 stop_sequence 20 arrival_time 08:08:51 (1734678531) is equal to previous stop departure_time 08:08:51 (1734678531) - times must increase between two sequential stops
- trip_id 1-637730821 stop_sequence 20 departure_time 08:08:51 (1734678531) is equal to previous stop departure_time 08:08:51 (1734678531) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 2 erreurs
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 1-637730821 stop_sequence 17 departure_time 08:04:51 (1734678291) is less than the same stop arrival_time 08:04:52 (1734678292) - departure time must be equal to or greater than arrival time
- trip_id 1-522387473 stop_sequence 5 departure_time 08:04:04 (1734678244) is less than the same stop arrival_time 08:04:14 (1734678254) - departure time must be equal to or greater than arrival time
Sequential stop_time_updates have the same stop_id E037 2 erreurs
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Exemples d'erreurs
- trip_id 1-1006698497 has repeating stop_id 421 at stop_sequence 2 - sequential stop_ids should be different
- trip_id 1-857866253 has repeating stop_id 812 at stop_sequence 2 - sequential stop_ids should be different
Avertissements
timestamp not populated W001 29 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 1-1006698497 does not have a timestamp
- trip_id 1-180289537 does not have a timestamp
- trip_id 1-671154180 does not have a timestamp
- trip_id 1-594739201-A50_5-LM_JV__ does not have a timestamp
- trip_id 1-671285253 does not have a timestamp
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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 3 779 | 29 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 633 | 29 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 | 75 | 23 fois (79 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 26 | 20 fois (69 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 26 | 20 fois (69 % 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. | 25 | 12 fois (41 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 22/12/2024 à 04h44 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (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 22/12/2024 à 04h44 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1734839077"
}
}