Resource details
Fichier GTFS-Flex décrivant l’offre TAD zonal du réseau de transport public du Clermontois.
This resource file is part of the dataset Réseau urbain Le Bus.
- Agencies : 1
- Blocks : 0
- Routes : 2
- Shapes : 0
- Stops : 19
- Trips : 4
Download availability
Learn more
HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.For SIRI and SIRI Lite feeds, we perform a
GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.Validation details
❌18 errors, 3 warnings
❌ Errors
missing_required_column 2 errors
A required column is missing in the input file.
Sample errors
| fieldName | filename |
|---|---|
| "date" | "calendar_dates.txt" |
| "exception_type" | "calendar_dates.txt" |
missing_trip_edge 16 errors
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.”
Relevant files
-
stop_times.txt
Sample errors
| 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" |
⚠️ Warnings
missing_recommended_file 1 error
A recommended file is missing.
Sample errors
| filename |
|---|
| "feed_info.txt" |
route_long_name_contains_short_name 2 errors
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"
Relevant files
-
routes.txt
Sample errors
| 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 errors
A column name is unknown.
Relevant links
Sample errors
| 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 error
A file is unknown.
Relevant links
Sample errors
| filename |
|---|
| "calendars.txt" |
Validation carried out using the current GTFS file the 2025-12-03 at 17:08 Europe/Paris using the Canonical GTFS Schedule Validator.