GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Iwade City Loop Bus (岩出市巡回バス)

Based on the feed this agency publishes

Service mode Bus

75.0 / 100

First scorecard for this agency

Catalogued in Wakayama, Japan.

Covers 255 daysAccessibility gapsRealtime not yet published

Iwade City's circulator 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 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

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

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.

⏱ 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

Correctness76.8 / 100

The MobilityData validator flagged 6 kinds of issue across 1167 instances (0 error, 1129 warning, 38 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

  • 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

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 Iwade City Loop Bus (岩出市巡回バス)'s feed
RouteTypeLine color
岩出市巡回バス 西巡回（紀泉台・吉田）コースBusteal (no shape in feed)
岩出市巡回バス 中央巡回（南大池・中黒）コースBusgreen (no shape in feed)
岩出市巡回バス 東巡回（船戸・根来）コースBusred (no shape in feed)

This feed has 177 stops.

List every stop
  • 西安上
  • 西安上
  • 西安上北
  • 西安上北
  • うぐいす台
  • うぐいす台
  • 紀泉台ロータリー
  • 紀泉台ロータリー
  • 紀泉台北
  • 紀泉台北
  • 紀泉台
  • 紀泉台
  • 相谷東
  • 相谷東
  • 相谷らんかん橋
  • 相谷らんかん橋
  • 相谷西
  • 相谷西
  • 相谷
  • 相谷
  • 市役所
  • 経塚南
  • 経塚南
  • 山池ノ前
  • 山池ノ前
  • 山大原
  • 山大原
  • 山村西
  • 山村
  • 山村
  • 山石原
  • 山石原
  • 吉田団地
  • 吉田団地
  • 吉田
  • 吉田
  • 鴨沼団地
  • 鴨沼団地
  • 吉田南
  • 吉田南
  • 中迫南
  • 中黒南
  • 中黒南
  • 中島前島
  • 中島前島
  • 中島大畑毛
  • 中島大畑毛
  • さぎのせ公園
  • さぎのせ公園
  • 中島古川南
  • 中島古川南
  • 中島東
  • 中島東
  • 中島北
  • 中島北
  • 金屋
  • 金屋
  • 畑毛
  • 畑毛
  • 畑毛交番
  • 畑毛交番
  • 中迫
  • 中迫
  • 宮
  • 宮
  • 観光案内所・岩出地区公民館
  • 観光案内所・岩出地区公民館
  • 岩出駅
  • 岩出駅
  • 清水北
  • 清水北
  • 大町
  • 大町
  • 那賀総合庁舎前
  • 那賀総合庁舎前
  • 中迫住友団地西
  • 中迫住友団地西
  • 中迫住友団地
  • 中迫住友団地
  • 高塚井ノ上
  • 高塚井ノ上
  • 水栖
  • 水栖
  • 荊本
  • 荊本
  • 南大池
  • 南大池
  • 北大池
  • 北大池
  • 野上野
  • 野上野
  • 野上野南
  • 野上野南
  • 岩出第二中学校前
  • 岩出第二中学校前
  • 桜台
  • 桜台
  • 桜台地区公民館前
  • 桜台地区公民館前
  • さくら公園
  • さくら公園
  • 桜台西
  • 桜台西
  • 根来東
  • 根来東
  • 曽屋白才
  • 曽屋白才
  • 根来寺大門前
  • 根来寺大門前
  • 岩出図書館
  • 根来郵便局前
  • 根来郵便局前
  • 根来
  • 根来
  • 根来西
  • 根来西
  • 安上
  • 安上
  • 金池住吉橋前
  • 金池住吉橋前
  • 中黒北
  • 中黒北
  • 中黒西
  • 中黒西
  • 黒木
  • 黒木
  • 交通公園
  • 交通公園
  • 山崎地区公民館
  • 山崎地区公民館
  • 岩出中学校西
  • 岩出中学校西
  • 荊本西
  • 荊本西
  • 市民総合体育館
  • 市民総合体育館
  • 岩出中学校東
  • 岩出中学校東
  • 船戸跨線橋北詰
  • 船戸山古墳前
  • 船戸箱山
  • 山崎
  • 船山地区公民館
  • 曽屋久保
  • 曽屋久保
  • 船戸
  • 大町南
  • 大町南
  • 溝川
  • 溝川
  • おひさま子ども園前
  • おひさま子ども園前
  • 岡田才ノ神
  • 岡田才ノ神
  • 東公園前
  • 東公園前
  • 西国分西
  • 西国分西
  • 新田広芝南
  • 新田広芝南
  • 新田広芝北
  • 新田広芝北
  • 上岩出コミセン
  • 上岩出コミセン
  • 総合保健福祉センター
  • 北大池村中
  • 北大池村中
  • 緑花センター・根来公園墓地前
  • 緑花センター・根来公園墓地前
  • 根来寺
  • 根来寺
  • ねごろ歴史の丘
  • ねごろ歴史の丘
  • 川尻三叉路
  • 川尻三叉路
  • 安上南
  • 安上南

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

9 findings, ordered by severity.

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

  • Warning177 instances

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

    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

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

    Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • 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

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

    Validator rule: trip_headsign_matches_intermediate_stop · 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 77 / 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.

Iwade City Loop 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/iwade-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.