Feed status · checked 2026-09-05
Ako City Yuranosuke Bus (赤穂市「ゆらのすけ」)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Hyogo, 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
254 of 254 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
32 of 32 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
- 254 of 254 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
- 32 of 32 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 237 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 4 kinds of issue across 1413 instances (0 error, 1410 warning, 3 informational).
Service data covers the next 237 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 (市内循環バスゆらのすけ・南北ルートA, 市内循環バスゆらのすけ・南北ルートB, 市内循環バスゆらのすけ・高野ルート, 市内循環バスゆらのすけ・尾崎・御崎ルート).
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
This feed has no route shapes, so the map shows its stops only.
This feed has 254 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.
| Route | Type | Line color |
|---|---|---|
| 市内循環バスゆらのすけ・南北ルートA | Bus | red (no shape in feed) |
| 市内循環バスゆらのすけ・南北ルートB | Bus | green (no shape in feed) |
| 市内循環バスゆらのすけ・東西ルート | Bus | blue (no shape in feed) |
| 市内循環バスゆらのすけ・高野ルート | Bus | orange (no shape in feed) |
| 市内循環バスゆらのすけ・みどり団地ルート | Bus | purple (no shape in feed) |
| 市内循環バスゆらのすけ・尾崎・御崎ルート | Bus | teal (no shape in feed) |
List every stop
- 坂越駅
- 田端集会所
- 高野高取
- 高野集会所
- 上高野集会所
- 高野第二
- 坂越幼稚園前
- 坂越幼稚園前
- 坂越港
- 坂越港
- 坂越港
- 浜社宅前
- 浜社宅前
- アース製薬前
- ハーモニーホール
- ハーモニーホール
- 大泊
- 黒崎
- 赤穂駅北
- 営農センター前
- 営農センター前
- さくら公園前
- さくら公園前
- 北集会所前
- 北集会所前
- 高山
- みどり団地
- 原組
- 五軒屋西
- 五軒屋西
- イオン赤穂店
- 赤穂市役所北
- 赤穂市役所北
- 赤穂中央病院東
- 赤穂中央病院東
- 赤穂中央病院前
- 赤穂中央病院前
- 赤穂城大手門前
- 赤穂城大手門前
- 赤穂車庫
- 千種ハイランド入口
- 千種ハイランド入口
- 木戸門
- 木戸門
- 汐見
- 汐見
- 赤穂化成前
- 赤穂化成前
- 駅東
- 駅東
- 大黒
- 大黒
- 小島港
- 小島港
- 小島
- 御崎駐在所前
- 正保橋北
- 正保橋北
- 御崎小学校前
- 御崎小学校前
- 御崎小学校前
- 御崎小学校前
- 元塩公園
- 元塩公園
- 清水町
- 清水町
- 南宮公園
- 南宮公園
- 南宮町
- 南宮町
- 水源地
- 水源地
- 本水尾町
- 本水尾町
- 本水尾西
- 本水尾西
- 明神木北
- 明神木北
- 赤穂八幡宮前
- 赤穂八幡宮前
- 高須集会所
- 高須集会所
- 尾崎農協前
- 尾崎農協前
- 赤穂警察前
- 赤穂警察前
- 加里屋
- 加里屋
- 坂越橋西詰
- 坂越橋西詰
- 下高谷
- 下長田橋
- 下長田橋
- はりま台北
- 権現前
- 権現前
- 出口
- 出口
- 門前
- 門前
- 桜木
- 桜木
- 砂子
- 砂子
- 浜市
- 浜市
- 大工村
- 大工村
- 龍泉寺前
- 龍泉寺前
- 播州赤穂駅
- 木津宮前
- 木津宮前
- 千種集会所前
- 千種集会所前
- 千種峠
- 千種峠
- 花畑蔵田
- 花畑蔵田
- 真殿門前
- 真殿門前
- 真殿天満神社
- 真殿天満神社
- 真殿林
- 真殿林
- 中山下
- 中山下
- 中山児童遊園
- 中山児童遊園
- 富原橋
- 富原橋
- 赤穂市役所
- 赤穂市役所
- 宮前
- 宮前
- 宮前
- 浄泉寺
- 有年公民館
- 楢原三軒屋
- 楢原野田
- 楢原上所
- 楢原中所
- 楢原新田
- 原小学校
- 北畠
- 花岳寺通
- 花岳寺通
- 牟礼第一児童遊園
- 牟礼公民館
- 成林
- 畑
- JA有年
- 横尾中町
- 谷口
- 有年橋
- 東有年第二児童遊園
- 木津
- 木津
- 赤穂城前
- 赤穂城前
- 目坂
- 目坂
- 月見草団地
- 月見草団地
- 根木
- 根木
- 周世ふれあい市場
- 真殿
- 真殿
- 中山
- 中山
- 上菅生
- はりま台
- 横山橋
- 横山橋
- 横山六軒家
- 横山六軒家
- 県住前
- 県住前
- 横山
- 上組
- 北組
- 大円寺
- 大避神社
- 中野橋
- 有年小学校
- 有年診療所
- 上仮屋北
- 上仮屋北
- 城西小学校
- 城西小学校
- 赤穂市民病院
- 三樋町
- 三樋町
- 板屋町
- 板屋町
- 主婦の店
- 主婦の店
- 磯浜町
- 磯浜町
- 塩屋幼稚園
- 塩屋幼稚園
- 関西福祉大学
- 関西福祉大学
- 新田五軒屋
- 新田五軒屋
- 新田西部児童遊園
- 新田西部児童遊園
- 西部診療所
- 西部診療所
- 石ヶ崎橋
- 石ヶ崎橋
- 大石神社東
- 大石神社東
- 折方駐在所
- 国道天和
- 国道天和
- 天和荒神社
- 天和荒神社
- 天和駅
- 天和駅
- 槙
- 槙
- 本町
- 本町
- 法光寺
- 法光寺
- 備前福河駅口
- 備前福河駅口
- 寺西集会所
- 寺西集会所
- 寺西
- 中洲
- 中洲
- 福浦コミュニティセンター
- 福浦コミュニティセンター
- 福浦新田
- 福浦新田
- 入電
- 二軒屋
- 二軒屋
- 八軒屋
- 八軒屋
- 古池
- すこやかセンター
- すこやかセンター
- 南野中
- 南野中
- 野中・砂子公園
- 野中・砂子公園
- and 4 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
6 findings, ordered by severity.
Show every finding
- Warning1402 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)
- Warning254 instances
254 of 254 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)
- Warning32 instances
32 of 32 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)
- Warning8 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)
- Info2 instances
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.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · 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 237 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 237 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 85 / 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/ako-yuranosuke-bus/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.