Feed status · checked 2026-07-19
Tagawa City Community Bus (田川市コミュニティバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
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.
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
197 of 197 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
78 of 78 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 438 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 7 kinds of issue across 34900 instances (0 error, 34885 warning, 15 informational).
Service data covers the next 438 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
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 2, 5, 7).
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.
- 1 (red)
- 2 (red)
- 3 (brown)
- 4 (yellow)
- 5 (teal)
- 6 (white)
- 7 (green)
| Route | Type | Line color |
|---|---|---|
| 1 まちなか循環線（右回り） | Bus | red |
| 2 まちなか循環線（左回り） | Bus | red |
| 3 坂谷線 | Bus | brown |
| 4 伊加利・鎮西線 | Bus | yellow |
| 5 弓削田・川宮線 | Bus | teal |
| 6 桜町・川宮線 | Bus | white |
| 7 金川線 | Bus | green |
This feed has 197 stops.
List every stop
- 西田川高校入口
- 西田川高校入口
- 文化センター
- 文化センター
- 荒牧医院入口
- 荒牧医院入口
- 美術館・図書館
- あきさと園入口
- あきさと園入口
- 岩屋公民館
- 岩屋公民館
- 内越
- 新生病院
- 新生病院
- 秋里
- 秋里
- 村方
- 村方
- 位登八幡
- ほしい西
- 田川団地
- 田川団地
- 桜ヶ丘
- 桜ヶ丘
- 日吉町口
- 日吉町口
- 元町
- 地蔵前
- バイパス川宮北
- バイパス川宮南
- 川宮プラチナタウン
- 西保育所
- 西保育所
- 上位登
- 汐井川
- 汐井川
- 桜町
- 桜町
- 後藤寺小学校
- 後藤寺小学校
- 野上公民館
- 松ノ木（宮田設備横）
- 奈良森ヶ坪
- 新庄橋
- 新庄橋
- コスパ伊田
- 上伊田東
- 上伊田東
- 上鎮西
- 下位登
- 重藤内科
- 重藤内科
- 鉄砲町
- 鉄砲町
- 東町・福智高校東
- 東町・福智高校東
- 夏吉
- 夏吉
- 棚木
- 棚木公園
- 棚木教育集会所
- 吉田西
- みそぎ口
- 清瀬
- 三ヶ瀬北
- 三ヶ瀬北
- 猪位金郵便局
- 猪位金郵便局
- 位登産業
- トライアル田川後藤寺店前
- トライアル田川後藤寺店前
- 生目神社
- 中郷
- 上弓削田
- 弓削田
- 弓削田
- 西鉄後藤寺
- 西鉄後藤寺
- 坂谷
- 春日橋
- 春日橋
- 春日神社前
- 春日神社前
- 後藤寺
- 後藤寺
- 田川後藤寺駅前
- 田川後藤寺駅前
- 社会保険田川病院
- 大浦上ノ山団地
- 県住大浦団地
- サンリット産業
- 東団地４棟前
- 後藤寺第２地区３町内集会所
- 三軒屋フリー乗降区間
- 藤下医院前
- 後藤寺西団地
- 上弓削田公民館
- 文字山公民館
- コーポ谷口前
- 文字山団地
- 文字山団地
- 角銅原交差点
- 弓削田中学校
- 九電変電所横
- 井上商店前
- 猪国集落フリー乗降区間
- 川宮
- 西岸寺前
- 大藪小学校前
- メルクス前
- メルクス前
- 田川科学技術高校
- 田川科学技術高校
- 田川市立病院
- 山賊鍋
- 平原公民館
- 平原郵便局
- 砥石
- 木城口
- 城山団地入口
- 城山団地入口
- 城山団地
- 城山団地
- 月美台
- 月美台
- 県営中央団地
- 中央団地なかしま理容店前
- 芳ヶ谷団地第一集会所前
- 鎮西白鳥口
- 成道寺前
- 成道寺前
- 古賀町
- 古賀町
- 新橋
- 新橋
- 猪膝集落フリー乗降区間
- 村上外科前
- 村上外科前
- 田川伊田駅前
- 伊田本町口
- 伊田本町口
- 南大通り
- 南大通り
- 総合庁舎前
- 総合庁舎前
- 松原団地
- 松原団地
- 田川市役所玄関前
- 田川市民会館
- 総合体育館・市民プール
- 総合体育館・市民プール
- 青少年文化ホール
- 青少年文化ホール
- いいかねパレット前
- 三井伊田団地
- 博物館スマイルプラザ
- 鎮西第一集会所
- 鎮西第一集会所
- 鎮西団地
- 鎮西団地
- 赤子（丸山組前）
- 道手
- 伊加利公民館
- 伊加利公民館
- 田中
- 田中
- 下伊加利（佐々木商店前）
- 下伊加利（佐々木商店前）
- 鎮西中学校前
- 金国太祖神社前
- 金国太祖神社前
- RSHOPなかがみ前
- 上伊田駅
- 稲荷町
- 稲荷町
- 旬の里かみいた
- 旬の里かみいた
- 県立大学旧門前
- 県立大学旧門前
- 県大正門前・福智高校西
- 県大正門前・福智高校西
- 下伊田
- 下伊田
- 猪位金学園前
- 緑ヶ丘
- 下吉田教育集会所（吉田公民館）
- 金川農協
- 糒東公民館
- 糒郵便局
- 糒社宅
- 糒社宅
- 白鳥工業団地
- 白鳥工業団地
- 東鷹高校
- 東鷹高校
- 田川産業前
- 分院前
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 78.7 | first check |
| 2026-07-19 | 78.7 | 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
9 findings, ordered by severity.
Show every finding
- Warning34865 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)
- Warning197 instances
197 of 197 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)
- Warning78 instances
78 of 78 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)
- Warning19 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 have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Validator rule: service_has_no_active_day_of_the_week · Read the fix guide · 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)
- Info4 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Validator rule: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 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)
- 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 438 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 438 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 80 / 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/tagawa-city-community-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.