GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-07T16:16:28Z,
for the dataset file:///tmp/1_in.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
KEOLIS NEVERS
Publisher URL:
http://www.taneo-bus.fr
Feed Language:
French
Feed Start Date:
2023-09-04
Feed End Date:
2024-07-07

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts

  • Agencies: 1
  • Blocks: 1
  • Routes: 41
  • Shapes: 0
  • Stops: 833
  • Trips: 1332

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Feed InformationRoute ColorsHeadsignsWheelchair AccessibilityLocation Types

Specification Compliance report

35427 notices reported (0 errors, 35427 warnings, 0 infos)

Notice Code Severity Total
duplicate_route_name WARNING 4

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
11 "5_24" 12 "5_25" "5" "Ligne 5" 3 "01"
11 "5_24" 13 "5_26" "5" "Ligne 5" 3 "01"
39 "T1_20" 40 "T1_23" "T1" "Ligne T1" 3 "01"
41 "T2_20" 42 "T2_24" "T2" "Ligne T2" 3 "01"
expired_calendar WARNING 5

expired_calendar

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.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
27 "PVS 2023-10 SS VAL BAT_009_S"
29 "PVS 2023-10 SS VAL BAT_009_LMWJVS"
30 "PVS 2023-10 SS VAL BAT_009_DF"
28 "PVS 2023-10 SS VAL BAT_009_VS"
26 "PVS 2023-10 SS VAL BAT_009_LMWJV"
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20240607" "20240707" "20240707"
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
missing_timepoint_value WARNING 35289

missing_timepoint_value

stop_times.timepoint value is missing for a record.

Even though the column timepoint is optional in stop_times.txt according to the specification, stop_times.timepoint should not be empty when provided.

You can see more about this notice here.

Only the first 50 of 35289 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's `stop_times.trip_id`. stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2 "120816{16_20}-Production SST SCO_024_V" 1
3 "120816{16_20}-Production SST SCO_024_V" 2
4 "120816{16_20}-Production SST SCO_024_V" 3
5 "120816{16_20}-Production SST SCO_024_V" 4
6 "120816{16_20}-Production SST SCO_024_V" 5
7 "120816{16_20}-Production SST SCO_024_V" 6
8 "120816{16_20}-Production SST SCO_024_V" 7
9 "120816{16_20}-Production SST SCO_024_V" 8
10 "120816{16_20}-Production SST SCO_024_V" 9
11 "120816{16_20}-Production SST SCO_024_V" 10
12 "120817{16_20}-Production SST SCO_024_W" 1
13 "120817{16_20}-Production SST SCO_024_W" 2
14 "120817{16_20}-Production SST SCO_024_W" 3
15 "120817{16_20}-Production SST SCO_024_W" 4
16 "120817{16_20}-Production SST SCO_024_W" 5
17 "120817{16_20}-Production SST SCO_024_W" 6
18 "120817{16_20}-Production SST SCO_024_W" 7
19 "120817{16_20}-Production SST SCO_024_W" 8
20 "120817{16_20}-Production SST SCO_024_W" 9
21 "120817{16_20}-Production SST SCO_024_W" 10
22 "120818{16_20}-Production SST SCO_024_LMJ" 1
23 "120818{16_20}-Production SST SCO_024_LMJ" 2
24 "120818{16_20}-Production SST SCO_024_LMJ" 3
25 "120818{16_20}-Production SST SCO_024_LMJ" 4
26 "120818{16_20}-Production SST SCO_024_LMJ" 5
27 "120818{16_20}-Production SST SCO_024_LMJ" 6
28 "120818{16_20}-Production SST SCO_024_LMJ" 7
29 "120818{16_20}-Production SST SCO_024_LMJ" 8
30 "120818{16_20}-Production SST SCO_024_LMJ" 9
31 "120818{16_20}-Production SST SCO_024_LMJ" 10
32 "120819{16_20}-Production SST SCO_024_LMWJV" 1
33 "120819{16_20}-Production SST SCO_024_LMWJV" 2
34 "120819{16_20}-Production SST SCO_024_LMWJV" 3
35 "120819{16_20}-Production SST SCO_024_LMWJV" 4
36 "120819{16_20}-Production SST SCO_024_LMWJV" 5
37 "120819{16_20}-Production SST SCO_024_LMWJV" 6
38 "120819{16_20}-Production SST SCO_024_LMWJV" 7
39 "120819{16_20}-Production SST SCO_024_LMWJV" 8
40 "120819{16_20}-Production SST SCO_024_LMWJV" 9
41 "120819{16_20}-Production SST SCO_024_LMWJV" 10
42 "120820{12_20}-Production SST SCO_024_W" 1
43 "120820{12_20}-Production SST SCO_024_W" 2
44 "120820{12_20}-Production SST SCO_024_W" 3
45 "120820{12_20}-Production SST SCO_024_W" 4
46 "120820{12_20}-Production SST SCO_024_W" 5
47 "120820{12_20}-Production SST SCO_024_W" 6
48 "120820{12_20}-Production SST SCO_024_W" 7
49 "120820{12_20}-Production SST SCO_024_W" 8
50 "120820{12_20}-Production SST SCO_024_W" 9
51 "120820{12_20}-Production SST SCO_024_W" 10
mixed_case_recommended_field WARNING 111

mixed_case_recommended_field

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 Text Dataset
"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"

You can see more about this notice here.

Only the first 50 of 111 affected records are displayed below.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"routes.txt" "route_desc" "L13 version SEP 21 modif temps parcour" 4
"routes.txt" "route_desc" "2020 - 20 min plage été 2020 (sur base parcours 2017)" 14
"trips.txt" "trip_headsign" "SP2 CHALLUY/SERMOISE" 7
"trips.txt" "trip_headsign" "SP2 CHALLUY/SERMOISE" 8
"trips.txt" "trip_headsign" "SP8 MARZY ECOLE" 11
"trips.txt" "trip_headsign" "SP8 MARZY ECOLE" 12
"trips.txt" "trip_headsign" "SP3 GIMOUILLE/SAINCAIZE" 13
"trips.txt" "trip_headsign" "SP3 GIMOUILLE/SAINCAIZE" 14
"trips.txt" "trip_headsign" "SP1 CHALLUY/SERMOISE" 16
"trips.txt" "trip_headsign" "SP1 CHALLUY/SERMOISE" 17
"trips.txt" "trip_headsign" "14 ESAT" 40
"trips.txt" "trip_headsign" "14 ESAT" 41
"trips.txt" "trip_headsign" "14 ESAT" 42
"trips.txt" "trip_headsign" "14 ESAT" 43
"trips.txt" "trip_headsign" "14 ESAT" 44
"trips.txt" "trip_headsign" "14 ESAT" 45
"trips.txt" "trip_headsign" "14 ESAT" 46
"trips.txt" "trip_headsign" "14 ESAT" 53
"trips.txt" "trip_headsign" "14 ESAT" 54
"trips.txt" "trip_headsign" "14 ESAT" 55
"trips.txt" "trip_headsign" "14 ESAT" 56
"trips.txt" "trip_headsign" "14 ESAT" 57
"trips.txt" "trip_headsign" "14 ESAT" 58
"trips.txt" "trip_headsign" "14 ESAT" 59
"trips.txt" "trip_headsign" "14 ESAT" 66
"trips.txt" "trip_headsign" "14 ESAT" 67
"trips.txt" "trip_headsign" "14 ESAT" 68
"trips.txt" "trip_headsign" "14 ESAT" 69
"trips.txt" "trip_headsign" "14 ESAT" 70
"trips.txt" "trip_headsign" "14 ESAT" 71
"trips.txt" "trip_headsign" "14 ESAT" 72
"trips.txt" "trip_headsign" "P10BIS NEVERS GARES" 202
"trips.txt" "trip_headsign" "P10BIS LPA-LEGTA" 203
"trips.txt" "trip_headsign" "P10BIS LPA-LEGTA" 204
"trips.txt" "trip_headsign" "SP6 BANLAY" 215
"trips.txt" "trip_headsign" "SP6 BANLAY" 216
"trips.txt" "trip_headsign" "SP6 BANLAY" 217
"trips.txt" "trip_headsign" "SP6 BANLAY" 218
"trips.txt" "trip_headsign" "SP6 BANLAY" 219
"trips.txt" "trip_headsign" "NOCTI EST" 221
"trips.txt" "trip_headsign" "NOCTI EST" 222
"trips.txt" "trip_headsign" "NOCTI EST" 223
"trips.txt" "trip_headsign" "NOCTI EST" 224
"trips.txt" "trip_headsign" "NOCTI EST" 225
"trips.txt" "trip_headsign" "NOCTI EST" 226
"trips.txt" "trip_headsign" "NOCTI EST" 227
"trips.txt" "trip_headsign" "NOCTI EST" 228
"trips.txt" "trip_headsign" "NOCTI OUEST" 229
"trips.txt" "trip_headsign" "NOCTI OUEST" 230
"trips.txt" "trip_headsign" "NOCTI OUEST" 231
route_color_contrast WARNING 2

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeColor (?) The faulty record's HTML route color. routeTextColor (?) The faulty record's HTML route text color.
"12_20" 3 "#9FD6F6" "#FFFFFF"
"P8_23" 30 "#8000FF" "#000000"
route_long_name_contains_short_name WARNING 14

route_long_name_contains_short_name

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"

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`. routeLongName (?) The faulty record's `route_long_name`.
"NOCTE_21" 15 "NOCTE" "Nocte"
"NOCTO_20" 16 "NOCTO" "Nocto"
"P10_20" 18 "P10" "P10"
"P11_20" 20 "P11" "P11"
"P12_20" 21 "P12" "P12"
"P13_20" 22 "P13" "P13"
"P14_22" 23 "P14" "P14 - rentrée 2022"
"SP1_20" 32 "SP1" "SP1 Challuy > Sermoise"
"SP2_20" 33 "SP2" "SP2 Challuy > Sermoise"
"SP3_20" 34 "SP3" "SP3 Gimouille > Saincaize"
"SP4_20" 35 "SP4" "SP4 G.Moquet > P.Eluard -New Rés"
"SP6_20" 36 "SP6" "SP6"
"SP8_20" 37 "SP8" "SP8 Marzy DUfaud > Maternelle"
"SP9_20" 38 "SP9" "SP9"