Feed status · checked 2026-09-05
Yonago City Dandan Bus (米子市「だんだんバス」「どんぐりコロコロ」)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Tottori, 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 1 hours ago; last changed 1 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
210 of 210 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
85 of 85 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
Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1.Likely your export tool
Some rows in stop_times.txt leave the timepoint column blank. That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.
⏱ Usually one export setting.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
- 210 of 210 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
- 85 of 85 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 rows in stop_times.txt leave the timepoint column blank.
- Next action
- Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1.
- 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.
Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. · 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 148 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 2974 instances (0 error, 2963 warning, 11 informational).
Service data covers the next 148 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.
This feed has 210 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 | green (no shape in feed) |
| 米子市淀江町巡回バス | Bus | green (no shape in feed) |
| 箕蚊屋巡回バス | Bus | green (no shape in feed) |
| 弓浜巡回バス | Bus | green (no shape in feed) |
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
- Warning2953 instances
Some rows in stop_times.txt leave the timepoint column blank.
That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.
Fix: Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. (Usually one export setting.)
Finding code: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning210 instances
210 of 210 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)
- Warning85 instances
85 of 85 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)
- Warning8 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)
- Info4 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)
- Info3 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)
- Info3 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.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: platform_without_parent_station · 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 148 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 148 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/yonago-city-dandan-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.