Feed status · checked 2026-09-05
Ugo Kotsu, Honjo area (羽後交通（本荘地区）)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Akita, 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.3, validator 8.0.1.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
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
575 of 575 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
294 of 294 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
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 575 of 575 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 294 of 294 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some internal IDs use characters outside the basic text set.
- Next action
- 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.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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 86 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 5 kinds of issue across 72000 instances (0 error, 71992 warning, 8 informational).
Service data covers the next 86 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.
This feed has 575 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 仁賀保高 (red)
- 子吉 (red)
- 本荘伏見 (red)
- 本荘市内 (red)
- 本荘循環 (red)
- 本荘横手 (red)
- 本荘横手 (red)
- 本荘矢島 (red)
- 本荘秋田 (red)
- 本荘秋田 (red)
- 本荘秋田 (red)
- 本荘秋田 (red)
- 東由利 (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 |
| 本荘秋田 本荘秋田線 | Bus | red |
| 本荘秋田 本荘秋田線 | Bus | red |
| 本荘秋田 本荘秋田線 | Bus | red |
| 本荘秋田 本荘秋田線 | Bus | red |
| 東由利 東由利線 | Bus | red |
| 東由利 東由利線 | Bus | red |
| 松ヶ崎 松ヶ崎線 | Bus | red |
| 畑谷・土谷スクール線 | Bus | red |
| 県大 県立大学線 | Bus | red |
| 福祉エリア 福祉エリア線 | Bus | red |
| 象潟 本荘象潟線 | Bus | red |
| 象潟 本荘象潟線 | Bus | red |
List every stop
- 本荘営業所（羽後交通）
- 本荘営業所（羽後交通）
- 本荘営業所（羽後交通）
- 栄町一丁目
- 栄町一丁目
- 栄町一丁目
- 北都銀行前
- 北都銀行前
- 桜小路
- 桜小路
- 本荘駅前（羽後本荘駅）
- 本荘駅前（羽後本荘駅）
- 市役所前（市役所）
- 市役所前（市役所）
- 市役所前（市役所）
- 市役所前（市役所）
- 市役所前（市役所）
- 市役所前（市役所）
- 本荘大町
- 本荘大町
- 美倉町
- 岩渕下
- 岩渕下
- 岩渕下
- 岩渕下
- 本荘第一病院前
- 本荘第一病院前
- 本荘第一病院前
- 県立大学入口
- 県立大学入口
- 由利高校入口
- 由利高校入口
- 柴野入口
- 柴野入口
- 由利組合病院前
- 川口
- 石脇
- 中町
- 中町
- 上ノ山団地入口
- 上ノ山団地入口
- 三軒町
- 三軒町
- 緑町
- 緑町
- 新山公園前
- 新山公園前
- 新山小学校入口
- 新山小学校入口
- 竜巻
- 竜巻
- 山ノ神
- 石脇交番前
- 石脇交番前
- 石脇交番前
- 竜巻局前
- 竜巻局前
- 赤冗
- 由利工業高校前
- 技能センター前
- 技能センター前
- ぱいんすぱ前
- 車検場前（市内）
- 団地前
- 促進住宅前
- 田尻
- イオン本荘前
- 夢うさぎ
- 松美町
- 竜巻公園
- ナイスアリーナ
- ハローワーク本荘前
- ハローワーク本荘前
- 本荘マリーナ入口
- 本荘マリーナ入口
- 本荘マリーナ入口
- 田尻野
- 菅原病院前
- 石脇ショッピングセンター
- 石脇ショッピングセンター
- 由利振興局前
- 由利振興局前
- 砂子下
- 砂子下
- 砂子下
- 東北電力前
- 田頭
- 田頭
- 本荘公園前
- 本荘公園前
- 本荘駅前角
- 本荘駅前角
- 本荘駅前角
- 本荘駅前角
- 赤沼
- 赤沼
- 飛鳥神社前
- 飛鳥神社前
- 県立大学前
- ポンパル
- 上三川
- 上三川
- 三川
- 三川
- 栗山
- 栗山
- 深沢（本荘秋田・松ヶ崎）
- 深沢（本荘秋田・松ヶ崎）
- 小屋川
- 小屋川
- 向村
- 親川
- 親川
- 芦川
- 芦川
- 折林
- 折林
- 松ヶ崎浜辺
- 松ヶ崎浜辺
- 松ヶ崎出張所前
- 松ヶ崎出張所前
- 神の沢
- 松ヶ崎大町
- 松ヶ崎大町
- 松ヶ崎共済会館前
- 羽後亀田駅
- 御門町
- 御門町
- 一番堰
- 一番堰
- 一番堰
- 一番堰
- 一番堰
- 蓼沼
- 蓼沼
- 交流センター前
- 交流センター前
- 東中学校入口
- 東中学校入口
- 東中学校前
- ナイス本荘インター店前
- 二十六木
- 三条
- 三条
- 荒町入口
- 荒町入口
- 万願寺入口
- 万願寺入口
- 荒田目
- 下万願寺
- 万願寺
- 鮎瀬入口
- 上野
- 田高
- 雪車町
- 石名坂
- 石名坂
- 石沢小学校前
- 石沢小学校前
- 石沢
- 館
- 柳生入口
- 一本木
- 鳥田目
- 上鳥田目
- 笹井
- 大簗
- 山内
- 山内
- 畑村
- 畑村
- 下舟木
- 下舟木
- 上舟木
- 大琴診療所前
- 大琴
- 上大琴
- 上大琴
- 宿
- 宿
- 横渡
- 上横渡
- 蔵
- 蔵新田
- 島
- 老方新町
- 老方横小路
- 老方
- 東由利総合支所
- 道の駅黄桜の里
- 土谷
- 谷地
- 柴野
- 柴野神社前
- 福田入口
- 畑谷
- 鶴舞町
- 鶴舞町
- 水林
- 水林
- 海士剥
- 海士剥
- 西目道の駅
- 西目道の駅
- 上豊栄
- 若松町
- 若松町
- 西目高校前
- 西目高校前
- 西目浜山
- 西目浜山
- 西目中学校前
- 西目中学校前
- 潮騒の丘ニュータウン前
- 潮騒の丘ニュータウン前
- 下出戸
- 下出戸
- 上出戸
- 上出戸
- 西の沢
- 山田下
- 両前寺
- 両前寺
- 前田
- 琴浦
- 琴浦公民館前
- 琴浦公民館前
- 平沢新町
- 仁賀保公園前
- 仁賀保公園前
- 仁賀保神社前
- 京田
- 新平森
- 新平森
- 午の浜温泉入口
- 午の浜温泉入口
- 三ツ森入口
- 三ツ森入口
- 白雪橋
- 白雪橋
- 下黒川
- 下黒川
- 上黒川
- 白瀬記念館入口
- 白瀬記念館入口
- 竹島潟
- 竹島潟
- 勢至公園前
- 金浦駅前角
- 金浦駅前角
- and 325 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
7 findings, ordered by severity.
Show every finding
- Warning71713 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.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning575 instances
575 of 575 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning294 instances
294 of 294 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning272 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.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
Two or more routes share the same name.
Riders can't tell the routes apart in apps.
Fix: Give each route a distinct short or long name. (One field per route.)
Finding code: duplicate_route_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 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.)
Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
One requirement remains for this feed to earn 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 86 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 86 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 73 / 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/ugo-kotsu-honjo/2026-09-05.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-09-05. 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.