GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Wako City Loop Bus Wakoba (和光市内循環バス「わこば」)

Based on the feed this agency publishes

Service mode Bus

81.2 / 100

unchanged since 2026-07-18

Catalogued in Saitama, Japan.

Covers 165 daysAccessibility gapsRealtime not yet published

Wako City's Wakoba city loop bus (市内循環バス「わこば」); a second Saitama feed record distinct from Kumagaya City.

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

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

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

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

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.

⏱ A planned ID change, not a quick text cleanup.worth about +8 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. 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.

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

  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.

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

Correctness85.5 / 100

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

Freshness100.0 / 100

Service data covers the next 165 days.

Rider experience60.0 / 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.

1 accessibility depth signal

  • 4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (市内循環赤池コース, 市内循環越後山コース, 市内循環向山・牛房コース, 市内循環白子・吹上コース).

    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.

FaresLegacy fares

Fares are applied to trips.

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 Wako City Loop Bus Wakoba (和光市内循環バス「わこば」)'s feed
RouteTypeLine color
市内循環赤池コース 和光市内循環バス赤池コースBusorange (no shape in feed)
市内循環越後山コース 和光市内循環バス越後山コースBusteal (no shape in feed)
市内循環向山・牛房コース 和光市内循環バス向山・牛房コースBusgreen (no shape in feed)
市内循環白子・吹上コース 和光市内循環バス白子・吹上コースBuspink (no shape in feed)
市内循環坂下・新倉コース 和光市内循環バス坂下・新倉コースBusyellow (no shape in feed)

This feed has 88 stops.

List every stop
  • ふたば公園
  • 団地センター前
  • 団地センター前
  • 和光市総合体育館
  • 和光市総合体育館
  • 二軒新田集会所入口
  • 総合福祉会館
  • 南大和団地
  • 南大和団地
  • 越後山
  • 越後山
  • 越後山南
  • 越後山南
  • 越後山橋入口
  • 越後山橋入口
  • 和光市立第三中学校
  • 和光市立第三中学校
  • 和光市役所
  • 和光市南公民館
  • 和光市南公民館
  • 諏訪原団地
  • 諏訪原団地
  • 埼玉病院
  • 新倉氷川神社
  • 新倉北地域センター
  • 和光郵便局
  • 和光郵便局
  • 和光市中央公民館
  • 和光市中央公民館
  • 和光市立大和中学校入口
  • 和光市立大和中学校入口
  • 丸山台３丁目
  • 丸山台３丁目
  • 白子コミセン
  • 白子コミセン
  • 和光市立本町小学校
  • 和光市立本町小学校
  • 和光陸橋
  • 和光市立第五小学校入口
  • 向山地域センター入口
  • 白子牛房
  • 牛房コミセン
  • 牛房通り
  • 消防白子分署
  • 和光市立大和中学校
  • 和光市立大和中学校
  • 白子宿地域センター
  • 和光市立白子小学校入口
  • 和光市図書館前
  • 和光市図書館前
  • 南市場
  • 稲荷神社下
  • 吹上観音下
  • 白子３丁目東
  • 野川公園入口
  • 白子吹上コミセン
  • 下新倉氷川神社
  • 中新田通り
  • 谷中
  • 大和橋
  • わぴあ
  • 古美山
  • 大坂通り
  • 新倉コミセン
  • 新倉コミセン
  • 和光市立北原小学校入口
  • ふるさと民家園入口
  • 和光市坂下公民館
  • 下新倉４丁目公園
  • 下新倉４丁目東
  • 金泉寺
  • 氷川通り
  • 和光市駅南口
  • 上谷津ふれあいの森
  • 新倉高齢者福祉センター入口
  • 下里
  • 和光市図書館
  • 和光市図書館
  • 埼玉病院入口
  • 新道坂上
  • 新倉ロータリー
  • 新倉ロータリー
  • 地蔵橋
  • 地蔵橋
  • 谷津橋
  • 谷津橋
  • 赤池
  • 赤池

Over time

Overall score across the last 2 checks — unchanged since 2026-07-18.

2026-07-18: 81.22026-07-19: 81.2
Show the numbers
CheckScoreChange
2026-07-1881.2 first check
2026-07-1981.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

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

    Validator rule: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules

  • Warning88 instances

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

  • Warning50 instances

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

  • Warning11 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

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

    Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules

Conformance mark Not yet

This feed is close to 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 165 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 165 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 60 / 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.

Wako City Loop Bus Wakoba (和光市内循環バス「わこば」) GTFS data quality grade: B

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/wako-city-loop-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.