Search
  1. Home
  2. Japan Feeds
  3. suwacity-karinchanbas
  4. Source Data Validation Report

suwacity-karinchanbas — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-24T00:14:30Z,
for the dataset file:///shared/suwacity-karinchanbas_b5addd06.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-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. stop_times.txt
  9. stops.txt
  10. transfers.txt
  11. translations.txt
  12. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 5
  • Shapes: 0
  • Stops: 169
  • Trips: 25

Specification Compliance report

1235 notices reported (0 errors, 1233 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 11

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" "上諏訪駅諏訪湖口（西口）" 2
"trips.txt" "trip_headsign" "上諏訪駅諏訪湖口（西口）" 12
"trips.txt" "trip_headsign" "上諏訪駅諏訪湖口（西口）" 13
"trips.txt" "trip_headsign" "上諏訪駅諏訪湖口（西口）" 14
"trips.txt" "trip_headsign" "上諏訪駅諏訪湖口（西口）" 15
"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
non_ascii_or_non_printable_char WARNING 1220

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 1220 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全日_06時45分_系統101"
"trips.txt" 2 "service_id" "全日"
"trips.txt" 3 "trip_id" "1全日_16時42分_系統102"
"trips.txt" 3 "service_id" "全日"
"trips.txt" 4 "trip_id" "1全日_18時20分_系統103"
"trips.txt" 4 "service_id" "全日"
"trips.txt" 5 "trip_id" "1全日_06時40分_系統201"
"trips.txt" 5 "service_id" "全日"
"trips.txt" 6 "trip_id" "1全日_16時50分_系統202"
"trips.txt" 6 "service_id" "全日"
"trips.txt" 7 "trip_id" "1全日_18時40分_系統203"
"trips.txt" 7 "service_id" "全日"
"trips.txt" 8 "trip_id" "1全日_08時05分_系統301"
"trips.txt" 8 "service_id" "全日"
"trips.txt" 9 "trip_id" "1全日_10時20分_系統302"
"trips.txt" 9 "service_id" "全日"
"trips.txt" 10 "trip_id" "1全日_12時20分_系統303"
"trips.txt" 10 "service_id" "全日"
"trips.txt" 11 "trip_id" "1全日_14時15分_系統304"
"trips.txt" 11 "service_id" "全日"
"trips.txt" 12 "trip_id" "1全日_08時00分_系統401"
"trips.txt" 12 "service_id" "全日"
"trips.txt" 13 "trip_id" "1全日_09時45分_系統402"
"trips.txt" 13 "service_id" "全日"
"trips.txt" 14 "trip_id" "1全日_11時40分_系統403"
"trips.txt" 14 "service_id" "全日"
"trips.txt" 15 "trip_id" "1全日_13時30分_系統404"
"trips.txt" 15 "service_id" "全日"
"trips.txt" 16 "trip_id" "2平日_06時26分_系統501"
"trips.txt" 16 "service_id" "平日"
"trips.txt" 17 "trip_id" "2平日_06時40分_系統502"
"trips.txt" 17 "service_id" "平日"
"trips.txt" 18 "trip_id" "2平日_07時18分_系統503"
"trips.txt" 18 "service_id" "平日"
"trips.txt" 19 "trip_id" "2平日_07時50分_系統504"
"trips.txt" 19 "service_id" "平日"
"trips.txt" 20 "trip_id" "2平日_09時30分_系統505"
"trips.txt" 20 "service_id" "平日"
"trips.txt" 21 "trip_id" "2平日_13時10分_系統506"
"trips.txt" 21 "service_id" "平日"
"trips.txt" 22 "trip_id" "2平日_14時50分_系統507"
"trips.txt" 22 "service_id" "平日"
"trips.txt" 23 "trip_id" "2平日_16時35分_系統508"
"trips.txt" 23 "service_id" "平日"
"trips.txt" 24 "trip_id" "2平日_17時30分_系統509"
"trips.txt" 24 "service_id" "平日"
"trips.txt" 25 "trip_id" "2平日_18時38分_系統510"
"trips.txt" 25 "service_id" "平日"
"trips.txt" 26 "trip_id" "2平日_19時20分_系統511"
"trips.txt" 26 "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