GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T18:23:36Z,
for the dataset file:///shared/pref-wakayama-lg-jp.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
新温泉町
Feed Email:
kikaku@town.shinonsen.lg.jp
Feed Language:
Japanese
Feed Start Date:
2025-03-01
Feed End Date:
2026-03-31

Files included

  1. agency.txt
  2. agency_jp.txt
  3. calendar.txt
  4. calendar_dates.txt
  5. fare_attributes.txt
  6. fare_rules.txt
  7. feed_info.txt
  8. office_jp.txt
  9. routes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. translations.txt
  14. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 11
  • Shapes: 0
  • Stops: 169
  • Trips: 132

Specification Compliance report

14 notices reported (0 errors, 12 warnings, 2 infos)

Notice Code Severity Total
expired_calendar WARNING 1

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.
3 "S2"
missing_recommended_field WARNING 1

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"feed_info.txt" 2 "feed_version"
mixed_case_recommended_field WARNING 10

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" "新温泉町民バス「夢つばめ」" 2
"routes.txt" "route_long_name" "照来循環線［下照来］" 7
"routes.txt" "route_long_name" "照来循環線［上照来］" 8
"routes.txt" "route_long_name" "赤崎循環線［右まわり］" 9
"routes.txt" "route_long_name" "赤崎循環線［左まわり］" 10
"stops.txt" "stop_name" "浜坂Ｂ＆Ｇ海洋センター" 71
"trips.txt" "trip_headsign" "浜坂Ｂ＆Ｇ海洋センター" 18
"trips.txt" "trip_headsign" "浜坂Ｂ＆Ｇ海洋センター" 21
"trips.txt" "trip_headsign" "浜坂Ｂ＆Ｇ海洋センター" 22
"trips.txt" "trip_headsign" "浜坂Ｂ＆Ｇ海洋センター" 68
unknown_file INFO 2

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"agency_jp.txt"
"office_jp.txt"