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
❌288 erreurs, 113 avertissements
De nombreuses erreurs de validation indiquent que les identifiants du GTFS-RT ne correspondent pas aux identifiants du GTFS.
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 10/03/2026 à 08h10 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 27 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-739311617 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-671744001 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-755564545 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-604897281 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-689111041 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 27 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 40 does not exist in the GTFS data routes.txt
- route_id 45 does not exist in the GTFS data routes.txt
- route_id 36 does not exist in the GTFS data routes.txt
- route_id 41 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 227 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 1-739311617 stop_id 18205 does not exist in GTFS data stops.txt
- trip_id 1-739311617 stop_id 10763 does not exist in GTFS data stops.txt
- trip_id 1-739311617 stop_id 17663 does not exist in GTFS data stops.txt
- trip_id 1-739311617 stop_id 17963 does not exist in GTFS data stops.txt
- trip_id 1-739311617 stop_id 17876 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 1-689111041 stop_sequence 3 arrival_time 08:04:36 (1773126276) is equal to previous stop departure_time 08:04:36 (1773126276) - times must increase between two sequential stops
- trip_id 1-689111041 stop_sequence 5 arrival_time 08:05:30 (1773126330) is equal to previous stop departure_time 08:05:30 (1773126330) - times must increase between two sequential stops
- trip_id 1-689111041 stop_sequence 6 arrival_time 08:05:34 (1773126334) is equal to previous stop departure_time 08:05:34 (1773126334) - times must increase between two sequential stops
- trip_id 1-689111041 stop_sequence 7 arrival_time 08:05:36 (1773126336) is equal to previous stop departure_time 08:05:36 (1773126336) - times must increase between two sequential stops
- trip_id 1-689111041 stop_sequence 8 arrival_time 08:05:38 (1773126338) is equal to previous stop departure_time 08:05:38 (1773126338) - times must increase between two sequential stops
Avertissements
timestamp not populated W001 63 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 1-739311617 does not have a timestamp
- trip_id 1-671744001 does not have a timestamp
- trip_id 1-755564545 does not have a timestamp
- trip_id 1-604897281 does not have a timestamp
- trip_id 1-689111041 does not have a timestamp
vehicle_id not populated W002 50 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 1-621674499 does not have a vehicle_id
- trip_id 1-604962818 does not have a vehicle_id
- trip_id 1-353239041 does not have a vehicle_id
- trip_id 1-353173505 does not have a vehicle_id
- trip_id 1-638386178 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 137 | 23 fois (74 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 940 | 23 fois (74 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 323 | 13 fois (42 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 323 | 13 fois (42 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2 877 | 13 fois (42 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 43 | 8 fois (26 % 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. | 8 | 6 fois (19 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 11/03/2026 à 05h22 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 11/03/2026 à 05h22 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1773202931"
}
}