Call-prep brief · checked 2026-08-01
Owari Asahi Asapy-go (尾張旭市営バス あさぴー号)
Grade C · 71.9 / 100
Up 3.2 points since 2026-07-31 (D to C).
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
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality up 15.9
Top three things to fix
Ask your AVL vendor to publish updates at least every 20 seconds (the Caltrans guideline).
Realtime data was up to 428 seconds old when sampled. Stale positions and predictions are worse than none: riders watch a bus that already left.
Effort: A vendor configuration question.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
169 of 169 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.
76 of 76 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.
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
- Realtime data was up to 428 seconds old when sampled.
- Next action
- Ask your AVL vendor to publish updates at least every 20 seconds (the Caltrans guideline).
- 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
- 169 of 169 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
- 76 of 76 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
Key facts
- Feed URL
- https://api.gtfs-data.jp/v2/organizations/owariasahicity/feeds/communitybus/files/feed.zip?rid=current
- Last checked
- 2026-08-01
- Service window
- 121 days of service data remain. Last service date 2026-11-30.
- Feed version
- 2026/04/01改正-見える化ver2.6e
- Location
- Aichi, Japan
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.