Feed status · checked 2026-09-05
Minamishinshu Takagi Village Community Bus (南信州広域連合 喬木村コミュニティバス)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Nagano, 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.
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
197 of 197 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
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
- 197 of 197 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
- 41 of 41 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 101 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 8 kinds of issue across 1588 instances (0 error, 1582 warning, 6 informational).
Service data covers the next 101 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
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (E3 喬木村民バス 喬木大島線 せせらぎ, E4 喬木村民バス 氏乗線 そよかぜ, E6 たかぎコミュニティバス 伊久間線, E7 たかぎｺﾐｭﾆﾃｨﾊﾞｽ厚生病院線).
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.
This feed has 197 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.
- E3 喬木村民バス 喬木大島線 せせらぎ (teal)
- E4 喬木村民バス 氏乗線 そよかぜ (brown)
- E5 たかぎコミュニティバス 阿島線 (pink)
- E6 たかぎコミュニティバス 伊久間線 (yellow)
- E7 たかぎｺﾐｭﾆﾃｨﾊﾞｽ厚生病院線 (orange)
- E8 喬木村民バス 上平線 (green)
- E9 喬木村民バス 富田線 (pink)
| Route | Type | Line color |
|---|---|---|
| E3 喬木村民バス 喬木大島線 せせらぎ | Bus | teal |
| E4 喬木村民バス 氏乗線 そよかぜ | Bus | brown |
| E5 たかぎコミュニティバス 阿島線 | Bus | pink |
| E6 たかぎコミュニティバス 伊久間線 | Bus | yellow |
| E7 たかぎｺﾐｭﾆﾃｨﾊﾞｽ厚生病院線 | Bus | orange |
| E8 喬木村民バス 上平線 | Bus | green |
| E9 喬木村民バス 富田線 | Bus | pink |
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
11 findings, ordered by severity.
Show every finding
- Warning1566 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)
- Warning197 instances
197 of 197 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)
- 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning11 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
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · 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)
- Info2 instances
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)
- Info2 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
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 101 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 101 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 72 / 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/minamishinshu-takagi/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.