Feed status · checked 2026-07-19
Kakogawa City Kako Bus (加古川市かこバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Hyogo, Japan.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.2, validator 8.0.1.
Checked for changes 4 hours ago; last changed 4 hours ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
404 of 404 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
500 of 500 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.
Some internal IDs use characters outside the basic text set. These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
⏱ A planned ID change, not a quick text cleanup.worth about +8 points in its category
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 134 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 5 kinds of issue across 13001 instances (0 error, 12997 warning, 4 informational).
Service data covers the next 134 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
10 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (かこバス・浜手ルート, かこバスミニ・志方西ルート, かこバスミニ・志方中ルート, かこバスミニ・志方中ルート（こども療育センター経由）, かこバスミニ・志方東ルート, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- かこバス・浜手ルート (red)
- かこバス・別府ルート (teal)
- かこバス・鳩里・尾上ルート (orange)
- かこバスミニ・平岡北ルート (yellow)
- 病院ライナー (green)
- かこバスミニ・平岡東南ルート (blue)
- かこバスミニ・志方西ルート (green)
- かこバスミニ・志方中ルート (red)
- かこバスミニ・志方中ルート（こども療育センター経由） (orange)
- かこバスミニ・志方東ルート (teal)
- かこバスミニ・山手ルート (pink)
- かこバスミニ・平岡東ルート (teal)
- かこバス・東加古川ルート (green)
| Route | Type | Line color |
|---|---|---|
| かこバス・浜手ルート | Bus | red |
| かこバス・別府ルート | Bus | teal |
| かこバス・鳩里・尾上ルート | Bus | orange |
| かこバスミニ・平岡北ルート | Bus | yellow |
| 病院ライナー | Bus | green |
| かこバスミニ・平岡東南ルート | Bus | blue |
| かこバスミニ・志方西ルート | Bus | green |
| かこバスミニ・志方中ルート | Bus | red |
| かこバスミニ・志方中ルート（こども療育センター経由） | Bus | orange |
| かこバスミニ・志方東ルート | Bus | teal |
| かこバスミニ・山手ルート | Bus | pink |
| かこバスミニ・平岡東ルート | Bus | teal |
| かこバス・東加古川ルート | Bus | green |
This feed has 404 stops.
List every stop
- 陵北小学校前
- 陵北小学校前
- 新神野局前
- 新神野局前
- 新神野５丁目
- 新神野５丁目
- 新神野３丁目
- 新神野３丁目
- 神野駅前
- 神野駅前
- 新神野４丁目東
- 新神野４丁目東
- 西条山手１丁目
- 西条山手１丁目
- 西条山手郵便局前
- 西条山手郵便局前
- 加古川北公民館
- 西条山手２丁目
- 西条山手２丁目
- 南備後
- 南備後
- 北山公園
- 北山公園
- 山手２丁目
- 山手２丁目
- 兵中北山公園
- 兵中北山公園
- はくほう会加古川病院
- 山手公民館
- 山手公民館
- はぐるまの家
- はぐるまの家
- 山手３丁目
- 山手３丁目
- 東神野公園
- 東神野公園
- 高岡
- 高岡
- 高岡会館
- 旭西
- 旭西
- 尾上の松駅
- 喜瀬川台３号棟前
- 喜瀬川台４号棟前
- 喜瀬川台４号棟前
- 平岡団地３号棟前
- 平岡団地３号棟前
- 平岡団地20号棟前
- 平岡団地20号棟前
- 平岡団地集会室前
- 平岡団地集会室前
- 大崎
- 大崎
- 宮地医院
- 宮地医院
- 平岡東小学校南
- 平岡東小学校南
- 土山駅南口
- JA加古川南 土山支所
- JA加古川南 土山支所
- 土山公会堂
- 土山公会堂
- リカーショップ小南
- リカーショップ小南
- 平岡公民館
- イオンタウン東加古川
- 北在家東口
- 北在家東口
- 良野南口
- 良野南口
- 養田
- 養田
- 良野東口
- 良野東口
- 長砂西口
- 長砂西口
- 長砂公民館前
- 長砂公民館前
- 長砂東口
- 長砂東口
- 古大内中曽根会館前
- 古大内中曽根会館前
- 二屋南口
- 二屋南口
- 南芳苑・かこてらす前
- 南芳苑・かこてらす前
- 二俣西口
- 二俣西口
- 二俣
- 二俣
- 中野
- 中野
- 長田
- 長田
- 万葉ハイツ前
- 万葉ハイツ前
- 神鋼二俣社宅前
- 神鋼二俣社宅前
- 山之上西口
- 山之上西口
- 平岡幼稚園前
- 平岡幼稚園前
- 平岡小学校前
- 平岡小学校前
- 西谷
- 西谷
- 新在家東口
- 新在家東口
- 国道東加古川
- 東加古川
- 東加古川駅
- 池田西口
- 池田西口
- 木村南
- 木村南
- 稲屋
- 稲屋
- 友沢北
- 友沢北
- 友沢南
- 友沢南
- 稲屋中央
- 稲屋中央
- 稲屋南
- 稲屋南
- 養田北
- 養田北
- 今福南
- 今福南
- 東深田公園
- 東深田公園
- 尾上市民センター前
- 尾上市民センター前
- 池田
- 池田
- 池田西
- 池田西
- 池田南
- 池田南
- 池田公園前
- 池田公園前
- 尾上公民館前
- 尾上公民館前
- 平野
- 平野
- 平野東
- 平野東
- 水道局前
- 水道局前
- 松風ギャラリー前
- 松風ギャラリー前
- 安田北
- 安田北
- 鶴林寺
- 鶴林寺
- 浜の宮公園南
- 浜の宮公園南
- 十王堂
- 十王堂
- 長田公園前
- 長田公園前
- Ｍプラザ前
- Ｍプラザ前
- 浜の宮駅北
- 浜の宮駅北
- 浜の宮駅
- 浜の宮天神社北
- 新野辺北町3丁目西
- 新野辺北町3丁目東
- 新野辺北町2丁目
- 別府東町
- 別府東町
- 別府西小学校前
- 別府西小学校前
- 加古川駅
- 加古川駅
- スポーツ交流館前
- スポーツ交流館前
- 海洋文化センター前
- 生駒橋
- 新野辺北町5丁目西
- 新野辺北町5丁目東
- 別府中学校前
- 新野辺第9
- 別府駅北
- 原
- 原
- 山中公会堂
- 新野辺
- 新野辺
- 投松公会堂
- 野口山
- 鶴池北公園
- 鶴池北公園
- 鶴池中央公園
- 総合文化センター
- 平岡北幼稚園南
- 平岡北幼稚園南
- 中央公園
- 北芳苑公会堂
- 北芳苑公会堂
- ネオハイツ前
- ネオハイツ前
- 野辻
- 野辻
- 別府公民館前
- 別府公民館前
- 兵庫大学東
- 兵庫大学東
- 寺田
- 高下集会所
- 高下集会所
- 高畑公園
- ハローズ
- 医療モール前
- 医療モール前
- 東加古川駅
- 加古川中央市民病院
- 北野添２丁目
- 北野添２丁目
- 西野添１丁目
- 西野添１丁目
- 加古のうみこども園前
- 加古のうみこども園前
- 蓮池小学校前
- 蓮池小学校前
- 野添北公園前
- 野添北公園前
- 野添城３丁目
- 野添城３丁目
- 大中遺跡南
- 城の宮第２公園
- 大西医院
- 高畑辻ヶ内
- 高畑辻ヶ内
- ハローズ前
- ハローズ前
- JR宝殿駅
- 近畿安全衛生技術センター前
- 近畿安全衛生技術センター前
- 別府駅
- 西之山公民館
- 中村公民館前
- 中村公民館前
- 日岡苑
- 別府駅南
- 別府駅南
- 別府
- 別府
- 宝殿駅
- and 154 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 78.3 | first check |
| 2026-07-19 | 78.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-18.
Same feed file as 2026-07-18; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
7 findings, ordered by severity.
Show every finding
- Warning12939 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Validator rule: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning500 instances
500 of 500 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning404 instances
404 of 404 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning57 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 134 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 134 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.
- Correctness 79 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
- Rider experience 60 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/kakogawa-city-kako-bus/2026-07-19.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-07-19. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.