Jeu de données ouvert gtfs-rt - Réseau Alternéo - RT - service Trip Update pour Réseau urbain Alternéo - CA CIVIS (Communauté Intercommunale des Villes Solidaires)

Détails de la ressource

Nom du fichier : Réseau Alternéo - RT - service Trip Update

Format : gtfs-rt

Flux GTFS-RT service Trip Update

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

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

❌150 erreurs, 180 avertissements

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

Erreurs

stop_times_updates not strictly sorted E002 2 erreurs

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

Exemples d'erreurs

trip_id 0_61051550 stop_sequence [3, 4, 5, 6, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36] is not strictly sorted by increasing stop_sequence
trip_id 0_61051540 stop_sequence [3, 4, 5, 6, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36] is not strictly sorted by increasing stop_sequence

GTFS-rt stop_sequence isn't provided for trip that visits same stop_id more than once E009 2 erreurs

If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence

Exemples d'erreurs

trip_id 0_61051623 visits stop_id [0:17800C, 0:05343C] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
trip_id 0_61051629 visits stop_id [0:17800C, 0:05343C] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided

Sequential stop_time_update times are not increasing E022 70 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 0_61052300 stop_sequence 2 arrival_time 10:29:32 (1786170572) is equal to previous stop departure_time 10:29:32 (1786170572) - times must increase between two sequential stops
trip_id 0_61052300 stop_sequence 2 departure_time 10:29:32 (1786170572) is equal to previous stop departure_time 10:29:32 (1786170572) - times must increase between two sequential stops
trip_id 0_61052300 stop_sequence 24 arrival_time 10:49:33 (1786171773) is equal to previous stop arrival_time 10:49:33 (1786171773) - times must increase between two sequential stops
trip_id 0_61052300 stop_sequence 24 arrival_time 10:49:33 (1786171773) is equal to previous stop departure_time 10:49:33 (1786171773) - times must increase between two sequential stops
trip_id 0_61052300 stop_sequence 24 departure_time 10:49:33 (1786171773) is equal to previous stop departure_time 10:49:33 (1786171773) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 76 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 0_61051502 stop_sequence 10 has stop_id 0:04030C but GTFS stop_sequence 10 has stop_id 0:13010C - stop_ids should be the same
GTFS-rt trip_id 0_61051502 stop_sequence 11 has stop_id 0:04040C but GTFS stop_sequence 11 has stop_id 0:13020C - stop_ids should be the same
GTFS-rt trip_id 0_61051502 stop_sequence 12 has stop_id 0:04050C but GTFS stop_sequence 12 has stop_id 0:13030C - stop_ids should be the same
GTFS-rt trip_id 0_61051502 stop_sequence 13 has stop_id 0:04060C but GTFS stop_sequence 13 has stop_id 0:04050C - stop_ids should be the same
GTFS-rt trip_id 0_61051502 stop_sequence 14 has stop_id 0:04070C but GTFS stop_sequence 14 has stop_id 0:04060C - stop_ids should be the same

Avertissements

timestamp not populated W001 111 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs

trip_id 0_61052300 does not have a timestamp
trip_id 0_61052301 does not have a timestamp
trip_id 0_61052553 does not have a timestamp
trip_id 0_61052548 does not have a timestamp
trip_id 0_61052509 does not have a timestamp

vehicle_id not populated W002 69 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id 0_61052301 does not have a vehicle_id
trip_id 0_61052553 does not have a vehicle_id
trip_id 0_61052509 does not have a vehicle_id
trip_id 0_61052323 does not have a vehicle_id
trip_id 0_61051673 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	112	29 fois (100 % des validations)
E009	If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence	61	29 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.	3 623	29 fois (100 % des validations)
W001	Timestamps should be populated for all elements	2 863	29 fois (100 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	1 839	29 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	1 292	24 fois (83 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	6	3 fois (10 % 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.	1	1 fois (3 % des validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	1	1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 08/08/2026 à 23h18 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 08/08/2026 à 23h18 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


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