Feed status · checked 2026-07-23
巡回バス/ふくひめ号/福崎町・加西市連携コミュニティバス
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Hyogo, 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
196 of 196 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
42 of 42 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 4 kinds of issue across 1741 instances (0 error, 1740 warning, 1 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
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (巡回バス・まちなか便, 巡回バス・郊外便（川西A）, 巡回バス・郊外便（川西B）, 巡回バス・買い物便, ふくひめ号（通勤便A）, 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.
- 巡回バス・まちなか便 (pink)
- 巡回バス・郊外便（川西A） (teal)
- 巡回バス・郊外便（川西B） (gray)
- 巡回バス・買い物便 (teal)
- ふくひめ号（通勤便A） (pink)
- ふくひめ号（通勤便B） (green)
- ふくひめ号（連携便） (orange)
| Route | Type | Line color |
|---|---|---|
| 巡回バス・まちなか便 | Bus | pink |
| 巡回バス・郊外便（川西A） | Bus | teal |
| 巡回バス・郊外便（川西B） | Bus | gray |
| 巡回バス・買い物便 | Bus | teal |
| ふくひめ号（通勤便A） | Bus | pink |
| ふくひめ号（通勤便B） | Bus | green |
| ふくひめ号（連携便） | Bus | orange |
This feed has 196 stops.
List every stop
- 西大貫（信号西）
- 西大貫（信号西）
- 大門（セブンイレブン前）
- 大門（セブンイレブン前）
- 大門東
- 大門東
- 北野（公民館北）
- 北野（公民館北）
- 加治谷（公民館）
- 加治谷（公民館）
- 井ノ口（公民館）
- 井ノ口（公民館）
- 辻川（公民館）
- 辻川（公民館）
- 神積寺前
- 神積寺前
- 福崎町役場（サルビア会館前）
- 福崎町役場（サルビア会館前）
- 吉田東（ミナミ整形前）
- 吉田東（ミナミ整形前）
- 吉田西（ラ・ムー前）
- 吉田西（ラ・ムー前）
- 吉田北（マルアイ前）
- 吉田北（マルアイ前）
- 田尻南（ライフ前）
- 田尻南（ライフ前）
- 田尻住宅（ナンバ前）
- 田尻住宅（ナンバ前）
- 北野
- 北野
- 大門（公民館）
- 大門（公民館）
- 鬼追橋
- 鬼追橋
- 文珠荘
- 駅前（交通広場）
- 田尻（熊野神社）
- 田尻（熊野神社）
- もちむぎのやかた
- 辻川観光交流センター前
- 辻川観光交流センター前
- 西野南（ボンマルシェ前）
- 西野南（ボンマルシェ前）
- 西野北（ツタヤ前）
- 西野北（ツタヤ前）
- 新町東
- 新町東
- 馬田東
- 馬田東
- 文化センター（エルデホール前）
- 文化センター（エルデホール前）
- 山崎（立石記念碑）
- 福田（播磨福崎高校西）
- 福田（播磨福崎高校西）
- 馬田（西正寺）
- 馬田（西正寺）
- 福田（旧公民館）
- 福田（旧公民館）
- 福田住宅
- 福田住宅
- 桜（公民館）
- 桜（公民館）
- 板坂新田南（郵便局前）
- 板坂新田南（郵便局前）
- 板坂新田北
- 板坂新田北
- 板坂（公民館）
- 田口南
- 田口南
- 田口（集落センター）
- 長野（公民館）
- 長野（公民館）
- 長野（山本商店前）
- 長野（山本商店前）
- 長野（山本商店前）
- 長野（山本商店前）
- 新町（公民館）
- 新町（公民館）
- 神谷（旧公民館前）
- 神谷（旧公民館前）
- 第１デイサービスセンター
- 第１デイサービスセンター
- 西治（北ノ岡）
- 西治（北ノ岡）
- 西谷（大歳神社下）
- 西谷（公民館東）
- 西谷西
- 高橋（官舎下）
- 高橋（官舎下）
- 高橋（橋ノ本）
- 高橋（橋ノ本）
- 西治（赤坂）
- 西治（赤坂）
- 西治撰果場
- 西治撰果場
- 福崎小学校前
- 福崎小学校前
- 西治（下庄）
- 西治（下庄）
- 新町西（アキタケ診療所南）
- 新町西（アキタケ診療所南）
- 駅南（吉田クリニック西）
- 駅南（吉田クリニック西）
- 駅東
- 駅東
- 山崎東
- 山崎（二之宮神社）
- 西治北（おおにしクリニック前）
- 西治北（おおにしクリニック前）
- 西谷（信号南）
- 西谷（信号南）
- 日本レイヤー前
- 日本レイヤー前
- サミットスチール前
- サミットスチール前
- 出屋敷
- 出屋敷
- トンボ工業前
- トンボ工業前
- IDEC前
- IDEC前
- 石塚硝子前
- 石塚硝子前
- 凸版印刷前
- 凸版印刷前
- 溝口ニュータウン北
- 溝口ニュータウン北
- 溝口ニュータウン集会所前
- 溝口ニュータウン集会所前
- 溝口ニュータウン南口
- 溝口ニュータウン南口
- 香寺北公民館前
- 香寺北公民館前
- JR溝口駅前
- 溝口（セブンイレブン前）
- 溝口（セブンイレブン前）
- 図書館
- 宮脇口（神姫バス停）
- 宮脇口（神姫バス停）
- 八幡集会所前
- 八幡集会所前
- 中島（精米所前）
- 中島（精米所前）
- 八反田東（ラ・ムー西）
- 八反田東（ラ・ムー西）
- 八反田（八坂神社）
- 八反田（八坂神社）
- 長目北
- 長目北
- 長目南
- 長目南
- 中島南
- 中島南
- 西光寺（墓地駐車場）
- 西光寺（墓地駐車場）
- 西光寺（神姫バス停）
- 西光寺（神姫バス停）
- 旬彩蔵
- 西光寺（公民館下）
- 西光寺（公民館下）
- 上中島（神姫バス停）
- 上中島（神姫バス停）
- 西光寺（児童公園北）
- 西光寺（児童公園北）
- 余田新田（塚本）
- 余田新田（塚本）
- 南大貫西（神姫バス停）
- 南大貫西（神姫バス停）
- 庄西垣内
- 庄西垣内
- 鍛冶屋（地蔵堂）
- 鍛冶屋（地蔵堂）
- 庄（公民館東）
- 庄（公民館東）
- 庄（城谷医院前）
- 庄（城谷医院前）
- 余田（公民館）
- 余田（公民館）
- 新町清水（JA神飾統括前）
- 新町清水（JA神飾統括前）
- 庄稲荷口南
- 庄稲荷口南
- 小倉
- 小倉
- 八千種小学校前
- 八千種小学校前
- 南大貫（どんど）
- 南大貫（どんど）
- 南大貫（公民館前）
- 南大貫（公民館前）
- 西大貫（神姫バス停）
- 西大貫（神姫バス停）
- 東大貫中
- 東大貫（神姫バス停）
- 福崎大橋東（さとう前）
- 福崎大橋東（さとう前）
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
- Warning1579 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)
- Warning196 instances
196 of 196 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)
- Warning160 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)
- Warning42 instances
42 of 42 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)
- Info1 instance
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)
- 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 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 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/fukusakitown-junkai-fukuhime-fukusakikasairenkei/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.