Bisbee Bus

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_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   1 of 35 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.

   Estimated effort: A column in stops.txt; your scheduling software likely has it.

2. Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside.

   Some service dates fall outside the date window set in feed_info.txt. feed_info.txt should span every day your service runs, so apps know when the data applies.

   Estimated effort: Two fields in feed_info.txt, or one export setting.

This feed is built with National RTAP's GTFS Builder. Your staff can usually make these changes in the GTFS Builder spreadsheets and republish, and National RTAP's help desk supports that at no cost.