Feed status · checked 2026-09-05
Machida City Community Bus (町田市コミュニティバス・市民バス)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Tokyo, 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.
Measured 3 of 4 score categories from the official feed URL on file.
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 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
132 of 132 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
185 of 185 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
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
- 132 of 132 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
- 185 of 185 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
- Some internal IDs use characters outside the basic text set.
- Next action
- 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.
- 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.
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 573 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 3288 instances (0 error, 3141 warning, 147 informational).
Service data covers the next 573 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
16 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.
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
This feed has no route shapes, so the map shows its stops only.
This feed has 132 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.
| Route | Type | Line color |
|---|---|---|
| かわせみ号：わさび田公園前経由 | Bus | teal (no shape in feed) |
| かわせみ号：南中学校東経由 | Bus | teal (no shape in feed) |
| まちっこ：公共施設巡回ルート | Bus | orange (no shape in feed) |
| まちっこ：相原ルート（往路） | Bus | orange (no shape in feed) |
| まちっこ：相原ルート（復路） | Bus | orange (no shape in feed) |
| 小山田桜台多摩南部地域病院間バス（往路） | Bus | green (no shape in feed) |
| 小山田桜台多摩南部地域病院間バス（復路） | Bus | green (no shape in feed) |
| 玉ちゃんバス：北ルート1 | Bus | yellow (no shape in feed) |
| 玉ちゃんバス：北ルート2 | Bus | yellow (no shape in feed) |
| 玉ちゃんバス：北ルート「有楽入口」止まり | Bus | yellow (no shape in feed) |
| 玉ちゃんバス：北ルート「金井小学校」始発 | Bus | yellow (no shape in feed) |
| 玉ちゃんバス：南ルート | Bus | yellow (no shape in feed) |
| 玉ちゃんバス：東ルート1 | Bus | yellow (no shape in feed) |
| 玉ちゃんバス：東ルート2 | Bus | yellow (no shape in feed) |
| 玉ちゃんバス：東ルート「昭和薬科大学」始発 | Bus | yellow (no shape in feed) |
| 玉ちゃんバス：東ルート「東玉川学園二丁目」止まり | Bus | yellow (no shape in feed) |
List every stop
- ゆうき山公園
- 木倉有楽
- 有楽入口
- 金井小学校
- 松風台
- 夕日ヶ丘
- 玉川学園なかよし公園
- 小山田桜台
- 桜台入口
- 清住平
- 清住平
- 都営金森第１１入口
- 大泉寺
- 大泉寺
- 山の端
- 山の端
- 大善倶楽部
- 大善倶楽部
- 山中集会所
- 山中集会所
- 唐木田駅東
- 唐木田駅東
- 多摩南部地域病院
- 柳橋
- 市営住宅入口
- 南中学校北
- わさび田公園前
- みずき山ふるさとの森
- 南第四小学校入口
- 都立小川高校前
- 成瀬が丘二丁目西
- 南中学校前［町田市］
- 南中学校東
- 成瀬駅南口前
- 成瀬駅南口前
- 町田バスセンター
- 町田バスセンター
- 町田市役所市民ホール前
- 第四小学校前［町田市］
- 中町二丁目
- 旭町
- 町田市民病院
- 五間道路
- 図書館前［町田市］
- 中町一丁目
- 原町田五丁目
- 成瀬が丘三丁目東
- 原町田四丁目
- 町田ターミナル
- ネイチャーファクトリー東京町田
- 上大戸
- 大戸橋
- 公会堂前［町田市］
- 水の口
- 円林寺前
- 境橋［町田市］
- 根岸［相原町］
- 三丁目児童公園入口
- 相原十字路
- 開都
- 相原小学校前
- 諏訪神社前［町田市］
- 相原
- 堺市民センター前
- 堺中学校前
- 堺農協前
- 坂下［町田市相原町］
- 相原境
- 成瀬が丘三丁目西
- 久保ヶ谷戸
- 田端［町田市］
- 片所
- 小山小学校前
- 常盤
- 桜橋［町田市］
- 市立室内プール［町田市］
- 忠生三丁目
- 忠生公園前
- 玉川学園前駅南口
- 玉川学園前駅南口
- 金森図書館前
- 鶯谷
- 鶯谷南
- 鶯谷南
- 旭ヶ丘東
- 旭ヶ丘東
- 東急台入口
- 東急台入口
- つつじヶ丘
- つつじヶ丘
- 成瀬南台公園
- 児童公園前［町田市］
- 児童公園前［町田市］
- 東玉川学園四丁目
- 東玉川学園四丁目
- こすもす会館
- 化石谷公園
- 松葉谷戸公園入口
- 昭和薬科大学
- 成瀬山緑地
- 成瀬台三丁目
- 成瀬中央通り
- 成瀬台四丁目西
- 東急台南
- 東玉川学園二丁目
- 鶯谷北
- ぬぼこ山
- 七丁目児童公園前
- 都営金森第９前
- 松見ヶ丘北
- 松見ヶ丘西
- 松見ヶ丘南
- 松見ヶ丘尾根
- 松見ヶ丘東
- 無窮坂上
- のらくろ坂下
- 玉川学園前駅
- 玉川学園前駅
- 玉川学園前駅西
- 玉川学園一丁目
- 金森二丁目中央
- 月見ヶ丘
- 一丁目児童公園
- 玉園台児童遊園
- 玉園台
- 玉林台駐在所
- 第五小学校
- さくらんぼホール
- 朝日公園
- すみれ児童公園
- 金井なかよし公園
- 金森
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
- Warning3101 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)
- Warning185 instances
185 of 185 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)
- Warning132 instances
132 of 132 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)
- Warning30 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)
- Warning9 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · 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)
- Info140 instances
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.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info5 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 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 573 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 573 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/machida-city-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.