Feed status · checked 2026-07-23
Hokushin Bus (北振バス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Okayama, 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
213 of 213 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
154 of 154 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 228 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 18873 instances (0 error, 18873 warning, 0 informational).
Service data covers the next 228 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.
- フジグラン前～粟根 (green)
- フジグラン前～山野下市～山野田原 (green)
- フジグラン前～東城別～山野田原 (green)
- フジグラン前～東城別～粟根 (green)
- 広瀬中学校前～苅光～フジグラン前 (green)
- フジグラン前～苅光～楠田 (green)
- 井原～与井～佐屋 (green)
- 井原～簗瀬～佐屋 (green)
- 井原～川相～山野田原 (green)
- 井原～川相～山野下市 (green)
- 井原～共和～弥高山入口 (green)
- 美星支所～興譲館高校前～井原 (green)
- 井原～田輪～美星支所 (green)
- 井原～芳井支所前 (green)
- 矢掛～美砂橋～美星産直プラザ (green)
| Route | Type | Line color |
|---|---|---|
| フジグラン前～粟根 | Bus | green |
| フジグラン前～山野下市～山野田原 | Bus | green |
| フジグラン前～東城別～山野田原 | Bus | green |
| フジグラン前～東城別～粟根 | Bus | green |
| 広瀬中学校前～苅光～フジグラン前 | Bus | green |
| フジグラン前～苅光～楠田 | Bus | green |
| 井原～与井～佐屋 | Bus | green |
| 井原～簗瀬～佐屋 | Bus | green |
| 井原～川相～山野田原 | Bus | green |
| 井原～川相～山野下市 | Bus | green |
| 井原～共和～弥高山入口 | Bus | green |
| 美星支所～興譲館高校前～井原 | Bus | green |
| 井原～田輪～美星支所 | Bus | green |
| 井原～芳井支所前 | Bus | green |
| 矢掛～美砂橋～美星産直プラザ | Bus | green |
This feed has 213 stops.
List every stop
- 下田東
- 谷下
- 谷上
- 上組
- 中谷
- 千ノ坂
- 美砂橋
- 東水砂
- 米田
- 昭和橋
- 昭和橋
- 一本松
- 車谷
- 仏田
- 川面農協
- 北田
- 田町
- 矢掛病院前
- 井原線矢掛駅
- ネバーランド前
- 矢掛高校前
- 向町
- 向町
- 矢掛高校入口
- 矢掛中町
- 矢掛中町
- 矢掛西町
- 矢掛西町
- 矢掛
- 加茂ハイツ入口
- 加茂診療所入口
- 加茂診療所入口
- 芦原
- 芦原
- フジグラン前
- ビッグローズ前
- ビッグローズ前
- 中国中央病院前
- 向町入口
- 向町入口
- 平成大学前
- 平成大学前
- 平成大学西
- 平成大学西
- 正戸山
- 正戸山
- 下加茂南
- 下加茂南
- 下加茂
- 下加茂
- 二葉大橋北
- 二葉大橋北
- 平成大橋
- 平成大橋
- 加茂昭和橋
- 加茂昭和橋
- 加茂ヶ丘団地口
- 加茂ヶ丘団地口
- 加茂小学校前
- 加茂小学校前
- 長川
- 芦原下
- 芦原下
- 芦原団地口
- 芦原団地口
- 芦原上
- 芦原上
- 四川別
- 四川別
- 旭保育所前
- 旭保育所前
- 庭田
- 庭田
- 粟根
- 粟根
- 上粟根
- 苅光
- 苅光
- 青笹
- 飯名
- 大谷中
- 谷中
- 若林
- 大谷広間
- 大谷下
- 大谷高尾
- 山野支所前
- 山野下市
- 山野農協前
- 小迫
- 梶江
- 梶江
- 発電所前
- 東の免
- 池尻下
- 池尻
- 妻屋橋
- 山野田原
- 東城別
- 東城別
- 上中野
- 上中野
- 簗瀬
- 落合橋
- 竜王
- 芋原東
- 芋原
- 広瀬郵便局前
- 広瀬中学校前
- 芳井中学校前
- 広瀬学校前
- 楠田
- 芳井郵便局前
- 与井
- 井原バスセンター
- 与井上
- 佐原
- 芳井支所前
- 戎橋
- 片塚
- 谷の宮
- 横谷
- 種入口
- 明治局前
- 明治
- 駅前通り
- 駅前通り
- 土頭
- 佐屋入口
- 佐屋
- 沢岡
- 沢岡
- 通峠
- 山内
- 天神
- 戸儀
- 川相
- 川相
- 川相学校前
- 井原郵便局前
- 井原郵便局前
- 川相上組
- 仁吾山
- 山村
- 梅木
- 下崎
- 川町
- 小原
- 山戸
- 共和
- 上鴫
- 井原駅
- 蛇の穴
- 畑谷
- 下谷
- 三原小学校前
- 三原
- 神迫
- 入野尻
- 村入
- 杖立
- 太刀洗
- 市民会館前
- 市民会館前
- 高山市
- 弥高山入口
- 田中苑
- 田中苑
- ＪＡ岡山西
- ＪＡ岡山西
- 井原中学校前
- 井原中学校前
- 興譲館高校前
- やすらぎセンター
- やすらぎセンター
- 東新町
- 東新町
- 長谷入口
- 長谷入口
- 戸倉
- 戸倉
- 市役所前
- 市役所前
- 戸倉上
- 戸倉上
- 才児下
- 永祥寺入口
- 永祥寺入口
- 那須与一の墓入口
- 那須与一の墓入口
- 細見
- 細見
- 田輪
- 長草
- 江良
- 栩木
- 小松
- 井原小学校前
- 井原小学校前
- 木野山
- 矢谷
- 谷山
- 志村
- 美星産直プラザ
- 美星診療所前
- 三山西
- 美星農協前
- 美星支所前
- 大元
- 市民病院前
- 下田
- 井原高入口
- 井原高入口
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
- Warning18732 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)
- Warning213 instances
213 of 213 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)
- Warning154 instances
154 of 154 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)
- Warning141 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)
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 228 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 228 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/hokushin-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.