GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Shimokita Kotsu (下北交通)

Based on the feed this agency publishes

Service mode Bus

71.2 / 100

unchanged since 2026-07-18

Catalogued in Aomori, Japan.

Covers 255 daysAccessibility gapsRealtime not yet published

Shimokita Kotsu operates route buses on the Shimokita Peninsula in northern Aomori.

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

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

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

Correctness68.2 / 100

The MobilityData validator flagged 8 kinds of issue across 6015 instances (0 error, 6004 warning, 11 informational).

Freshness100.0 / 100

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

1 accessibility depth signal

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

  • 青森線 (pink)
  • むつ病院・中央クリニック循環線 (white)
  • むつ病院循環線 (orange)
  • 野辺地線 (blue)
  • むつ・佐井線 (red)
  • 風間浦コミュニティバス (green)
  • むつ線 (yellow)
  • 泊線 (gray)
  • 六ヶ所線 (yellow)
  • 恐山線 (brown)
  • むつ市内線① (gray)
  • むつ市内線② (gray)
  • むつ市内線② (gray)
  • むつ市内線③ (gray)
Routes in Shimokita Kotsu (下北交通)'s feed
RouteTypeLine color
青森線Buspink
むつ病院・中央クリニック循環線Buswhite
むつ病院循環線Busorange
野辺地線Busblue
むつ・佐井線Busred
風間浦コミュニティバスBusgreen
むつ線Busyellow
泊線Busgray
六ヶ所線Busyellow
恐山線Busbrown
むつ市内線①Busgray
むつ市内線②Busgray
むつ市内線②Busgray
むつ市内線③Busgray

This feed has 689 stops.

List every stop
  • 田野向
  • 田野向
  • 臨時停留所
  • 臨時停留所
  • 金谷沢
  • 金谷沢
  • 大室平
  • 大室平
  • 一里小屋
  • 一里小屋
  • 並木
  • 並木
  • 南大曲
  • 南大曲
  • 大曲
  • 大曲
  • 大曲一丁目
  • 大曲一丁目
  • 第三田名部小学校前
  • 第三田名部小学校前
  • 後萢通
  • 後萢通
  • 金曲
  • 金曲
  • むつ営業所前
  • むつ営業所前
  • むつ新町
  • むつ新町
  • 新町中央
  • 新町中央
  • 本町
  • 本町
  • むつ
  • むつ
  • 大畑駅前
  • 大畑上新町
  • 大畑上新町
  • 大畑下新町
  • 大畑下新町
  • 湊
  • 湊
  • ＪA青森支店前
  • ＪA青森支店前
  • 上野
  • 上野
  • 水木沢
  • 水木沢
  • 戦敷
  • 戦敷
  • 正津川小学校前
  • 正津川小学校前
  • 正津川
  • 正津川
  • 優婆寺前
  • 優婆寺前
  • 下正津川
  • 下正津川
  • 烏沢
  • 烏沢
  • 安畑
  • 安畑
  • 上川代
  • 上川代
  • 道の駅ゆーさ浅虫前
  • 道の駅ゆーさ浅虫前
  • 川代
  • 川代
  • 浜関根口
  • 浜関根口
  • 浜関根
  • 前浜
  • 出戸橋
  • 出戸（むつ市）
  • 出戸（むつ市）
  • 石神温泉前
  • 石神温泉前
  • 山田板金前
  • 山田板金前
  • 関根駐在所前
  • 関根駐在所前
  • 北関根
  • 北関根
  • 土屋番所跡
  • 土屋番所跡
  • 南関根
  • 南関根
  • 名子平
  • 名子平
  • 北椛山
  • 北椛山
  • 南椛山
  • 南椛山
  • 早掛沼公園前
  • 早掛沼公園前
  • 迎坂
  • 迎坂
  • 女館
  • 女館
  • むつ中学校前
  • むつ中学校前
  • 柳町二丁目
  • 柳町二丁目
  • むつ郵便局前
  • むつ郵便局前
  • ほたて広場前
  • ほたて広場前
  • 古川（むつ市）
  • 古川（むつ市）
  • 田名部高校前
  • 田名部高校前
  • 田名部中学校前
  • 田名部中学校前
  • 緑町
  • 緑町
  • 緑町
  • 下北町
  • 下北町
  • 下北駅前
  • 下北駅前
  • 土屋
  • 土屋
  • 佐井車庫前
  • 佐井村役場前
  • 佐井村役場前
  • 佐井
  • 古佐井
  • 古佐井
  • 黒岩
  • 黒岩
  • 佐井中学校前
  • 佐井中学校前
  • 大石平（平内町）
  • 大石平（平内町）
  • 上原田
  • 上原田
  • 原田
  • 原田
  • 高橋農場前
  • 高橋農場前
  • 材木
  • 材木
  • 新釜
  • 新釜
  • 奥戸黒岩
  • 奥戸黒岩
  • 奥戸小学校前
  • 奥戸小学校前
  • 奥戸
  • 奥戸
  • 下奥戸
  • 下奥戸
  • 向町
  • 向町
  • 平内中野
  • 平内中野
  • 北奥戸
  • 北奥戸
  • 小奥戸
  • 小奥戸
  • 七郎平
  • 七郎平
  • 中磯
  • 中磯
  • 上根田内
  • 上根田内
  • 根田内
  • 根田内
  • フェリー乗場前
  • マエダストア前
  • マエダストア前
  • 上町
  • 上町
  • 大間
  • 大間
  • 西平内郵便局前
  • 西平内郵便局前
  • 東浜町
  • 船見町
  • 日和町
  • 日和町
  • 割石
  • 割石
  • 潮見町
  • 潮見町
  • 大間崎
  • 大間崎
  • 美島町
  • 美島町
  • 朝日町
  • 朝日町
  • 大間平
  • 大間平
  • 三番坂
  • 三番坂
  • 藤沢
  • 藤沢
  • 青森駅前
  • 県営住宅前
  • 県営住宅前
  • 大間高校前
  • 大間高校前
  • 大間病院前
  • 大間病院前
  • 大間ウイング前
  • 大間ウイング前
  • ばんや前
  • ばんや前
  • 潜石
  • 潜石
  • 古釜谷
  • 古釜谷
  • 蛇浦石上
  • 蛇浦石上
  • 蛇浦
  • 蛇浦
  • 下蛇浦
  • 下蛇浦
  • スキー工場前
  • スキー工場前
  • 沢の黒
  • 沢の黒
  • 孫三郎澗
  • 孫三郎澗
  • 風間浦中学校前
  • 風間浦中学校前
  • 易国間郵便局前
  • 易国間郵便局前
  • 易国間
  • 易国間
  • 易国間新町
  • 易国間新町
  • 易国間下新町
  • 易国間下新町
  • 菅の尻
  • 菅の尻
  • 桑畑
  • 桑畑
  • 大川尻
  • 大川尻
  • 平内中央病院通り
  • 平内中央病院通り
  • 日和崎
  • 日和崎
  • 立石
  • 立石
  • 下風呂温泉
  • 下風呂温泉
  • 風間浦駐在所前
  • 風間浦駐在所前
  • 畑尻
  • and 439 more (see the full list on the map or in the GeoJSON)

Over time

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

2026-07-18: 71.22026-07-19: 71.2
Show the numbers
CheckScoreChange
2026-07-1871.2 first check
2026-07-1971.2 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

11 findings, ordered by severity.

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

  • Warning689 instances

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

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

  • Warning84 instances

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

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

    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

  • 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

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

    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

  • 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 68 / 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.

Shimokita Kotsu (下北交通) 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/shimokita-kotsu/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.