Feed status · checked 2026-09-05
Onomichi Bus (おのみちバス)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Hiroshima, 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.
Checked for changes 1 hours ago; last changed 1 hours ago.
Measured 4 of 4 score categories from the official feed URL on file.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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
472 of 472 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
1406 of 1406 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
Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.
907 of 1406 trips have no headsign, the text that tells riders where the bus is going. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
⏱ Usually one value per route pattern in your scheduling source.worth about +10 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
- 472 of 472 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
- 1406 of 1406 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
- 907 of 1406 trips have no headsign, the text that tells riders where the bus is going.
- Next action
- Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.
- 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.
Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. · 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.
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 177 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
- One or more realtime feeds were reachable; live-arrival coverage is not known.
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 8 kinds of issue across 31446 instances (0 error, 31395 warning, 51 informational).
Service data covers the next 177 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.
Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 472 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.
- 04 (green)
- 尾道市立大学線 (green)
- 向島西循環線 (green)
- 市民病院線 (green)
- 立花線 (green)
- 瀬戸田線 (green)
- 千光寺公園線 (green)
- 向東線 (green)
- 尾道因島線 (green)
- 新尾道駅線 (green)
- びんご運動公園線 (green)
- 三美園線 (green)
- 東西本線 (green)
- 尾道工業団地線 (green)
- 如水館線 (green)
- JA尾道総合病院線 (green)
| Route | Type | Line color |
|---|---|---|
| 04 駅前渡船－向島支所 | Bus | green |
| 尾道市立大学線 | Bus | green |
| 向島西循環線 | Bus | green |
| 市民病院線 | Bus | green |
| 48 尾道駅前－流通団地東 | Bus | green (no shape in feed) |
| 4 流通団地南－尾道駅前 | Bus | green (no shape in feed) |
| 立花線 | Bus | green |
| 瀬戸田線 | Bus | green |
| 千光寺公園線 | Bus | green |
| 向東線 | Bus | green |
| 尾道因島線 | Bus | green |
| 新尾道駅線 | Bus | green |
| びんご運動公園線 | Bus | green |
| 三美園線 | Bus | green |
| 東西本線 | Bus | green |
| 尾道工業団地線 | Bus | green |
| 如水館線 | Bus | green |
| JA尾道総合病院線 | Bus | green |
List every stop
- 赤羽根
- 赤羽根
- 合同庁舎入口
- 合同庁舎入口
- 合同庁舎入口
- 古島整形外科前
- 古島整形外科前
- 尾道クリニック前
- 尾道クリニック前
- 込原
- 西国寺裏参道
- 西国寺下
- 西国寺下
- DCM尾道店前
- DCM尾道店前
- 三美園
- 三美園
- 三美園口
- 三美園口
- 地蔵院下
- 地蔵院下
- 今宮
- 今宮
- 市民病院
- 市民病院
- 市役所前
- 市役所前
- 高須車庫
- 高須車庫
- 商工会議所前
- 商工会議所前
- 正徳橋
- 正徳橋
- 浄土寺下
- 浄土寺下
- 浄土寺下
- 浄土寺下
- 如水館前
- 如水館前
- 白方
- 白江
- 白江
- 今免
- 今免
- 新尾道駅①番
- 新尾道駅
- 新尾道駅②番
- 新尾道駅③番
- 亀川局前
- 亀川局前
- 新開
- 神社前
- 新高山一丁目
- 新高山一丁目
- 新高山市営住宅前
- 新高山市営住宅前
- 新高山市営住宅前
- 新高山二丁目
- 新高山二丁目
- 尾道国際ホテル前
- 尾道国際ホテル前
- 久山田水源地
- 岩子島
- 千光寺公園
- 千光寺公園
- 仙入峠
- 仙入峠
- 大学前
- 大通寺前
- 高須新涯
- 高須新涯
- 高須農協前
- 高須農協前
- 高見山登山口
- 高見山登山口
- 高諸神社
- 高諸神社
- 田尻
- 田尻
- 岩子島渡
- 立花農協前
- 立石
- ベイタウン中央
- ベイタウン中央
- 堤
- 天満町
- 天満町
- 天理教前
- 因島北インター入口
- 因島北インター入口
- 東西橋
- 東西橋
- 徳島
- 徳島
- 鳴滝登山口
- 鳴滝登山口
- 長江一丁目
- 長江一丁目
- 長江口
- 長江口
- 長江口
- 長江口
- 長江口
- 尾道長江郵便局前（旧長江小学校下)
- 尾道長江郵便局前（旧長江小学校下)
- みなと小学校下（旧長江中学校前)
- みなと小学校下（旧長江中学校前)
- 長江二丁目
- 長江二丁目
- 中越
- 中越
- 因島大橋
- 因島大橋
- 中州
- なかた美術館前
- なかた美術館前
- 中富浜
- 中野（如水館線)
- 西御所
- 西御所
- 西富浜
- きららラポール桜並木前
- きららラポール桜並木前
- 西藤小学校入口（旧 西藤町農協前)
- 二番潟
- 二番潟
- 田辺クリニック前
- 田辺クリニック前
- 因島総合支所前
- 因島総合支所前
- 則末
- 則末
- バイパス東口
- バイパス東口
- バイパス東口
- はきもの資料館前
- はきもの資料館前
- 畠岡
- 畠岡
- 馬場の鼻
- 馬場の鼻
- 土生港前
- 土生港前
- 番所
- 番所
- 東尾道駅
- 東尾道駅
- 因島車庫前
- 因島車庫前
- ベイタウン入口
- ベイタウン入口
- 東高前
- 原田内科前
- 原田内科前
- 尾道学園前
- 尾道学園前
- 干汐
- 干汐口
- 干汐新開
- 日比小前
- 日比小前
- びんご運動公園
- 栗原小学校前（旧うすい橋)
- 栗原小学校前（旧うすい橋)
- 深下組
- 福祉センター前
- 福祉センター前
- ふくしむら
- ふくしむら
- フジグラン前
- フジグラン前
- 芙美子像前
- 芙美子像前
- プレス工業前
- プレス工業前
- プレス工業前
- プレス工業前
- 防地口
- 防地口
- 防地口
- 防地口
- 防地口
- ボートレースチケットショップ尾道
- 尾道インター入口
- 尾道インター入口
- 槙ヶ峰
- 阿草
- 阿草
- おのみち海辺の美術館前
- おのみち海辺の美術館前
- 松永
- 松永駅前
- 松永駅前
- 松永駅南口
- 松永駅南口
- 松永スポーツセンター前
- 松永スポーツセンター前
- 松永中学校前
- 松永中学校前
- 松永農協会館前
- 松永農協会館前
- マリンユースセンター入口
- 丸山
- 道越
- 歌
- 道輝会前
- 道輝会前
- 南高下
- 南高下
- 南松永
- 南松永
- 三成
- 三成
- 宮の鼻
- 宮の鼻
- 宮の前
- 宮の前
- 三幸校前
- 御幸橋
- 妙見
- 妙見
- 明神橋
- 向島ＢＳ
- 向島ＢＳ
- 向島大橋
- 向島農協前
- 向島農協前
- 向東小学校前
- 向東小学校前
- 向東農協前
- 向東農協前
- 向峠
- 向峠
- 門田
- 門田
- 矢垣内
- 鳥の風呂
- 八坂神社前
- 山波
- 山波
- 山波郵便局前
- 山波郵便局前
- 山本病院前
- 山本病院前
- 遊亀橋
- 遊亀橋
- 郵便局前
- 長和島南
- 長和島南
- 陽光台
- and 222 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
12 findings, ordered by severity.
Show every finding
- Warning30758 instances
Some rows in stop_times.txt leave the timepoint column blank.
That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.
Fix: Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. (Usually one export setting.)
Finding code: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1406 instances
1406 of 1406 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)
- Warning907 instances
907 of 1406 trips have no headsign, the text that tells riders where the bus is going.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning508 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)
- Warning472 instances
472 of 472 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)
- Warning117 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
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info40 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)
- Info11 instances
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)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · 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 177 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 6 of 472 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Realtime reliability
The realtime feed responded on 100.0% of 7 checks over the last 1 day, with 22s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 177 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 60 / 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 42 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 100 / 100
- 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/onomichi-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.