Feed status · checked 2026-07-18
Higashine City Bus (東根市営バス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Yamagata, 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
176 of 176 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
16 of 16 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 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
The MobilityData validator flagged 5 kinds of issue across 568 instances (0 error, 566 warning, 2 informational).
Service data covers the next 256 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.
Fares are applied to trips.
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 dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| 市民バス 休石線 | Bus | red (no shape in feed) |
| 市民バス 休石線（公立病院経由） | Bus | red (no shape in feed) |
| 市民バス 北部循環線 | Bus | green (no shape in feed) |
| 市民バス 向原神町東根線（公立病院経由） | Bus | teal (no shape in feed) |
| 市民バス 向原神町東根線（長瀞・公立病院経由） | Bus | white (no shape in feed) |
| 市民バス 荷口神町東根線 | Bus | brown (no shape in feed) |
| 市民バス 河北線 | Bus | orange (no shape in feed) |
| 市民バス 中央循環東根線 | Bus | yellow (no shape in feed) |
This feed has 176 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
- Warning554 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)
- Warning176 instances
176 of 176 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)
- Warning16 instances
16 of 16 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)
- Warning10 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)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
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)
- 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 (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 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 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.
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/higashine-city-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.