GTFS Schedule Validation Report

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

Use this report alongside our documentation.

Summary

Agencies included

  • BUS URBAINS THONONAIS

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. routes.txt
  7. shapes.txt
  8. stop_times.txt
  9. stops.txt
  10. transfers.txt
  11. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 0
  • Shapes: 0
  • Stops: 0
  • Trips: 0

Specification Compliance report

22 notices reported (19 errors, 3 warnings, 0 infos)

Notice Code Severity Total
empty_column_name ERROR 19

empty_column_name

A column name is empty.

Such columns are skipped by the validator.

You can see more about this notice here.

filename (?) The name of the faulty file. index (?) The index of the empty column.
"calendar_dates.txt" 4
"fare_attributes.txt" 7
"fare_attributes.txt" 8
"fare_rules.txt" 6
"fare_rules.txt" 7
"fare_rules.txt" 8
"fare_rules.txt" 9
"routes.txt" 10
"routes.txt" 11
"routes.txt" 12
"routes.txt" 13
"routes.txt" 14
"shapes.txt" 5
"stop_times.txt" 8
"stop_times.txt" 9
"stop_times.txt" 10
"stop_times.txt" 11
"stops.txt" 10
"trips.txt" 10
missing_recommended_column WARNING 1

missing_recommended_column

A recommended column is missing in the input file.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the missing column.
"stop_times.txt" "timepoint"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
mixed_case_recommended_field WARNING 1

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.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"agency.txt" "agency_name" "BUS URBAINS THONONAIS" 2