Feed status · checked 2026-09-05
Kotoura Town 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 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
306 of 306 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
51 of 51 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
- 306 of 306 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
- 51 of 51 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 6 kinds of issue across 1638 instances (0 error, 1631 warning, 7 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 306 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) |
List every stop
- 二軒屋
- 二軒屋
- 逢束一区公民館前
- 逢束一区公民館前
- 逢束二区公民館前
- 逢束二区公民館前
- 逢束自治公民館前
- 逢束自治公民館前
- あじさい公園
- あじさい公園
- 徳万尻
- 徳万尻
- トライアル
- 徳万
- 徳万
- 浦安駅
- 浦安駅
- 丸尾
- 丸尾
- 東伯中学校前
- 東伯中学校前
- 琴浦町役場本庁舎前
- 琴浦町役場本庁舎前
- 総合公園入口
- 総合公園入口
- 寿団地
- 寿団地
- アプト前
- アプト前
- 農業改良普及所前
- 農業改良普及所前
- 丸尾北口
- 丸尾北口
- 八橋東入口
- 八橋東入口
- 雇用促進住宅前
- 雇用促進住宅前
- 八橋一区
- 八橋一区
- 八橋二区
- 八橋二区
- 八橋三区
- 八橋三区
- 八橋駅入口
- 八橋駅入口
- 八橋六区
- 八橋六区
- 諏訪神社前
- 諏訪神社前
- 八橋七区
- 八橋七区
- ポート赤碕
- ポート赤碕
- 朝日町
- 朝日町
- 亀崎神社前
- 亀崎神社前
- 港町
- 港町
- 東三軒屋公民館
- 東三軒屋公民館
- 三軒屋
- 三軒屋
- 赤碕地区公民館
- 赤碕地区公民館
- 仲之町
- 仲之町
- 西仲町
- 西仲町
- 化粧橋
- 化粧橋
- 琴浦町赤碕分庁舎前
- 琴浦町赤碕分庁舎前
- ＪＡ赤碕支所前
- ＪＡ赤碕支所前
- 赤碕駅
- 赤碕駅
- 診療所前
- 診療所前
- 向原
- 向原
- 緑団地
- 緑団地
- 船上小学校
- 国主
- 国主
- 太一垣
- 太一垣
- 下中村
- 下中村
- 中村橋
- 中村橋
- 上中村
- 光
- 光
- 尾張公民館
- 尾張入口
- 尾張入口
- 安田小学校
- 安田小学校
- 梅田
- 梅田
- 坂ノ上入口
- 坂ノ上入口
- 箆津西口
- 箆津西口
- 箆津
- 箆津
- 箆津東口
- 箆津東口
- 八幡中央
- 八幡中央
- 八幡東口
- 八幡東口
- 下市公園前
- 下市公園前
- 赤碕中学校前
- 赤碕中学校前
- 丸尾入口
- 丸尾入口
- 浦安車庫
- 浦安車庫
- 鈴ヶ野
- 鈴ヶ野
- 文化センター入口
- 文化センター入口
- 浦安駅南口
- 浦安駅南口
- 福祉センター前
- 福祉センター前
- 浦安小学校入口
- 浦安小学校入口
- 上伊勢
- 上伊勢
- 中尾入口
- 中尾入口
- 川東集荷場前
- 川東集荷場前
- 斉尾団地
- 斉尾団地
- 金屋
- 金屋
- 杉下
- 聖郷小学校前
- 上法万
- 上法万
- 上法万中央
- 上法万中央
- 大法
- 大法
- 森藤
- 森藤
- 杉下東口
- 杉下東口
- 平和
- 警察署駅南
- 警察署駅南
- トレーニングセンター前
- トレーニングセンター前
- 西地蔵町
- 西地蔵町
- 地蔵町
- 地蔵町
- 大山町
- 大山町
- 扇町
- 扇町
- 桜ケ丘
- 桜ケ丘
- 東山
- 東山
- 出上
- 出上
- 大石
- 大石
- 佐崎入口
- 佐崎入口
- 今在家
- 今在家
- 中坪入口
- 中坪入口
- 分乗寺
- 分乗寺
- 竹ノ内
- 竹ノ内
- 金屋
- 金屋
- 宮木
- 宮木
- 高岡
- 高岡
- 高岡中央
- 高岡中央
- 山川入口
- 山川入口
- 山川北口
- 山川北口
- 山川
- 山川
- 岸ノ下
- 岸ノ下
- 山川木地
- 山川木地
- 国実
- 国実
- 大父入口
- 大父入口
- 新屋前
- 新屋前
- 大父
- 大父
- 大父南口
- 大父南口
- 平田ヶ平
- 平田ヶ平
- 大父木地入口
- 大父木地入口
- 大父木地
- 大父木地
- 船上山
- 船上山
- 少年自然の家
- 少年自然の家
- 丸尾
- 丸尾
- 金市
- 金市
- 高松
- 高松
- 三保
- 三保
- 倉坂入口
- 倉坂入口
- 東下大江
- 東美好
- 釛
- 釛
- 一ツ屋
- 倉坂
- 下大江
- 下大江
- 美好
- 美好
- カウベルホール前
- カウベルホール前
- 釛
- 釛
- 公文入口
- 公文入口
- 東公文
- and 56 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
- Warning1628 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)
- Warning306 instances
306 of 306 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)
- Warning51 instances
51 of 51 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)
- 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)
- Warning1 instance
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · 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 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
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 79 / 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/kotoura-town-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.