GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

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

Based on the feed this agency publishes

Service mode Bus

70.3 / 100

First scorecard for this agency

Catalogued in Tokyo, Japan.

Covers 69 daysAccessibility gapsFlexible serviceRealtime not yet published

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

Fix 01

Review the rule documentation for 'stop_time_timepoint_without_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Stop time timepoint without times (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +18 points in its category

Fix 02

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

120 of 120 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

Fix 03

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

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

  1. Review the rule documentation for 'stop_time_timepoint_without_times' 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.

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

  3. 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 69 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.

Score by category

Correctness72.0 / 100

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

Freshness100.0 / 100

Service data covers the next 69 days.

Rider experience44.2 / 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.

Skip to route and stop data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

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

This feed has 120 stops.

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

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

7 findings, ordered by severity.

Show every finding
  • Error8 instances

    Stop time timepoint without times (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'stop_time_timepoint_without_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: stop_time_timepoint_without_times · See MobilityData GTFS Validator rules

  • Warning120 instances

    120 of 120 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

  • 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

  • Warning2 instances

    2 of 2 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

  • 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.)

    Validator rule: unexpected_enum_value · See MobilityData GTFS Validator rules

  • 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.)

    Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices

  • 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.)

    Validator rule: scorecard_flex_service

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 69 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 69 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 8 validator errors, 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 72 / 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 44 / 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.

Mizuho Town Choi-Soko Demand Transit (チョイソコみずほまち) GTFS data quality grade: C

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-07-23.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-23. 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.