Search
  1. Home
  2. Japan Feeds
  3. kumejima
  4. Source Data Validation Report

kumejima — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-28T15:31:19Z,
for the dataset file:///shared/kumejima_e3eecddb.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
特定非営利活動法人OTTOP
Publisher URL:
https://www.ottop.org
Feed Email:
contact@ottop.org
Feed Language:
Japanese
Feed Start Date:
2026-08-26
Feed End Date:
2026-09-30

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. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. translations.txt
  14. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 6
  • Shapes: 11
  • Stops: 91
  • Trips: 66

Specification Compliance report

92 notices reported (0 errors, 89 warnings, 3 infos)

Notice Code Severity Total
mixed_case_recommended_field WARNING 8

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.
"routes.txt" "route_short_name" "兼城港（比屋定）イーフ線" 4
"routes.txt" "route_long_name" "兼城港（比屋定）イーフ線" 4
"routes.txt" "route_short_name" "兼城港（比屋定）イーフ線" 5
"routes.txt" "route_long_name" "兼城港（比屋定）イーフ線（嘉手刈イーフ線接続）" 5
"routes.txt" "route_short_name" "兼城港（嘉手刈）イーフ線" 6
"routes.txt" "route_long_name" "兼城港（嘉手刈）イーフ線（比屋定イーフ線接続）" 6
"stops.txt" "stop_name" "西奥武（バーデハウス前）" 21
"stops.txt" "stop_name" "グラウンド前・BG前" 77
non_ascii_or_non_printable_char WARNING 78

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 78 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" "全日（2026/7/17～2026/8/31）"
"calendar.txt" 3 "service_id" "平日（2026/7/17～2026/8/31）"
"calendar.txt" 4 "service_id" "土日祝（2026/7/17～2026/8/31）"
"calendar.txt" 5 "service_id" "全日（2026/9/1～2026/9/30）"
"calendar.txt" 6 "service_id" "平日（2026/9/1～2026/9/30）"
"calendar.txt" 7 "service_id" "土日祝（2026/9/1～2026/9/30）"
"calendar_dates.txt" 2 "service_id" "平日（2026/9/1～2026/9/30）"
"calendar_dates.txt" 3 "service_id" "平日（2026/9/1～2026/9/30）"
"calendar_dates.txt" 4 "service_id" "平日（2026/9/1～2026/9/30）"
"calendar_dates.txt" 5 "service_id" "土日祝（2026/9/1～2026/9/30）"
"calendar_dates.txt" 6 "service_id" "土日祝（2026/9/1～2026/9/30）"
"calendar_dates.txt" 7 "service_id" "土日祝（2026/9/1～2026/9/30）"
"trips.txt" 2 "service_id" "全日（2026/7/17～2026/8/31）"
"trips.txt" 3 "service_id" "全日（2026/7/17～2026/8/31）"
"trips.txt" 4 "service_id" "全日（2026/7/17～2026/8/31）"
"trips.txt" 5 "service_id" "全日（2026/7/17～2026/8/31）"
"trips.txt" 6 "service_id" "全日（2026/7/17～2026/8/31）"
"trips.txt" 7 "service_id" "全日（2026/7/17～2026/8/31）"
"trips.txt" 8 "service_id" "全日（2026/7/17～2026/8/31）"
"trips.txt" 9 "service_id" "全日（2026/7/17～2026/8/31）"
"trips.txt" 10 "service_id" "全日（2026/7/17～2026/8/31）"
"trips.txt" 11 "service_id" "全日（2026/7/17～2026/8/31）"
"trips.txt" 12 "service_id" "全日（2026/7/17～2026/8/31）"
"trips.txt" 13 "service_id" "全日（2026/7/17～2026/8/31）"
"trips.txt" 14 "service_id" "平日（2026/7/17～2026/8/31）"
"trips.txt" 15 "service_id" "平日（2026/7/17～2026/8/31）"
"trips.txt" 16 "service_id" "平日（2026/7/17～2026/8/31）"
"trips.txt" 17 "service_id" "平日（2026/7/17～2026/8/31）"
"trips.txt" 18 "service_id" "平日（2026/7/17～2026/8/31）"
"trips.txt" 19 "service_id" "平日（2026/7/17～2026/8/31）"
"trips.txt" 20 "service_id" "平日（2026/7/17～2026/8/31）"
"trips.txt" 21 "service_id" "平日（2026/7/17～2026/8/31）"
"trips.txt" 22 "service_id" "平日（2026/7/17～2026/8/31）"
"trips.txt" 23 "service_id" "平日（2026/7/17～2026/8/31）"
"trips.txt" 24 "service_id" "平日（2026/7/17～2026/8/31）"
"trips.txt" 25 "service_id" "平日（2026/7/17～2026/8/31）"
"trips.txt" 26 "service_id" "土日祝（2026/7/17～2026/8/31）"
"trips.txt" 27 "service_id" "土日祝（2026/7/17～2026/8/31）"
"trips.txt" 28 "service_id" "土日祝（2026/7/17～2026/8/31）"
"trips.txt" 29 "service_id" "土日祝（2026/7/17～2026/8/31）"
"trips.txt" 30 "service_id" "土日祝（2026/7/17～2026/8/31）"
"trips.txt" 31 "service_id" "土日祝（2026/7/17～2026/8/31）"
"trips.txt" 32 "service_id" "土日祝（2026/7/17～2026/8/31）"
"trips.txt" 33 "service_id" "土日祝（2026/7/17～2026/8/31）"
"trips.txt" 34 "service_id" "土日祝（2026/7/17～2026/8/31）"
"trips.txt" 35 "service_id" "全日（2026/9/1～2026/9/30）"
"trips.txt" 36 "service_id" "全日（2026/9/1～2026/9/30）"
"trips.txt" 37 "service_id" "全日（2026/9/1～2026/9/30）"
"trips.txt" 38 "service_id" "全日（2026/9/1～2026/9/30）"
"trips.txt" 39 "service_id" "全日（2026/9/1～2026/9/30）"
route_long_name_contains_short_name WARNING 3

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`.
"860" 2 "空港線" "空港線"
"862" 3 "空港線快速" "空港線快速"
"864" 4 "兼城港（比屋定）イーフ線" "兼城港（比屋定）イーフ線"
service_window_outside_feed_period INFO 3

service_window_outside_feed_period

A service window is not covered by the feed's validity period.

You can see more about this notice here.

serviceId (?) The service_id whose active window extends outside the feed validity period. serviceWindowStartDate (?) The first active date of the service window. serviceWindowEndDate (?) The last active date of the service window. daysBeforeFeedStart (?) Number of days the service window extends before feed_start_date (0 if none). daysAfterFeedEnd (?) Number of days the service window extends after feed_end_date (0 if none).
"平日（2026/7/17～2026/8/31）" "2026-07-17" "2026-08-31" 40 0
"土日祝（2026/7/17～2026/8/31）" "2026-07-18" "2026-08-30" 39 0
"全日（2026/7/17～2026/8/31）" "2026-07-17" "2026-08-31" 40 0