Feed status · checked 2026-07-19
Koryo Kotsu (高知高陵交通)
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 9 hours ago; last changed 9 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
583 of 583 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
121 of 121 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 163 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 36111 instances (0 error, 36109 warning, 2 informational).
Service data covers the next 163 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
8 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (須崎～高岡線, 梼原～須崎線, 矢井賀～須崎線, 越知面線, 竜王線, 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.
- 上西の川線 (red)
- 竜王線 (red)
- 四万川線 (red)
- 松原線 (red)
- 梼原～須崎線 (red)
- 矢井賀～須崎線 (red)
- 越知面線 (red)
- 須崎～高岡線 (red)
| Route | Type | Line color |
|---|---|---|
| 上西の川線 | Bus | red |
| 竜王線 | Bus | red |
| 四万川線 | Bus | red |
| 松原線 | Bus | red |
| 梼原～須崎線 | Bus | red |
| 矢井賀～須崎線 | Bus | red |
| 越知面線 | Bus | red |
| 須崎～高岡線 | Bus | red |
This feed has 583 stops.
List every stop
- 鳴川通
- 鳴川通
- 高岡営業所
- 日本たばこ前
- 日本たばこ前
- 県造船前
- 県造船前
- 市役所通
- 市役所通
- 西崎住宅前
- 多ノ郷駅前
- 土崎分岐
- 保育園前
- 池尻
- 池尻
- 新荘駅前
- 新荘駅前
- 中村分岐
- 中村分岐
- 中村分岐学校前
- 中村分岐学校前
- 新荘小学校前
- 新荘小学校前
- 岡本
- 岡本
- 水源地
- 水源地
- 高沖
- 高沖
- 中氏
- 中氏
- 天満宮前
- 天満宮前
- 西の谷
- 西の谷
- 下遅越
- 下遅越
- 中遅越
- 中遅越
- 遅越
- 遅越
- 寺尾
- 寺尾
- 大谷
- 大谷
- 上分支所前
- 上分支所前
- 首永
- 首永
- 檜の川橋
- 檜の川橋
- 平野
- 平野
- 笹野第一
- 笹野第一
- 笹野
- 笹野
- 天神橋
- 天神橋
- 夫領
- 夫領
- 二又橋
- 二又橋
- 馬関橋
- 馬関橋
- 新土居
- 新土居
- ムクノ木
- ムクノ木
- 西谷口
- 西谷口
- 山崎
- 山崎
- 姫野々新町
- 姫野々新町
- 葉山荘前
- 葉山荘前
- 葉山小学校前
- 葉山小学校前
- 姫野々上町
- 姫野々上町
- 久保川橋
- 久保川橋
- 永野(津野)
- 永野(津野)
- 津野町役場本庁舎前
- 津野町役場本庁舎前
- 聖音寺前
- 聖音寺前
- 石神奈路
- 石神奈路
- 赤木
- 赤木
- 桑の川口
- 桑の川口
- 船野入口
- 船野入口
- 梶足
- 梶足
- 栗の木入口
- 栗の木入口
- 大野
- 大野
- 黒川入口
- 黒川入口
- 農協西支所前
- 農協西支所前
- 杉ノ川
- 杉ノ川
- 杉ノ川診療所前
- 杉ノ川診療所前
- 日浦
- 日浦
- 大谷橋
- 大谷橋
- 大川下
- 大川下
- 大川第一
- 大川第一
- 大川
- 大川
- 桃ノ木大橋
- 桃ノ木大橋
- 駄馬
- 駄馬
- 新重谷
- 新重谷
- 新大西橋
- 新大西橋
- 桂トンネル
- 桂トンネル
- 布施ヶ坂公園
- 布施ヶ坂公園
- 船戸東
- 船戸東
- 船戸
- 船戸
- 船戸西
- 船戸西
- 大野見分岐
- 大野見分岐
- 上森獄
- 上森獄
- 川上橋
- 川上橋
- 烏出川
- 烏出川
- 芹川入口
- 芹川入口
- 力石
- 力石
- 力石西
- 力石西
- 高原荘前
- 高原荘前
- 新田東口
- 新田東口
- 津野町役場西庁舎前
- 津野町役場西庁舎前
- 新田
- 新田
- 北川
- 北川
- 北川西
- 北川西
- 大古味分岐
- 大古味分岐
- 宮谷
- 宮谷
- 木桑川橋
- 木桑川橋
- お大師前
- お大師前
- 木桑口
- 木桑口
- 西坂口
- 西坂口
- 神在居
- 神在居
- 太郎川公園前
- 太郎川公園前
- 太郎川
- 太郎川
- 屋敷前
- 屋敷前
- 化粧坂
- 化粧坂
- ゆすはら営業所
- ゆすはら営業所
- 高野中
- 高野中
- 須崎営業所
- 文化会館前
- 文化会館前
- 須崎駅前
- 須崎駅前
- 極楽橋
- 極楽橋
- 須崎局前
- 須崎局前
- 横町
- 横町
- 須崎ゆたか前
- 須崎ゆたか前
- 池山
- 池山
- 須崎市役所前
- 須崎市役所前
- 西大間
- 西大間
- 大間
- 大間
- 横浪分岐
- 横浪分岐
- 西崎町
- 西崎町
- 岩永
- 岩永
- 朝ヶ丘中学校前
- 朝ヶ丘中学校前
- 尾殿
- 尾殿
- 鯛の川口
- 鯛の川口
- 吾桑支所前
- 吾桑支所前
- 吾桑桜橋
- 吾桑桜橋
- チチ川
- チチ川
- 名古屋トンネル西口
- 名古屋トンネル西口
- 衆秀橋
- 衆秀橋
- 大津賀
- 大津賀
- 小立目
- 小立目
- 久保地
- 久保地
- 貞藤
- 貞藤
- 市野々
- 市野々
- オソ着
- オソ着
- 石指
- 石指
- 診療所前
- 診療所前
- and 333 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
5 findings, ordered by severity.
Show every finding
- Warning35983 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)
- Warning583 instances
583 of 583 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)
- Warning126 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)
- Warning121 instances
121 of 121 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)
- Info2 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)
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 163 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 163 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/koryo-kotsu/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.