GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Aridagawa Town Community Bus (有田川町コミュニティバス)

Based on the feed this agency publishes

Service mode Bus

72.5 / 100

unchanged since 2026-07-18

Catalogued in Wakayama, Japan.

Covers 255 daysAccessibility gapsRealtime not yet published

Aridagawa Town's community bus network; counted as one feed record.

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

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

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

Correctness71.0 / 100

The MobilityData validator flagged 7 kinds of issue across 601 instances (0 error, 597 warning, 4 informational).

Freshness100.0 / 100

Service data covers the next 255 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.

1 accessibility depth signal

  • 6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (有田川町コミュニティバス 金屋4コース, 有田川町コミュニティバス 楠本線, 有田川町コミュニティバス 沼谷線, 有田川町コミュニティバス 板尾線, 有田川町コミュニティバス 五郷線, 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

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 Aridagawa Town Community Bus (有田川町コミュニティバス)'s feed
RouteTypeLine color
有田川町コミュニティバス 金屋3コースBusgray (no shape in feed)
有田川町コミュニティバス 金屋4コースBusorange (no shape in feed)
有田川町コミュニティバス 金屋5コースBuswhite (no shape in feed)
有田川町コミュニティバス 楠本線Busred (no shape in feed)
有田川町コミュニティバス 境川線Buswhite (no shape in feed)
有田川町コミュニティバス 遠井線Busteal (no shape in feed)
有田川町コミュニティバス 沼谷線Busbrown (no shape in feed)
有田川町コミュニティバス 室川線Buspurple (no shape in feed)
有田川町コミュニティバス 板尾線Busorange (no shape in feed)
有田川町コミュニティバス 湯川線Busblack (no shape in feed)
有田川町コミュニティバス 沼線Busgray (no shape in feed)
有田川町コミュニティバス 五郷線Busgreen (no shape in feed)
有田川町コミュニティバス 三瀬川線Buspink (no shape in feed)
有田川町コミュニティバス 日物川線Busyellow (no shape in feed)
有田川町コミュニティバス 東大谷線Busteal (no shape in feed)

This feed has 164 stops.

List every stop
  • 松
  • 小池
  • 桜峠
  • 元農協前
  • 沼診療所前
  • 西番
  • 井本宅前・柵
  • 楠本小学校前
  • 江立川
  • 中
  • 丸山宅前（楠本上）
  • 青石スタンド前
  • 新尼ヶ瀬橋
  • 学校登口四叉路
  • 大岡店前
  • 馬場医院
  • なかむら医院
  • 清水行政局前
  • 堀本宅前
  • 堅山宅前
  • 中峯１
  • 中尾宅横防火水槽前
  • 楠木商店前
  • 木下宅前
  • 保坂宅前
  • 北峰宅上三叉路
  • 高松宅前
  • 花田宅前
  • 休場酒店前
  • 元小学校前
  • 尾上宅上
  • 本堂
  • 田中宅前
  • 山手橋詰
  • 保田宅前
  • 柳生宅前
  • 岩脇宅下
  • 植野宅前
  • 中尾宅前（北）
  • 上班上がり口三叉路
  • 山本宅下三叉路
  • 北畑宅前
  • 沼田
  • 中尾宅前（南）
  • 東宅下自動販売機前
  • 前田宅前
  • トマト集荷場前
  • 岩井宅下
  • 鈴木宅下（大蔵）
  • 山本宅下
  • 紀東工営倉庫前
  • 岩井宅横
  • 林宅下
  • 中峯２
  • 鈴木宅下（宮川）
  • 藤井宅上
  • 消防詰所前
  • 旧道出会い三叉路
  • 室川
  • 坂本谷林道入り口
  • 集会所前（室川）
  • 東宅前
  • 堀田宅前（東）
  • 堀田宅前（西）
  • 西ヶ峯下
  • 安諦出張所前
  • 松谷医院板尾出張所前
  • 松谷医院前
  • 小薮宅前
  • 久保宅下
  • 束前宅下
  • 上湯川
  • 下原口
  • 湯川
  • 五段口
  • 青田
  • 福井
  • 中村
  • 学校前
  • 多井口
  • 多井
  • 峠
  • 倉谷
  • 奥野
  • 清水口
  • 清水
  • 延坂
  • 西原集会所前
  • お寺下
  • 上畑宅前
  • 丸山宅前（楠本下）
  • 青石宅上
  • 高垣宅前
  • 古岡宅乗り口の県道三叉路
  • 西本宅前
  • 前島宅前
  • 三澤宅下三叉路
  • 尾上
  • 中谷宅前
  • 西八幡選果場
  • 元沼分校
  • 沼プール上四叉路
  • 岩橋宅前
  • 前宅前
  • 区集会所前（北野川）
  • 向井宅前（北）
  • 向井宅前（南）
  • 上田宅前
  • 小原
  • 金屋口
  • 谷関宅前
  • 東本宅前
  • 東本宅上
  • 洞宅前
  • 中林宅前
  • 区集会所前（二澤）
  • 二澤口橋詰
  • 向井宅前（川合）
  • 西浦宅前
  • 西浦建設事務所前
  • 生石
  • 五郷出張所前
  • 芋原薬局前
  • 五郷郵便局前
  • 神社前
  • 南理容店前
  • 平野宅横倉庫前
  • 向谷宅下
  • 笠松医院前
  • 有木宅前
  • 集会所前（三瀬川）
  • 伏羊
  • 田和宅下
  • 久保地区登り口
  • なかむら内科クリニック城山出張所前
  • 沼田宅前
  • 高垣宅上防火水槽前
  • 神崎宅前
  • 古垣宅横
  • 高垣宅下三叉路（西）
  • 長硲宅前
  • 高垣宅下三叉路（東）
  • 立石
  • 的場宅前
  • 西鉄工所上三叉路
  • 北浦宅上三叉路
  • 井上宅前
  • 平岩宅下
  • 古田宅前
  • お寺前
  • 大硲宅上三叉路
  • 防火水槽前
  • 大硲宅前
  • 谷
  • 金屋庁舎
  • 金屋庁舎
  • 上野
  • 上野
  • 吉田
  • 有原・宮田店
  • 西ヶ峯上
  • 畦田
  • 平成橋
  • 瀬井

Over time

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

2026-07-18: 72.52026-07-19: 72.5
Show the numbers
CheckScoreChange
2026-07-1872.5 first check
2026-07-1972.5 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

10 findings, ordered by severity.

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

  • Warning164 instances

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

  • Warning33 instances

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

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

  • Warning25 instances

    The feed contains route shapes no trip uses.

    Harmless to riders, but it bloats the feed and suggests stale export data.

    Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)

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

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

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

  • Warning1 instance

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

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

  • Info2 instances

    The feed has a stretch of two weeks or more with no service running.

    A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

    Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

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

  • Info2 instances

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

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

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Validator rule: scorecard_no_feed_contact · 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 71 / 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.

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.

Aridagawa Town Community 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/aridagawa-town-community-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.