gtfs10-highway02oitakotsu — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-28T04:17:27Z,
for the dataset file:///shared/gtfs10-highway02oitakotsu_aa2cb77b.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
大分交通株式会社
Feed Email:
N/A
Feed Language:
Japanese
Feed Start Date:
2025-04-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. pattern_jp.txt
  10. routes.txt
  11. shapes.txt
  12. stop_times.txt
  13. stops.txt
  14. transfers.txt
  15. translations.txt
  16. trips.txt

Counts


  • Agencies: 5
  • Blocks: 0
  • Routes: 20
  • Shapes: 6
  • Stops: 46
  • Trips: 160

Specification Compliance report

51 notices reported (3 errors, 43 warnings, 5 infos)

Notice Code Severity Total
missing_required_column ERROR 3

missing_required_column

A required 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.
"translations.txt" "field_name"
"translations.txt" "language"
"translations.txt" "table_name"
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 "20260328" "20260331" "20260404"
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_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 22

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_long_name" "大分~福岡空港~博多(とよのくに号)" 2
"routes.txt" "route_long_name" "博多~福岡空港~大分(とよのくに号)" 3
"routes.txt" "route_long_name" "大分~博多(とよのくに号)" 4
"routes.txt" "route_long_name" "博多~大分(とよのくに号)" 5
"routes.txt" "route_long_name" "大分~長崎(サンライト号)" 6
"routes.txt" "route_long_name" "長崎~大分(サンライト号)" 7
"routes.txt" "route_long_name" "大分~福岡空港~博多(とよのくに号)" 8
"routes.txt" "route_long_name" "博多~福岡空港~大分(とよのくに号)" 9
"routes.txt" "route_long_name" "大分~博多(とよのくに号)" 10
"routes.txt" "route_long_name" "博多~大分(とよのくに号)" 11
"routes.txt" "route_long_name" "大分~福岡空港~博多(とよのくに号)" 12
"routes.txt" "route_long_name" "博多~福岡空港~大分(とよのくに号)" 13
"routes.txt" "route_long_name" "大分~博多(とよのくに号)" 14
"routes.txt" "route_long_name" "博多~大分(とよのくに号)" 15
"routes.txt" "route_long_name" "大分~長崎(サンライト号)" 16
"routes.txt" "route_long_name" "長崎~大分(サンライト号)" 17
"routes.txt" "route_long_name" "大分~長崎(サンライト号)" 18
"routes.txt" "route_long_name" "長崎~大分(サンライト号)" 19
"routes.txt" "route_long_name" "大分~長崎(サンライト号)" 20
"routes.txt" "route_long_name" "長崎~大分(サンライト号)" 21
"stops.txt" "stop_name" "中央通①(トキハ前)" 5
"stops.txt" "stop_name" "中央通り①(トキハ前)" 23
non_ascii_or_non_printable_char WARNING 15

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.

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.
"fare_attributes.txt" 2 "fare_id" "Agency1_運賃_大分_福岡_10"
"fare_attributes.txt" 40 "fare_id" "Agency2_運賃_大分_福岡_10"
"fare_attributes.txt" 41 "fare_id" "Agency3_運賃_大分_福岡_10"
"fare_rules.txt" 2 "fare_id" "Agency1_運賃_大分_福岡_10"
"fare_rules.txt" 3 "fare_id" "Agency1_運賃_大分_福岡_10"
"fare_rules.txt" 4 "fare_id" "Agency1_運賃_大分_福岡_10"
"fare_rules.txt" 5 "fare_id" "Agency1_運賃_大分_福岡_10"
"fare_rules.txt" 166 "fare_id" "Agency2_運賃_大分_福岡_10"
"fare_rules.txt" 167 "fare_id" "Agency2_運賃_大分_福岡_10"
"fare_rules.txt" 168 "fare_id" "Agency2_運賃_大分_福岡_10"
"fare_rules.txt" 169 "fare_id" "Agency2_運賃_大分_福岡_10"
"fare_rules.txt" 170 "fare_id" "Agency3_運賃_大分_福岡_10"
"fare_rules.txt" 171 "fare_id" "Agency3_運賃_大分_福岡_10"
"fare_rules.txt" 172 "fare_id" "Agency3_運賃_大分_福岡_10"
"fare_rules.txt" 173 "fare_id" "Agency3_運賃_大分_福岡_10"
stop_too_far_from_shape WARNING 2

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
138 "8020" "8020+1+1" 1140 "8002 2" "要町" [33.234325500000004,131.6075803] 187.24968860933492
150 "8021" "8321+1+1" 1330 "8002 1" "要町" [33.2346104,131.6073822] 223.59117685934652
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.
"20260328" "20240429" "20260331"
unknown_column INFO 2

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"translations.txt" "trans_id" 1
"translations.txt" "lang" 2
unknown_file INFO 3

unknown_file

A file is unknown.

You can see more about this notice here.

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