Search
  1. Home
  2. Japan Feeds
  3. gtfs10-highway04hita
  4. Source Data Validation Report

gtfs10-highway04hita — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-23T21:09:33Z,
for the dataset file:///shared/gtfs10-highway04hita_988929ec.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
日田バス株式会社
Publisher URL:
https://hitabus.com/
Feed Email:
N/A
Feed Language:
Japanese
Feed Start Date:
2026-04-01
Feed End Date:
2027-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: 3
  • Blocks: 0
  • Routes: 18
  • Shapes: 12
  • Stops: 51
  • Trips: 199

Specification Compliance report

36 notices reported (3 errors, 28 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"
duplicate_route_name WARNING 5

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`.
2 "24-down" 6 "28-down" "" "日田～福岡（ひた号）" 3 "6320001010183"
3 "25-up" 7 "29-up" "" "福岡～日田（ひた号）" 3 "6320001010183"
11 "124-down" 15 "128-down" "" "日田～福岡（ひた号）" 3 "4290001009413"
12 "125-up" 16 "129-up" "" "福岡～日田（ひた号）" 3 "4290001009413"
11 "124-down" 17 "131-down" "" "日田～福岡（ひた号）" 3 "4290001009413"
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
mixed_case_recommended_field WARNING 20

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.
"stops.txt" "stop_name" "筑紫野・二日市温泉入口" 44
"stops.txt" "stop_name" "筑紫野・二日市温泉入口" 45
"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
unused_shape WARNING 2

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"36 9" 11869
"37 0" 12692
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.
"agency_jp.txt"
"pattern_jp.txt"
"office_jp.txt"