shinshirocity-sbus — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-07-11T09:12:17Z,
for the dataset file:///shared/shinshirocity-sbus_d821e094.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:
2026-04-06
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. stop_times.txt
  9. stops.txt
  10. transfers.txt
  11. translations.txt
  12. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 10
  • Shapes: 0
  • Stops: 156
  • Trips: 56

Specification Compliance report

2382 notices reported (0 errors, 2366 warnings, 16 infos)

Notice Code Severity Total
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 5

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" "Sバス塩瀬線(塩瀬布里循環線)" 9
"stops.txt" "stop_name" "もっくる新城(正面)" 24
"stops.txt" "stop_name" "新城総合公園(東側)" 25
"stops.txt" "stop_name" "1班消防詰所前" 43
"stops.txt" "stop_name" "柿本城跡(道の駅鳳来三河三石)" 96
non_ascii_or_non_printable_char WARNING 2357

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 2357 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.txt" 15 "service_id" "鳳来寺山もっくる新城線11月"
"calendar.txt" 16 "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" "夏季月~土盆休"
route_color_contrast WARNING 1

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeColor (?) The faulty record's HTML route color. routeTextColor (?) The faulty record's HTML route text color.
"12" 4 "#FFC000" "#FFFFFF"
big_gap_in_service INFO 8

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.
"北部登校日" "2026-07-17" "2026-09-01" 45
"北部登校日" "2026-12-23" "2027-01-07" 14
"北部登校日以外" "2026-04-07" "2026-07-21" 104
"北部登校日以外" "2026-08-31" "2026-12-24" 114
"北部登校日以外" "2027-01-06" "2027-03-25" 77
"秋葉登校日" "2026-07-17" "2026-09-01" 45
"秋葉登校日" "2026-12-23" "2027-01-07" 14
"鳳来寺山もっくる新城線通常月~土" "2026-10-31" "2026-12-01" 30
trip_headsign_matches_intermediate_stop INFO 6

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.

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 "3月~金_07時40分_系統101001" "新城市民病院" "110_03" 9 "164_01"
4 "3月~金_12時10分_系統101003" "バロー新城店" "150_01" 2 "150_01"
5 "3月~金_16時10分_系統101003" "バロー新城店" "150_01" 2 "150_01"
6 "3月~金_10時40分_系統101004" "バロー新城店" "150_01" 2 "150_01"
7 "3月~金_14時40分_系統101004" "バロー新城店" "150_01" 2 "150_01"
18 "3月~金_09時20分_系統121002" "バロー新城店" "150_01" 9 "150_01"
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