GTFS Scorecard
← All agencies

Feed status · checked 2026-07-18

Hanamaki City Community Bus (花巻市コミュニティバス)

Based on the feed this agency publishes

Service mode Bus

73.3 / 100

First scorecard for this agency

Catalogued in Iwate, Japan.

Covers 256 daysAccessibility gapsRealtime not yet published

Hanamaki City's community bus network in central Iwate; 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 3 hours ago; last changed 3 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

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

60 of 60 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 256 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

Correctness73.0 / 100

The MobilityData validator flagged 6 kinds of issue across 2141 instances (0 error, 2135 warning, 6 informational).

Freshness100.0 / 100

Service data covers the next 256 days.

Rider experience52.4 / 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.

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.

  • 花巻市街地循環バス (green)
  • 大迫地区・岩手医科大学附属病院・盛岡赤十字病院連絡バス (green)
  • 岩手医科大学附属病院利用者連絡バス (green)
  • 土沢線 (green)
  • 大迫花巻線 (green)
Routes in Hanamaki City Community Bus (花巻市コミュニティバス)'s feed
RouteTypeLine color
花巻市街地循環バスBusgreen
大迫地区・岩手医科大学附属病院・盛岡赤十字病院連絡バスBusgreen
岩手医科大学附属病院利用者連絡バスBusgreen
土沢線Busgreen
大迫花巻線Busgreen

This feed has 201 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
  • Warning2068 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

  • Warning201 instances

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

  • Warning60 instances

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

  • Warning57 instances

    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

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

  • 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

  • Info4 instances

    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

  • 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 256 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 256 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 73 / 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.

Hanamaki City 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/hanamaki-community-bus/2026-07-18.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-18. 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.