Détails de la ressource
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- TripUpdate
Cette ressource fait partie du jeu de données Réseau urbain et scolaire Guingamp-Paimpol Mobilité.
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
❌186 erreurs, 91 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 30/01/2025 à 08h15 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 21 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-739180545 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-604766209 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-638189569 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-705363969 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-655097857 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 21 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id 44 does not exist in the GTFS data routes.txt
- route_id 36 does not exist in the GTFS data routes.txt
- route_id 38 does not exist in the GTFS data routes.txt
- route_id 42 does not exist in the GTFS data routes.txt
- route_id 39 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 139 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 1-739180545 stop_id 18205 does not exist in GTFS data stops.txt
- trip_id 1-739180545 stop_id 17663 does not exist in GTFS data stops.txt
- trip_id 1-739180545 stop_id 17963 does not exist in GTFS data stops.txt
- trip_id 1-739180545 stop_id 17876 does not exist in GTFS data stops.txt
- trip_id 1-739180545 stop_id 17465 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 4 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-705363969 stop_sequence 8 arrival_time 07:43:47 (1738219427) is less than previous stop arrival_time 08:14:04 (1738221244) - times must increase between two sequential stops
- trip_id 1-705363969 stop_sequence 8 arrival_time 07:43:47 (1738219427) is less than previous stop departure_time 08:14:23 (1738221263) - times must increase between two sequential stops
- trip_id 1-705363969 stop_sequence 8 departure_time 07:43:55 (1738219435) is less than previous stop departure_time 08:14:23 (1738221263) - times must increase between two sequential stops
- trip_id 1-705363969 stop_sequence 8 departure_time 07:43:55 (1738219435) is less than previous stop arrival_time 08:14:04 (1738221244) - 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 15-67371009 stop_sequence 11 departure_time 08:13:31 (1738221211) is less than the same stop arrival_time 08:14:29 (1738221269) - departure time must be equal to or greater than arrival time
Avertissements
timestamp not populated W001 51 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 1-739180545 does not have a timestamp
- trip_id 1-604766209 does not have a timestamp
- trip_id 1-638189569 does not have a timestamp
- trip_id 1-705363969 does not have a timestamp
- trip_id 15-67371009 does not have a timestamp
vehicle_id not populated W002 40 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 15-16908304 does not have a vehicle_id
- trip_id 15-16908305 does not have a vehicle_id
- trip_id 15-16908291 does not have a vehicle_id
- trip_id 15-16908292 does not have a vehicle_id
- trip_id 15-16908293 does not have a vehicle_id
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 | 1 074 | 21 fois (68 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 821 | 21 fois (68 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 465 | 19 fois (61 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 464 | 19 fois (61 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3 828 | 19 fois (61 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 22 | 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. | 10 | 7 fois (23 % des validations) |
| E041 | Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 31/01/2025 à 00h30 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 31/01/2025 à 00h30 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1738279832"
}
}