Feed status · checked 2026-09-05
Akaiwa City Bus (赤磐市広域路線バス・市民バス)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Okayama, 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.3, validator 8.0.1.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
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
361 of 361 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
133 of 133 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
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 361 of 361 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 133 of 133 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some internal IDs use characters outside the basic text set.
- Next action
- 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.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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 327 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 6 kinds of issue across 19270 instances (0 error, 19269 warning, 1 informational).
Service data covers the next 327 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
7 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.
This feed has 361 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 赤磐・和気線 (orange)
- 赤磐市広域路線バス赤磐・瀬戸線 (purple)
- 赤磐市広域路線バス赤磐・美作線 (purple)
- 赤磐市民バス可真・桜が丘東線 (blue)
- 赤磐市民バス小野田線 (orange)
- 赤磐市民バス山陽団地線 (orange)
- 赤磐市民バス山陽団地線 (orange)
- 赤磐市民バス山陽団地線 (orange)
- 赤磐市民バス松木・下市線 (pink)
- 赤磐市民バス西山線 (green)
- 赤磐市民バス豊田・熊山線 (green)
- 赤磐市民バス高月・高陽南線 (teal)
- 赤磐市民バス高陽北西線 (pink)
| Route | Type | Line color |
|---|---|---|
| 赤磐・和気線 赤磐市広域路線バス赤磐・和気線 | Bus | orange |
| 赤磐市広域路線バス赤磐・瀬戸線 | Bus | purple |
| 赤磐市広域路線バス赤磐・美作線 赤磐・美作線 | Bus | purple |
| 赤磐市民バス可真・桜が丘東線 可真・桜が丘東線 | Bus | blue |
| 赤磐市民バス小野田線 小野田線 | Bus | orange |
| 赤磐市民バス山陽団地線 山陽団地線 | Bus | orange |
| 赤磐市民バス山陽団地線 | Bus | orange |
| 赤磐市民バス山陽団地線 | Bus | orange |
| 赤磐市民バス松木・下市線 松木・下市線 | Bus | pink |
| 赤磐市民バス西山線 西山線 | Bus | green |
| 赤磐市民バス豊田・熊山線 豊田・熊山線 | Bus | green |
| 赤磐市民バス高月・高陽南線 高月・高陽南線 | Bus | teal |
| 赤磐市民バス高陽北西線 高陽北西線 | Bus | pink |
List every stop
- 正崎
- 正崎
- 金剛橋西詰
- 金剛橋西詰
- 富士見橋
- 和気駅前
- 和気駅前
- 和気郵便局
- ＪＡ和気支店
- 赤坂支所
- 町苅田中
- 町苅田東
- 町苅田
- 新道穂崎
- 新道穂崎
- 由津里
- 五日市下
- 五日市下
- 山口東
- 山口
- 斗有上
- 斗有中
- 斗有下
- 西窪田
- 西山団地
- 仁保上
- 下仁保
- 仁保下
- 五日市上
- 五日市上
- 西山公民館
- 西中集会所
- ノアスギモト
- 鴨前地蔵堂
- 熊崎
- 下市（イズミ停留所）
- 赤磐市役所
- 赤磐医師会病院
- 老人福祉センター
- 高陽台
- 農業試験場口
- 農業試験場口
- 沼田本村口
- 斎富
- 南方
- 船廻
- 船廻
- 大苅田
- 神田
- 津崎
- 尾谷
- ふれあい公園
- 正崎
- 東窪田
- 東窪田
- 高屋
- 岩田交差点
- 馬屋消防機庫
- 望の里団地
- 穂崎中
- 福吉集会所
- 窪田
- 窪田
- 長尾
- 立川中
- 窪田上
- 西山団地東
- ＪＡ山陽支店
- マルナカ
- 熊山診療所
- 新田橋
- 町苅田下
- 町苅田下
- 石砂
- 町苅田
- 町苅田
- 沢原共撰場
- ＪＲ熊山駅
- 小瀬木東
- 河田原口
- 庄
- 一支部
- りゅう王
- 一分団消防機庫
- 蒲共撰場
- 稗田
- 赤坂支所前
- 赤坂支所前
- 可真上共撰場
- 小山
- 弥上
- 東３丁目東
- 東４丁目公園
- 東４丁目南
- 東２丁目中
- 東２丁目南
- 東２丁目公園
- 東１丁目東
- 赤坂中学前
- 赤坂中学前
- 東１丁目東下
- 東１丁目南
- 東１丁目西
- 東２丁目西
- 東２丁目西
- 桜が丘中学校入口
- 桜が丘中学校入口
- 交流センター
- 交流センター
- 東５丁目（桜が丘郵便局）
- 東５丁目（桜が丘郵便局）
- 東６丁目
- 東６丁目
- 東６丁目上
- 東６丁目上
- 新道立川口
- 新道立川口
- 野間（宇野バス連絡所）
- 野間（宇野バス連絡所）
- 軽部住宅前
- 軽部住宅前
- 野間入口
- 野間入口
- 老人憩の家
- ＪＡ可真支店
- 粕尾
- 殿谷下
- 殿谷中
- 英国庭園前
- 岡
- 軽部下
- 軽部下
- 小野地口
- 池ノ内
- 森国
- 酌田
- グリーンタウン殿谷
- 軽部上
- 軽部上
- 釣井
- 徳富南
- 徳富北
- 小瀬木西
- 円光寺
- 東円光寺
- 畑
- 吉原東
- 吉原中
- 多賀下
- 多賀下
- 丁切口
- 豊田小学校
- 西７丁目北
- 西７丁目北
- 西７丁目東
- 西７丁目西
- 山陽北小学校入口
- 山陽北小学校入口
- 西１丁目集会所
- 日古木・中島口
- 日古木・中島口
- 新道赤磐市役所入口
- 多賀上
- 多賀上
- 新道赤磐市役所入口（中国銀行赤磐支店前）
- 出屋
- 出屋
- 河本北
- 河本南
- 岩田東
- 岩田
- 西７番
- 西６番
- 西５番
- 西４番
- 足王神社口
- 西３番
- 出屋上
- 出屋上
- 西２番
- 西１番
- １丁目集会所入口
- 東１番
- 東２番
- 東３番
- ３丁目集会所前
- 東４番
- 東５番
- 東６番
- 坂辺
- 坂辺
- 佐伯庁舎
- 坂辺上
- 坂辺上
- 合田下
- 合田下
- 新道河本西
- 新道河本西
- 合田
- 合田
- 合田上
- 合田上
- 仁堀下
- 仁堀下
- 仁堀
- 仁堀
- 仁堀局前
- 仁堀局前
- 仁堀上
- 仁堀上
- 菊ヶ峠
- 菊ヶ峠
- 塩木上
- 塩木上
- 塩木中
- 塩木中
- 塩木下
- 塩木下
- 新道河本
- 新道河本
- 湯免温泉
- 湯免温泉
- 佐伯北
- 佐伯北
- 総合センター入口
- 総合センター入口
- 高田
- 高田
- 稲蒔
- 稲蒔
- 福田住宅前
- 福田住宅前
- 福田
- 福田
- 山方口
- 山方口
- 吉井中学校前
- 吉井中学校前
- 周匝
- 周匝
- 新道山陽マルナカ前
- 新道山陽マルナカ前
- 周匝上
- 周匝上
- 落合
- 落合
- 高下
- 高下
- 奥
- 奥
- and 111 more (see the full list on the map or in the GeoJSON)
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
8 findings, ordered by severity.
Show every finding
- Warning19114 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.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning361 instances
361 of 361 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning150 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.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning133 instances
133 of 133 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning3 instances
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Two or more routes share the same name.
Riders can't tell the routes apart in apps.
Fix: Give each route a distinct short or long name. (One field per route.)
Finding code: duplicate_route_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Same name and description for route (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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.)
Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
One requirement remains for this feed to earn 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 327 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 327 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 72 / 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/akaiwa-city-bus/2026-09-05.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-09-05. 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.