Jeu de données ouvert gtfs-rt - GTFS RT pour Réseau urbain TADAO - CA de Lens

Détails de la ressource

Nom du fichier : GTFS RT

Format : gtfs-rt

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

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

❌961 erreurs, 210 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 20/09/2026 à 09h11 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

Sequential stop_time_update times are not increasing E022 72 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 12991183 stop_sequence 32 arrival_time 09:29:08 (1789889348) is less than previous stop arrival_time 09:29:23 (1789889363) - times must increase between two sequential stops
trip_id 12991183 stop_sequence 32 arrival_time 09:29:08 (1789889348) is less than previous stop departure_time 09:29:23 (1789889363) - times must increase between two sequential stops
trip_id 12991183 stop_sequence 32 departure_time 09:29:08 (1789889348) is less than previous stop departure_time 09:29:23 (1789889363) - times must increase between two sequential stops
trip_id 12991183 stop_sequence 32 departure_time 09:29:08 (1789889348) is less than previous stop arrival_time 09:29:23 (1789889363) - times must increase between two sequential stops
trip_id 12990917 stop_sequence 31 arrival_time 09:32:00 (1789889520) is less than previous stop arrival_time 09:45:26 (1789890326) - times must increase between two sequential stops

Vehicle position far from trip shape E029 1 erreur

The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.

Exemples d'erreurs

vehicle.id 8016 trip_id 13102959 at (50.455486,2.548299) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR

Sequential stop_time_updates have the same stop_id E037 5 erreurs

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Exemples d'erreurs

trip_id 13164100 has repeating stop_id BET1HDPO at stop_sequence 11 - sequential stop_ids should be different
trip_id 13104447 has repeating stop_id AVI2BH23 at stop_sequence 23 - sequential stop_ids should be different
trip_id 13094339 has repeating stop_id SAL1HDVS at stop_sequence 30 - sequential stop_ids should be different
trip_id 13094304 has repeating stop_id SAL2LAO2 at stop_sequence 18 - sequential stop_ids should be different
trip_id 13104490 has repeating stop_id LEN1GAR1 at stop_sequence 14 - sequential stop_ids should be different

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 879 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 13102954 stop_sequence 31 has stop_id HOU2BH01 but GTFS stop_sequence 31 has stop_id HOU2BH03 - stop_ids should be the same
GTFS-rt trip_id 13102954 stop_sequence 32 has stop_id HOU2BH03 but GTFS stop_sequence 32 has stop_id HOU2PLAC - stop_ids should be the same
GTFS-rt trip_id 13104435 stop_sequence 1 has stop_id AVI1PLEB but GTFS stop_sequence 1 has stop_id AVI1REPU - stop_ids should be the same
GTFS-rt trip_id 13104435 stop_sequence 2 has stop_id AVI1REPU but GTFS stop_sequence 2 has stop_id AVI1BH23 - stop_ids should be the same
GTFS-rt trip_id 13102979 stop_sequence 1 has stop_id BEU1BA02 but GTFS stop_sequence 1 has stop_id BEU2BH02 - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 4 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 12990985 contains stop_sequence 27 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 12990917 contains stop_sequence 61 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 13094311 contains stop_sequence 39 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 13104421 contains stop_sequence 24 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 46 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs

trip_id 12990985 does not have a timestamp
trip_id 13102954 does not have a timestamp
trip_id 13104435 does not have a timestamp
trip_id 13102979 does not have a timestamp
trip_id 12991224 does not have a timestamp

vehicle_id not populated W002 21 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id 12990985 does not have a vehicle_id
trip_id 13102954 does not have a vehicle_id
trip_id 13104435 does not have a vehicle_id
trip_id 13102979 does not have a vehicle_id
trip_id 12991224 does not have a vehicle_id

ID in one feed missing from the other W003 25 erreurs

a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed

Exemples d'erreurs

vehicle_id 5617 is in VehiclePositions but not in TripUpdates feed
trip_id 13104433 is in VehiclePositions but not in TripUpdates feed
vehicle_id 3401 is in VehiclePositions but not in TripUpdates feed
trip_id 13110548 is in VehiclePositions but not in TripUpdates feed
trip_id 12990904 is in TripUpdates but not in VehiclePositions feed

schedule_relationship not populated W009 118 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs

trip_id 12990985 stop_sequence 27 (and potentially more for this trip) does not have a schedule_relationship
trip_id 12990985 does not have a schedule_relationship
trip_id 13102954 does not have a schedule_relationship
trip_id 13104435 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 13104435 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
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	6 662	30 fois (100 % 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	60 512	30 fois (100 % des validations)
W001	Timestamps should be populated for all elements	5 121	30 fois (100 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	3 211	30 fois (100 % des validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	12 345	30 fois (100 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	308	29 fois (97 % des validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	536	29 fois (97 % des validations)
W003	a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed	3 762	28 fois (93 % des validations)
E029	The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.	138	17 fois (57 % des validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	18	10 fois (33 % des validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	19	10 fois (33 % des validations)
E047	If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.	10	7 fois (23 % des validations)
E028	The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt.	1	1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 21/09/2026 à 03h44 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 vehicle_positions

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 21/09/2026 à 03h44 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


        {
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1789955081"
  }
}