Feed status · checked 2026-07-23
春日市コミュニティバスやよい
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.
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
271 of 271 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
84 of 84 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 251 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 2726 instances (0 error, 2717 warning, 9 informational).
Service data covers the next 251 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.
- やよい ① 桜ヶ丘線 (pink)
- やよい ② 須玖線 (green)
- やよい ③ 上白水線 (red)
- やよい ④ 星見ヶ丘線 (teal)
- やよい ⑤ 平田台線 (purple)
- やよい ⑥ 春日公園線 (teal)
- やよい ⑦ 春日原線 (orange)
| Route | Type | Line color |
|---|---|---|
| やよい ① 桜ヶ丘線 | Bus | pink |
| やよい ② 須玖線 | Bus | green |
| やよい ③ 上白水線 | Bus | red |
| やよい ④ 星見ヶ丘線 | Bus | teal |
| やよい ⑤ 平田台線 | Bus | purple |
| やよい ⑥ 春日公園線 | Bus | teal |
| やよい ⑦ 春日原線 | Bus | orange |
This feed has 271 stops.
List every stop
- バスセンター
- バスセンター
- バスセンター
- バスセンター
- バスセンター
- バスセンター
- バスセンター
- 大谷２丁目
- 大谷２丁目
- 福祉ぱれっと館前
- 福祉ぱれっと館前
- 住吉神社前
- 住吉神社前
- 小倉５丁目
- 小倉５丁目
- 小倉６丁目
- 小倉６丁目
- 岡本４丁目
- 岡本４丁目
- 奴国の丘歴史資料館前
- 大和町５丁目
- 大和町５丁目
- サン・ビオ公民館前
- 日の出町公民館前
- 日の出町公民館前
- 日の出町２丁目
- 日の出町２丁目
- 桜ヶ丘公民館前
- 桜ヶ丘公民館前
- 桜ヶ丘公園前
- 桜ヶ丘公園前
- 徳洲会病院
- 須玖北公園前
- 桜ヶ丘２丁目
- 御陵
- 御陵
- 須玖北公民館入口
- 須玖北公民館入口
- 須玖北５丁目ぶどうの庭入口
- 須玖北５丁目ぶどうの庭入口
- 岡本１丁目
- 岡本１丁目
- いきいきプラザ前
- いきいきプラザ前
- 社会福祉センター前
- 社会福祉センター前
- 下白水北３丁目
- 下白水北３丁目
- 下白水南４丁目
- 下白水南４丁目
- 下白水北７丁目
- 下白水北７丁目
- 泉３丁目
- 泉３丁目
- 泉公民館前
- 泉公民館前
- 泉１丁目
- 泉１丁目
- 下白水北５丁目
- 下白水北５丁目
- 福岡女学院前
- 福岡女学院前
- 須玖南５丁目
- 須玖南５丁目
- 須玖南公民館前
- 須玖南公民館前
- 須玖南４丁目
- 須玖南４丁目
- 須玖交差点
- 須玖交差点
- 岡本交差点
- 岡本交差点
- 須玖南１丁目
- 須玖南１丁目
- 須玖小学校前
- 須玖小学校前
- 弥生１丁目
- 弥生１丁目
- 弥生公民館前
- 弥生公民館前
- 須玖南親水公園前
- 須玖南親水公園前
- 竹の本団地前
- 竹の本団地前
- 北スポーツセンター前
- 北スポーツセンター前
- 昇町１丁目
- 昇町１丁目
- 春日小学校前
- 昇町４丁目
- 昇町４丁目
- 一の谷６丁目
- 一の谷６丁目
- 春日西中学校前
- 春日西中学校前
- 春日西小学校前
- 春日西小学校前
- 上白水公民館前
- 上白水公民館前
- 上白水公園前
- 上白水公園前
- 中白水
- 中白水
- ＪＲ博多南駅
- ＪＲ博多南駅
- 上白水公民館入口
- 上白水公民館入口
- ウトグチ瓦窯展示館前
- ウトグチ瓦窯展示館前
- 白水ヶ丘公民館前
- 白水ヶ丘公民館前
- 白水ヶ丘中央公園前
- 白水ヶ丘中央公園前
- 白水ヶ丘１丁目
- 白水ヶ丘１丁目
- 白水池３丁目
- 白水池３丁目
- 白水大池公園ちびっこ広場前
- 白水大池公園ちびっこ広場前
- 白水池２丁目
- 白水池２丁目
- 白水池公民館前
- 白水池公民館前
- 天神山３丁目
- 天神山３丁目
- 天神山
- 天神山
- 池の下
- 池の下
- 一の谷１丁目
- 一の谷１丁目
- 昇町５丁目
- 昇町５丁目
- 大谷公民館前
- 大谷公民館前
- ふれあい文化センター前
- ふれあい文化センター前
- 昇町６丁目
- 昇町６丁目
- 大土居
- 大土居
- 白水大池公園噴水前
- 白水大池公園噴水前
- 春日南中学校前
- 春日南中学校前
- 松ヶ丘２丁目
- 松ヶ丘２丁目
- 松ヶ丘公民館前
- 松ヶ丘公民館前
- 松ヶ丘６丁目
- 松ヶ丘６丁目
- ナギの木苑前
- ナギの木苑前
- 星見ヶ丘２丁目
- 星見ヶ丘２丁目
- 星見ヶ丘３丁目
- 大丸池公園前
- 星見ヶ丘入口
- 星見ヶ丘入口
- 塚原台２丁目南
- 塚原台２丁目南
- 塚原台２丁目北
- 塚原台２丁目北
- 塚原台１丁目
- 塚原台１丁目
- 春日１０丁目
- 春日１０丁目
- 春日６丁目
- 春日６丁目
- 春日８丁目
- 春日８丁目
- ちくし台５丁目
- ちくし台５丁目
- 紅葉ヶ丘東２丁目
- 紅葉ヶ丘東２丁目
- ちくし台１丁目
- ちくし台１丁目
- 若葉台西７丁目
- 若葉台西７丁目
- 紅葉ヶ丘東８丁目
- 紅葉ヶ丘東８丁目
- 紅葉ヶ丘第３公園前
- 紅葉ヶ丘第３公園前
- 紅葉ヶ丘東１０丁目
- 紅葉ヶ丘東１０丁目
- 紅葉ヶ丘第４公園前
- 紅葉ヶ丘第４公園前
- 惣利５丁目
- 惣利５丁目
- アクロスモール春日前
- アクロスモール春日前
- 位瀬公園前
- 位瀬公園前
- 平田台１丁目
- 平田台１丁目
- 平田台３丁目
- 平田台３丁目
- 平田台４丁目
- 平田台４丁目
- 平田台公民館前
- 平田台公民館前
- 平田台５丁目
- 平田台５丁目
- 惣利２丁目
- 惣利２丁目
- 惣利４丁目
- 惣利４丁目
- 惣利３丁目
- 惣利３丁目
- 惣利公民館前
- 惣利公民館前
- 大土居公民館前
- 大土居２丁目
- 大土居２丁目
- 大土居１丁目
- 大土居１丁目
- 昇町７丁目
- 昇町７丁目
- 紅葉ヶ丘公民館前
- 紅葉ヶ丘公民館前
- 春日神社前
- 春日神社前
- 春日２丁目
- 春日２丁目
- 御供田公園前
- 春日公園２丁目
- 春日公園２丁目
- ＪＲ大野城駅
- 春日大橋
- 春日大橋
- 春日公園１丁目
- 春日公園１丁目
- 市役所前
- 春日原小学校前
- 春日原小学校前
- 西鉄春日原駅前
- 西鉄春日原駅前
- ＪＲ春日駅
- ＪＲ春日駅
- 春日警察署前
- 春日警察署前
- 市役所入口
- 水道企業団前
- 水道企業団前
- 若葉台東公民館入口
- 若葉台東公民館入口
- 若葉台東３丁目
- 若葉台東３丁目
- ちくし台２丁目
- ちくし台２丁目
- and 21 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
9 findings, ordered by severity.
Show every finding
- Warning2575 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)
- Warning271 instances
271 of 271 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)
- Warning140 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)
- Warning84 instances
84 of 84 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)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info7 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
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)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: scorecard_no_feed_contact · 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 251 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 251 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 75 / 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 52 / 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/kasugacity-yayoi-kasuga/2026-07-23.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-23. 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.