GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Oyabe City Bus (小矢部市営バス)

Based on the feed this agency publishes

Service mode Bus

78.6 / 100

First scorecard for this agency

Catalogued in Toyama, Japan.

Covers 255 daysAccessibility gapsRealtime not yet published

Oyabe City's municipal bus.

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 5 hours ago; last changed 11 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

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

27 of 27 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 255 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

Correctness80.0 / 100

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

Freshness100.0 / 100

Service data covers the next 255 days.

Rider experience59.6 / 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

  • 17 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (津沢線, 津沢線, 正得線, 正得線, 蟹谷線, and more).

    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.

  • 南谷線 (purple)
  • 南谷線 (purple)
  • 宮島線 (teal)
  • 宮島線 (teal)
  • 宮島線 (teal)
  • 正得線 (orange)
  • 正得線 (orange)
  • 正得線 (orange)
  • 正得線 (orange)
  • 正得線 (orange)
  • 正得線 (orange)
  • 津沢線 (pink)
  • 津沢線 (pink)
  • 津沢線 (pink)
  • 津沢線 (pink)
  • 津沢線 (pink)
  • 津沢線 (pink)
  • 津沢線 (pink)
  • 蟹谷線 (teal)
  • 蟹谷線 (teal)
  • 蟹谷線 (teal)
  • 蟹谷線 (teal)
Routes in Oyabe City Bus (小矢部市営バス)'s feed
RouteTypeLine color
南谷線Buspurple
南谷線Buspurple
宮島線Busteal
宮島線Busteal
宮島線Busteal
正得線Busorange
正得線Busorange
正得線Busorange
正得線Busorange
正得線Busorange
正得線Busorange
津沢線Buspink
津沢線Buspink
津沢線Buspink
津沢線Buspink
津沢線Buspink
津沢線Buspink
津沢線Buspink
蟹谷線Busteal
蟹谷線Busteal
蟹谷線Busteal
蟹谷線Busteal

This feed has 105 stops.

List every stop
  • JA本店・東部支店口
  • 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

5 findings, ordered by severity.

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

  • Warning105 instances

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

  • Warning27 instances

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

  • Warning17 instances

    Two or more routes share the same name.

    Riders can't tell the routes apart in apps.

    Fix: Give each route a distinct short or long name. (One field per route.)

    Validator rule: duplicate_route_name · See MobilityData GTFS Validator rules

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

    Validator rule: mixed_case_recommended_field · 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 255 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 255 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 80 / 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.

Oyabe City Bus (小矢部市営バス) 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/oyabe-city-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.