Détails de la ressource
Les données horaires correspondent à l’ensemble de l’offre du réseau TLP Mobilités : les horaires de l’ensemble des lignes commerciales et les informations géographiques associées (topographie du réseau).
Cette ressource fait partie du jeu de données Réseau urbain TLP.
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
❌385 erreurs, 4 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 23/11/2024 à 08h08 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 36 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
- vehicle_id zenbus:Vehicle:887170002:LOC trip_id 4896235301371904:1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4896235301371904:1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 5155106674704384:0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:893260002:LOC trip_id 5205932977946624:1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 5205932977946624:1 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 36 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- vehicle_id zenbus:Vehicle:887170002:LOC route_id zenbus:Line:860950003:LOC does not exist in the GTFS data routes.txt
- route_id zenbus:Line:860950003:LOC does not exist in the GTFS data routes.txt
- route_id zenbus:Line:855090008:LOC does not exist in the GTFS data routes.txt
- vehicle_id zenbus:Vehicle:893260002:LOC route_id zenbus:Line:853230005:LOC does not exist in the GTFS data routes.txt
- route_id zenbus:Line:853230005:LOC does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 313 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id zenbus:Vehicle:887170002:LOC stop_id zenbus:StopPoint:SP:904950007:LOC does not exist in GTFS data stops.txt
- trip_id 4896235301371904:1 stop_id zenbus:StopPoint:SP:904950007:LOC does not exist in GTFS data stops.txt
- trip_id 4896235301371904:1 stop_id zenbus:StopPoint:SP:908930002:LOC does not exist in GTFS data stops.txt
- trip_id 4896235301371904:1 stop_id zenbus:StopPoint:SP:851280012:LOC does not exist in GTFS data stops.txt
- trip_id 4896235301371904:1 stop_id zenbus:StopPoint:SP:906860012:LOC does not exist in GTFS data stops.txt
Avertissements
vehicle_id not populated W002 2 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 5155106674704384:0 does not have a vehicle_id
- trip_id 4801417224126464:1 does not have a vehicle_id
ID in one feed missing from the other W003 2 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
- trip_id 5155106674704384:0 is in TripUpdates but not in VehiclePositions feed
- trip_id 4801417224126464:1 is in TripUpdates but not in VehiclePositions feed
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 |
---|---|---|---|
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 199 | 23 fois (88 % des validations) |
E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 199 | 23 fois (88 % des validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 9 209 | 23 fois (88 % des validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 37 | 21 fois (81 % 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 | 37 | 21 fois (81 % des validations) |
W008 | The data in a GTFS-realtime feed should always be less than one minute old | 3 | 3 fois (12 % des validations) |
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 2 | 2 fois (8 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 24/11/2024 à 01h21 Europe/Paris.
trip_updates (2) vehicle_positions (2) service_alerts (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updates vehicle_positionsFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 24/11/2024 à 01h21 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"entity": [
{
"id": "zenbus:Vehicle:887170002:LOC",
"vehicle": {
"current_status": "IN_TRANSIT_TO",
"current_stop_sequence": 18,
"position": {
"latitude": 43.12810134887695,
"longitude": -0.029260000213980675
},
"stop_id": "zenbus:StopPoint:SP:882880006:LOC",
"timestamp": "1732407216",
"trip": {
"route_id": "zenbus:Line:860950003:LOC",
"start_date": "20241123",
"start_time": "18:35:00",
"trip_id": "5998217578676224:11"
},
"vehicle": {
"id": "zenbus:Vehicle:887170002:LOC"
}
}
},
{
"id": "20241123:4821015227006976:11",
"trip_update": {
"stop_time_update": [
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:906860018:LOC",
"stop_sequence": 17
},
{
"arrival": {
"time": "1732407926"
},
"departure": {
"time": "1732407936"
},
"stop_id": "zenbus:StopPoint:SP:882880006:LOC",
"stop_sequence": 18
}
],
"timestamp": "1732407636",
"trip": {
"route_id": "zenbus:Line:860950003:LOC",
"start_date": "20241123",
"start_time": "18:35:00",
"trip_id": "5998217578676224:11"
},
"vehicle": {
"id": "zenbus:Vehicle:887170002:LOC"
}
}
},
{
"id": "zenbus:Vehicle:889230002:LOC",
"vehicle": {
"current_status": "IN_TRANSIT_TO",
"current_stop_sequence": 18,
"position": {
"latitude": 43.24126052856445,
"longitude": 0.014639000408351421
},
"stop_id": "zenbus:StopPoint:SP:723140019:LOC",
"timestamp": "1732407701",
"trip": {
"route_id": "zenbus:Line:835930009:LOC",
"start_date": "20241123",
"start_time": "20:10:00",
"trip_id": "5075828826177536:13"
},
"vehicle": {
"id": "zenbus:Vehicle:889230002:LOC"
}
}
},
{
"id": "20241123:5131564610486272:13",
"trip_update": {
"stop_time_update": [
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:904970009:LOC",
"stop_sequence": 14
},
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:880890014:LOC",
"stop_sequence": 15
},
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:910860007:LOC",
"stop_sequence": 16
},
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:912830006:LOC",
"stop_sequence": 17
},
{
"arrival": {
"time": "1732408172"
},
"departure": {
"time": "1732408182"
},
"stop_id": "zenbus:StopPoint:SP:723140019:LOC",
"stop_sequence": 18
}
],
"timestamp": "1732407703",
"trip": {
"route_id": "zenbus:Line:835930009:LOC",
"start_date": "20241123",
"start_time": "20:10:00",
"trip_id": "5075828826177536:13"
},
"vehicle": {
"id": "zenbus:Vehicle:889230002:LOC"
}
}
}
],
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1732407703"
}
}