Feed status · checked 2026-07-19
Higashiomi City Chokotto Bus (東近江市ちょこっとバス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
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.
Checked for changes 64 minutes ago; last changed 64 minutes ago.
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
271 of 271 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
115 of 115 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 73 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 7 kinds of issue across 4748 instances (0 error, 4744 warning, 4 informational).
Service data covers the next 73 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
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (ちょこっとバス 2 愛東線, ちょこっとバス 3 湖東線).
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
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.
- ちょこっとバス 1 市原線 (teal)
- ちょこっとバス 6 市街地循環線 (teal)
- ちょこっとバス 市辺上平木線 (brown)
- ちょこっとバス 大中線 (yellow)
- ちょこっとバス 政所線 (yellow)
- ちょこっとバス 甲津畑線 (green)
- ちょこっとバス 2 愛東線 (teal)
- ちょこっとバス 2 愛東線(南回り) (yellow)
- ちょこっとバス 2 愛東線(北回り) (yellow)
- ちょこっとバス 3 湖東線 (teal)
- ちょこっとバス 4 沖野玉緒線 (purple)
- ちょこっとバス 5 南部御園線 (pink)
| Route | Type | Line color |
|---|---|---|
| ちょこっとバス 1 市原線 | Bus | teal |
| ちょこっとバス 6 市街地循環線 | Bus | teal |
| ちょこっとバス 市辺上平木線 | Bus | brown |
| ちょこっとバス 大中線 | Bus | yellow |
| ちょこっとバス 政所線 | Bus | yellow |
| ちょこっとバス 甲津畑線 | Bus | green |
| ちょこっとバス 2 愛東線 | Bus | teal |
| ちょこっとバス 2 愛東線(南回り) | Bus | yellow |
| ちょこっとバス 2 愛東線(北回り) | Bus | yellow |
| ちょこっとバス 3 湖東線 | Bus | teal |
| ちょこっとバス 4 沖野玉緒線 | Bus | purple |
| ちょこっとバス 5 南部御園線 | Bus | pink |
This feed has 271 stops.
List every stop
- 池田
- 今代
- 寺
- 岡田
- 林田
- 妙法寺・中村医院前
- 妙法寺・中村医院前
- 玉園中学校前
- 宮の平
- 宮の平
- 葵町
- 沖野会館前
- 沖野会館前
- 市原野上
- 沖野中央
- 沖野中央
- 生長の家前
- 生長の家前
- 南部コミュニティセンター
- 南部コミュニティセンター
- ひばり丘団地
- ひばり丘団地
- 八日市南高校
- 八日市南高校
- 敬愛病院
- 敬愛病院
- 大凧会館前
- 大凧会館前
- 大通り商店街東口
- 堺
- 堺
- 南町
- 南町
- 市原野下
- 北町
- 滋賀学園・河辺の森前
- すこやかの杜口
- 小田苅口
- 小田苅
- 小田苅
- 長村口
- 下岸本口
- 下岸本口
- 池庄口
- 池庄
- 診療所前（湖東）
- 新出口
- 湖東支所
- 探検の殿堂・味咲館
- 大沢
- 湖東ひばり幼児園前
- 平松東
- 今在家口
- 湖東記念病院
- 湖東記念病院口
- 下里
- 僧坊
- 新出
- 中里
- 北花沢
- 南花沢
- ひばり公園
- 鳴谷
- 上平木
- 下羽田開発
- 下羽田
- 野端
- 平田コミュニティセンター
- 一式
- 光明寺前
- 柏木
- 平田駅前
- 三津屋西
- 三津屋
- あかね幼児園
- 野口
- 市辺コミュニティセンター
- 市辺
- 石谷
- 蛇溝
- 今堀
- 文芸会館・青葉メディカル前
- 文芸会館・青葉メディカル前
- 図書館・江州音頭会館前
- 図書館・江州音頭会館前
- ＪＡグリーン近江前
- ＪＡグリーン近江前
- 君ケ畑
- 蛭谷
- 箕川
- 政所
- 政所高橋
- 瓜生津
- 黄和田口
- 黄和田
- 黄和田上
- 杠葉尾
- 杠葉尾口
- 奥永源寺渓流の里
- 蓼畑
- 中畑
- 如来堂
- 小代
- 上大森
- 萱尾
- 佐目
- 永源寺ダム
- 相谷（夏季）
- 相谷口（夏季）
- 永源寺車庫
- 永源寺前
- 永源寺前
- 永源寺駐在所
- 紅葉橋北
- 山上東口
- 大森
- 山上小学校前
- 山上
- 大中
- 栗見新田
- 栗見新田
- 栗見出在家
- 宮前
- 能登川北小前
- 福堂
- 福堂東
- 乙女浜北
- 下大森
- 永源寺支所
- 乙女浜
- 山路西
- 伊庭西
- 伊庭
- 山路
- 図書館・能登川アリーナ前
- 能登川グラウンド前
- 松尾医院前
- 松尾医院前
- 能登川支所
- 能登川支所
- 水谷整形外科１
- 豊道
- 水谷整形外科２
- 能登川駅西口
- 能登川駅東口
- 能登川南小口
- 能登川病院
- わかたけ公園
- 甲津畑
- 甲津畑口
- 和南新田
- 和南
- 東近江総合医療センター
- 山上新田
- 山上新田口
- マックスバリュ東近江店
- つちだ内科医院前
- 南眼科医院前
- 建部東穂作会館
- 建部東穂作会館
- 八日市北小前
- 八日市北小前
- 相谷（冬季）
- 相谷口（冬季）
- 中小路南
- 中小路南
- 中小路東・西
- 中小路
- 駒寺
- 神田
- 広間
- 外
- 川合寺
- 診療所前（永源寺）
- 緑町東
- 緑町東
- 市役所（東近江市）
- 市役所（東近江市）
- 発達支援センター
- 発達支援センター
- 八日市高校
- 八日市高校
- 広島外科前
- 広島外科前
- アピア前
- 八日市駅
- 愛東支所・診療所
- マーガレットステーション
- 妹北口
- 妹北口
- 永源寺図書館
- 妹
- 中戸
- 鯰江
- 上岸本
- 小神田
- 御河辺神社前
- 野村
- 若松
- 八日市営業所前
- 八日市営業所前
- 八日市営業所前
- 東本町・敬愛病院前
- 東本町・敬愛病院前
- 池之脇
- 西友前
- 西友前
- 関電前
- 関電前
- 小神田北
- 小神田北
- 中岸本
- 中岸本
- 下岸本
- 下岸本
- 梅林
- 大萩
- こすぎクリニック前
- 池之尻
- 下中野
- 上二俣
- 上中野
- 愛東北小前
- アイ・マート前
- 市ケ原
- 大林
- 大覚寺
- 園
- 平尾
- 愛東外町
- 小倉
- 上二俣中
- 青山
- 曽根
- 百済寺口
- 百済寺本町
- 読合堂
- 近江温泉病院
- 北坂
- 百済寺町
- 百済寺本坊前
- 上山町
- 高木
- 新大森団地
- 宝積
- 玉緒駐在所
- 尻無
- 尻無
- 下二俣
- 下二俣
- and 21 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
10 findings, ordered by severity.
Show every finding
- Warning4702 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)
- Warning271 instances
271 of 271 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)
- Warning115 instances
115 of 115 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)
- Warning38 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)
- Warning2 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Validator rule: expired_calendar · 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)
- 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.)
Validator rule: big_gap_in_service · 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 73 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 73 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 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/higashiomi-chokotto-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.