bus-takasaki-gunma — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-27T04:51:33Z,
for the dataset file:///shared/bus-takasaki-gunma_a62d335d.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:
2024-04-01
Feed End Date:
2025-03-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. routes.txt
  8. stop_times.txt
  9. stops.txt
  10. transfers.txt
  11. translations.txt
  12. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 13
  • Shapes: 0
  • Stops: 292
  • Trips: 158

Specification Compliance report

5205 notices reported (0 errors, 5128 warnings, 77 infos)

Notice Code Severity Total
expired_calendar WARNING 13

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 "全日"
3 "月曜日から金曜日"
4 "土日祝日"
5 "月曜日から土曜日"
6 "はるバス月曜日から土曜日"
7 "はるバス学"
8 "よしいバス学"
9 "よしいバス月土"
10 "よしいバス月金"
11 "アリーナ(元日除く)"
12 "アリーナ(通常)"
13 "新町線月金"
14 "新町線月土"
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 "20260627" "20250331" "20260704"
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 2

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.
"fare_attributes.txt" 2 "agency_id"
"fare_attributes.txt" 3 "agency_id"
mixed_case_recommended_field WARNING 15

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" "0 ぐるりん都心循環線" 2
"routes.txt" "route_long_name" "11 ぐるりん倉賀野線" 3
"routes.txt" "route_long_name" "12 ぐるりん倉賀野線" 4
"routes.txt" "route_long_name" "13 ぐるりん観音山線" 5
"routes.txt" "route_long_name" "14 ぐるりん観音山線" 6
"routes.txt" "route_long_name" "35 ぐるりん新町線" 7
"routes.txt" "route_long_name" "36 ぐるりん新町線" 8
"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
"stops.txt" "stop_name" "総合保健センター・中央図書館" 14
"stops.txt" "stop_name" "東京電力・スズラン入口" 16
"stops.txt" "stop_name" "モントレー・オーパ前" 22
non_ascii_or_non_printable_char WARNING 5095

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 5095 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" "全日"
"calendar.txt" 3 "service_id" "月曜日から金曜日"
"calendar.txt" 4 "service_id" "土日祝日"
"calendar.txt" 5 "service_id" "月曜日から土曜日"
"calendar.txt" 6 "service_id" "はるバス月曜日から土曜日"
"calendar.txt" 7 "service_id" "はるバス学"
"calendar.txt" 8 "service_id" "よしいバス学"
"calendar.txt" 9 "service_id" "よしいバス月土"
"calendar.txt" 10 "service_id" "よしいバス月金"
"calendar.txt" 11 "service_id" "アリーナ(元日除く)"
"calendar.txt" 12 "service_id" "アリーナ(通常)"
"calendar.txt" 13 "service_id" "新町線月金"
"calendar.txt" 14 "service_id" "新町線月土"
"calendar_dates.txt" 2 "service_id" "アリーナ(元日除く)"
"calendar_dates.txt" 3 "service_id" "はるバス学"
"calendar_dates.txt" 4 "service_id" "はるバス学"
"calendar_dates.txt" 5 "service_id" "はるバス学"
"calendar_dates.txt" 6 "service_id" "はるバス学"
"calendar_dates.txt" 7 "service_id" "はるバス学"
"calendar_dates.txt" 8 "service_id" "はるバス学"
"calendar_dates.txt" 9 "service_id" "はるバス学"
"calendar_dates.txt" 10 "service_id" "はるバス学"
"calendar_dates.txt" 11 "service_id" "はるバス学"
"calendar_dates.txt" 12 "service_id" "はるバス学"
"calendar_dates.txt" 13 "service_id" "はるバス学"
"calendar_dates.txt" 14 "service_id" "はるバス学"
"calendar_dates.txt" 15 "service_id" "はるバス学"
"calendar_dates.txt" 16 "service_id" "はるバス学"
"calendar_dates.txt" 17 "service_id" "はるバス学"
"calendar_dates.txt" 18 "service_id" "はるバス学"
"calendar_dates.txt" 19 "service_id" "はるバス学"
"calendar_dates.txt" 20 "service_id" "はるバス学"
"calendar_dates.txt" 21 "service_id" "はるバス学"
"calendar_dates.txt" 22 "service_id" "はるバス学"
"calendar_dates.txt" 23 "service_id" "はるバス学"
"calendar_dates.txt" 24 "service_id" "はるバス学"
"calendar_dates.txt" 25 "service_id" "はるバス学"
"calendar_dates.txt" 26 "service_id" "はるバス学"
"calendar_dates.txt" 27 "service_id" "はるバス学"
"calendar_dates.txt" 28 "service_id" "はるバス学"
"calendar_dates.txt" 29 "service_id" "はるバス学"
"calendar_dates.txt" 30 "service_id" "はるバス学"
"calendar_dates.txt" 31 "service_id" "はるバス学"
"calendar_dates.txt" 32 "service_id" "はるバス学"
"calendar_dates.txt" 33 "service_id" "はるバス学"
"calendar_dates.txt" 34 "service_id" "はるバス学"
"calendar_dates.txt" 35 "service_id" "はるバス学"
"calendar_dates.txt" 36 "service_id" "はるバス学"
"calendar_dates.txt" 37 "service_id" "はるバス学"
"calendar_dates.txt" 38 "service_id" "はるバス学"
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.
"20260627" "20240401" "20250331"
big_gap_in_service INFO 4

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
"はるバス学" "2024-07-19" "2024-09-02" 44
"はるバス学" "2024-12-19" "2025-01-06" 17
"よしいバス学" "2024-07-19" "2024-09-02" 44
"よしいバス学" "2024-12-19" "2025-01-06" 17
platform_without_parent_station INFO 2

platform_without_parent_station

A platform has no parent_station field set.

This is different from location_without_parent_station since it is less severe.

You can see more about this notice here.

csvRowNumber (?) Row number of the faulty record. stopId (?) The id of the faulty record. stopName (?) The stop name of the faulty record.
2 "1_03" "高崎駅西口"
3 "1_04" "高崎駅西口"
trip_headsign_matches_intermediate_stop INFO 69

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record in `trips.txt`. tripId (?) The id of the trip with the problematic headsign. tripHeadsign (?) The headsign value that matches an intermediate stop name. stopId1 (?) The id of the intermediate stop whose name matches the headsign. stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign. stopId2 (?) The id of the actual last stop of the trip.
2 "1全日_09時00分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
3 "1全日_09時20分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
4 "1全日_09時40分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
5 "1全日_10時00分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
6 "1全日_10時20分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
7 "1全日_10時40分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
8 "1全日_11時00分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
9 "1全日_11時20分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
10 "1全日_11時40分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
11 "1全日_12時00分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
12 "1全日_12時20分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
13 "1全日_12時40分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
14 "1全日_13時00分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
15 "1全日_13時20分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
16 "1全日_13時40分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
17 "1全日_14時00分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
18 "1全日_14時20分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
19 "1全日_14時40分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
20 "1全日_15時00分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
21 "1全日_15時20分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
22 "1全日_15時40分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
23 "1全日_16時00分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
24 "1全日_16時20分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
25 "1全日_16時40分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
26 "1全日_17時00分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
27 "1全日_17時20分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
28 "1全日_17時40分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
29 "1全日_18時00分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
30 "2月曜日から金曜日_07時40分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
31 "2月曜日から金曜日_08時00分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
32 "2月曜日から金曜日_08時20分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
33 "2月曜日から金曜日_08時40分_系統1001" "高崎駅西口" "1_04" 1 "1_05"
34 "1全日_07時58分_系統111001" "高崎駅西口" "1_03" 1 "1_05"
35 "1全日_09時26分_系統111001" "高崎駅西口" "1_03" 1 "1_05"
36 "1全日_10時54分_系統111001" "高崎駅西口" "1_03" 1 "1_05"
37 "1全日_12時42分_系統111001" "高崎駅西口" "1_03" 1 "1_05"
38 "1全日_14時10分_系統111001" "高崎駅西口" "1_03" 1 "1_05"
39 "1全日_15時38分_系統111001" "高崎駅西口" "1_03" 1 "1_05"
40 "1全日_17時10分_系統111001" "高崎駅西口" "1_03" 1 "1_05"
41 "2月曜日から金曜日_06時30分_系統111001" "高崎駅西口" "1_03" 1 "1_05"
42 "1全日_07時43分_系統112001" "高崎駅西口" "1_03" 1 "1_05"
43 "1全日_09時11分_系統112001" "高崎駅西口" "1_03" 1 "1_05"
44 "1全日_10時39分_系統112001" "高崎駅西口" "1_03" 1 "1_05"
45 "1全日_12時27分_系統112001" "高崎駅西口" "1_03" 1 "1_05"
46 "1全日_13時55分_系統112001" "高崎駅西口" "1_03" 1 "1_05"
47 "1全日_15時23分_系統112001" "高崎駅西口" "1_03" 1 "1_05"
48 "1全日_16時51分_系統112001" "高崎駅西口" "1_03" 1 "1_05"
49 "1全日_18時19分_系統112001" "高崎駅西口" "1_03" 1 "1_05"
50 "2月曜日から金曜日_06時15分_系統112001" "高崎駅西口" "1_03" 1 "1_05"
51 "2月曜日から金曜日_19時50分_系統112001" "高崎駅西口" "1_03" 1 "1_05"
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.
"trips.txt" "jp_trip_desc" 9
"trips.txt" "jp_pattern_id" 10