Feed status · checked 2026-07-19
Misawa City Community Bus Me-Bus (三沢市コミュニティバス「みーばす」)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Aomori, 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
Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid phone number (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
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
237 of 237 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
43 of 43 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
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.
Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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_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.
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 7 kinds of issue across 1553 instances (1 error, 1543 warning, 9 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
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (43みーばす ビードル西線).
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.
- 30みーばす 北浜線 (purple)
- 43みーばす ビードル西線 (red)
- 60みーばす 大津前平線 (orange)
- 63みーばす 大津前平線 (orange)
- 74みーばす ビードル東線 (gray)
- 75みーばす ビードル東線 (gray)
| Route | Type | Line color |
|---|---|---|
| 30みーばす 北浜線 | Bus | purple |
| 43みーばす ビードル西線 | Bus | red |
| 60みーばす 大津前平線 | Bus | orange |
| 63みーばす 大津前平線 | Bus | orange |
| 74みーばす ビードル東線 | Bus | gray |
| 75みーばす ビードル東線 | Bus | gray |
This feed has 237 stops.
List every stop
- 古間木小学校前
- ファミリーショップフルタ
- ファミリーショップフルタ
- 春日台三丁目
- 春日台三丁目
- 小松ヶ丘通り
- 小松ヶ丘通り
- 晴ヶ丘
- 晴ヶ丘
- 春日台
- 春日台
- 三沢駅
- 三沢駅
- 新町二丁目
- 新町二丁目
- 三沢公園
- 三沢公園
- 滝の沢公園
- 滝の沢公園
- 大町二丁目
- 中央三丁目
- 大通
- アメリカ広場
- 三沢中央
- 三沢中央
- 桜町
- 桜町
- 高校通
- 高校通
- サンマル通り
- サンマル通り
- ミス・ビードルドーム
- 工場団地通
- 工場団地通
- 木崎野小前
- 木崎野小前
- 雇用促進住宅前
- 雇用促進住宅前
- 泉町東
- 泉町東
- 市立病院
- 市役所・公会堂前
- 市役所・公会堂前
- 市役所前
- 市役所前
- 上下水道庁舎前
- 上下水道庁舎前
- 中央四丁目
- 中央四丁目
- 古間木交流センター
- 小松ヶ丘四丁目
- 小松ヶ丘四丁目
- 日の出三丁目
- 日の出三丁目
- 深谷
- 深谷
- さつきヶ丘団地前
- さつきヶ丘団地前
- 国際交流センター前
- 国際交流センター前
- 老人ホーム前
- 老人ホーム前
- 前平入口
- 前平入口
- 前平一丁目
- 前平一丁目
- 前平南
- 前平南
- 大津四川目
- 大津四川目
- 大津南
- 大津南
- 大雄寺前
- 大雄寺前
- 三川目
- 三川目
- 三沢漁港入口
- 三沢漁港入口
- 北三川目
- 北三川目
- 南鹿中
- 南鹿中
- 鹿中
- 鹿中
- 大津四丁目
- 大津四丁目
- 大津三丁目
- 大津三丁目
- 二中前
- 二中前
- 三沢駅東口
- 千代田町
- 千代田町
- 栄町
- 栄町
- 三沢郵便局前
- 三沢郵便局前
- 緑町三丁目
- 緑町三丁目
- 岡三沢二丁目
- 岡三沢二丁目
- 岡三沢七丁目
- 岡三沢七丁目
- 三沢空港温泉前
- 三沢空港温泉前
- 東岡三沢三丁目
- 東岡三沢三丁目
- 堀口三丁目
- 堀口三丁目
- こがね公園
- こがね公園
- 堀口中学校前
- 堀口中学校前
- ウイング三沢前
- ウイング三沢前
- アイスアリーナ前
- アイスアリーナ前
- 月光通り
- 泉町西
- 八幡
- 八幡
- 越下
- 越下
- 富崎
- 富崎
- 谷地頭
- 谷地頭
- 斗南藩記念観光村
- 斗南藩記念観光村
- 南谷地頭
- 南谷地頭
- 高ノ沢
- 高ノ沢
- 朝日
- 朝日
- 根井
- 根井
- 追舘
- 追舘
- 北平沼
- 北平沼
- 平沼
- 平沼
- 平沼入口
- 平沼入口
- 南平沼
- 南平沼
- 北倉内
- 北倉内
- 倉内
- 倉内
- 南倉内
- 南倉内
- 公営住宅前
- 公営住宅前
- 砂森入口
- 砂森入口
- 塩釜
- 塩釜
- 南塩釜
- 南塩釜
- 北織笠
- 北織笠
- 織笠
- 織笠
- 新森入口
- 新森入口
- 新森一丁目
- 新森一丁目
- 新森集会施設前
- 新森集会施設前
- 新森二丁目
- 新森二丁目
- はまなす団体活動センター前
- はまなす団体活動センター前
- 北六川目
- 北六川目
- 六川目
- 六川目
- 南六川目
- 南六川目
- 細谷
- 細谷
- 淋代海岸
- 淋代海岸
- 淋代局前
- 淋代局前
- 淋代
- 淋代
- 浜三沢
- 浜三沢
- 農協前
- 農協前
- 西浜三沢
- 西浜三沢
- 三沢空港通
- 三沢空港通
- 岡三沢市営住宅前
- 岡三沢市営住宅前
- 岡三沢
- 岡三沢
- 岡三沢小学校前
- 岡三沢小学校前
- 幸町一丁目
- 幸町一丁目
- Bバリ通り
- Bバリ通り
- 松園公園前
- 松園公園前
- 三沢案内所
- 三沢案内所
- 小松ヶ丘西口
- 小松ヶ丘西口
- 公園前
- 公園通
- 小松ヶ丘中央
- 小松ヶ丘中央
- 小松ヶ丘南
- 小松ヶ丘南
- 小松ヶ丘入口
- 小松ヶ丘入口
- 新町
- 新町
- ファミリーショップフルタ（虹ヶ丘経由専用）
- 虹ヶ丘
- 古間木二丁目
- 東町
- 東町
- 美野原
- 美野原
- 緑町二丁目
- 緑町二丁目
- 南山
- 南山
- マエダストア前
- マエダストア前
- 三沢空港前
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 71.2 | first check |
| 2026-07-19 | 71.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
10 findings, ordered by severity.
Show every finding
- Error1 instance
Invalid phone number (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: invalid_phone_number · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1532 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)
- Warning237 instances
237 of 237 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)
- Warning43 instances
43 of 43 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)
- Warning10 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)
- Info6 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
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Validator rule: trip_headsign_matches_intermediate_stop · 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. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- 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. The feed also carries 1 validator error, the other thing Maps checks at onboarding; the findings below name each fix.
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 68 / 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/misawa-city-me-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.