Détails de la ressource
Cette ressource fait partie du jeu de données Réseau scolaire de Flers.
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
❌26 erreurs, 21 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 17/11/2026 à 08h13 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
GTFS-rt stop_id does not exist in GTFS data E011 5 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id T17 stop_id 132 does not exist in GTFS data stops.txt
- trip_id T37 stop_id 347 does not exist in GTFS data stops.txt
- trip_id T30 stop_id 347 does not exist in GTFS data stops.txt
- trip_id T30 stop_id 347 does not exist in GTFS data stops.txt
- trip_id T30 stop_id 347 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 7 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 T24 stop_sequence 10 arrival_time 08:02:05 (1794898925) is less than previous stop departure_time 08:02:36 (1794898956) - times must increase between two sequential stops
- trip_id T24 stop_sequence 11 arrival_time 08:02:06 (1794898926) is less than previous stop departure_time 08:02:37 (1794898957) - times must increase between two sequential stops
- trip_id T24 stop_sequence 12 arrival_time 08:02:13 (1794898933) is less than previous stop departure_time 08:02:38 (1794898958) - times must increase between two sequential stops
- trip_id T30 stop_sequence 7 arrival_time 08:01:58 (1794898918) is less than previous stop arrival_time 08:29:06 (1794900546) - times must increase between two sequential stops
- trip_id T30 stop_sequence 7 arrival_time 08:01:58 (1794898918) is less than previous stop departure_time 08:29:06 (1794900546) - times must increase between two sequential stops
trip start_time does not match first GTFS arrival_time E023 1 erreur
For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip
Exemples d'erreurs
- GTFS-rt trip_id T28 start_time is 07:50:00 and GTFS initial arrival_time is 07:55:00 - times do not match
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 13 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 T17 stop_sequence 2 has stop_id 132 but GTFS stop_sequence 2 has stop_id 93 - stop_ids should be the same
- GTFS-rt trip_id T17 stop_sequence 3 has stop_id 93 but GTFS stop_sequence 3 has stop_id 82 - stop_ids should be the same
- GTFS-rt trip_id T17 stop_sequence 4 has stop_id 82 but GTFS stop_sequence 4 has stop_id 79 - stop_ids should be the same
- GTFS-rt trip_id T17 stop_sequence 5 has stop_id 79 but GTFS stop_sequence 5 has stop_id 61 - stop_ids should be the same
- GTFS-rt trip_id T17 stop_sequence 6 has stop_id 61 but GTFS stop_sequence 6 has stop_id 46 - stop_ids should be the same
Avertissements
timestamp not populated W001 21 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id T23 does not have a timestamp
- trip_id T24 does not have a timestamp
- trip_id T25 does not have a timestamp
- trip_id T5 does not have a timestamp
- trip_id T10 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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 209 | 11 fois (37 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 47 | 9 fois (30 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 50 | 9 fois (30 % 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 | 111 | 9 fois (30 % des validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 8 | 7 fois (23 % 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. | 11 | 4 fois (13 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 17/11/2026 à 21h42 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (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 17/11/2026 à 21h42 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1794948122"
}
}