Feed status · checked 2026-07-19
Katori City Loop Bus (香取市循環バス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Chiba, 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 5 hours ago; last changed 5 hours ago.
Measured 3 of 4 score categories from the agency's own feed.
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 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
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
138 of 138 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
88 of 88 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
Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.
Some internal IDs use characters outside the basic text set. These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
⏱ A planned ID change, not a quick text cleanup.worth about +8 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.
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.
Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.
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 285 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 4 kinds of issue across 1489 instances (0 error, 1488 warning, 1 informational).
Service data covers the next 285 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 (香取市循環バス休日周遊ルート, 香取市循環バス山田ルート).
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.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 香取市循環バス山田ルート (pink)
- 香取市循環バス佐原市街地ルート 東側ルート (green)
- 香取市循環バス佐原市街地ルート 西側ルート (blue)
- 香取市循環バス小見川市街地ルート 北西ルート (green)
- 香取市循環バス小見川市街地ルート 南西ルート (blue)
- 香取市循環バス小見川市街地ルート 北東ルート (orange)
- 香取市循環バス北佐原・新島ルート (yellow)
- 香取市循環バス休日周遊ルート (pink)
| Route | Type | Line color |
|---|---|---|
| 香取市循環バス山田ルート | Bus | pink |
| 香取市循環バス佐原市街地ルート 東側ルート | Bus | green |
| 香取市循環バス佐原市街地ルート 西側ルート | Bus | blue |
| 香取市循環バス小見川市街地ルート 北西ルート | Bus | green |
| 香取市循環バス小見川市街地ルート 南西ルート | Bus | blue |
| 香取市循環バス小見川市街地ルート 北東ルート | Bus | orange |
| 香取市循環バス北佐原・新島ルート | Bus | yellow |
| 香取市循環バス休日周遊ルート | Bus | pink |
This feed has 138 stops.
List every stop
- 小見川支所
- おみがわ医療センター
- 南原地
- 山田支所
- 北谷
- 竹之内
- 小見
- JAかとり前
- 新田橋
- 新田橋
- 野田青年館
- 野田青年館
- 小見川中学校下
- 小見川中学校下
- 下小川入口
- カインズ前
- 大割
- 北２丁目
- 北２丁目
- 佐原高校前
- 佐原高校前
- 小見川高校
- 小見川高校
- 田部仲新田
- 橘ふれあい公園
- 佐原駅北口
- 野田
- 丸昇前
- 水の郷さわら（臨時）
- 水の郷さわら（臨時）
- さくら館入口
- さくら館入口
- 稲生大神入口
- 稲生大神入口
- 下小堀
- 下小堀
- 分郷
- 分郷
- 八日市場
- 八日市場
- 中央大橋
- 中央大橋
- 大根塚
- 大根塚
- 千葉銀行小見川支店前
- 小見川海洋センター前
- 小見川団地東
- 小見川団地北
- くろべ運動公園前
- 新町通り
- 南八軒町
- 南八軒町
- 東大根塚
- 東大根塚
- 小見川東
- 小見川東
- 阿玉川
- 谷中踏切前
- 粉名口
- 粉名口
- 篠原西
- 篠原西
- 篠原東
- 篠原東
- 香取駅入口
- 香取駅入口
- 白楊高校前
- 白楊高校前
- 佐原自動車教習所前
- 佐原自動車教習所前
- 粉名口団地入口
- 粉名口団地入口
- コミュニティセンター裏
- コミュニティセンター裏
- 観福寺前
- 観福寺前
- 高野
- 高野
- 橋替
- 橋替
- 橋替団地
- 橋替団地
- 山之辺
- 山之辺
- 玉造２丁目
- 玉造２丁目
- 玉造北公園前
- 玉造北公園前
- 香取神宮
- 水の郷さわら
- 水郷佐原山車会館
- 水郷佐原山車会館
- 忠敬橋
- 忠敬橋
- 東関戸
- 佐原駅
- 諏訪神社
- 牧野
- 牧野
- 県立佐原病院
- 香取市役所
- 寺宿
- 寺宿
- 佐原郵便局入口
- 佐原郵便局入口
- 岩ケ崎東
- 岩ケ崎東
- 岩ケ崎稲荷神社
- 岩ケ崎稲荷神社
- 横利根閘門公園
- 横利根閘門公園
- 横利根閘門公園
- 荒川公会堂
- 笄島南
- 笄島中央
- 笄島北
- 長島消防機庫
- 長島第２
- 八筋川消防機庫
- 八筋川中央
- 八筋川北
- 本津
- 大島
- 三島
- 境島公民館
- 境島東
- 大割公民館
- 扇島第１
- 扇島
- 与田浦
- 中洲橋
- 中洲
- 篠原新田下組
- 篠原新田上組
- 向津
- 砂場水神
- 砂場
- 小見川駅
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
6 findings, ordered by severity.
Show every finding
- Warning1475 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Validator rule: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning138 instances
138 of 138 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)
- Warning88 instances
88 of 88 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)
- Warning10 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)
- Warning3 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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)
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 285 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 285 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 82 / 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 60 / 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/katori-loop-bus/2026-07-19.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-19. 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.