GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T21:24:51Z,
for the dataset file:///shared/yabucity-waiwai-sekimiya-yoka.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
ジョルダン株式会社
Publisher URL:
http://www.jorudan.co.jp
Feed Email:
N/A
Feed Language:
Japanese
Feed Start Date:
2021-10-01
Feed End Date:
2024-12-31

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. office_jp.txt
  8. routes.txt
  9. routes_jp.txt
  10. stop_times.txt
  11. stops.txt
  12. translations.txt
  13. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 13
  • Shapes: 0
  • Stops: 71
  • Trips: 33

Specification Compliance report

63 notices reported (0 errors, 60 warnings, 3 infos)

Notice Code Severity Total
duplicate_route_name WARNING 8

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 "R1" 3 "R2" "" "関宮ふれあいバス［ハチ高原線］" 3 "3000020282227"
4 "R3" 5 "R4" "" "関宮ふれあいバス［轟・鵜縄線］" 3 "3000020282227"
6 "R5" 7 "R6" "" "わいわいバス［高中～上野・Ｙタウン線］" 3 "3000020282227"
8 "R7" 9 "R8" "" "わいわいバス［畑～上野・Ｙタウン線］" 3 "3000020282227"
8 "R7" 10 "R9" "" "わいわいバス［畑～上野・Ｙタウン線］" 3 "3000020282227"
8 "R7" 11 "R10" "" "わいわいバス［畑～上野・Ｙタウン線］" 3 "3000020282227"
12 "R11" 13 "R12" "" "八鹿コミュニティバス" 3 "3000020282227"
12 "R11" 14 "R13" "" "八鹿コミュニティバス" 3 "3000020282227"
expired_calendar WARNING 2

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 "S1"
3 "S2"
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 "20251205" "20241231" "20251212"
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 37

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"
"fare_attributes.txt" 2 "agency_id"
"fare_attributes.txt" 3 "agency_id"
"fare_attributes.txt" 4 "agency_id"
"fare_attributes.txt" 5 "agency_id"
"fare_attributes.txt" 6 "agency_id"
"fare_attributes.txt" 7 "agency_id"
"fare_attributes.txt" 8 "agency_id"
"fare_attributes.txt" 9 "agency_id"
"fare_attributes.txt" 10 "agency_id"
"fare_attributes.txt" 11 "agency_id"
"fare_attributes.txt" 12 "agency_id"
"fare_attributes.txt" 13 "agency_id"
"fare_attributes.txt" 14 "agency_id"
"fare_attributes.txt" 15 "agency_id"
"fare_attributes.txt" 16 "agency_id"
"fare_attributes.txt" 17 "agency_id"
"fare_attributes.txt" 18 "agency_id"
"fare_attributes.txt" 19 "agency_id"
"fare_attributes.txt" 20 "agency_id"
"fare_attributes.txt" 21 "agency_id"
"fare_attributes.txt" 22 "agency_id"
"fare_attributes.txt" 23 "agency_id"
"fare_attributes.txt" 24 "agency_id"
"fare_attributes.txt" 25 "agency_id"
"fare_attributes.txt" 26 "agency_id"
"fare_attributes.txt" 27 "agency_id"
"fare_attributes.txt" 28 "agency_id"
"fare_attributes.txt" 29 "agency_id"
"fare_attributes.txt" 30 "agency_id"
"fare_attributes.txt" 31 "agency_id"
"fare_attributes.txt" 32 "agency_id"
"fare_attributes.txt" 33 "agency_id"
"fare_attributes.txt" 34 "agency_id"
"fare_attributes.txt" 35 "agency_id"
"fare_attributes.txt" 36 "agency_id"
"fare_attributes.txt" 37 "agency_id"
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.
"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
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.
"20251205" "20211001" "20241227"
unknown_column INFO 1

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.
"routes.txt" "jp_parent_route_id" 8
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.
"office_jp.txt"
"routes_jp.txt"