Détails de la ressource
Fichier GTFS-Flex décrivant l’offre TAD zonal du réseau de transport public du Clermontois.
Cette ressource fait partie du jeu de données Réseau urbain Le Bus.
- Agencies : 1
- Blocks : 0
- Routes : 2
- Shapes : 0
- Stops : 19
- Trips : 4
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
❌18 erreurs, 3 avertissements
❌ Erreurs
missing_required_column 2 erreurs
A required column is missing in the input file.
Exemples d'erreurs
| fieldName | filename |
|---|---|
| "date" | "calendar_dates.txt" |
| "exception_type" | "calendar_dates.txt" |
missing_trip_edge 16 erreurs
Missing trip edge arrival_time or departure_time.
First and last stop of a trip must define both arrival_time and departure_time fields. Per stop_times.txt, “If there are not separate times for arrival and departure at a stop, enter the same value for arrival_time and departure_time.”
Fichiers pertinents
-
stop_times.txt
Exemples d'erreurs
| csvRowNumber | specifiedField | stopSequence | tripId |
|---|---|---|---|
| 2 | "arrival_time" | 0 | "401" |
| 2 | "departure_time" | 0 | "401" |
| 20 | "arrival_time" | 18 | "401" |
| 20 | "departure_time" | 18 | "401" |
| 21 | "arrival_time" | 0 | "402" |
| 21 | "departure_time" | 0 | "402" |
| 39 | "arrival_time" | 18 | "402" |
| 39 | "departure_time" | 18 | "402" |
| 40 | "arrival_time" | 0 | "403" |
| 40 | "departure_time" | 0 | "403" |
| 58 | "arrival_time" | 18 | "403" |
| 58 | "departure_time" | 18 | "403" |
| 59 | "arrival_time" | 0 | "404" |
| 59 | "departure_time" | 0 | "404" |
| 77 | "arrival_time" | 18 | "404" |
| 77 | "departure_time" | 18 | "404" |
⚠️ Avertissements
missing_recommended_file 1 erreur
A recommended file is missing.
Exemples d'erreurs
| filename |
|---|
| "feed_info.txt" |
route_long_name_contains_short_name 2 erreurs
Long name should not contain short name for a single route.
In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.
Good examples:
route_short_name/route_long_name Dataset "N"/"Judah" Muni San Fransisco "6"/"ML King Jr Blvd" Trimet Portland Streetcar "55"/"Boulevard Saint Laurent" STM Montreal "1"/"Rangiora/Cashmere" Metro Christchurch
Bad examples:
route_short_name/route_long_name "604"/"604" "14"/"Route 14" "2"/"Route 2: Bellows Falls In-Town"
Fichiers pertinents
-
routes.txt
Exemples d'erreurs
| csvRowNumber | routeId | routeLongName | routeShortName |
|---|---|---|---|
| 2 | "254" | "Allo le TAD Aller" | "Allo le TAD" |
| 3 | "255" | "Allo le TAD Retour" | "Allo le TAD" |
ℹ️ Information
unknown_column 14 erreurs
A column name is unknown.
Liens pertinents
Exemples d'erreurs
| fieldName | filename | index |
|---|---|---|
| "monday" | "calendar_dates.txt" | 2 |
| "tuesday" | "calendar_dates.txt" | 3 |
| "wednesday" | "calendar_dates.txt" | 4 |
| "thursday" | "calendar_dates.txt" | 5 |
| "friday" | "calendar_dates.txt" | 6 |
| "saturday" | "calendar_dates.txt" | 7 |
| "sunday" | "calendar_dates.txt" | 8 |
| "start_date" | "calendar_dates.txt" | 9 |
| "end_date" | "calendar_dates.txt" | 10 |
| "location_id" | "location_groups.txt" | 2 |
| "start_pickup_dropoff_window" | "stop_times.txt" | 13 |
| "end_pickup_dropoff_window" | "stop_times.txt" | 14 |
| "mean_duration_factor" | "stop_times.txt" | 15 |
| "mean_duration_offset" | "stop_times.txt" | 16 |
unknown_file 1 erreur
A file is unknown.
Liens pertinents
Exemples d'erreurs
| filename |
|---|
| "calendars.txt" |
Validation effectuée en utilisant le fichier GTFS en vigueur le 03/12/2025 à 17h08 Europe/Paris avec le validateur GTFS canonique.