GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-06T00:09:38Z,
for the dataset file:///shared/shimanto-kotsu-gtfs-shimantotraffic-localbus.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • 株式会社四万十交通

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
Japanese
Feed Start Date:
2025-07-01
Feed End Date:
2025-10-04

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 15
  • Shapes: 39
  • Stops: 586
  • Trips: 241

Specification Compliance report

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

Notice Code Severity Total
duplicate_route_name WARNING 3

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`.
7 "105539-窪川～興津線_B" 8 "105539-窪川～興津線_A" "窪川～興津線" "" 3 "105539-7490002010842"
6 "105539-久礼～大野見線_C" 11 "105539-久礼～大野見線_A" "久礼～大野見線" "" 3 "105539-7490002010842"
6 "105539-久礼～大野見線_C" 12 "105539-久礼～大野見線_B" "久礼～大野見線" "" 3 "105539-7490002010842"
expired_calendar WARNING 3

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.
2 "105539-土曜"
3 "105539-平日"
4 "105539-日祝"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

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 "20251206" "20251004" "20251213"
mixed_case_recommended_field WARNING 243

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 243 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_short_name" "窪川～大野見線" 2
"routes.txt" "route_short_name" "窪川～佐賀線" 3
"routes.txt" "route_short_name" "窪川～影野線" 4
"routes.txt" "route_short_name" "窪川～大正線" 5
"routes.txt" "route_short_name" "久礼～大野見線" 6
"routes.txt" "route_short_name" "窪川～興津線" 7
"routes.txt" "route_short_name" "窪川～興津線" 8
"routes.txt" "route_short_name" "窪川～志和線" 9
"routes.txt" "route_short_name" "萩中～大野見線" 10
"routes.txt" "route_short_name" "久礼～大野見線" 11
"routes.txt" "route_short_name" "久礼～大野見線" 12
"routes.txt" "route_short_name" "大正駅～学校上線" 13
"routes.txt" "route_short_name" "窪川～松葉川温泉線" 14
"routes.txt" "route_short_name" "大正駅～大奈路線" 15
"routes.txt" "route_short_name" "大正駅～道の駅とおわ線" 16
"stops.txt" "stop_name" "秋丸(上秋丸)" 68
"stops.txt" "stop_name" "秋丸(上秋丸)" 69
"stops.txt" "stop_name" "神社前(大野見)" 106
"stops.txt" "stop_name" "神社前(大野見)" 107
"stops.txt" "stop_name" "伊与喜(国道)" 167
"stops.txt" "stop_name" "伊与喜(国道)" 168
"stops.txt" "stop_name" "秋丸(秋丸)" 310
"stops.txt" "stop_name" "秋丸(秋丸)" 311
"stops.txt" "stop_name" "西ノ川(与津地)" 385
"stops.txt" "stop_name" "西ノ川(与津地)" 386
"stops.txt" "stop_name" "一本松(興津)" 397
"stops.txt" "stop_name" "一本松(興津)" 398
"stops.txt" "stop_name" "学校上（ホビー館）" 509
"stops.txt" "stop_name" "学校上（ホビー館）" 510
"stops.txt" "stop_name" "西ノ川(大正)" 571
"stops.txt" "stop_name" "西ノ川(大正)" 572
"trips.txt" "trip_headsign" "影野（香月ヶ丘→西川角→小野川 経由）" 3
"trips.txt" "trip_headsign" "久礼駅（吉野(夏枯峠)→長沢 経由）" 4
"trips.txt" "trip_headsign" "興津（見付→本堂 経由）" 5
"trips.txt" "trip_headsign" "窪川駅（北ノ川→家地川駅前 経由）" 6
"trips.txt" "trip_headsign" "志和（見付→本堂 経由）" 7
"trips.txt" "trip_headsign" "松葉川温泉（東川角→小野川→米奥→日野地 経由）" 8
"trips.txt" "trip_headsign" "大正駅（家地川駅前→北ノ川 経由）" 9
"trips.txt" "trip_headsign" "窪川駅（小野川→西川角→香月ヶ丘 経由）" 10
"trips.txt" "trip_headsign" "大野見（東川角→小野川→滝本 経由）" 11
"trips.txt" "trip_headsign" "窪川駅（滝本→小野川→東川角 経由）" 12
"trips.txt" "trip_headsign" "佐賀中学校（市野瀬→中ノ川 経由）" 13
"trips.txt" "trip_headsign" "窪川駅（本堂→見付 経由）" 14
"trips.txt" "trip_headsign" "窪川駅（本堂→仁井田 経由）" 15
"trips.txt" "trip_headsign" "道の駅とおわ（昭和→十川 経由）" 16
"trips.txt" "trip_headsign" "大正駅（江師 経由）" 17
"trips.txt" "trip_headsign" "窪川駅（中ノ川→市野瀬 経由）" 19
"trips.txt" "trip_headsign" "松葉川温泉（東川角→小野川→米奥→日野地 経由）" 21
"trips.txt" "trip_headsign" "大正駅（国道→北ノ川 経由）" 22
"trips.txt" "trip_headsign" "久礼駅（床鍋(七子峠) 経由）" 23
non_ascii_or_non_printable_char WARNING 22939

non_ascii_or_non_printable_char

Non ascii or non printable char in ID field.

A value of a field with type ID contains non ASCII or non printable characters. This is not recommended.

You can see more about this notice here.

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

filename (?) Name of the faulty file. csvRowNumber (?) Row number of the faulty record. columnName (?) Name of the column where the error occurred. fieldValue (?) Faulty value.
"calendar.txt" 2 "service_id" "105539-土曜"
"calendar.txt" 3 "service_id" "105539-平日"
"calendar.txt" 4 "service_id" "105539-日祝"
"calendar_dates.txt" 2 "service_id" "105539-■"
"calendar_dates.txt" 3 "service_id" "105539-■"
"calendar_dates.txt" 4 "service_id" "105539-■"
"calendar_dates.txt" 5 "service_id" "105539-■"
"calendar_dates.txt" 6 "service_id" "105539-■"
"calendar_dates.txt" 7 "service_id" "105539-■"
"calendar_dates.txt" 8 "service_id" "105539-■"
"calendar_dates.txt" 9 "service_id" "105539-■"
"calendar_dates.txt" 10 "service_id" "105539-■"
"calendar_dates.txt" 11 "service_id" "105539-■"
"calendar_dates.txt" 12 "service_id" "105539-■"
"calendar_dates.txt" 13 "service_id" "105539-■"
"calendar_dates.txt" 14 "service_id" "105539-■"
"calendar_dates.txt" 15 "service_id" "105539-△"
"calendar_dates.txt" 16 "service_id" "105539-△"
"calendar_dates.txt" 17 "service_id" "105539-△"
"calendar_dates.txt" 18 "service_id" "105539-△"
"calendar_dates.txt" 19 "service_id" "105539-△"
"calendar_dates.txt" 20 "service_id" "105539-△"
"calendar_dates.txt" 21 "service_id" "105539-△"
"calendar_dates.txt" 22 "service_id" "105539-△"
"calendar_dates.txt" 23 "service_id" "105539-△"
"calendar_dates.txt" 24 "service_id" "105539-△"
"calendar_dates.txt" 25 "service_id" "105539-△"
"calendar_dates.txt" 26 "service_id" "105539-△"
"calendar_dates.txt" 27 "service_id" "105539-△"
"calendar_dates.txt" 28 "service_id" "105539-△"
"calendar_dates.txt" 29 "service_id" "105539-△"
"calendar_dates.txt" 30 "service_id" "105539-△"
"calendar_dates.txt" 31 "service_id" "105539-△"
"calendar_dates.txt" 32 "service_id" "105539-△"
"calendar_dates.txt" 33 "service_id" "105539-△"
"calendar_dates.txt" 34 "service_id" "105539-△"
"calendar_dates.txt" 35 "service_id" "105539-△"
"calendar_dates.txt" 36 "service_id" "105539-△"
"calendar_dates.txt" 37 "service_id" "105539-△"
"calendar_dates.txt" 38 "service_id" "105539-△"
"calendar_dates.txt" 39 "service_id" "105539-△"
"calendar_dates.txt" 40 "service_id" "105539-△"
"calendar_dates.txt" 41 "service_id" "105539-△"
"calendar_dates.txt" 42 "service_id" "105539-△"
"calendar_dates.txt" 43 "service_id" "105539-△"
"calendar_dates.txt" 44 "service_id" "105539-△"
"calendar_dates.txt" 45 "service_id" "105539-△"
"calendar_dates.txt" 46 "service_id" "105539-△"
"calendar_dates.txt" 47 "service_id" "105539-△"
"calendar_dates.txt" 48 "service_id" "105539-△"
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20251206" "20250721" "20251004"