Détails de la ressource
GTFS-RT pour le réseau urbain de Parthenay
Cette ressource fait partie du jeu de données Réseau urbain Pybus.
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
❌164 erreurs, 2 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 14/07/2025 à 09h03 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 10 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 60ddbcd0bb922d00013df8f1 trip_id C_23 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 686cec61688cf4e0d06c74f6 trip_id B_01 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 686cec19be97c0a2d3f4f810 trip_id A_01 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 60efd6e3556b6d0001d90ef8 trip_id Z_A_02 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id A_01 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 10 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- vehicle_id 60ddbcd0bb922d00013df8f1 route_id Ligne C does not exist in the GTFS data routes.txt
- vehicle_id 686cec61688cf4e0d06c74f6 route_id Ligne B does not exist in the GTFS data routes.txt
- vehicle_id 686cec19be97c0a2d3f4f810 route_id Ligne A does not exist in the GTFS data routes.txt
- vehicle_id 60efd6e3556b6d0001d90ef8 route_id Ligne Z does not exist in the GTFS data routes.txt
- route_id Ligne A does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 118 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id 60ddbcd0bb922d00013df8f1 stop_id MAISONSANTE_A does not exist in GTFS data stops.txt
- vehicle_id 686cec61688cf4e0d06c74f6 stop_id MAISONSANTE_A does not exist in GTFS data stops.txt
- vehicle_id 686cec19be97c0a2d3f4f810 stop_id PLACE-DARME_A does not exist in GTFS data stops.txt
- vehicle_id 60efd6e3556b6d0001d90ef8 stop_id PISCINE_AR does not exist in GTFS data stops.txt
- trip_id A_01 stop_id GARE-URB_AR does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 13 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 A_01 stop_sequence 13 arrival_time 08:59:10 (1752476350) is less than previous stop arrival_time 09:20:50 (1752477650) - times must increase between two sequential stops
- trip_id A_01 stop_sequence 13 arrival_time 08:59:10 (1752476350) is less than previous stop departure_time 09:20:50 (1752477650) - times must increase between two sequential stops
- trip_id C_22 stop_sequence 8 arrival_time 08:10:25 (1752473425) is less than previous stop arrival_time 08:16:04 (1752473764) - times must increase between two sequential stops
- trip_id C_23 stop_sequence 17 arrival_time 09:02:10 (1752476530) is less than previous stop arrival_time 09:36:30 (1752478590) - times must increase between two sequential stops
- trip_id C_23 stop_sequence 17 arrival_time 09:02:10 (1752476530) is less than previous stop departure_time 09:36:30 (1752478590) - 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 C_22 stop_sequence 7 departure_time 08:09:39 (1752473379) is less than the same stop arrival_time 08:16:04 (1752473764) - departure time must be equal to or greater than arrival time
Vehicle position outside agency coverage area E028 4 erreurs
The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt.
Exemples d'erreurs
- vehicle.id 60ddbcd0bb922d00013df8f1 at (47.000813,-2.2491078) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 686cec61688cf4e0d06c74f6 at (47.005047,-2.2551389) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 686cec19be97c0a2d3f4f810 at (46.999588,-2.2460735) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 60efd6e3556b6d0001d90ef8 at (46.99672,-2.2478292) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
Sequential stop_time_updates have the same stop_id E037 2 erreurs
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Exemples d'erreurs
- trip_id C_22 has repeating stop_id HERBAUPORT_TEC at stop_sequence 9 - sequential stop_ids should be different
- trip_id C_23 has repeating stop_id HERBAUPORT_TEC at stop_sequence 9 - sequential stop_ids should be different
stop_time_update doesn't have arrival or departure E043 4 erreurs
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Exemples d'erreurs
- trip_id C_22 stop_sequence 13 doesn't have arrival or departure
- trip_id Z_R_01 stop_sequence 0 doesn't have arrival or departure
- trip_id Z_R_01 stop_sequence 10 doesn't have arrival or departure
- trip_id Z_R_01 stop_sequence 19 doesn't have arrival or departure
VehiclePosition and TripUpdate ID pairing mismatch E047 2 erreurs
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Exemples d'erreurs
- trip_id Z_A_02 and vehicle_id 60efd6e3556b6d0001d90ef8 pairing in VehiclePositions does not match trip_id Z_R_01 and vehicle_id 60efd6e3556b6d0001d90ef8 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id A_01 and vehicle_id 686cec19be97c0a2d3f4f810 pairing in VehiclePositions does not match trip_id C_22 and vehicle_id 686cec19be97c0a2d3f4f810 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
Avertissements
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 C_22 is in TripUpdates but not in VehiclePositions feed
- trip_id Z_R_01 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 | 148 | 17 fois (57 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 148 | 17 fois (57 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 1 701 | 17 fois (57 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 153 | 17 fois (57 % des validations) |
| E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 66 | 17 fois (57 % 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 | 18 | 12 fois (40 % des validations) |
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 52 | 11 fois (37 % des validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 10 | 7 fois (23 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 5 | 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. | 2 | 2 fois (7 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 15/07/2025 à 01h45 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 vehicle_positionsFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 15/07/2025 à 01h45 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1752536703"
}
}