Feed status · checked 2026-07-19
Taiyo Kotsu (太陽交通)
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.
Checked for changes 6 hours ago; last changed 6 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
320 of 320 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
172 of 172 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 4 kinds of issue across 68531 instances (0 error, 68523 warning, 8 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
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (香春線, 長井線, 寒田線, 豊津木井馬場線, 豊津 築城線).
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)
- 寒田線 (gray)
- 新とよつ駅線 (white)
- 蓑島線 (blue)
- 豊津木井馬場線 (green)
- 豊津 築城線 (green)
- 郡界線 (red)
- 長井線 (blue)
- 香春線 (orange)
| Route | Type | Line color |
|---|---|---|
| 宮ノ杜・新町線 | Bus | purple |
| 寒田線 | Bus | gray |
| 新とよつ駅線 | Bus | white |
| 蓑島線 | Bus | blue |
| 豊津木井馬場線 | Bus | green |
| 豊津 築城線 | Bus | green |
| 郡界線 | Bus | red |
| 長井線 | Bus | blue |
| 香春線 | Bus | orange |
This feed has 320 stops.
List every stop
- 有久
- 有久
- 赤幡
- 赤幡
- 呰見
- 呰見
- 菩提
- 菩提
- 文久団地
- 文久団地
- 文久入口
- 文久入口
- 文久
- 文久
- 長養団地入口
- 長養団地入口
- 駐在所前
- 駐在所前
- 台ヶ下
- 台ヶ下
- 伝法寺
- 伝法寺
- 駅前通り
- 駅前通り
- 越崎
- 越崎
- 福祉センター
- 福祉センター
- 福原
- 福原
- 深野
- 深野
- 船津工務店
- 船津工務店
- 二塚
- 二塚
- 福富
- 福富
- 祇園橋
- 祇園橋
- 祇園下
- 祇園下
- 郡界
- 郡界
- 八景山南
- 八景山南
- 八景山入口
- 八景山入口
- 本町アパート前
- 本町アパート前
- 博多町入口
- 博多町入口
- 羽根木
- 羽根木
- 祓郷
- 祓郷
- 広末
- 広末
- ひえだ診療所
- 東新田原
- 東新田原
- 畑
- 畑
- 本町四辻
- 本町四辻
- 市場前
- 市場前
- 檪原
- 檪原
- 稲童中央公民館
- 稲童中央公民館
- 稲童漁港
- 稲童浜
- 稲童浜
- 犬丸
- 犬丸
- 石並園
- 石並園
- 今井西町
- 今井西町
- 岩ノ下
- 岩ノ下
- 石並
- 石並
- 浄喜寺
- 浄喜寺
- 新田原駅前
- 川原
- 川原
- 木井馬場
- 上別府
- 上別府
- 黒田橋
- 黒田橋
- 小長田団地入口
- 小長田団地入口
- 上伝法寺
- 上伝法寺
- 上深野
- 上深野
- 工業団地
- 牡蠣小屋
- 小呉
- 小呉
- 上稗田
- 上稗田
- 上本庄
- 上本庄
- 城井中
- 城井中
- 上稲童
- 上稲童
- 国分
- 国分
- 上黒田
- 上黒田
- 上川原
- 上川原
- 区民会館前
- 区民会館前
- 上城井農協
- 上城井農協
- 鏡山
- 鏡山
- 上久保
- 上久保
- 京築恵みの郷前
- 京築恵みの郷前
- 金敷
- 金敷
- 金屋
- 金屋
- 沓尾橋
- 沓尾橋
- 小長田
- 小長田
- 沓尾入口
- 沓尾入口
- 黒田
- 黒田
- 呉
- 呉
- 香春本町
- 香春本町
- 香楽
- 香楽
- 黒田小学校
- 黒田小学校
- 香春町役場
- 上寒田
- 国作
- 国作
- 袈裟丸
- 袈裟丸
- 海水浴場
- 北大野井
- 北大野井
- 香春
- 香春
- 鏡山口
- 鏡山口
- 鍵山医院
- 鍵山医院
- 道の駅
- 光富
- 光富
- 溝口
- 溝口
- 南本町
- 南本町
- 前川原橋
- 前川原橋
- 京都高校
- 京都高校
- 宮ノ杜中央
- 宮ノ杜中央
- 宮ノ杜入口
- 宮ノ杜入口
- 宮ノ杜インフォ
- 宮ノ杜インフォ
- 松丸
- 松丸
- 元永
- 元永
- 宮ノ杜
- 南大橋
- 南大橋
- 蓑島
- 西鉄営業所前
- 西鉄営業所前
- 長井
- 中川
- 中川
- 錦町
- 錦町
- 中ノ原
- 中ノ原
- 延永小
- 延永小
- 延永農協
- 延永農協
- 長峡川
- 仲津小学校
- 仲津小学校
- 西谷
- 西谷
- 中津熊
- 中津熊
- 大野井入口
- 大野井入口
- 岡野社宅前
- 岡野社宅前
- 大野井
- 大野井
- 大山
- 大山
- 長木
- 長木
- ルミエール
- ローム福岡
- ローム福岡
- 下別府
- 下別府
- 裁判所入口
- 裁判所入口
- 新仲哀トンネル
- 新仲哀トンネル
- 総合庁舎
- 総合庁舎
- 下稗田
- 下稗田
- 下本庄
- 下本庄
- 下本町
- 下本町
- 下稲童
- 下稲童
- 崎野神社前
- 崎野神社前
- 下久保
- 下久保
- 信金前
- 信金前
- 崎野
- 崎野
- 下黒田
- 下黒田
- 迫田
- 迫田
- 新勝山
- and 70 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 | 81.8 | first check |
| 2026-07-19 | 81.8 | 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
6 findings, ordered by severity.
Show every finding
- Warning68521 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)
- Warning320 instances
320 of 320 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)
- Warning172 instances
172 of 172 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)
- Warning2 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)
- 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 87 / 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/taiyo-kotsu-fukuoka/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.