Feed status · checked 2026-07-23
真室川町営バス
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
190 of 190 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
50 of 50 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 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
The MobilityData validator flagged 6 kinds of issue across 1323 instances (0 error, 1321 warning, 2 informational).
Service data covers the next 251 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 | gray (no shape in feed) |
| 真室川町路線バス | Bus | gray (no shape in feed) |
| 真室川町路線バス | Bus | white (no shape in feed) |
| 真室川町路線バス | Bus | yellow (no shape in feed) |
| 真室川町路線バス 東循環路線〔東町2〕経由 | Bus | teal (no shape in feed) |
| 真室川町路線バス 東循環路線〔宮町〕経由 | Bus | teal (no shape in feed) |
| 真室川町路線バス 東循環路線〔東町2・宮町1〕経由 | Bus | teal (no shape in feed) |
| 真室川町路線バス 西循環線〔新町・梅の里団地〕経由 | Bus | teal (no shape in feed) |
| 真室川町路線バス 西循環線〔新町・蟻喰〕経由 | Bus | teal (no shape in feed) |
| 真室川町路線バス 西循環線〔高坂・蓮花城〕経由 | Bus | teal (no shape in feed) |
This feed has 190 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
- Warning1307 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)
- Warning190 instances
190 of 190 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)
- Warning50 instances
50 of 50 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)
- Warning2 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)
- 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)
- 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 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 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/mamurogawatown-mamurogawatown/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.