Resource details
Fichier GTFS-Flex décrivant l’offre TAD zonal du réseau de transport public du Creillois.
This resource file is part of the dataset Réseau urbain AXO.
It is valid from 2021-03-29 to 9999-12-31.
- Agencies : 1
- Blocks : 0
- Routes : 12
- Shapes : 0
- Stops : 83
- Trips : 14
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
❌56 errors, 19 warnings
❌ Errors
missing_trip_edge 56 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 |
|---|---|---|---|
| 12 | "arrival_time" | 0 | "240" |
| 12 | "departure_time" | 0 | "240" |
| 21 | "arrival_time" | 9 | "240" |
| 21 | "departure_time" | 9 | "240" |
| 22 | "arrival_time" | 0 | "241" |
| 22 | "departure_time" | 0 | "241" |
| 29 | "arrival_time" | 7 | "241" |
| 29 | "departure_time" | 7 | "241" |
| 30 | "arrival_time" | 0 | "242" |
| 30 | "departure_time" | 0 | "242" |
| 60 | "arrival_time" | 30 | "242" |
| 60 | "departure_time" | 30 | "242" |
| 61 | "arrival_time" | 0 | "243" |
| 61 | "departure_time" | 0 | "243" |
| 68 | "arrival_time" | 7 | "243" |
| 68 | "departure_time" | 7 | "243" |
| 69 | "arrival_time" | 0 | "244" |
| 69 | "departure_time" | 0 | "244" |
| 99 | "arrival_time" | 30 | "244" |
| 99 | "departure_time" | 30 | "244" |
| 100 | "arrival_time" | 0 | "245" |
| 100 | "departure_time" | 0 | "245" |
| 142 | "arrival_time" | 42 | "245" |
| 142 | "departure_time" | 42 | "245" |
| 202 | "arrival_time" | 0 | "597" |
| 202 | "departure_time" | 0 | "597" |
| 211 | "arrival_time" | 9 | "597" |
| 211 | "departure_time" | 9 | "597" |
| 143 | "arrival_time" | 0 | "246" |
| 143 | "departure_time" | 0 | "246" |
| 187 | "arrival_time" | 44 | "246" |
| 187 | "departure_time" | 44 | "246" |
| 212 | "arrival_time" | 0 | "598" |
| 212 | "departure_time" | 0 | "598" |
| 221 | "arrival_time" | 9 | "598" |
| 221 | "departure_time" | 9 | "598" |
| 188 | "arrival_time" | 0 | "247" |
| 188 | "departure_time" | 0 | "247" |
| 194 | "arrival_time" | 6 | "247" |
| 194 | "departure_time" | 6 | "247" |
| 222 | "arrival_time" | 0 | "599" |
| 222 | "departure_time" | 0 | "599" |
| 223 | "arrival_time" | 1 | "599" |
| 223 | "departure_time" | 1 | "599" |
| 195 | "arrival_time" | 0 | "248" |
| 195 | "departure_time" | 0 | "248" |
| 201 | "arrival_time" | 6 | "248" |
| 201 | "departure_time" | 6 | "248" |
| 224 | "arrival_time" | 0 | "600" |
| 224 | "departure_time" | 0 | "600" |
Showing only the first 50 errors.
⚠️ Warnings
expired_calendar 2 errors
Dataset should not contain date ranges for services that have already expired.
This warning takes into account the calendar_dates.txt file as well as the calendar.txt
file.
Relevant files
-
calendar.txt -
calendar_dates.txt
Relevant links
Sample errors
| csvRowNumber | serviceId |
|---|---|
| 12 | "597" |
| 13 | "598" |
leading_or_trailing_whitespaces 4 errors
The value in CSV file has leading or trailing whitespaces.
This notice is emitted for values protected with double quotes since whitespaces for
non-protected values are trimmed automatically by CSV parser.
The validator strips whitespaces from protected values. We do not see any use case when such a
whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for
some values and omit them for the others. This is causing the largest problem when a primary key
and a foreign key differ just by a whitespace: it is clear that they are intended to be the same,
that is why we always strip whitespaces.
Sample errors
| csvRowNumber | fieldName | fieldValue | filename |
|---|---|---|---|
| 16 | "stop_name" | "Mairie de Cramoisy " | "stops.txt" |
| 17 | "stop_name" | "Salvador Allende " | "stops.txt" |
| 19 | "stop_name" | "Cité Marinoni " | "stops.txt" |
| 46 | "stop_name" | "Parc Alata 1 " | "stops.txt" |
missing_recommended_file 1 error
A recommended file is missing.
Sample errors
| filename |
|---|
| "feed_info.txt" |
route_long_name_contains_short_name 12 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 | "130" | "AXO +1 Aller LàV" | "AXO +1" |
| 3 | "131" | "AXO +1 Retour LàV" | "AXO +1" |
| 4 | "132" | "AXO +2 Aller" | "AXO +2" |
| 5 | "133" | "AXO +3 Aller" | "AXO +3" |
| 6 | "134" | "AXO +3 Retour" | "AXO +3" |
| 7 | "135" | "AXO +2 Retour" | "AXO +2" |
| 8 | "136" | "AXO +4 Aller" | "AXO +4" |
| 9 | "137" | "AXO +4 Retour" | "AXO +4" |
| 10 | "138" | "AXO +3 ST LEU Aller" | "AXO +3" |
| 11 | "139" | "AXO +3 ST LEU Retour" | "AXO +3" |
| 12 | "393" | "AXO +1 Aller Sa" | "AXO +1" |
| 13 | "394" | "AXO +1 Retour Sa" | "AXO +1" |
ℹ️ Information
service_extends_far_in_the_future 12 errors
A service end date is more than 2 years in the future.
Relevant files
-
calendar.txt -
calendar_dates.txt
Sample errors
| serviceId | serviceWindowEndDate |
|---|---|
| "239" | "9999-12-31" |
| "240" | "9999-12-31" |
| "241" | "9999-12-31" |
| "242" | "9999-12-31" |
| "243" | "9999-12-31" |
| "244" | "9999-12-31" |
| "245" | "9999-12-31" |
| "246" | "9999-12-31" |
| "247" | "9999-12-31" |
| "248" | "9999-12-31" |
| "599" | "9999-12-25" |
| "600" | "9999-12-25" |
unknown_column 5 errors
A column name is unknown.
Sample errors
| fieldName | filename | index |
|---|---|---|
| "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 |
Validation carried out using the current GTFS file the 2026-08-30 at 02:34 Europe/Paris using the Canonical GTFS Schedule Validator.