Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain Sète Agglopole 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
❌175 erreurs, 218 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 04/06/2025 à 09h10 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
stop_times_updates not strictly sorted E002 11 erreurs
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Exemples d'erreurs
- trip_id 87060_250604-4288 stop_sequence [0, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 13, 14] is not strictly sorted by increasing stop_sequence
- trip_id 87058_250604-4288 stop_sequence [0, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 13, 14] is not strictly sorted by increasing stop_sequence
- trip_id 87096_250604-4290 stop_sequence [0, 0, 16, 19, 20] is not strictly sorted by increasing stop_sequence
- trip_id 87094_250604-4290 stop_sequence [0, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 19, 20] is not strictly sorted by increasing stop_sequence
- trip_id 87095_250604-4300 stop_sequence [0, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 19, 20] is not strictly sorted by increasing stop_sequence
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 109 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 68616_250604-4281 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 68631_250604-4281 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 87106_250604-4287 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 87060_250604-4288 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 87036_250604-4288 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Sequential stop_time_update times are not increasing E022 44 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 87060_250604-4288 stop_sequence 1 arrival_time 09:10:00 (1749021000) is less than previous stop arrival_time 09:34:41 (1749022481) - times must increase between two sequential stops
- trip_id 87060_250604-4288 stop_sequence 1 arrival_time 09:10:00 (1749021000) is less than previous stop departure_time 09:34:41 (1749022481) - times must increase between two sequential stops
- trip_id 87060_250604-4288 stop_sequence 1 departure_time 09:10:00 (1749021000) is less than previous stop departure_time 09:34:41 (1749022481) - times must increase between two sequential stops
- trip_id 87060_250604-4288 stop_sequence 1 departure_time 09:10:00 (1749021000) is less than previous stop arrival_time 09:34:41 (1749022481) - times must increase between two sequential stops
- trip_id 87058_250604-4288 stop_sequence 1 arrival_time 10:10:00 (1749024600) is less than previous stop arrival_time 10:34:41 (1749026081) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_sequence E036 11 erreurs
Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence
Exemples d'erreurs
- trip_id 87060_250604-4288 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
- trip_id 87058_250604-4288 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
- trip_id 87096_250604-4290 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
- trip_id 87094_250604-4290 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
- trip_id 87095_250604-4300 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
Avertissements
timestamp not populated W001 109 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 68616_250604-4281 does not have a timestamp
- trip_id 68631_250604-4281 does not have a timestamp
- trip_id 87106_250604-4287 does not have a timestamp
- trip_id 87060_250604-4288 does not have a timestamp
- trip_id 87036_250604-4288 does not have a timestamp
schedule_relationship not populated W009 109 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id 68616_250604-4281 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 68631_250604-4281 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 87106_250604-4287 stop_sequence 14 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 87060_250604-4288 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 87036_250604-4288 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1 520 | 26 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 2 565 | 26 fois (100 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 2 564 | 26 fois (100 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 363 | 24 fois (92 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 24 | 2 fois (8 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 222 | 2 fois (8 % des validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 24 | 2 fois (8 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 05/06/2025 à 01h43 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 05/06/2025 à 01h43 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1749080610"
}
}