← All agencies

Feed status · checked 2026-10-15

Mizuho Town Choi-Soko Demand Transit (チョイソコみずほまち)

Based on the official feed source on file

Service mode Bus

FDCBA

74.2 / 100

unchanged since 2026-10-14

Cataloged in Tokyo, Japan.

Covers 167 daysAccessibility gapsFlexible serviceRealtime not yet published

Source feed: https://api.gtfs-data.jp/v2/organizations/mizuhotown/feeds/DemandResponsiveTransport/files/feed.zip?rid=current

Mizuho Town's reservation-based Choi-Soko shared service in western Tokyo.

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.4, validator 8.0.1.

Checked for changes 6 hours ago; last changed 20 days ago.

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.

About this feed

Mizuho Town Choi-Soko Demand Transit (チョイソコみずほまち)’s published feed lists 1 bus route, 1 scheduled trip and 125 stops. Its service dates run from 2024-10-01 through 2027-03-31. The published file last changed on 2026-09-25.

Top things to fix

Fix 01

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

125 of 125 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.

Fixing this covers all 125 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 02

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

1 of 1 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

Fixing this covers all 1 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

This one is about the feed as a whole, so there is no share of it to count.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Riders and need behind these fixes

Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
The served-area need overlays cover the United States and Canada, so none of them applies to this feed.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding: Fix 01 in Top things to fix: its feed evidence and the requested change.
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

Agency: Mizuho Town Choi-Soko Demand Transit (チョイソコみずほまち)
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 125 of 125 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/mizuho-choisoko-demand-transit/?finding=scorecard_wheelchair_boarding_unknown#finding-handoff

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.

Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown
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. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for scorecard_no_fare_data
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. See this feed's finding-clearance log.

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 167 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: No fare information is published in the feed.
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.

Hi,

Our GTFS feed (Mizuho Town Choi-Soko Demand Transit (チョイソコみずほまち)) scored C (74.2 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 125 of 125 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 1 of 1 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

3. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
   What: The feed contains no fare information.
   Finding code: scorecard_no_fare_data
   Guide: https://gtfsscorecard.org/fix/scorecard_no_fare_data/

Full scorecard: https://gtfsscorecard.org/agency/mizuho-choisoko-demand-transit/

Score by category

Correctness86.0 / 100

The MobilityData validator flagged 3 kinds of issue across 16 instances (0 error, 16 warning, 0 informational).

Freshness100.0 / 100

Service data covers the next 167 days.

Rider experience36.9 / 100

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 not published.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

Realtime qualityNot yet measured

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 125 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.

Routes in Mizuho Town Choi-Soko Demand Transit (チョイソコみずほまち)'s feed
Route	Type	Line color
瑞穂町デマンドチョイソコみずほまち	Bus	teal (no shape in feed)

List every stop

殿ケ谷会館
トヨタＳ＆Ｄ西東京瑞穂店
つつじ公園
松山町北
松山公園
武蔵野コミュニティセンター
むさしの公園
なかよし１号公園
さかえ町
みずほさかえ公園
きたはらファミリー歯科
富士見公園
多世代交流センターMIZCUL
つくし公園
トヨタＳ＆Ｄ　Ｕ－Ｃａｒ横田ベースサイド店
むさしの会館
南平ひばり公園東
南平北
山岸歯科医院
南平西
武蔵野防災会館
福生病院
フレッシュランド西多摩　よつ葉の湯
くぬぎ公園
稲荷ヶ丘公園
ローソン瑞穂町武蔵店
ローソン瑞穂町東松原店
ファミリーマート瑞穂長岡四丁目店
ファミリーマート多摩瑞穂店
ファミリーマート瑞穂駒形店
ファミリーマート瑞穂ルート１６店
福正寺
東砂町
石畑地区スポーツ広場
石畑会館
古川工務店
武蔵
石畑下集会所
玉林寺公園
石畑中央会館
吉野橋
石畑診療所
石畑上集会所
ふれあいセンター
保健センター
スカイホール
大正電設
栗原医科歯科医院・矯正歯科
第２分団詰所
下砂橋
狭山池公園
地域活動支援センターひまわり・瑞穂町福祉作業所さくら
瑞穂町役場
青梅信用金庫　瑞穂支店
岩永歯科医院
円福寺
瑞穂武道館
みずほ病院
良友園
ふれっしゅはうす
菜の花クリニック
オリンピック
瑞穂熟年塾農場
さくら公園
箱根ケ崎西会館
箱根ケ崎駅東口
箱根ケ崎駅西口
箱根ケ崎歯科医院
多摩信用金庫　瑞穂支店
JAにしたま　瑞穂支店
西武信用金庫　瑞穂支店
アドマンズ
瑞穂郵便局
高水医院
みずほエコパーク
東松原
松原ひがし公園
松原町町内会集会所
水井装備
松原中央公園
高水商店
町営第２グランド
寄り合いハウスいこい
シモダディスカウントセンター
東善院
丸野医院
新井クリニック
下野公園
西武信用金庫　長岡支店
ＪＡにしたま長岡キャッシュコーナー
長岡南会館
東長岡住宅
長岡四丁目
殿ケ谷ポケットパーク
かすが公園
かすが公園西緑道
長岡コミュニティセンター
長岡会館
幸永不動産
中垣園芸
フラワープラム
けんちの苑
シルバー人材センター
二本木公園北
スーパーナカムラ
元狭山コミュニティセンター
JAにしたま　元狭山支店
元狭山広域防災広場
元狭山スポーツ広場
ドラッグセイムス　瑞穂二本木店
不老の郷
栗原園芸
たまご工房うえの
まき工房ころぼっくる
ジョイフル本田
高根下公園
高根町会館
高根町
瑞穂ケーブルテレビ
富士山公園
けやき館
さやま花多来里の郷
瑞穂斎場
竜泉寺
みずほ園

Over time

Overall score across the last 14 checks — unchanged since 2026-10-14.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	74.2	first check
2026-10-03	74.2	no change
2026-10-04	74.2	no change
2026-10-05	74.2	no change
2026-10-06	74.2	no change
2026-10-07	74.2	no change
2026-10-08	74.2	no change
2026-10-09	74.2	no change
2026-10-10	74.2	no change
2026-10-11	74.2	no change
2026-10-12	74.2	no change
2026-10-13	74.2	no change
2026-10-14	74.2	no change
2026-10-15	74.2	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
Checked	Published file	Service dates through	Grade at the time
2026-10-02 to 2026-10-15 (14 checks)	`a1e036a08e44`	2027-03-31	Current rubric: see the trend above
2026-09-25 to 2026-10-01 (7 checks)	`a1e036a08e44`	2027-03-31	C, 74.2 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-09-24 (58 checks)	`ada29cbd7e51`	2026-09-30	F, 47.8 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-23 to 2026-07-24 (2 checks)	`ada29cbd7e51`	2026-09-30	C, 70.3 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade

Everything we checked

8 findings, ordered by severity.

Show every finding

Warning125 instances
125 of 125 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 for scorecard_wheelchair_boarding_unknown · 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.)
Finding code: mixed_case_recommended_field · Read the fix guide for mixed_case_recommended_field · 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 for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Unexpected enum value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unexpected_enum_value · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
1 of 1 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices 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 for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
This feed includes flexible (demand-responsive) service, and riders are told how to book it.
Dial-a-ride and zone service are described for trip planners, not just fixed routes.
Fix: No action needed. (None.)
Finding code: scorecard_flex_service

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 167 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 166 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 86 / 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 37 / 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.

Part of the Japan portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Tokyo

Other scorecards in Tokyo, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Badge HTML

<a href="https://gtfsscorecard.org/agency/mizuho-choisoko-demand-transit/"><img src="https://gtfsscorecard.org/agency/mizuho-choisoko-demand-transit/badge.svg" width="320" height="58" alt="Mizuho Town Choi-Soko Demand Transit (チョイソコみずほまち): current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Mizuho Town Choi-Soko Demand Transit (チョイソコみずほまち): current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/mizuho-choisoko-demand-transit/badge.svg)](https://gtfsscorecard.org/agency/mizuho-choisoko-demand-transit/)

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/mizuho-choisoko-demand-transit/2026-10-15.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-10-15. 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.

GTFS Scorecard. (2026). Mizuho Town Choi-Soko Demand Transit (チョイソコみずほまち) GTFS feed-quality record, dated 2026-10-15 (grade C (74.2/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 a1e036a08e44…). https://gtfsscorecard.org/data/artifacts/mizuho-choisoko-demand-transit/2026-10-15.json

@misc{gtfsscorecard-mizuho-choisoko-demand-transit-2026-10-15,
  title        = {Mizuho Town Choi-Soko Demand Transit (チョイソコみずほまち) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/mizuho-choisoko-demand-transit/2026-10-15.json}},
  note         = {Checked 2026-10-15; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade C (74.2/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.