Feed status · checked 2026-07-23
Komono Kamoshika Bus (菰野町 かもしか号)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Mie, 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.
Checked for changes 74 minutes ago; last changed 74 minutes ago.
Measured 4 of 4 score categories from the agency's own feed.
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 9 snapshots.
- 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
Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.
The realtime feed's last update was about 2 hours old when sampled. A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.
⏱ A vendor support ticket; treat it as a feed outage.worth about +50 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
99 of 99 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
61 of 61 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
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.
Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.
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.
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.
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 52 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 9 kinds of issue across 44 instances (0 error, 36 warning, 8 informational).
Service data covers the next 52 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.
1 accessibility depth signal
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (かもしか号1コース 神森福王山線, かもしか号3コース 小島永井線).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Fares are applied to trips.
Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.
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 |
|---|---|---|
| かもしか号1コース 神森福王山線 | Bus | red (no shape in feed) |
| かもしか号2コース 千種根の平線 | Bus | pink (no shape in feed) |
| かもしか号3コース 小島永井線 | Bus | green (no shape in feed) |
| かもしか号6コース 潤田福王山線 | Bus | yellow (no shape in feed) |
| かもしか号7コース 竹永小島線 | Bus | yellow (no shape in feed) |
| かもしか号9コース 神森菰野線 | Bus | gray (no shape in feed) |
This feed has 99 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
13 findings, ordered by severity.
Show every finding
- Error1 instance
The realtime feed's last update was about 2 hours old when sampled.
A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.
Fix: Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish. (A vendor support ticket; treat it as a feed outage.)
Validator rule: scorecard_rt_feed_lapsed
- Warning99 instances
99 of 99 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)
- Warning61 instances
61 of 61 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)
- Warning26 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)
- Warning6 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.)
Validator rule: 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.)
Validator rule: 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 stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some trips serve fewer than two stops.
A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.
Fix: Check the flagged trips in your scheduling software; remove them or restore their missing stops. (Worth a vendor question if it appears often.)
Validator rule: unusable_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Unused trip (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unused_trip' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: unused_trip · 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.)
Validator rule: 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.)
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Validator rule: service_window_outside_feed_period · 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).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: 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
This feed is close to 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 52 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 1 of 61 trips list fewer than two stops. A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist. Check your scheduling export: every trip should list each stop it calls at, in order, with times.
- 1 of 99 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Realtime reliability
The realtime feed responded on 100.0% of 1 checks, with 8646s 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 62 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 70 / 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 87 / 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 50 / 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/komono-kamoshika-bus/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.