Feed status · checked 2026-07-19
Omihachiman City Akakon Bus (近江八幡市あかこんバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Shiga, 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
449 of 449 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
133 of 133 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 316 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 6 kinds of issue across 4017 instances (0 error, 4015 warning, 2 informational).
Service data covers the next 316 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.
2 accessibility depth signals
6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (⑩北里・岡山・丸の内町コース, ⑫安土南・金田コース, ⑬老蘇・金田コース, ④北里・佐波江町・新畑コース, ⑤桐原・竹町・東川町コース, and more).
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.
1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("江ノ島集会所・B&G海洋センター").
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
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
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.
- ①島・沖島町コース (yellow)
- ⑩北里・岡山・丸の内町コース (brown)
- ⑪安土北・金田コース (yellow)
- ⑫安土南・金田コース (teal)
- ⑬老蘇・金田コース (gray)
- ②馬淵・新巻町コース (pink)
- ③武佐・末広町コース (purple)
- ④北里・佐波江町・新畑コース (orange)
- ⑤桐原・竹町・東川町コース (red)
- ⑥桐原・篠原コース (green)
- ⑧駅南・循環コース (green)
- ⑨島・岡山・王ノ浜コース (teal)
| Route | Type | Line color |
|---|---|---|
| ①島・沖島町コース | Bus | yellow |
| ⑩北里・岡山・丸の内町コース | Bus | brown |
| ⑪安土北・金田コース | Bus | yellow |
| ⑫安土南・金田コース | Bus | teal |
| ⑬老蘇・金田コース | Bus | gray |
| ②馬淵・新巻町コース | Bus | pink |
| ③武佐・末広町コース | Bus | purple |
| ④北里・佐波江町・新畑コース | Bus | orange |
| ⑤桐原・竹町・東川町コース | Bus | red |
| ⑥桐原・篠原コース | Bus | green |
| ⑧駅南・循環コース | Bus | green |
| ⑨島・岡山・王ノ浜コース | Bus | teal |
This feed has 449 stops.
List every stop
- 緑町中
- 緑町中
- 緑町北
- 緑町北
- 古川町
- 古川町
- 柳町
- 柳町
- ポリテクカレッジ
- 篠原公園
- 篠原公園
- 安養寺
- 安養寺
- 篠原駅南口
- 篠原自治会館前
- 篠原自治会館前
- 篠原三丁目
- 篠原三丁目
- 多賀
- 多賀
- 健康ふれあい公園
- 健康ふれあい公園
- 東
- 東
- 池田本町公民館
- 池田本町公民館
- 桐原コミュニティセンター
- 桐原コミュニティセンター
- 森尻
- 森尻
- 大森
- 大森
- 中小森
- 中小森
- 赤尾
- 赤尾
- 新中小森北
- 新中小森北
- 日吉野幸橋
- 日吉野幸橋
- きてか～な
- 日吉野東
- 日吉野東
- 近江八幡駅南口
- 鷹飼間野
- 鷹飼間野
- 鷹飼南
- 鷹飼南
- 西上田
- 西上田
- 農協八幡東支店
- 上田北
- 上田北
- 上田南
- 上田南
- 篠田神社
- 篠田神社
- 東中学校
- 東中学校
- 学園前
- 学園前
- 南本郷町公民館
- 南本郷町公民館
- 若葉自治会館
- 若葉自治会館
- 大手
- 大手
- 鷹飼八幡神社
- 鷹飼八幡神社
- 王ノ浜
- 王ノ浜
- 奥島
- 奥島
- 島
- 島
- 奥津島神社
- 奥津島神社
- 北津田東
- 北津田東
- よし笛会館
- よし笛会館
- 鍛治屋町
- 鍛治屋町
- 北津田西
- 北津田西
- 中之庄
- 中之庄
- 長命寺
- 運動公園
- 運動公園
- 南津田西
- 南津田西
- 南津田
- 南津田
- 山の手
- 山の手
- 船木
- 船木
- 小姓谷
- 小姓谷
- 図書館
- 図書館
- 元八幡
- 元八幡
- 本町
- 本町
- 西元会議所
- 西元会議所
- 小船木東
- 小船木東
- 小船木西
- 小船木西
- エコ村
- エコ村
- 八木
- 八木
- 丸の内
- 丸の内
- 丸の内西
- 丸の内西
- 江頭辻出
- 江頭辻出
- 江頭中
- 江頭中
- 仲屋上筋
- 仲屋上筋
- 江頭公民館
- 江頭公民館
- 田中江東
- 田中江東
- 加茂西
- 加茂西
- 加茂
- 加茂
- 神社前
- 神社前
- 小西
- 小西
- 木戸橋
- 木戸橋
- 元水茎
- 牧西
- 牧西
- 牧
- 牧
- 出町八商前
- 出町八商前
- 大房
- 大房
- 岡山小学校
- 岡山小学校
- 農協八幡西支店
- 農協八幡西支店
- 加茂東
- 加茂東
- 小門口
- 小門口
- 益田
- 益田
- 安土大中公民館
- 芦刈
- 芦刈
- 芦刈新町
- 芦刈新町
- 芦刈東
- 芦刈東
- 出町三丁目
- 出町三丁目
- 北原集会所
- 北原集会所
- 江ノ島集会所・B&G海洋センター
- 神楽橋
- 神楽橋
- 永町公民館
- 大船戸集会所
- 大船戸集会所
- 活津彦根神社
- 活津彦根神社
- 永町南出
- 永町南出
- 安土城跡前
- 安土城跡前
- 東町ぼうや地蔵
- 東町ぼうや地蔵
- 下豊浦お旅所
- 下豊浦お旅所
- 出町
- 出町
- 安土郵便局
- 安土郵便局
- 安土コミュニティセンター
- 安土コミュニティセンター
- 安土駅北口
- 常楽寺中央
- 常楽寺中央
- 安土ニュータウン集会所
- 香庄集会所
- 香庄集会所
- 浅小井東
- 浅小井東
- 浅小井西
- 浅小井西
- ヴォーリズみらいビレッジ
- ヴォーリズみらいビレッジ
- 西庄
- 西庄
- 出町南
- 出町南
- 堀切
- 西庄西
- 西庄西
- 黒橋
- 黒橋
- 黒橋公民館
- 黒橋公民館
- 黒橋北
- 黒橋北
- 文芸の郷
- 宮津住宅
- 宮津住宅
- 桑実寺
- 瓢箪山古墳
- 瓢箪山古墳
- 衣笠台北集会所
- 衣笠台北集会所
- 上十六中央口
- 上十六中央口
- 市役所
- 安土駅南広場
- 加賀信号口
- 加賀信号口
- 松原
- 松原
- 加賀中央
- 加賀中央
- 加賀南公園
- 加賀南公園
- 安土中学校
- 安土中学校
- 安土町総合支所
- 沙沙貴神社
- 沙沙貴神社
- 四ノ坪集会所
- 四ノ坪集会所
- 浄厳院
- 浄厳院
- 保健センター
- 長田
- 長田
- 杉森
- and 199 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 73.6 | first check |
| 2026-07-19 | 73.6 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-18.
Same feed file as 2026-07-18; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning3998 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)
- Warning449 instances
449 of 449 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)
- Warning133 instances
133 of 133 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)
- Warning14 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)
- 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.)
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Validator rule: unknown_column · 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).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: 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
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 316 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 316 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 74 / 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 52 / 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/omihachiman-akakon-bus/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.