Feed status · checked 2026-07-19
Kenko Hokubu 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.
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
438 of 438 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
101 of 101 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 168 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 43355 instances (0 error, 43343 warning, 12 informational).
Service data covers the next 168 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.
- 北浦橋・長沢線 (orange)
- 川口～土佐山線 (orange)
| Route | Type | Line color |
|---|---|---|
| 北浦橋・長沢線 | Bus | orange |
| 川口～土佐山線 | Bus | orange |
This feed has 438 stops.
List every stop
- 北山
- 北山
- 東駅前町
- 東駅前町
- 伊野駅前
- 伊野駅前
- 伊野天神町
- 伊野天神町
- 公園町
- 公園町
- 大国様前
- 大国様前
- 仁淀川橋東詰
- 仁淀川橋東詰
- 蓮池町通
- 蓮池町通
- 高知橋
- 高知橋
- 高知駅前
- 高知駅前
- 高知駅前
- 高知駅前
- 高知駅バスターミナル
- 高知駅バスターミナル
- 高知駅バスターミナル
- 愛宕山
- 愛宕山
- 鏡川橋
- 鏡川橋
- 新道鴨部
- 新道鴨部
- バイパス東口
- バイパス東口
- 米田
- 米田
- 中ノ谷橋
- 中ノ谷橋
- 中ノ谷
- 中ノ谷
- 八代
- 八代
- 枝川小学校通
- 枝川小学校通
- 八代二区
- 八代二区
- 愛宕町一丁目
- 愛宕町一丁目
- 愛宕町二丁目
- 愛宕町二丁目
- 愛宕中学校通
- 愛宕中学校通
- 江ノ口変電所前
- 江ノ口変電所前
- 愛宕小橋
- 愛宕小橋
- 中秦泉寺
- 中秦泉寺
- 金谷橋
- 金谷橋
- 谷の内
- 谷の内
- 北秦泉寺
- 北秦泉寺
- 北本町一丁目
- 北本町一丁目
- 蛍橋西
- 蛍橋西
- 本宮町
- 本宮町
- 杓田市商前
- 杓田市商前
- 塚の原
- 塚の原
- 鳥越峠
- 鳥越峠
- 福井分岐
- 福井分岐
- 鳥越
- 鳥越
- 伊野駅
- 谷町
- 谷町
- 渦の谷
- 渦の谷
- 小浜
- 小浜
- 鳴谷
- 鳴谷
- 竜王前
- 竜王前
- 加田土橋
- 加田土橋
- 加田半鐘前
- 加田半鐘前
- 加田
- 加田
- 毛田口
- 毛田口
- 又白
- 又白
- 神谷第一
- 神谷第一
- 神谷
- 神谷
- 神谷第二
- 神谷第二
- 割石
- 割石
- 梅ヶ佐古
- 梅ヶ佐古
- 三島
- 三島
- 鹿敷第一
- 鹿敷第一
- 鹿敷
- 鹿敷
- 鹿敷宮前
- 鹿敷宮前
- 岩村
- 岩村
- 足谷
- 足谷
- 勝賀瀬
- 勝賀瀬
- 西の谷第一
- 西の谷第一
- 西の谷第二
- 西の谷第二
- 岩の本
- 岩の本
- 楠瀬第一
- 楠瀬第一
- 楠瀬第二
- 楠瀬第二
- ヒノ谷
- ヒノ谷
- 屋敷谷
- 屋敷谷
- 柳瀬第一
- 柳瀬第一
- 柳瀬第二
- 柳瀬第二
- 柳瀬営業所
- 柳瀬第三
- 柳瀬第三
- 柳瀬第四
- 柳瀬第四
- 石見
- 石見
- 源次郎林
- 源次郎林
- 柏原
- 柏原
- 和田
- 和田
- 出来地小学校前
- 出来地小学校前
- 出来地
- 出来地
- 宮ヶ奈路
- 宮ヶ奈路
- 堂ヶ畝
- 堂ヶ畝
- 潰谷
- 潰谷
- 山王
- 山王
- 漉地
- 漉地
- 深瀬
- 深瀬
- 柿奈路
- 柿奈路
- 弘瀬
- 弘瀬
- 高岩
- 高岩
- 高岩
- 高岩上
- 高岩上
- 宮の瀬
- 宮の瀬
- 唐越
- 唐越
- 下清田
- 下清田
- 清田
- 清田
- 上清田
- 上清田
- 木の瀬第一
- 木の瀬第一
- 木の瀬第二
- 木の瀬第二
- 筋川橋
- 筋川橋
- 坊蔵
- 坊蔵
- 由野木野第二
- 由野木野第二
- 由野木野
- 由野木野
- 吾北総合支所前
- 吾北総合支所前
- 思地
- 思地
- スベット
- スベット
- 下葛川
- 下葛川
- 葛川
- 葛川
- 上葛川
- 上葛川
- 不動尊前
- 不動尊前
- 黒巣川
- 黒巣川
- 日比原下
- 日比原下
- 公民館前
- 公民館前
- 日比原
- 日比原
- ツバヤブ
- ツバヤブ
- 清水学校上
- 清水学校上
- 土居
- 土居
- 程野入口
- 程野入口
- 敷巻口
- 敷巻口
- 安望
- 安望
- 枝畝
- 枝畝
- 枋谷
- 枋谷
- 新大森トンネル
- 新大森トンネル
- 竹奈路
- 竹奈路
- 大森橋
- 大森橋
- 大森中山
- 大森中山
- 根来第一
- 根来第一
- and 188 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
- Warning43240 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)
- Warning438 instances
438 of 438 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)
- Warning103 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)
- Warning101 instances
101 of 101 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)
- Info12 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 168 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 168 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 83 / 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/kenko-hokubu-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.