Feed status · checked 2026-09-05
Tottori City 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 2 hours ago; last changed 2 hours ago.
Measured 4 of 4 score categories from the official feed URL on file.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 3 snapshots.
- 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
262 of 262 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
144 of 144 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
- 262 of 262 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
- 144 of 144 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
- One or more realtime feeds were reachable; live-arrival coverage is not known.
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 4002 instances (0 error, 3992 warning, 10 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.
Sampled 3 times: 1 of 1 configured feed healthy; vehicle position plausibility was not measurable.
Routes and stops
This feed has no route shapes, so the map shows its stops only.
This feed has 262 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) |
| くる梨青コース | 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) |
List every stop
- 丸由百貨店前
- 太平線
- 太平線
- 南町
- 鹿野橋
- 川端四丁目
- 茶町
- 鹿野町公園前
- 西町五丁目
- とりぎん文化会館
- 市民会館前
- 片原二丁目
- 鹿野町
- 片原五丁目
- 出合橋
- 大森公園前
- 相生町
- マルイ薬師町店前
- 城北高校前
- 新茶屋
- 富桑体育館前
- 富桑小学校前
- 南公園
- 寿町
- 行徳口
- 行徳二区
- 常忍寺前
- 聖神社北門前
- 行徳公園入口
- 行徳公園入口
- 今町
- 市役所前
- 今町二丁目
- 今町一丁目
- ＪＡ会館前
- 末広温泉町
- 生協病院前
- 鳥取市文化センター
- 内吉方
- 吉方町一丁目
- 山の手会館前
- 御弓町
- 中町
- 樗谿公園やまびこ館前
- 上町
- 大榎町
- 江崎町
- 鳥取赤十字病院
- 掛出町
- 寺町
- ＮＴＴ寺町・ＮＨＫ前
- 弥生橋
- 生協病院入口
- 永楽温泉町
- 瓦町
- 川端三丁目
- 元魚町二丁目
- 本町三丁目
- 福祉文化会館前
- わらべ館
- 裁判所前
- 仁風閣・県立博物館
- 市立武道館
- 鳥取県庁
- 本町一丁目
- 職人町
- 戎町
- パレットとっとり前
- 鳥取市移住・交流情報ガーデン前
- 市営駐輪場前
- さざんか会館
- ふれあい会館
- 鳥取駅南口
- 年金事務所前
- ふれあい会館
- 浪花団地入口
- 福部未来学園
- 福部未来学園
- 福部町総合支所
- 駅前
- ＪＲ福部駅
- 栗谷
- 南田
- 蔵見公民館
- 上南田
- 中村
- 久志羅
- 左近
- 採石場前
- 八重原
- 箭渓
- 宮ノ口
- 高江
- 細川口
- 細川
- 細川下
- 岩戸口
- 鳥取城跡
- 渡辺美術館
- 砂丘センター展望台
- 砂の美術館前
- 砂の美術館前
- こどもの国
- 鹿野町総合支所前
- 鹿野町総合支所前
- 鬼入道
- 二ツ家
- 法楽寺
- 日ノ丸鹿野営業所
- 日ノ丸鹿野営業所
- 鍛冶町
- 鍛冶町
- 立町
- 立町
- 上町
- 上町
- トレセン前
- 今町
- 今市
- 今市
- 山紫苑前
- 山紫苑前
- 越路ヶ丘
- 湯花団地
- 下石公民館
- 大工町
- 南川
- 南川
- 古仏谷
- 小別所
- 来日
- 鷲峰
- 矢原
- 毛古屋
- 滑石
- 公民館前
- 支所前
- 河内
- 上殿
- 下殿
- 上飯里
- 飯里
- 上原
- 田仲口
- 上睦逢
- 睦逢
- 郡家
- 高江
- 八幡
- 新町１丁目
- 新町１丁目
- 浜村警察
- エスマート前
- エスマート前
- 新町２丁目
- 新町２丁目
- 気高町総合支所
- 気高町総合支所
- 浜村温泉
- 浜村駅
- 浜村中央
- 浜村中央
- 矢口
- 矢口
- 宝木
- 宝木駅
- 宝木小学校
- 宝木小学校
- 常松
- 下光
- 大杉
- 上光
- 上光
- 上光公民館前
- 上光公民館前
- 塚手
- 塚手
- 広木
- 広木
- 閉野
- 出合橋南
- 上宿
- 土居
- 重高
- 瑞穂小学校
- 下坂本公民館
- 下坂本
- 高浜団地
- 浜村小学校前
- 下原新田
- 姫路公民館
- 船磯下
- 船磯東
- 姫路
- 姫路
- 桑原上
- 桑原
- 澄水
- 楠根
- 診療所前
- 紙屋
- 田原谷
- 八葉寺入口
- 不動滝入口
- 不動滝入口
- 鳴滝
- 北河原
- 川積
- 亀尻
- 城山団地
- 谷田
- 青谷中学校前
- 史跡公園東
- 史跡公園
- 青谷駅口
- 青谷駅
- 青谷駅
- 商工会館前
- 商工会館前
- ようこそ広場前
- ようこそ広場前
- 総合支所前県道
- 総合支所前県道
- 青谷小学校
- 青谷町総合支所
- 小畑上
- 小畑
- 河原
- 和紙工房前
- 山根
- 早牛
- 蔵内
- 大坪上
- 大坪
- 奥崎上
- 奥崎
- 奥崎
- 奥崎下
- 善田
- 平田前
- 鳥取バスターミナル
- 鳥取バスターミナル
- 砂丘会館（鳥取砂丘）
- 賀露神社前
- かにっこ館前
- 気高中学校前
- ビジターセンター
- オアシス広場
- 明徳小学校前
- 明徳小学校前
- and 12 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
- Warning3980 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)
- Warning262 instances
262 of 262 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)
- Warning144 instances
144 of 144 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)
- 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)
- Info5 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)
- Info4 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.
Realtime reliability
The realtime feed responded on 100.0% of 8 checks over the last 1 day, with 31s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
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 100 / 100
- 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/tottori-city-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.