Feed status · checked 2026-07-19
Kama City Bus (嘉麻市バス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Fukuoka, 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 2 hours ago; last changed 2 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
257 of 257 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
195 of 195 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 255 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 89132 instances (0 error, 89112 warning, 20 informational).
Service data covers the next 255 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
14 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.
- 市バス山田北回線（右回り） (purple)
- 市バス山田北回線（左回り） (purple)
- 市バス山田南回線（右回り） (orange)
- 市バス山田南回線（左回り） (orange)
- 市バス市内循環線東回り（上り） (pink)
- 市バス市内循環線東回り（下り） (pink)
- 市バス市内循環線西回り（上り） (orange)
- 市バス市内循環線西回り（下り） (orange)
- 市バス熊ヶ畑桂川線（上り） (green)
- 市バス熊ヶ畑桂川線（下り） (green)
- 市バス稲築北回線（右回り） (yellow)
- 市バス稲築北回線（左回り） (yellow)
- 市バス稲築南回線（右回り） (pink)
- 市バス稲築南回線（左回り） (pink)
- 市バス稲築桂川線（上り） (teal)
- 市バス稲築桂川線（下り） (teal)
| Route | Type | Line color |
|---|---|---|
| 市バス山田北回線（右回り） | Bus | purple |
| 市バス山田北回線（左回り） | Bus | purple |
| 市バス山田南回線（右回り） | Bus | orange |
| 市バス山田南回線（左回り） | Bus | orange |
| 市バス市内循環線東回り（上り） | Bus | pink |
| 市バス市内循環線東回り（下り） | Bus | pink |
| 市バス市内循環線西回り（上り） | Bus | orange |
| 市バス市内循環線西回り（下り） | Bus | orange |
| 市バス熊ヶ畑桂川線（上り） | Bus | green |
| 市バス熊ヶ畑桂川線（下り） | Bus | green |
| 市バス稲築北回線（右回り） | Bus | yellow |
| 市バス稲築北回線（左回り） | Bus | yellow |
| 市バス稲築南回線（右回り） | Bus | pink |
| 市バス稲築南回線（左回り） | Bus | pink |
| 市バス稲築桂川線（上り） | Bus | teal |
| 市バス稲築桂川線（下り） | Bus | teal |
This feed has 257 stops.
List every stop
- 昭嘉団地
- カントリーエレベーター
- 中央児童遊園
- 中央児童遊園
- 茶屋元橋
- 中央
- 枝坂公民館
- 枝坂北
- 深見
- 深見
- 東岩崎公民館
- 樋渡公民館
- 原町口
- 平東
- ひまわり団地
- 稲築西義務教育学校
- 稲築八幡宮
- いこいの家上
- 下鴨生駅
- 藤見台入口
- 藤見台入口
- 藤見台
- 藤見台
- なつきが丘
- なつきが丘
- 鴨生東町
- 鴨生東町
- 鴨生西町
- 鴨生西町
- 鴨生団地
- 鴨生団地
- 枝坂
- 枝坂
- 平
- 平
- 岩崎
- 岩崎
- 吉隈保育所
- 又手
- 嘉穂総合高校入口
- 嘉穂総合高校入口
- 柳ヶ谷
- 柳ヶ谷
- 総合バスステーション
- 鴨生第二
- 鴨生第二
- いこいの家
- 五日町
- 岩崎橋
- 岩崎橋
- 稲築才田日吉
- 飯田新町
- 飯田新町
- 稲築サンライズ才田
- 稲築学校
- 稲築学校
- 稲築交番
- 稲築才田
- 次郎五郎台
- 次郎五郎台下
- 次郎五郎台上
- 神幸一番区
- 人権啓発センターあかつき
- 住民ホール
- 住民ホール
- 神社前
- 神社前
- 城ケ浦橋
- 九郎原
- 江星団地
- 嘉麻警察署
- 上西口
- 上西郷公民館
- 井土
- 西郷
- 織田廣喜美術館
- 飯田公園前
- 黒田
- 松寿園
- 大西浦
- 大西浦
- 志耕館高校
- 志耕館高校
- 稲築病院
- 嘉穂総合高校
- 嘉穂中学校口
- 嘉穂支所
- 光台橋
- 光台橋
- 鴨生第一公民館
- 鴨生第一消防詰所
- 貴船団地
- 熊ヶ畑
- 琴平団地
- 琴平口
- 琴平口
- 口春１５組
- 口春児童遊園
- 熊本
- 口ノ戸団地
- 嘉穂支所口
- 桂川町役場
- 嘉麻市役所（本庁舎前）
- 口春
- 口春
- 旧山田庁舎
- 旧山田高校
- 道の駅うすい
- 道の駅うすい
- 緑ヶ丘
- 百々谷
- 百々谷
- 門前
- 松山団地
- 宮地
- なつき文化ホール前
- なつき文化ホール北
- 日赤病院前
- 日赤病院前
- 中篭１組
- 長野町
- 西岩崎
- 西岩崎
- 日赤病院
- 西鉄西の郷
- 中の坪団地口
- 沖出入口
- 屋内ゲートボール場
- 大隈
- 老松団地
- 大坪団地
- 笹原本町
- 笹原公民館
- サルビアパーク
- 笹原
- 銭代坊公民館
- 銭代坊公民館上
- 生涯学習館（山田支所）
- 白門団地
- 白木口
- 新山野団地
- 新原
- 新原
- 下の谷
- 新大橋橋
- 白門
- サンライズ南部
- 下臼井西
- 下臼井下
- 下臼井上
- 新屋敷団地
- 新山野集会所
- 下山田小学校下
- 土居四角
- 辻入口
- 辻入口
- つた山石碑
- 碓井支所
- 漆生東社宅入口
- 漆生本村
- 漆生東社宅
- 漆生北
- 漆生南部
- 漆生郵便局
- 漆生南部口
- 漆生東
- 碓井交番
- 碓井交番
- 堀川
- 市立図書館
- 日吉
- 日吉
- 日吉峠
- 福岡県消防学校
- 牛隈
- 牛隈
- 西牛隈
- 西牛隈
- 第二保育所
- 第二保育所
- 吉隈
- 笹尾橋
- 下臼井口
- 笹尾
- 弥栄
- 吉隈保育所
- 又手
- 桂川駅
- 牟多田
- 牟多田
- 松岡病院
- 上牛隈
- 上牛隈
- 大橋
- 猪之鼻口
- 猪之鼻口
- 猪之鼻
- 大谷口
- 坂谷
- 長原口
- 政所
- 熊田
- 尾浦上
- 尾浦中
- 尾浦第一
- 尾浦下
- 嘉穂百谷
- 上山住宅
- 百々谷上
- 筑紫
- 筑紫集会所
- 大師
- 下木城
- 木城団地
- 東ヶ丘団地
- 三菱第一
- さくらが丘団地
- ゆうひが丘
- ゆうひが丘北
- 県営住宅
- ゆうひが丘南
- 観音谷
- 梅林公園下
- 西新
- 虹ヶ丘
- 虹ヶ丘
- ウナブシ団地
- 石ヶ崎集会所
- 嘉麻市役所
- 嘉麻市役所
- 大藪
- 大藪
- 鴨生口第一
- なつきの湯
- なつきの湯
- 稲築東中学校前
- 稲築東中学校前
- 山田中学校
- 山田中学校
- 山田交番
- 山田交番
- 山野
- 山野
- 山下
- 山下
- 山野団地
- 山野団地
- 山野第二入口
- 吉成溜池
- 山野第二四組
- and 7 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
7 findings, ordered by severity.
Show every finding
- Warning89076 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)
- Warning257 instances
257 of 257 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)
- Warning195 instances
195 of 195 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)
- Warning36 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)
- Info12 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info5 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 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 255 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 255 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 84 / 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/kama-city-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.