minamishinshu-minamishinshu-shinnan-1 — Enhanced Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-09T19:45:22Z,
for the dataset file:///shared/minamishinshu-minamishinshu-shinnan-1_009c166c.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
Japanese
Feed Start Date:
2026-04-01
Feed End Date:
2027-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. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. translations.txt
  12. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 6
  • Shapes: 26
  • Stops: 288
  • Trips: 94

Specification Compliance report

3809 notices reported (0 errors, 3809 warnings, 0 infos)

Notice Code Severity Total
duplicate_route_name WARNING 2

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`.
4 "105442-3L" 5 "105442-3LA" "E0 阿島線" "" 3 "105442-2100001022519"
4 "105442-3L" 6 "105442-3R" "E0 阿島線" "" 3 "105442-2100001022519"
missing_recommended_field WARNING 7

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"
"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"
mixed_case_recommended_field WARNING 16

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" "中央通り3丁目" 6
"stops.txt" "stop_name" "中央通り3丁目" 7
"stops.txt" "stop_name" "中央通り1丁目" 8
"stops.txt" "stop_name" "知久町1丁目" 9
"stops.txt" "stop_name" "一色アップルロード(イオン前)" 16
"stops.txt" "stop_name" "一色アップルロード(平安堂前)" 17
"stops.txt" "stop_name" "名古熊東(アピタ前)" 20
"stops.txt" "stop_name" "名古熊東(信金前)" 21
"stops.txt" "stop_name" "伝馬町1丁目" 37
"stops.txt" "stop_name" "伝馬町1丁目" 38
"stops.txt" "stop_name" "知久町3丁目" 39
"stops.txt" "stop_name" "エス・バード" 171
"stops.txt" "stop_name" "宮の前(南信濃)" 213
"stops.txt" "stop_name" "宮の前(南信濃)" 214
"stops.txt" "stop_name" "診療所前(上村)" 237
"stops.txt" "stop_name" "診療所前(上村)" 238
non_ascii_or_non_printable_char WARNING 3782

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 3782 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" "105442-土日祝"
"calendar.txt" 3 "service_id" "105442-土曜日"
"calendar.txt" 4 "service_id" "105442-平日"
"calendar.txt" 5 "service_id" "105442-日祝日"
"calendar_dates.txt" 2 "service_id" "105442-土日祝"
"calendar_dates.txt" 3 "service_id" "105442-土日祝"
"calendar_dates.txt" 4 "service_id" "105442-土日祝"
"calendar_dates.txt" 5 "service_id" "105442-土日祝"
"calendar_dates.txt" 6 "service_id" "105442-土日祝"
"calendar_dates.txt" 7 "service_id" "105442-土日祝"
"calendar_dates.txt" 8 "service_id" "105442-土日祝"
"calendar_dates.txt" 9 "service_id" "105442-土日祝"
"calendar_dates.txt" 10 "service_id" "105442-土日祝"
"calendar_dates.txt" 11 "service_id" "105442-土日祝"
"calendar_dates.txt" 12 "service_id" "105442-土日祝"
"calendar_dates.txt" 13 "service_id" "105442-土日祝"
"calendar_dates.txt" 14 "service_id" "105442-土日祝"
"calendar_dates.txt" 15 "service_id" "105442-土日祝"
"calendar_dates.txt" 16 "service_id" "105442-土日祝"
"calendar_dates.txt" 17 "service_id" "105442-土日祝"
"calendar_dates.txt" 18 "service_id" "105442-土日祝"
"calendar_dates.txt" 19 "service_id" "105442-土日祝"
"calendar_dates.txt" 20 "service_id" "105442-土曜日"
"calendar_dates.txt" 21 "service_id" "105442-土曜日"
"calendar_dates.txt" 22 "service_id" "105442-平日"
"calendar_dates.txt" 23 "service_id" "105442-平日"
"calendar_dates.txt" 24 "service_id" "105442-平日"
"calendar_dates.txt" 25 "service_id" "105442-平日"
"calendar_dates.txt" 26 "service_id" "105442-平日"
"calendar_dates.txt" 27 "service_id" "105442-平日"
"calendar_dates.txt" 28 "service_id" "105442-平日"
"calendar_dates.txt" 29 "service_id" "105442-平日"
"calendar_dates.txt" 30 "service_id" "105442-平日"
"calendar_dates.txt" 31 "service_id" "105442-平日"
"calendar_dates.txt" 32 "service_id" "105442-平日"
"calendar_dates.txt" 33 "service_id" "105442-平日"
"calendar_dates.txt" 34 "service_id" "105442-平日"
"calendar_dates.txt" 35 "service_id" "105442-平日"
"calendar_dates.txt" 36 "service_id" "105442-平日"
"calendar_dates.txt" 37 "service_id" "105442-平日"
"calendar_dates.txt" 38 "service_id" "105442-平日"
"calendar_dates.txt" 39 "service_id" "105442-平日"
"calendar_dates.txt" 40 "service_id" "105442-平日"
"calendar_dates.txt" 41 "service_id" "105442-日祝日"
"calendar_dates.txt" 42 "service_id" "105442-日祝日"
"calendar_dates.txt" 43 "service_id" "105442-日祝日"
"calendar_dates.txt" 44 "service_id" "105442-日祝日"
"calendar_dates.txt" 45 "service_id" "105442-日祝日"
"calendar_dates.txt" 46 "service_id" "105442-日祝日"
"calendar_dates.txt" 47 "service_id" "105442-日祝日"
stops_match_shape_out_of_order WARNING 2

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

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. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
54 "105442-12006" "105442-1平日_16時30分_系統12006" 1503 "105442-1529_01" "中関団地入口" [35.44799759370736,137.75467302543666] 1502 "105442-1528_01" "阿智高校前" [35.448625017084,137.75673981025435]
38 "105442-12003" "105442-1平日_16時10分_系統12003" 1017 "105442-1529_01" "中関団地入口" [35.44799759370736,137.75467302543666] 1016 "105442-1528_01" "阿智高校前" [35.448625017084,137.75673981025435]