GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

八戸市南郷コミュニティバス

Based on the feed this agency publishes

Service mode Bus

75.3 / 100

First scorecard for this agency

Catalogued in Aomori, Japan.

Covers 251 daysAccessibility gapsRealtime not yet published

八戸市南郷コミュニティバス is the public schedule named by the repository. This registry item represents 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.

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

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

12 of 12 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 251 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

Correctness77.5 / 100

The MobilityData validator flagged 5 kinds of issue across 378 instances (0 error, 376 warning, 2 informational).

Freshness100.0 / 100

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

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.

  • 南郷コミュニティバス 頃巻沢線 (red)
  • 南郷コミュニティバス 泉清水線 (blue)
  • 南郷コミュニティバス 七枚田線 (orange)
  • 南郷コミュニティバス 田代線 (purple)
  • 南郷コミュニティバス 大平線 (green)
  • 南郷コミュニティバス 古里線 (teal)
Routes in 八戸市南郷コミュニティバス's feed
RouteTypeLine color
南郷コミュニティバス 頃巻沢線Busred
南郷コミュニティバス 泉清水線Busblue
南郷コミュニティバス 七枚田線Busorange
南郷コミュニティバス 田代線Buspurple
南郷コミュニティバス 大平線Busgreen
南郷コミュニティバス 古里線Busteal

This feed has 171 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

8 findings, ordered by severity.

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

  • Warning171 instances

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

  • Warning12 instances

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

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

  • 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

    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 251 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 251 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 78 / 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.

八戸市南郷コミュニティバス 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/hachinohecity-hachinohe-nango/2026-07-23.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-23. 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.