Jeu de données ouvert gtfs-rt - Temps réel GTFS-RT TripUpdate pour Réseau urbain Mistral

Détails de la ressource

Nom du fichier : Temps réel GTFS-RT TripUpdate

Format : gtfs-rt

Horaires de prochains passages aux arrêts

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

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

❌523 erreurs, 227 avertissements

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

Erreurs

stop_times_updates not strictly sorted E002 19 erreurs

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

Exemples d'erreurs

trip_id 5177677 stop_sequence for stop_ids [VAVAGN, VAVAGS, GACAMS, GA4CH4, GAUNSN, GAHOPO, GATRIN, GAJAVO, GAGPHO, GAHVIO, GAPOSO, GAGYGN, GAROLN, GABSJE, GADAUE, GAPATN, GASAVN, GAOASN, GANOLN, GALSMN, GAGINN, TOPSUE, TOEPSN, TOCNRE, TOFDCN, TOPALE, TOPRAO, TOBRTN, TOASSN, TOPSJN, TOEGLN, TOREGN, TOMERN, TOAMIN, TOCMAN, TOCLEN, TOSTRN, TOLIBI, TOPOBN, TOCASN, TOFOCN, TOBIDN, TOPDSN, TOBNRN, TOBRCN, TOBRE4, TOSTBN, TOPCAN, TOCILO, TOLYSN, TOOCLN, TOPYRN, SEGARO, SECITN, SEWALN, SEBTON, SEPELO, SEBTHS, SEHOPO, SEPEYS, SEGAGO, SEROLO, SECENS, SEPCHS, SESEYS] is not strictly sorted by increasing stop_sequence
trip_id 5177678 stop_sequence for stop_ids [VAVAGN, VAVAGS, GACAMS, GA4CH4, GAUNSN, GAHOPO, GATRIN, GAJAVO, GAGPHO, GAHVIO, GAPOSO, GAGYGN, GAROLN, GABSJE, GADAUE, GAPATN, GASAVN, GAOASN, GANOLN, GALSMN, GAGINN, TOPSUE, TOEPSN, TOCNRE, TOFDCN, TOPALE, TOPRAO, TOBRTN, TOASSN, TOPSJN, TOEGLN, TOREGN, TOMERN, TOAMIN, TOCMAN, TOCLEN, TOSTRN, TOLIBI, TOPOBN, TOCASN, TOFOCN, TOBIDN, TOPDSN, TOBNRN, TOBRCN, TOBRE4, TOSTBN, TOPCAN, TOCILO, TOLYSN, TOOCLN, TOPYRN, SEGARO, SECITN, SEWALN, SEBTON, SEPELO, SEBTHS, SEHOPO, SEPEYS, SEGAGO, SEROLO, SECENS, SEPCHS, SESEYS] is not strictly sorted by increasing stop_sequence
trip_id 5177679 stop_sequence for stop_ids [VAVAGN, VAVAGS, GACAMS, GA4CH4, GAUNSN, GAHOPO, GATRIN, GAJAVO, GAGPHO, GAHVIO, GAPOSO, GAGYGN, GAROLN, GABSJE, GADAUE, GAPATN, GASAVN, GAOASN, GANOLN, GALSMN, GAGINN, TOPSUE, TOEPSN, TOCNRE, TOFDCN, TOPALE, TOPRAO, TOBRTN, TOASSN, TOPSJN, TOEGLN, TOREGN, TOMERN, TOAMIN, TOCMAN, TOCLEN, TOSTRN, TOLIBI, TOPOBN, TOCASN, TOFOCN, TOBIDN, TOPDSN, TOBNRN, TOBRCN, TOBRE4, TOSTBN, TOPCAN, TOCILO, TOLYSN, TOOCLN, TOPYRN, SEGARO, SECITN, SEWALN, SEBTON, SEPELO, SEBTHS, SEHOPO, SEPEYS, SEGAGO, SEROLO, SECENS, SEPCHS, SESEYS] is not strictly sorted by increasing stop_sequence
trip_id 5177681 stop_sequence for stop_ids [VAVAGN, VAVAGS, GACAMS, GA4CH4, GAUNSN, GAHOPO, GATRIN, GAJAVO, GAGPHO, GAHVIO, GAPOSO, GAGYGN, GAROLN, GABSJE, GADAUE, GAPATN, GASAVN, GAOASN, GANOLN, GALSMN, GAGINN, TOPSUE, TOEPSN, TOCNRE, TOFDCN, TOPALE, TOPRAO, TOBRTN, TOASSN, TOPSJN, TOEGLN, TOREGN, TOMERN, TOAMIN, TOCMAN, TOCLEN, TOSTRN, TOLIBI, TOPOBN, TOCASN, TOFOCN, TOBIDN, TOPDSN, TOBNRN, TOBRCN, TOBRE4, TOSTBN, TOPCAN, TOCILO, TOLYSN, TOOCLN, TOPYRN, SEGARO, SECITN, SEWALN, SEBTON, SEPELO, SEBTHS, SEHOPO, SEPEYS, SEGAGO, SEROLO, SECENS, SEPCHS, SESEYS] is not strictly sorted by increasing stop_sequence
trip_id 5177675 stop_sequence for stop_ids [VAVAGN, VAVAGS, GACAMS, GA4CH4, GAUNSN, GAHOPO, GATRIN, GAJAVO, GAGPHO, GAHVIO, GAPOSO, GAGYGN, GAROLN, GABSJE, GADAUE, GAPATN, GASAVN, GAOASN, GANOLN, GALSMN, GAGINN, TOPSUE, TOEPSN, TOCNRE, TOFDCN, TOPALE, TOPRAO, TOBRTN, TOASSN, TOPSJN, TOEGLN, TOREGN, TOMERN, TOAMIN, TOCMAN, TOCLEN, TOSTRN, TOLIBI, TOPOBN, TOCASN, TOFOCN, TOBIDN, TOPDSN, TOBNRN, TOBRCN, TOBRE4, TOSTBN, TOPCAN, TOCILO, TOLYSN, TOOCLN, TOPYRN, SEGARO, SECITN, SEWALN, SEBTON, SEPELO, SEBTHS, SEHOPO, SEPEYS, SEGAGO, SEROLO, SECENS, SEPCHS, SESEYS] 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 5 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 9527 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 9555 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 9556 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 400102 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 400105 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 5 erreurs

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

Exemples d'erreurs

route_id 0095 does not exist in the GTFS data routes.txt
route_id 0095 does not exist in the GTFS data routes.txt
route_id 0095 does not exist in the GTFS data routes.txt
route_id 4001 does not exist in the GTFS data routes.txt
route_id 4001 does not exist in the GTFS data routes.txt

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

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

Exemples d'erreurs

trip_id 5177677 stop_id GAGYGN does not exist in GTFS data stops.txt
trip_id 5177678 stop_id GAGYGN does not exist in GTFS data stops.txt
trip_id 5177679 stop_id GAGYGN does not exist in GTFS data stops.txt
trip_id 5177681 stop_id GAGYGN does not exist in GTFS data stops.txt
trip_id 5177675 stop_id GAGYGN does not exist in GTFS data stops.txt

Header timestamp should be greater than or equal to all other timestamps E012 118 erreurs

No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp

Exemples d'erreurs

trip_id 4968799 timestamp 1744700859 is greater than the header
trip_id 4968990 timestamp 1744700869 is greater than the header
trip_id 4968746 timestamp 1744700859 is greater than the header
trip_id 4968785 timestamp 1744700859 is greater than the header
trip_id 4968948 timestamp 1744700859 is greater than the header

Sequential stop_time_update times are not increasing E022 345 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 4968799 stop_id TOEGLN arrival_time 08:43:06 (1744699386) is equal to previous stop departure_time 08:43:06 (1744699386) - times must increase between two sequential stops
trip_id 4968990 stop_id TOPESS arrival_time 08:27:11 (1744698431) is equal to previous stop departure_time 08:27:11 (1744698431) - times must increase between two sequential stops
trip_id 4968990 stop_id VADEBS arrival_time 09:03:53 (1744700633) is equal to previous stop arrival_time 09:03:53 (1744700633) - times must increase between two sequential stops
trip_id 4968990 stop_id VADEBS arrival_time 09:03:53 (1744700633) is equal to previous stop departure_time 09:03:53 (1744700633) - times must increase between two sequential stops
trip_id 4968744 stop_id VALPVE arrival_time 08:53:56 (1744700036) is equal to previous stop departure_time 08:53:56 (1744700036) - 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 4974581 stop_id TOPESS departure_time 10:14:29 (1744704869) is less than the same stop arrival_time 10:14:30 (1744704870) - departure time must be equal to or greater than arrival time

Avertissements

vehicle_id not populated W002 227 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id 4968947 does not have a vehicle_id
trip_id 4968746 does not have a vehicle_id
trip_id 4968948 does not have a vehicle_id
trip_id 4968747 does not have a vehicle_id
trip_id 4968995 does not have a vehicle_id

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	513	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	128	30 fois (100 % des validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	128	30 fois (100 % des validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	755	30 fois (100 % des validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	10 344	30 fois (100 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	6 813	30 fois (100 % des validations)
E012	No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp	2 288	28 fois (93 % 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.	42	22 fois (73 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	1 066	10 fois (33 % des validations)

Contenu du flux GTFS-RT

Entités

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


{
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1744761138"
  }
}