goshogawara-communitybus — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-17T12:50:07Z,
for the dataset file:///shared/goshogawara-communitybus_e255e5fd.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-03-27
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. transfers.txt
  12. translations.txt
  13. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 6
  • Shapes: 15
  • Stops: 123
  • Trips: 18

Specification Compliance report

485 notices reported (0 errors, 483 warnings, 2 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 1

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"
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.
"trips.txt" "trip_headsign" "金木タウンセンター(ノア)" 14
"trips.txt" "trip_headsign" "金木タウンセンター(ノア)" 17
"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
"stops.txt" "stop_name" "金木タウンセンター(ノア)" 68
"stops.txt" "stop_name" "有限会社なかにし第3資材置場付近" 117
non_ascii_or_non_printable_char WARNING 471

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 471 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.
"trips.txt" 2 "trip_id" "1月曜_08時45分_系統10101"
"trips.txt" 2 "service_id" "月曜"
"trips.txt" 3 "trip_id" "1月曜_10時50分_系統10201"
"trips.txt" 3 "service_id" "月曜"
"trips.txt" 4 "trip_id" "1月曜_12時09分_系統10202"
"trips.txt" 4 "service_id" "月曜"
"trips.txt" 5 "trip_id" "3水曜_08時40分_系統20101"
"trips.txt" 5 "service_id" "水曜"
"trips.txt" 6 "trip_id" "3水曜_10時50分_系統20201"
"trips.txt" 6 "service_id" "水曜"
"trips.txt" 7 "trip_id" "3水曜_12時00分_系統20202"
"trips.txt" 7 "service_id" "水曜"
"trips.txt" 8 "trip_id" "5金曜_08時40分_系統30101"
"trips.txt" 8 "service_id" "金曜"
"trips.txt" 9 "trip_id" "5金曜_10時50分_系統30201"
"trips.txt" 9 "service_id" "金曜"
"trips.txt" 10 "trip_id" "5金曜_12時00分_系統30202"
"trips.txt" 10 "service_id" "金曜"
"trips.txt" 11 "trip_id" "2火曜_08時50分_系統40101"
"trips.txt" 11 "service_id" "火曜"
"trips.txt" 12 "trip_id" "2火曜_12時30分_系統40201"
"trips.txt" 12 "service_id" "火曜"
"trips.txt" 13 "trip_id" "2火曜_14時20分_系統40201"
"trips.txt" 13 "service_id" "火曜"
"trips.txt" 14 "trip_id" "3水曜_08時45分_系統50101"
"trips.txt" 14 "service_id" "水曜"
"trips.txt" 15 "trip_id" "3水曜_12時30分_系統50201"
"trips.txt" 15 "service_id" "水曜"
"trips.txt" 16 "trip_id" "3水曜_14時20分_系統50201"
"trips.txt" 16 "service_id" "水曜"
"trips.txt" 17 "trip_id" "4木曜_08時50分_系統60101"
"trips.txt" 17 "service_id" "木曜"
"trips.txt" 18 "trip_id" "4木曜_12時30分_系統60201"
"trips.txt" 18 "service_id" "木曜"
"trips.txt" 19 "trip_id" "4木曜_14時25分_系統60201"
"trips.txt" 19 "service_id" "木曜"
"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_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" "火曜"
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