Feed status · checked 2026-09-05
Shiso City Shitan Bus, other lines (宍粟市しーたんバス（蔦沢線・大谷線以外）)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Hyogo, 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
441 of 441 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
151 of 151 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
- 441 of 441 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
- 151 of 151 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 207 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 6447 instances (0 error, 6438 warning, 9 informational).
Service data covers the next 207 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.
This feed has 441 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.
- しーたんバス 循環線 (green)
- しーたんバス 土万線 (teal)
- しーたんバス 塩田線 (red)
- しーたんバス 染河内川西線 (green)
- しーたんバス 下三方線 (green)
- しーたんバス 戸倉線（飯見経由） (green)
- しーたんバス 戸倉線（音水経由） (green)
- しーたんバス 谷今市線 (green)
- しーたんバス 水谷線 (green)
- しーたんバス 戸原線 (gray)
- しーたんバス 城下線 (red)
- しーたんバス 梯河東線（三谷経由） (yellow)
- しーたんバス 梯河東線（三谷経由無し） (yellow)
- しーたんバス 与位河東線（三谷経由） (yellow)
- しーたんバス 与位河東線（三谷経由無し） (yellow)
| Route | Type | Line color |
|---|---|---|
| しーたんバス 循環線 | Bus | green |
| しーたんバス 土万線 | Bus | teal |
| しーたんバス 塩田線 | Bus | red |
| しーたんバス 染河内川西線 | Bus | green |
| しーたんバス 下三方線 | Bus | green |
| しーたんバス 戸倉線（飯見経由） | Bus | green |
| しーたんバス 戸倉線（音水経由） | Bus | green |
| しーたんバス 谷今市線 | Bus | green |
| しーたんバス 水谷線 | Bus | green |
| しーたんバス 戸原線 | Bus | gray |
| しーたんバス 城下線 | Bus | red |
| しーたんバス 梯河東線（三谷経由） | Bus | yellow |
| しーたんバス 梯河東線（三谷経由無し） | Bus | yellow |
| しーたんバス 与位河東線（三谷経由） | Bus | yellow |
| しーたんバス 与位河東線（三谷経由無し） | Bus | yellow |
List every stop
- 下宇原４
- 下宇原４
- 下宇原５
- 下宇原５
- 宇原１
- 宇原０
- 八幡下
- 八幡下
- 加生山崎高校前
- 加生山崎高校前
- 木谷橋
- 木谷橋
- 市場公民館前
- 市場公民館前
- 米山口
- 米山口
- 広岡橋
- 広岡橋
- 高下公民館前
- 高下公民館前
- 菅野郵便局前
- 菅野郵便局前
- 宇原２
- 宇原２
- 山崎西小学校前
- 山崎西小学校前
- 青木
- 青木
- 折橋
- 折橋
- 鍛冶屋橋
- 鍛冶屋橋
- 比地町東
- 比地町東
- 比地町
- 比地町
- 矢の口
- 矢の口
- 葛根
- 葛根
- 葛根西口
- 葛根西口
- 土万
- 土万
- 宇原３
- 宇原３
- 土万９
- 土万９
- 土万８
- 土万８
- 土万３
- 土万３
- 土万２
- 土万２
- 塩山１
- 塩山１
- 塩山２
- 塩山２
- 塩山４
- 塩山４
- 塩山５
- 塩山５
- 塩山６
- 塩山６
- 大沢１
- 大沢１
- 宇原４
- 宇原４
- 大沢２
- 大沢２
- 大沢３
- 大沢３
- 段
- 大沢４
- 大沢４
- 大沢５
- 大沢５
- 小茅野２
- 小茅野２
- 小茅野１
- 高下
- 高下
- 大谷橋
- 大谷橋
- 青木１
- 青木１
- 宇原５
- 宇原５
- 塩田２
- 塩田２
- 塩田３
- 塩田３
- 塩田４
- 塩田４
- 塩田５
- 塩田５
- 塩田６
- 塩田６
- 椴ヶ段
- 中山
- 中山
- 亜細亜
- 亜細亜
- 本谷お堂前
- 本谷お堂前
- 岩花下
- 岩花下
- 岩花下
- 川戸１
- 川戸１
- 横地
- 横地
- 中坪公民館前
- 中坪公民館前
- 才樫
- 才樫
- 観音寺前
- 観音寺前
- 山田口
- 山田口
- 山田口
- 山田口
- 福田お堂前
- 福田お堂前
- 長野
- 長野
- 上長
- 上長
- 山田お堂前
- 山田お堂前
- 山田公民館前
- 川戸２
- 川戸２
- 山崎
- 森林大学校前
- 森林大学校前
- 能倉公民館前
- 能倉公民館前
- ふれあい公園前
- ふれあい公園前
- 上野田
- 上野田
- 上土居
- 上土居
- 中土居
- 中土居
- 一宮南中学校前
- 一宮南中学校前
- 染河内口
- 染河内口
- はりま一宮小学校前
- はりま一宮小学校前
- 三軒屋
- 三軒屋
- 川戸３
- 川戸３
- 閏賀口
- 閏賀口
- 一宮市民協働センター前
- 一宮市民協働センター前
- 曲里
- 曲里
- 伊和高校前
- 伊和高校前
- 西安積橋口
- 西安積橋口
- 西安積公民館前
- 西安積公民館前
- 西八幡神社下
- 西八幡神社下
- 普門寺前
- 上垣内
- 上垣内
- 川戸４
- 川戸４
- 林垣内
- 林垣内
- 閏賀北口
- 閏賀北口
- 閏賀公民館前
- 閏賀公民館前
- やすらぎ
- 福知渓谷
- 福知渓谷
- 登橋
- 登橋
- 奥福知橋
- 奥福知橋
- 薮
- 薮
- 津羅橋
- 津羅橋
- 明願寺前
- 明願寺前
- 川戸５
- 川戸５
- 福知公民館前
- 福知公民館前
- 西福橋
- 西福橋
- 西深集会所前
- 西深集会所前
- 下西深
- 下西深
- 深河谷
- 深河谷
- 深河谷詰所前
- 深生橋
- 深生橋
- 楽里
- 楽里
- 嵯峨山
- 嵯峨山
- 御名東
- 御名東
- 御名高下
- 御名高下
- JA城下支店
- JA城下支店
- 城の子公園前
- 城の子公園前
- 皆木
- 飯見詰所北
- 飯見詰所北
- 飯見公民館前
- 飯見公民館前
- 飯見橋
- 飯見橋
- 下野尻
- 下野尻
- 野尻
- 野尻
- 金谷北
- 金谷北
- 原有賀
- 原有賀
- 原
- 原
- 赤西口
- 赤西口
- 二連瀬
- 二連瀬
- 日の原
- 日の原
- 音水口
- 音水口
- 引原ダム
- 引原ダム
- 引原トンネル
- 引原トンネル
- and 191 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
9 findings, ordered by severity.
Show every finding
- Warning6417 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)
- Warning441 instances
441 of 441 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)
- Warning151 instances
151 of 151 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)
- Warning19 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)
- 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)
- 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.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info7 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 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 207 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 207 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 77 / 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/shiso-shitan-bus-wing-shinki/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.