Call-prep brief · checked 2026-08-01
BAS.MY Kuching
Grade D · 63.6 / 100
Up 25.0 points since 2026-07-31 (F to D).
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 up 68.0
- Freshness no change
- Rider experience down 15.3
No longer reported since the last check (4 findings):
- Stop time with arrival before previous departure time (flagged by the MobilityData validator). (stop_time_with_arrival_before_previous_departure_time)
- Foreign key violation (flagged by the MobilityData validator). (foreign_key_violation)
- Some scheduled trips move faster between stops than a bus can. (fast_travel_between_consecutive_stops)
- Fast travel between far stops (flagged by the MobilityData validator). (fast_travel_between_far_stops)
This compares feed state. It does not identify who made a change or why.
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.
0 of 0 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.
Add feed_info.txt with feed_start_date and feed_end_date to your export.
feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Effort: Two fields, set once in export settings.
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Effort: A small file for most flat-fare systems.
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
- 0 of 0 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
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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
- The feed contains no fare information.
- Next action
- Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
- 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.data.gov.my/gtfs-static/mybas-kuching
- Last checked
- 2026-08-01
- Service window
- 152 days of service data remain. Last service date 2026-12-31.
- Location
- Sarawak, Malaysia
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.