Transport Public Ungheni

What this grade measures

The quality of the schedule data this agency publishes for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

1. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   1254 of 1626 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

   Estimated effort: A default or per-trip field in your export.

2. 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.

   Estimated effort: A quick look at the flagged files.

3. Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra.

   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.

   Estimated effort: A quick look at the flagged file.

This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.