Feed status · checked 2026-09-05
Murakami City Community Bus (村上市コミュニティバス)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Niigata, 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.3, validator 8.0.1.
Checked for changes 2 hours ago; last changed 2 hours ago.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
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
314 of 314 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
119 of 119 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
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 314 of 314 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 119 of 119 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some internal IDs use characters outside the basic text set.
- Next action
- 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.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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 327 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 7 kinds of issue across 4709 instances (0 error, 4696 warning, 13 informational).
Service data covers the next 327 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
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (大須戸線, 河内線, 瀬波温泉・粟島号, まちなか循環（小回り）, せなみ巡回, and more).
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
This feed has no route shapes, so the map shows its stops only.
This feed has 314 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| まちなか循環（大回り） | Bus | red (no shape in feed) |
| 大須戸線 | Bus | gray (no shape in feed) |
| 塩野町線 | Bus | purple (no shape in feed) |
| 北中線 | Bus | teal (no shape in feed) |
| 河内線 | Bus | red (no shape in feed) |
| 町屋号 | Bus | green (no shape in feed) |
| 瀬波温泉・粟島号 | Bus | red (no shape in feed) |
| まちなか循環（小回り） | Bus | teal (no shape in feed) |
| せなみ巡回 | Bus | teal (no shape in feed) |
| 雷・勝木線 | Bus | yellow (no shape in feed) |
| 大毎・鼠ヶ関線 | Bus | teal (no shape in feed) |
| 岩船巡回 | Bus | orange (no shape in feed) |
| 縄文の里朝日線 | Bus | brown (no shape in feed) |
| 高根線 | Bus | pink (no shape in feed) |
List every stop
- 茎太
- 岩崩
- 三面発電所
- 縄文の里朝日
- 村上IC入口
- 村上IC入口
- 牛沢
- 牛沢
- 田口
- 田口
- 十川
- 上十川
- 高田入口
- 飯野二丁目
- 下新保
- 岩沢
- 岩沢
- 川端道
- 野村
- 朝日支所前
- 朝日支所前
- 中原
- 朝日みどり小学校前
- 黒田
- 関口診療所前
- 関口
- 細工町
- 関口上通前
- 北大平
- 荒沢入口
- 高根グラウンド前
- 食堂IRORI前
- 雲上橋
- 高根
- 小助島
- 小助島
- 泉町
- 泉町
- 山辺里
- 山辺里
- 村上税務署前
- 村上税務署前
- 四日市
- 四日市
- 古渡路
- 古渡路
- 小川
- 小川
- 小川国道
- 小川国道
- 宮ノ下
- 宮ノ下
- 鵜渡路
- 鵜渡路
- 森林研究所前
- 森林研究所前
- 上野
- 上野
- 朝日さくら小学校前
- 朝日さくら小学校前
- 猿沢
- 猿沢
- 二之町
- 二之町
- 猿沢上町
- 猿沢上町
- 桧原
- 桧原
- 桧原中通
- 桧原中通
- 桧原上通
- 桧原上通
- 村上市ごみ処理場前
- 村上市ごみ処理場前
- 板屋越三差路
- 板屋越三差路
- 板屋越
- 板屋越
- 早稲田三差路
- 早稲田三差路
- 早稲田
- 早稲田
- 松岡
- 松岡
- 三之町
- 塩野町
- 塩野町
- 塩野町郵便局前
- 塩野町郵便局前
- 竜門寺前
- 竜門寺前
- 塩野町車庫前
- 塩野町車庫前
- 大須戸
- 大須戸（国道）
- 大須戸（国道）
- 下大行
- 大行鉱泉前
- 大行鉱泉前
- 蒲萄入口
- 蒲萄入口
- 蒲萄
- 蒲萄
- しぶや小児科前
- しぶや小児科前
- 中小屋
- 中小屋
- 大沢入口
- 大毎宮前
- 大毎宮前
- 北中上
- 北中上
- 北中
- 松原町二丁目
- 松原町二丁目
- 学校町
- 学校町
- 上助渕
- 上助渕
- 山屋
- 里本庄
- 新町
- 新町
- 殿岡
- 小出
- 有明
- 桃川下
- 桃川中
- 桃川中
- 桃川上
- 河内
- 新町（国道）
- 新町（国道）
- 石原
- 上片町
- 上片町
- 村上駅前
- 片町
- 片町
- 片町三差路
- 片町三差路
- 秋葉神社前
- 秋葉神社前
- 加賀町
- 塩町
- 塩町稲荷神社前
- 鍛冶町（北線）
- 村上保健所前
- 村上保健所前
- 大欠
- 大欠
- 緑町
- 緑町
- 旧病院前
- 旧病院前
- 村上総合病院前
- 原信村上西店前
- 肴町
- 肴町
- 田端町
- 中央図書館前
- 肴町弁天坂
- 鍛冶町
- 鍛冶町
- 小国町
- 小国町
- イヨボヤ会館
- 安良町
- 安良町
- 村上営業所
- 村上営業所
- 大町
- 小町
- 村上小町郵便局前
- 村上小学校前
- 村上市役所
- 上町
- 長井町
- 長井町
- 羽黒町
- 羽黒町
- 県営南町住宅前
- 県営南町住宅前
- 南町
- 南町
- 村上高校前
- 村上高校前
- 山北徳新会病院前
- 福祉センター前
- 福祉センター前
- 碁石
- 碁石
- 府屋駅前
- 山北支所前
- 山北支所前
- 中等教育学校前
- 中等教育学校前
- 府屋中町
- 府屋中町
- 雷
- 大代
- 小俣
- 日本国麓郵便局前
- 岩石
- 遅郷
- 杉平
- 温出
- 堀ノ内
- 瀬波地域コミュニティセンター前
- 瀬波地域コミュニティセンター前
- 山北中学校前
- 府屋上町
- 勝木駅前
- 勝木三差路
- 勝木中町
- さんぽく小学校前
- 勝木営業所
- 大毎
- 大毎下
- 中津原
- はまなす病院前
- 上大鳥
- 北田中
- 北田中
- 下大鳥
- 下大鳥入口
- 下大鳥入口
- 北赤谷
- 北赤谷
- 板屋沢
- 板屋沢
- 長坂
- 長坂
- 上大蔵
- 上大蔵
- 立島
- 立島
- 岩崎
- 瀬波病院
- 黒崎
- 中浜
- マックスバリュあつみ店
- 雷向村
- 大谷沢
- 府屋浜町
- 瀬波温泉
- 瀬波温泉
- 瀬波温泉なぎさ通り
- あかまつ荘前
- 松波町
- and 64 more (see the full list on the map or in the GeoJSON)
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
10 findings, ordered by severity.
Show every finding
- Warning4677 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.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning314 instances
314 of 314 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning119 instances
119 of 119 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning15 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.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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.)
Finding code: 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.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info10 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.)
Finding code: trip_headsign_matches_intermediate_stop · 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.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: 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
One requirement remains for this feed to earn 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 327 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 327 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 76 / 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/murakami-city-community-bus/2026-09-05.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-09-05. 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.