GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Otone Kotsu (大利根交通)

Based on the feed this agency publishes

Service mode Bus

85.0 / 100

unchanged since 2026-07-18

Catalogued in Ibaraki, Japan.

Covers 263 daysAccessibility gapsRealtime not yet published

Otone Kotsu operates route buses in western Ibaraki.

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.

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

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

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

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

Fix 03

Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool

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.

⏱ Often a bulk fix in your scheduling software.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. 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.

  3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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 263 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 100% 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

Correctness83.5 / 100

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

Freshness100.0 / 100

Service data covers the next 263 days.

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

Accessibility37.5 / 100

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

1 accessibility depth signal

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

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

Skip to route and stop data

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

  • 利根ニュータウン東⇒布佐駅 (yellow)
  • 取手駅⇔もえぎ野台（東京藝術大学通過） (blue)
  • 取手駅⇔もえぎ野台（東京藝術大学経由） (teal)
  • 取手駅⇔もえぎ野台（東京藝術大学通過、羽黒経由） (white)
  • 取手駅⇔利根ニュータウン東（東京藝術大学通過） (pink)
  • 利根ニュータウン東⇔取手駅（東京藝術大学経由） (blue)
  • 取手駅⇔北方車庫（東京藝術大学通過） (red)
  • 取手駅⇔北方車庫（東京藝術大学経由） (teal)
  • 取手駅⇔立崎（東京藝術大学通過、もえぎ野台経由） (green)
  • 取手駅⇔立崎（東京藝術大学経由、もえぎ野台経由） (white)
  • 布佐駅⇒利根ニュータウン東 (purple)
Routes in Otone Kotsu (大利根交通)'s feed
RouteTypeLine color
利根ニュータウン東⇒布佐駅Busyellow
取手駅⇔もえぎ野台（東京藝術大学通過）Busblue
取手駅⇔もえぎ野台（東京藝術大学経由）Busteal
取手駅⇔もえぎ野台（東京藝術大学通過、羽黒経由）Buswhite
取手駅⇔利根ニュータウン東（東京藝術大学通過）Buspink
利根ニュータウン東⇔取手駅（東京藝術大学経由）Busblue
取手駅⇔北方車庫（東京藝術大学通過）Busred
取手駅⇔北方車庫（東京藝術大学経由）Busteal
取手駅⇔東京藝術大学（臨時便）Busteal (no shape in feed)
取手駅⇔立崎（東京藝術大学通過、もえぎ野台経由）Busgreen
取手駅⇔立崎（東京藝術大学経由、もえぎ野台経由）Buswhite
布佐駅⇒利根ニュータウン東Buspurple

This feed has 109 stops.

List every stop
  • 取手駅
  • 仲町
  • 仲町
  • 市民会館入口
  • 市民会館入口
  • 片町
  • 片町
  • 東三丁目
  • 東三丁目
  • 新道
  • 新道
  • 長町住宅
  • 長町住宅
  • 吉田
  • 吉田
  • 城根
  • 城根
  • 馬坂
  • 馬坂
  • 平石
  • 平石
  • 中妻
  • 中妻
  • 小文間公民館前
  • 小文間公民館前
  • 東京藝術大学
  • 東京芸大前
  • 東京芸大前
  • 天神前
  • 天神前
  • 戸田井
  • 戸田井
  • 戸田井橋
  • 戸田井橋
  • 羽根野
  • 羽根野
  • 羽根野
  • 羽黒
  • 東羽黒
  • 北方
  • 諏訪神社
  • 諏訪神社
  • 羽根野台
  • 羽根野台
  • 公園前
  • 公園前
  • 団地中央
  • 団地中央
  • 早尾台
  • 早尾台
  • 早尾台東
  • 早尾台東
  • 北方車庫
  • 北方
  • 北方
  • 東北方
  • 東北方
  • もえぎ野台一丁目
  • もえぎ野台一丁目
  • もえぎ野台自然公園
  • もえぎ野台自然公園
  • もえぎ野台四丁目
  • もえぎ野台四丁目
  • もえぎ野台五丁目
  • もえぎ野台五丁目
  • もえぎ野台
  • もえぎ野台入口
  • もえぎ野台入口
  • 奧山
  • 奧山
  • 押戸
  • 押戸
  • 大房四ツ角
  • 大房四ツ角
  • 大房
  • 大房
  • 立木
  • 立木
  • 立木新田
  • 立木新田
  • 立崎
  • 立崎
  • 利根町公民館前
  • 利根町公民館前
  • 押付
  • 押付
  • 利根フレッシュタウン北
  • 利根フレッシュタウン北
  • とねっ子公園前
  • とねっ子公園前
  • 浄水場前
  • 浄水場前
  • 布川東前
  • 布川東前
  • 油内
  • 油内
  • ショッピングセンター前
  • ショッピングセンター前
  • 風の公園前
  • 風の公園前
  • 利根ニュータウン東
  • 利根フレッシュタウン
  • 利根フレッシュタウン
  • 利根町役場前
  • 利根町役場前
  • 布佐本町
  • 布佐本町
  • 都
  • 布佐駅

Over time

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

2026-07-18: 85.02026-07-19: 85.0
Show the numbers
CheckScoreChange
2026-07-1885.0 first check
2026-07-1985.0 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

4 findings, ordered by severity.

Show every finding
  • Warning19136 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

  • Warning109 instances

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

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

  • Info1 instance

    Platform without parent station (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: platform_without_parent_station · 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 100% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 263 days.
Accessible Not yet
States wheelchair access on 0% of stops and 100% 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 263 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 84 / 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 75 / 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.

Otone Kotsu (大利根交通) 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/otone-kotsu/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.