Feed status · checked 2026-07-23
佐川町コミュニティバス「さかわぐるぐるバス」
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Kochi, 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
167 of 167 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
71 of 71 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 2 kinds of issue across 10387 instances (0 error, 10387 warning, 0 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.
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.
- 中心部ぐるぐる線 (yellow)
- 四ツ白線 (yellow)
- 川ノ内線 (yellow)
- 斗賀野線 (yellow)
- 本村線 (yellow)
- 狩場線 (yellow)
- 荷稲･川内ケ谷線 (yellow)
- 薄木線 (yellow)
- 西山線 (yellow)
- 長竹線 (yellow)
| Route | Type | Line color |
|---|---|---|
| 中心部ぐるぐる線 | Bus | yellow |
| 四ツ白線 | Bus | yellow |
| 川ノ内線 | Bus | yellow |
| 斗賀野線 | Bus | yellow |
| 本村線 | Bus | yellow |
| 狩場線 | Bus | yellow |
| 荷稲･川内ケ谷線 | Bus | yellow |
| 薄木線 | Bus | yellow |
| 西山線 | Bus | yellow |
| 長竹線 | Bus | yellow |
This feed has 167 stops.
List every stop
- 郵便局前
- 郵便局前
- 佐川町役場
- かわせみ
- 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
4 findings, ordered by severity.
Show every finding
- Warning10314 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)
- Warning167 instances
167 of 167 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)
- Warning73 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)
- Warning71 instances
71 of 71 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)
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 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/sakawatown-gtfs-sakawatown-bus/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.