Feed status · checked 2026-07-23
外ヶ浜町営バス
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Aomori, Japan.
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
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
135 of 135 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
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
41 of 41 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
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.
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.
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.
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 161 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
The MobilityData validator flagged 6 kinds of issue across 855 instances (0 error, 853 warning, 2 informational).
Service data covers the next 161 days.
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.
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.
Fares are applied to trips.
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 dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 外ヶ浜町営 蟹田地区バス（病院線） (yellow)
- 外ヶ浜町営 蟹田地区バス（温泉行） (red)
- 外ヶ浜町営 蟹田地区バス（温泉行） (red)
- 外ヶ浜町営 平舘地区バス (green)
- 外ヶ浜町営 平舘地区バス (brown)
- 外ヶ浜町営 三厩地区バス（病院） (teal)
- 外ヶ浜町営 三厩地区バス（病院） (gray)
- 外ヶ浜町営 三厩地区バス (teal)
- 外ヶ浜町営 三厩地区バス (gray)
| Route | Type | Line color |
|---|---|---|
| 外ヶ浜町営 蟹田地区バス（病院線） | Bus | yellow |
| 外ヶ浜町営 蟹田地区バス（温泉行） | Bus | red |
| 外ヶ浜町営 蟹田地区バス（温泉行） | Bus | red |
| 外ヶ浜町営 平舘地区バス | Bus | green |
| 外ヶ浜町営 平舘地区バス | Bus | brown |
| 外ヶ浜町営 三厩地区バス（病院） | Bus | teal |
| 外ヶ浜町営 三厩地区バス（病院） | Bus | gray |
| 外ヶ浜町営 三厩地区バス | Bus | teal |
| 外ヶ浜町営 三厩地区バス | Bus | gray |
This feed has 135 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
- Warning822 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 (opens the validator rules on an external site)
- Warning135 instances
135 of 135 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 (opens the GTFS Schedule reference on an external site)
- Warning41 instances
41 of 41 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 (opens the GTFS Schedule reference on an external site)
- Warning24 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 (opens the validator rules on an external site)
- Warning4 instances
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 (opens the validator rules on an external site)
- Warning2 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 (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
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 161 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 161 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 74 / 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.
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/sotogahamatown-sotogahama-townbus/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.