Feed status · checked 2026-07-19
Kuroiwa Kanko (黒岩観光)
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.
Checked for changes 3 hours ago; last changed 3 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
181 of 181 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
55 of 55 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 158 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 3 kinds of issue across 6818 instances (0 error, 6817 warning, 1 informational).
Service data covers the next 158 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 (佐川・川渡線, 佐川・大崎・狩山口線, 黒岩線, 尾川線).
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.
- 佐川・大崎・狩山口線 (teal)
- 佐川・川渡線 (teal)
- 尾川線 (teal)
- 黒岩線 (teal)
| Route | Type | Line color |
|---|---|---|
| 佐川・大崎・狩山口線 | Bus | teal |
| 佐川・川渡線 | Bus | teal |
| 尾川線 | Bus | teal |
| 黒岩線 | Bus | teal |
This feed has 181 stops.
List every stop
- 文化センター
- 田中公園前
- 田中公園前
- 松崎
- 松崎
- 中本町
- 中本町
- 富士見町
- 富士見町
- 藤井医院前
- 藤井医院前
- 西佐川駅
- 清和前
- 清和前
- 岡崎
- 岡崎
- 由留岐橋
- 由留岐橋
- 高平
- 高平
- 下郷
- 下郷
- 尾川橋
- 尾川橋
- 天神町
- 天神町
- 尾川学校前
- 尾川学校前
- 堂野々
- 堂野々
- 松ノ木
- 松ノ木
- 小屋谷
- 小屋谷
- 古畑
- 下山
- 下山
- 上馬ノ原
- 上馬ノ原
- 馬ノ原
- 馬ノ原
- 八重栗
- 八重栗
- 瑞応口
- 瑞応口
- 庄田
- 庄田
- 黒岩通
- 宮ノ原
- 宮ノ原
- 薬師堂口
- 薬師堂口
- 原
- 原
- 黒岩支所前
- 黒岩支所前
- 場所が内
- 場所が内
- 平野太田川通
- 平野太田川通
- 西平野
- 西平野
- 柴尾
- 柴尾
- 女川通
- 女川通
- 東町
- 中町
- 西町
- 国道西町
- 国道西町
- 佐川駅
- 佐川郵便局前
- 佐川郵便局前
- NTT前
- NTT前
- 役場前
- 佐川高校前
- 佐川高校前
- 柳瀬
- 柳瀬
- 川内ケ谷
- 川内ケ谷
- 中組
- 中組
- 上川内ケ谷
- 上川内ケ谷
- 乙川
- 乙川
- 国道東町
- 国道東町
- 越知
- 越知
- 横倉口
- 横倉口
- 宮ノ前公園
- 宮ノ前公園
- 赤の谷
- 赤の谷
- 楠神
- 楠神
- キャンプ場口
- キャンプ場口
- 倉良
- 倉良
- 野老山
- 野老山
- 熊秋
- 熊秋
- 寺村橋
- 寺村橋
- 西浦
- 西浦
- 蕨谷
- 蕨谷
- 葛原
- 葛原
- 大崎役場前
- 大崎役場前
- 土佐大崎
- 土佐大崎
- 土佐相能
- 土佐相能
- 引地橋
- 引地橋
- 二子野
- 二子野
- 崎の山
- 崎の山
- 正の石
- 正の石
- 名野川
- 名野川
- 上仁淀
- 上仁淀
- 川口
- 川口
- 川口住宅前
- 川口住宅前
- 南谷
- 南谷
- 田村
- 田村
- 長屋
- 長屋
- 神母谷
- 神母谷
- 池川役場前
- 池川役場前
- 酒井医院前
- 酒井医院前
- 北浦橋
- 北浦橋
- ふれあい橋
- ふれあい橋
- 狩山口
- 高北病院
- 森口橋
- 森口橋
- 五味(仁淀川町)
- 五味(仁淀川町)
- 森
- 森
- 川渡
- 川渡
- 集落活動センター
- 楠原
- 桜座
- 桜座
- 岬
- 岬
- 柏原
- 柏原
- 郵便局前
- 郵便局前
- 病院通り
- 病院通り
- サンプラザ佐川店
- サンプラザ佐川店
- 佐川町立図書館さくと
- 佐川町立図書館さくと
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
5 findings, ordered by severity.
Show every finding
- Warning6764 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)
- Warning181 instances
181 of 181 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)
- Warning55 instances
55 of 55 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)
- Warning53 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)
- Info1 instance
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)
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 158 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 158 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/kuroiwa-kanko/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.