Feed status · checked 2026-09-05
Nichinan Town Tattamo 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
258 of 258 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
59 of 59 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
- 258 of 258 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
- 59 of 59 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 7 kinds of issue across 1970 instances (0 error, 1963 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 258 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 8 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
- Warning1958 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)
- Warning258 instances
258 of 258 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)
- Warning59 instances
59 of 59 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)
- Warning2 instances
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)
- 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 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)
- 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 75 / 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/nichinan-town-tattamo-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.