← All agencies

Feed status · checked 2026-10-20

Saitama City Minuma Ward Community Bus (さいたま市見沼区コミュニティバス)

Based on the official feed source on file

Service mode Bus

FDCBA

73.9 / 100

unchanged since 2026-10-19

Cataloged in Saitama, Japan.

Covers 162 daysAccessibility gapsRealtime not yet published

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

Saitama City's community bus for Minuma Ward. The city publishes one archive per ward service.

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 32 minutes ago; last changed 45 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

Saitama City Minuma Ward Community Bus (さいたま市見沼区コミュニティバス)’s published feed lists 2 bus routes, 24 scheduled trips and 76 stops. Its service dates run from 2022-04-01 through 2027-03-31. The published file has not changed since our first check on 2026-09-05.

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

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

24 of 24 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 24 trips in the feed.

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

Fix 03

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.

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ A planned ID change, not a quick text cleanup.worth about +8 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: Saitama City Minuma Ward Community Bus (さいたま市見沼区コミュニティバス)
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 76 of 76 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/saitama-city-minuma-ward-community-bus/?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. Self-check a feed before you publish.
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. Self-check a feed before you publish.
Fix 03
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 162 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.

Hi,

Our GTFS feed (Saitama City Minuma Ward Community Bus (さいたま市見沼区コミュニティバス)) scored C (73.9 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: 76 of 76 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: 24 of 24 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. 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.
   What: Some internal IDs use characters outside the basic text set.
   Finding code: non_ascii_or_non_printable_char

Full scorecard: https://gtfsscorecard.org/agency/saitama-city-minuma-ward-community-bus/

Score by category

Correctness74.2 / 100

The MobilityData validator flagged 7 kinds of issue across 1095 instances (0 error, 1080 warning, 15 informational).

Freshness100.0 / 100

Service data covers the next 162 days.

Rider experience52.5 / 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 published.

Accessibility0 / 100

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

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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.

This feed has 76 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.

見沼区コミュニティバス(さぎ山記念公園ルート) (green)
見沼区コミュニティバス(沖郷会館ルート) (green)

Routes in Saitama City Minuma Ward Community Bus (さいたま市見沼区コミュニティバス)'s feed
Route	Type	Line color
見沼区コミュニティバス(さぎ山記念公園ルート)	Bus	green
見沼区コミュニティバス(沖郷会館ルート)	Bus	green

List every stop

片柳コミュニティセンター
染谷中花しょうぶ園
染谷中花しょうぶ園
染谷北
染谷北
顕徳寺
顕徳寺
やどかりの里
やどかりの里
染谷氷川神社
染谷氷川神社
市営霊園思い出の里
市営霊園思い出の里
向大谷
向大谷
大谷
大谷
七里コミュニティセンター入口
七里コミュニティセンター入口
さぎ山記念公園(構内)
大谷県営住宅
東宮下団地
東宮下団地
七里サンコーポ
七里サンコーポ
東門前
東門前
七里商店街
七里商店街
七里駅西
七里駅西
蓮沼小学校
蓮沼小学校
蓮沼住宅
蓮沼住宅
見沼区役所
見沼区役所
大和田町二丁目
大和田町二丁目
野田宝永
野田宝永
大和田駅
大和田町一丁目中央
大和田町一丁目中央
大和田町一丁目東
大和田町一丁目東
蓮沼北
蓮沼北
大谷中通り西
大谷中通り西
大谷中学校
大谷中学校
東宮下団地入口北
東宮下団地入口北
大谷中通り東
大谷中通り東
神宮台入口
神宮台入口
七里学校前
七里学校前
見沼自然公園締切橋
見沼自然公園締切橋
八石
八石
大谷県営住宅
三崎台見沼くらしっく館
三崎台見沼くらしっく館
染谷新道東
染谷新道東
沖郷会館
平台
平台
見沼消防署
見沼消防署
染谷南
染谷南

Over time

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

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	73.9	first check
2026-10-03	73.9	no change
2026-10-04	73.9	no change
2026-10-05	73.9	no change
2026-10-06	73.9	no change
2026-10-07	73.9	no change
2026-10-08	73.9	no change
2026-10-09	73.9	no change
2026-10-10	73.9	no change
2026-10-11	73.9	no change
2026-10-12	73.9	no change
2026-10-13	73.9	no change
2026-10-14	73.9	no change
2026-10-15	73.9	no change
2026-10-16	73.9	no change
2026-10-17	73.9	no change
2026-10-18	73.9	no change
2026-10-19	73.9	no change
2026-10-20	73.9	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-20 (19 checks)	`782fba3f4a0c`	2027-03-31	Current rubric: see the trend above
2026-09-05 to 2026-10-01 (23 checks)	`782fba3f4a0c`	2027-03-31	C, 73.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall grade and score held steady since 2026-10-19.

Same feed file as 2026-10-19; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

Everything we checked

10 findings, ordered by severity.

Show every finding

Warning1061 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)
Warning76 instances
76 of 76 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)
Warning24 instances
24 of 24 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)
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.)
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)
Warning8 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.)
Finding code: missing_recommended_field · Read the fix guide for missing_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)
Info12 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)
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 for unknown_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
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.)
Finding code: unknown_column · Read the fix guide for unknown_column · 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 for scorecard_no_feed_contact · 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 162 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 162 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.

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

Similar feeds in Saitama

Other scorecards in Saitama, 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/saitama-city-minuma-ward-community-bus/"><img src="https://gtfsscorecard.org/agency/saitama-city-minuma-ward-community-bus/badge.svg" width="320" height="58" alt="Saitama City Minuma Ward Community Bus (さいたま市見沼区コミュニティバス): current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Saitama City Minuma Ward Community Bus (さいたま市見沼区コミュニティバス): current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/saitama-city-minuma-ward-community-bus/badge.svg)](https://gtfsscorecard.org/agency/saitama-city-minuma-ward-community-bus/)

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/saitama-city-minuma-ward-community-bus/2026-10-20.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-20. 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). Saitama City Minuma Ward Community Bus (さいたま市見沼区コミュニティバス) GTFS feed-quality record, dated 2026-10-20 (grade C (73.9/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 782fba3f4a0c…). https://gtfsscorecard.org/data/artifacts/saitama-city-minuma-ward-community-bus/2026-10-20.json

@misc{gtfsscorecard-saitama-city-minuma-ward-community-bus-2026-10-20,
  title        = {Saitama City Minuma Ward Community Bus (さいたま市見沼区コミュニティバス) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/saitama-city-minuma-ward-community-bus/2026-10-20.json}},
  note         = {Checked 2026-10-20; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade C (73.9/100)}
}

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