Burlington Metro Real-Time Bus Tracking and Alerts

Burlington Metro's real-time bus tracking and alert system gives riders live vehicle position data and automated notifications covering delays, detours, and service disruptions across the transit network. This page explains how the tracking infrastructure functions, the scenarios where it delivers the most operational value, and the boundaries riders and planners should understand when interpreting the data it produces. Accurate use of real-time tools reduces missed connections and helps riders adapt quickly when schedules change.

Definition and scope

Real-time bus tracking refers to the continuous, automated reporting of vehicle location and status using onboard GPS transponders and a supporting data pipeline that feeds public-facing interfaces. For Burlington Metro, this system covers fixed-route service across all active lines listed in the Burlington Metro Routes and Lines directory.

The scope of the tracking system includes:

• Vehicle position — GPS coordinates updated at intervals typically between 15 and 30 seconds, transmitted from each active bus to a central dispatch feed
• Predicted arrival times — algorithm-generated estimates that factor in current position, historical travel-time patterns, and known traffic conditions
• Service alerts — structured notifications pushed when a route is detoured, a stop is temporarily closed, or a vehicle is removed from service mid-run

The Burlington Metro Service Alerts and Detours page handles disruption-specific communications, while the tracking system described here produces the underlying position and timing data that alert systems draw upon.

Paratransit and demand-responsive services operate under a separate dispatch model and are not covered by the fixed-route real-time feed. Riders using those services should consult Burlington Metro Paratransit Options for scheduling protocols specific to that service category.

How it works

The technical architecture behind real-time tracking follows a 3-layer model common to mid-sized transit agencies in the United States:

1. Onboard AVL unit — An Automatic Vehicle Location device mounted in each bus records GPS coordinates and transmits positional data over a cellular or radio network to the agency's operations center. Most modern AVL units achieve positional accuracy within 5 to 10 meters under open-sky conditions.

2. Data aggregation and prediction engine — The agency's back-end server receives raw position pings and applies schedule-matching logic to estimate arrival times at downstream stops. Prediction algorithms weight recent speed and dwell time against historical patterns for the same route and time window. The General Transit Feed Specification Realtime (GTFS-RT) format, maintained by Google Transit and broadly adopted by agencies following the MobilityData open standard, is the most widely used protocol for packaging and distributing this data.

3. Public interfaces — Processed data flows to rider-facing surfaces: the Burlington Metro Mobile App, stop-level electronic displays where installed, and third-party transit applications that consume the agency's GTFS-RT feed. Riders planning a trip can also use the Burlington Metro Trip Planning tool, which integrates real-time arrival data alongside static schedule information.

A key distinction exists between scheduled time and predicted time. Scheduled time is the static timetable value published in the Burlington Metro Bus Schedules reference. Predicted time is dynamically recalculated as the vehicle moves and may differ from the schedule by 2 minutes or more during peak congestion or following a service disruption.

Common scenarios

Understanding when real-time data is most and least reliable helps riders make better decisions.

High-value scenarios:

• Pre-departure monitoring — A rider at home or work can watch a bus approach the nearest stop on the mobile app and time departure accordingly, reducing wait time at the stop itself.
• Transfer timing — On a multi-leg trip, real-time arrival data for the connecting route allows the rider to assess whether a transfer will succeed before committing to a boarding decision. Burlington Metro Express Routes with less frequent headways particularly benefit from this.
• Detour identification — When a service alert is triggered for construction or an emergency road closure, the real-time feed immediately reflects the bus's new path, and stop predictions are recalculated for the modified route geometry.

Lower-reliability scenarios:

• Tunnel or parking structure segments — GPS signal loss of 30 seconds or more can cause position data to lag, making predictions temporarily stale.
• First departure of the day — Before an AVL unit has transmitted enough data points for the prediction engine to calibrate, arrival estimates carry higher uncertainty.
• Severe weather — Ice, flooding, or high winds that affect road speeds faster than historical patterns can absorb produce systematically optimistic arrival predictions until the engine recalibrates.

Decision boundaries

Riders and agency staff should apply clear rules about when to rely on real-time data and when to fall back on scheduled information.

Rely on real-time predictions when:
- The bus is within 3 stops of the boarding location and the prediction confidence indicator in the app shows a normal status
- The route has not been flagged with an active detour alert

Fall back to the static schedule when:
- The app displays "Scheduled" rather than "Real-Time" next to an arrival time — this label means the AVL feed for that trip is unavailable and the system is showing timetable data only
- A major service disruption is in effect and the detour geometry has not yet been mapped into the prediction system (typically the first 10 to 20 minutes after a reroute is activated)
- The bus has not yet departed its origin terminal, making all downstream predictions schedule-derived rather than GPS-derived

The Burlington Metro homepage provides the primary entry point for checking live system status, including whether real-time feeds are operating normally across all routes. Riders who encounter persistent tracking errors or missing data can find resolution pathways through Burlington Metro Frequently Asked Questions.

Real-time tracking data is supplementary to the published schedule, not a replacement for it. The static timetable, accessible via Burlington Metro Bus Schedules, remains the authoritative reference for planned service and the basis against which on-time performance is measured.

References

• MobilityData — GTFS Realtime Reference
• Federal Transit Administration — AVL and Automatic Passenger Counters Overview
• U.S. Department of Transportation — Open Government Data and GTFS Standards
• Transit Cooperative Research Program (TCRP) — Report 173: Improving Transit Data Quality