Feed status · checked 2026-07-19
Oshu City Community Bus (奥州市コミュニティバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Iwate, 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
368 of 368 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
90 of 90 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 255 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 3377 instances (0 error, 3373 warning, 4 informational).
Service data covers the next 255 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 (Zバス 佐倉河線, Zバス 南方線, 市営バス 田原線, 市営バス 街なか循環線).
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.
- Zバス 佐倉河線 (green)
- Zバス 南方線 (pink)
- Zバス 羽田線 (yellow)
- Zバス 見分森線 (blue)
- 市営バス 伊手藤里線 (brown)
- 市営バス 広瀬稲瀬線 (green)
- 市営バス 梁川線 (purple)
- 市営バス 田原線 (red)
- 市営バス 街なか循環線 (gray)
- 市営バス 米里玉里線 (blue)
- 衣川バス 衣里線 (green)
- 胆沢水沢線 (green)
| Route | Type | Line color |
|---|---|---|
| Zバス 佐倉河線 | Bus | green |
| Zバス 南方線 | Bus | pink |
| Zバス 羽田線 | Bus | yellow |
| Zバス 見分森線 | Bus | blue |
| 市営バス 伊手藤里線 | Bus | brown |
| 市営バス 広瀬稲瀬線 | Bus | green |
| 市営バス 梁川線 | Bus | purple |
| 市営バス 田原線 | Bus | red |
| 市営バス 街なか循環線 | Bus | gray |
| 市営バス 米里玉里線 | Bus | blue |
| 衣川バス 衣里線 | Bus | green |
| 胆沢水沢線 | Bus | green |
This feed has 368 stops.
List every stop
- 山際
- 舘城
- 寺向公民館前
- 表
- 伝承館前
- 長者ヶ原廃寺跡前
- 接待館前
- 池田住宅前
- 池田
- 瀬原
- 瀬原
- 羽田
- 前沢駅東口
- アスティまえさわ
- アスティまえさわ
- イオン前沢店
- 江刺バスセンター
- 川原町
- 川原町
- 六日町
- 江刺幹部交番前
- 男石一丁目
- 工業団地入口
- 工業団地入口
- 江刺病院前
- 水沢江刺駅
- 江刺総合支所前
- 中町
- 栄町
- 栄町
- 鞍馬田
- 鞍馬田
- 餅田
- 餅田
- 餅田
- 餅田
- 苗代沢
- 上苗代沢
- 野
- 鋳物歴史公園前
- 鋳物歴史公園前
- 竹洞
- 二日市
- 上長沢
- 清水柳
- 藤里沢田
- 雲南田（藤里）
- 雲南田（岩谷堂）
- 岩明
- 岩明
- 赤坂
- 桝和
- 八幡（伊手）
- 小谷木
- 小谷木
- ＪＡ伊手営農センター前
- 伊手
- 伊手
- 藤里
- 藤里
- 車茶屋
- 寺後
- 瀬戸屋
- ヒロノ福祉パーク
- 豊田町
- 豊田町
- 杉ノ町
- 杉ノ町
- 競馬場入口
- 競馬場入口
- イオンタウン江刺北
- イオンタウン江刺
- 江刺第一中学校前
- 江刺第一中学校前
- サンエー
- 運動公園前
- 運動公園前
- 根岸
- 岩瀬橋
- 広岡
- 男石二丁目
- 江刺保育園前
- 杉の堂
- 杉の堂
- 銭町
- 南町
- 向山南口
- 稲瀬地区センター
- 前畑
- 伊加里
- 関の下
- 歌読
- 茶臼
- 石関
- 東中通り
- 三の関
- 二の関
- 一の関
- 広瀬
- 広瀬
- 豊ヶ丘
- 長根坂
- 山居
- 石田
- 稲荷
- 五位塚
- 常盤小学校前
- 戸崎
- 鹿野
- 土谷
- 石山
- 熊川橋
- 田原小学校前
- 小田代
- 花園集会所前
- 花園集会所前
- 本町
- 本町
- 前田町
- 前田町
- 中野
- Ｚホール前
- Ｚホール前
- 鵜ノ木
- 増沢
- 玉崎
- 次丸
- 大森
- 大内田
- 江刺ひがし小学校前
- 玉里
- 玉里
- 大筒口
- 竜宮一
- 火石沢
- 水沢常盤通郵便局入口
- 水沢常盤通郵便局入口
- 柳沢
- 大和田
- 津田橋
- 下川辺
- 和山
- 立石
- ＪＡ米里営農センター前
- 人首新町
- 人首新町
- 米里
- 米里
- 荒町橋
- ふれあいセンター
- 人首荒町
- 四丑通り
- 新田前
- 鴨沢
- 江刺東中学校入口
- 小菅生
- 秋葉町
- 秋葉町
- 月山
- 菅生
- 濁沢
- 角川原
- 栗生沢
- 長根橋
- 道合
- 昭和堂
- 日の神
- 梁川下町
- おとめばし
- 梁川
- 梁川
- 並柳
- 並柳
- 水沢駅口
- 水沢駅口
- 梁川地区センター
- 並木前
- 田原地区センター
- 伊手地区センター
- 胆沢病院
- 十文字
- 十文字
- 水沢駅通り
- 水沢駅通り
- 水沢駅通り
- 水沢駅通り
- 中ノ町
- 梨畑
- 梨畑
- 八幡神社前
- 八幡神社前
- 水沢駅前
- 水沢駅前
- 裁判所前
- 裁判所前
- 薬師堂温泉入口
- 薬師堂温泉入口
- 徳沢
- 徳沢
- 白鳥
- 白鳥
- 塔ケ崎
- 塔ケ崎
- 丁切
- 丁切
- まごころ病院
- まごころ病院
- 胆沢若柳郵便局前
- 胆沢若柳郵便局前
- 供養塚
- 供養塚
- 奥州市役所前
- 奥州市役所前
- 広表
- 広表
- 田中前
- 田中前
- 高綱
- 高綱
- 南都田地区センター前
- 南都田地区センター前
- 辻
- 辻
- 角塚公園前
- 角塚公園前
- 宇南田
- 宇南田
- 谷地田
- 谷地田
- 雇用促進西宿舎前
- 雇用促進西宿舎前
- 西光田
- 西光田
- 水沢病院
- 北鵜ノ木会館前
- 石田温泉前
- 石田温泉前
- 寺領
- 寺領
- 匠田
- 匠田
- 匠田
- 西町
- 西町
- 西町
- 西町
- 桜屋敷
- 桜屋敷
- 見分森入口
- 見分森入口
- and 118 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 | 74.2 | first check |
| 2026-07-19 | 74.2 | 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
- Warning3330 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)
- Warning368 instances
368 of 368 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)
- Warning90 instances
90 of 90 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)
- Warning28 instances
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)
- 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)
- Info2 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.)
Validator rule: platform_without_parent_station · 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 255 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 255 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 75 / 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/oshu-city-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.