Feed status · checked 2026-07-23
町民バス夢つばめ (新温泉町)
Based on the feed this agency publishes
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.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
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points in its category
Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing calendar and calendar date files (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
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
169 of 169 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
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.
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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_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.
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
- No fare information is published in the feed.
- 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 150 instances (133 error, 11 warning, 6 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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
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 | green (no shape in feed) |
| 八田線 | Bus | green (no shape in feed) |
| 浜坂温泉線 | Bus | green (no shape in feed) |
| 海上線 | Bus | green (no shape in feed) |
| 久斗山線 | Bus | green (no shape in feed) |
| 居組線 | Bus | green (no shape in feed) |
| 春来線 | Bus | green (no shape in feed) |
| 照来循環線［下照来］ | Bus | green (no shape in feed) |
| 照来循環線［上照来］ | Bus | green (no shape in feed) |
| 赤崎循環線［右まわり］ | Bus | green (no shape in feed) |
| 赤崎循環線［左まわり］ | Bus | green (no shape in feed) |
This feed has 169 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
- Error132 instances
Foreign key violation (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: foreign_key_violation · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Missing calendar and calendar date files (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_calendar_and_calendar_date_files · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning169 instances
169 of 169 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)
- Warning132 instances
132 of 132 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
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)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info6 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Validator rule: unknown_file · 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. 2 validator errors to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- 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.
Below the Google and Apple Maps four-week coverage bar. This feed has no service end date, so Maps cannot tell how far ahead it runs. Set a feed_info end date and a calendar that covers at least the next four weeks, then re-export. The feed also carries 133 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 53 / 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 45 / 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/shinonsentown-yumetsubame/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.