Call-prep brief · checked 2026-10-22
Transport Public Ungheni
Grade A · 96.3 / 100
Unchanged since 2026-10-21.
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
Top three things to fix
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
647 of 981 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers 647 of 981 trips, about 66% of them.
Effort: A default or per-trip field in your export.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
6 of 391 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.
Fixing this covers 6 of 391 stops, about 2% of them.
Effort: A column in stops.txt; your scheduling software likely has it.
Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: A quick look at the flagged files.
Riders and need behind these fixes
- Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
- The served-area need overlays cover the United States and Canada, so none of them applies to this feed.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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
- 647 of 981 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
- 6 of 391 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
- Some files contain columns that are not part of the GTFS spec.
- Next action
- Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.
- 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://github.com/UngheniTransport/gtfs/raw/refs/heads/main/ungheni_gtfs.zip
- Last checked
- 2026-10-22
- Service window
- 435 days of service data remain. Last service date 2027-12-31.
- Feed version
- 1.0.30
- Location
- Ungheni, Moldova
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.