Call-prep brief · checked 2026-09-05
Shizuoka City Ryogochi Koko Bus (静岡市両河内地区ココバス)
Grade B · 85.5 / 100
First check for this agency, so there is no trend yet.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.
What changed since the last check
No category changes since the last check.
Top three 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.
39 of 39 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.
Effort: A column in stops.txt; your scheduling software likely has it.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
146 of 146 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Effort: A default or per-trip field in your export.
Give each route a distinct short or long name.
Two or more routes share the same name. Riders can't tell the routes apart in apps.
Effort: One field per route.
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
- 39 of 39 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
- 146 of 146 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
- Two or more routes share the same name.
- Next action
- Give each route a distinct short or long name.
- 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
Key facts
- Feed URL
- https://api.gtfs-data.jp/v2/organizations/shizuokacity/feeds/ryougouchi/files/feed.zip?rid=current
- Last checked
- 2026-09-05
- Service window
- 298 days of service data remain. Last service date 2027-06-30.
- Feed version
- 2026v2-2026年06月30日 16時19分52秒-西沢ツールver8.30
- Location
- Shizuoka, Japan
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.