Resource details
Fichier GTFS-Flex décrivant l’offre TAD zonal du réseau de transport public de la Plaine d’Estrées.
This resource file is part of the dataset Réseau urbain Hoplà.
- Agencies : 1
- Blocks : 0
- Routes : 38
- Shapes : 0
- Stops : 75
- Trips : 37
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
❌150 errors, 44 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 148 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 |
|---|---|---|---|
| 1202 | "arrival_time" | 0 | "490" |
| 1202 | "departure_time" | 0 | "490" |
| 1276 | "arrival_time" | 74 | "490" |
| 1276 | "departure_time" | 74 | "490" |
| 1277 | "arrival_time" | 0 | "491" |
| 1277 | "departure_time" | 0 | "491" |
| 1351 | "arrival_time" | 74 | "491" |
| 1351 | "departure_time" | 74 | "491" |
| 1352 | "arrival_time" | 0 | "492" |
| 1352 | "departure_time" | 0 | "492" |
| 1426 | "arrival_time" | 74 | "492" |
| 1426 | "departure_time" | 74 | "492" |
| 1427 | "arrival_time" | 0 | "493" |
| 1427 | "departure_time" | 0 | "493" |
| 1501 | "arrival_time" | 74 | "493" |
| 1501 | "departure_time" | 74 | "493" |
| 1502 | "arrival_time" | 0 | "494" |
| 1502 | "departure_time" | 0 | "494" |
| 1576 | "arrival_time" | 74 | "494" |
| 1576 | "departure_time" | 74 | "494" |
| 1577 | "arrival_time" | 0 | "495" |
| 1577 | "departure_time" | 0 | "495" |
| 1651 | "arrival_time" | 74 | "495" |
| 1651 | "departure_time" | 74 | "495" |
| 2 | "arrival_time" | 0 | "474" |
| 2 | "departure_time" | 0 | "474" |
| 76 | "arrival_time" | 74 | "474" |
| 76 | "departure_time" | 74 | "474" |
| 1652 | "arrival_time" | 0 | "496" |
| 1652 | "departure_time" | 0 | "496" |
| 1726 | "arrival_time" | 74 | "496" |
| 1726 | "departure_time" | 74 | "496" |
| 77 | "arrival_time" | 0 | "475" |
| 77 | "departure_time" | 0 | "475" |
| 151 | "arrival_time" | 74 | "475" |
| 151 | "departure_time" | 74 | "475" |
| 1727 | "arrival_time" | 0 | "497" |
| 1727 | "departure_time" | 0 | "497" |
| 1801 | "arrival_time" | 74 | "497" |
| 1801 | "departure_time" | 74 | "497" |
| 152 | "arrival_time" | 0 | "476" |
| 152 | "departure_time" | 0 | "476" |
| 226 | "arrival_time" | 74 | "476" |
| 226 | "departure_time" | 74 | "476" |
| 1802 | "arrival_time" | 0 | "498" |
| 1802 | "departure_time" | 0 | "498" |
| 1876 | "arrival_time" | 74 | "498" |
| 1876 | "departure_time" | 74 | "498" |
| 227 | "arrival_time" | 0 | "477" |
| 227 | "departure_time" | 0 | "477" |
Showing only the first 50 errors.
⚠️ Warnings
leading_or_trailing_whitespaces 2 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 |
|---|---|---|---|
| 59 | "stop_name" | "TAD - Mairie Grandfresnoy " | "stops.txt" |
| 61 | "stop_name" | "TAD - Sucrerie " | "stops.txt" |
missing_recommended_file 1 error
A recommended file is missing.
Sample errors
| filename |
|---|
| "feed_info.txt" |
mixed_case_recommended_field 3 errors
This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).
This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.
Good examples: Field TextDataset "Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg "Red Hook/Atlantic Basin" NYC Ferry "Campo Grande Norte" Carris
Bad examples: Field Text "GALLERIA MALL" "3427 GG 17" "21 Clark Rd Est"
Relevant links
Sample errors
| csvRowNumber | fieldName | fieldValue | filename |
|---|---|---|---|
| 2 | "stop_name" | "TAD - GARE ESTREES SAINT DENIS" | "stops.txt" |
| 3 | "stop_name" | "TAD - PLACE DU MARCHE ESTREES SAINT DENIS" | "stops.txt" |
| 40 | "stop_name" | "TAD - RD 13" | "stops.txt" |
route_long_name_contains_short_name 38 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 | "309" | "HOPLÀ Arsy Aller" | "HOPLÀ" |
| 3 | "310" | "HOPLÀ Arsy Retour" | "HOPLÀ" |
| 4 | "311" | "HOPLÀ Canly Aller" | "HOPLÀ" |
| 5 | "312" | "HOPLÀ Canly Retour" | "HOPLÀ" |
| 6 | "313" | "HOPLÀ Avrigny Aller" | "HOPLÀ" |
| 7 | "314" | "HOPLÀ Avrigny Retour" | "HOPLÀ" |
| 8 | "315" | "HOPLÀ Bailleul le Soc Aller" | "HOPLÀ" |
| 9 | "316" | "HOPLÀ Bailleul le Soc Retour" | "HOPLÀ" |
| 10 | "317" | "HOPLÀ Chevrières Aller" | "HOPLÀ" |
| 11 | "318" | "HOPLÀ Chevrières Retour" | "HOPLÀ" |
| 12 | "319" | "HOPLÀ Choisy-la-Victoire Aller" | "HOPLÀ" |
| 13 | "320" | "HOPLÀ Choisy-la-Victoire Retour" | "HOPLÀ" |
| 14 | "321" | "HOPLÀ Épineuse Aller" | "HOPLÀ" |
| 15 | "322" | "HOPLÀ Épineuse Retour" | "HOPLÀ" |
| 16 | "323" | "HOPLÀ Estrées-Saint-Denis Aller" | "HOPLÀ" |
| 17 | "324" | "HOPLÀ Estrées-Saint-Denis Retour" | "HOPLÀ" |
| 18 | "325" | "HOPLÀ Blincourt Retour" | "HOPLÀ" |
| 19 | "326" | "HOPLÀ Blincourt Aller" | "HOPLÀ" |
| 20 | "327" | "HOPLÀ Francières Aller" | "HOPLÀ" |
| 21 | "328" | "HOPLÀ Francières Retour" | "HOPLÀ" |
| 22 | "329" | "HOPLÀ Grandfresnoy Aller" | "HOPLÀ" |
| 23 | "330" | "HOPLÀ Grandfresnoy Retour" | "HOPLÀ" |
| 24 | "331" | "HOPLÀ Hémévillers Aller" | "HOPLÀ" |
| 25 | "332" | "HOPLÀ Hémévillers Retour" | "HOPLÀ" |
| 26 | "333" | "HOPLÀ Houdancourt Aller" | "HOPLÀ" |
| 27 | "334" | "HOPLÀ Houdancourt Retour" | "HOPLÀ" |
| 28 | "335" | "HOPLÀ Le Fayel Aller" | "HOPLÀ" |
| 29 | "336" | "HOPLÀ Le Fayel Retour" | "HOPLÀ" |
| 30 | "337" | "HOPLÀ Longueil-Sainte-Marie Aller" | "HOPLÀ" |
| 31 | "338" | "HOPLÀ Longueil-Sainte-Marie Retour" | "HOPLÀ" |
| 32 | "339" | "HOPLÀ Montmartin Aller" | "HOPLÀ" |
| 33 | "340" | "HOPLÀ Montmartin Retour" | "HOPLÀ" |
| 34 | "341" | "HOPLÀ Moyvillers Aller" | "HOPLÀ" |
| 35 | "342" | "HOPLÀ Moyvillers Retour" | "HOPLÀ" |
| 36 | "343" | "HOPLÀ Rémy Aller" | "HOPLÀ" |
| 37 | "344" | "HOPLÀ Rémy Retour" | "HOPLÀ" |
| 38 | "345" | "HOPLÀ Rivecourt Aller" | "HOPLÀ" |
| 39 | "346" | "HOPLÀ Rivecourt Retour" | "HOPLÀ" |
ℹ️ 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:10 Europe/Paris using the Canonical GTFS Schedule Validator.