About RouteWise Miami

How answers are produced

1. An AI model (Google Gemini) reads your question and decides what to look up, or asks you a clarifying question.
2. A deterministic transit engine does all the work with times: departures, transfer buffers, risk bands, and trip planning (RAPTOR algorithm, up to 2 transfers) over Miami-Dade Transit's published schedule.
3. The AI explains the engine's result in plain English or Spanish. The cards under each answer are rendered directly from the engine output, with sources, so you can check the explanation against them.

What the labels mean

SCHEDULED

From Miami-Dade Transit's published timetable (GTFS). It is not a real-time prediction. Some bus times are interpolated by the agency between timepoints, and the cards mark those as approximate.

LIVE

From Miami-Dade's GTFS-Realtime feed (distributed via Swiftly). Shown only when that feed is connected and responding.

YOU REPORTED (user-provided)

A delay or no-show you told RouteWise about. It is applied only to the trip you described.

SIMULATED

Produced in scenario-testing mode from conditions you entered. It never reflects current conditions.

Risk bands are a fixed rule on the time buffer, not a probability: Comfortable: at least 5 min to spare after walking. Tight: 2–5 min. At risk: under 2 min — any further delay misses it. Missed: you would arrive after the scheduled departure.

Walking times are estimates: straight-line distance × 1.3 at 1.2 m/s, plus 2 minutes to reach a Metrorail or Metromover platform. They don't account for elevators, stairs, crowds, or personal mobility needs.

Data sources

• Miami-Dade Transit static GTFS, from https://www.miamidade.gov/transit/googletransit/current/google_transit.zip. Published file last modified Fri, 31 Jul 2026 20:10:53 GMT, schedule effective 2026-08-03, calendars valid through 2026-11-22. Processed 2026-10-29: 123 routes, 6973 stops, 24285 trips.
• Miami-Dade GTFS-Realtime (trip updates, alerts), listed on the county's Transit Open Data Feeds page. It needs an API key. When the key isn't configured, RouteWise says plainly that answers are schedule-only and can't see disruptions.

Known limitations

• Without live data, RouteWise can't know about current delays, detours, or cancellations unless you report them.
• Places are matched by station, stop, or landmark name. Street addresses are not geocoded.
• The feed has no reliable wheelchair-accessibility data per stop, so RouteWise makes no accessibility claims.
• Coverage is Miami-Dade Transit's feed (Metrorail, Metromover, Metrobus and municipal trolleys included in it). Tri-Rail and Broward/Palm Beach services are not included.
• Dates outside the published schedule window are flagged, because service may differ.
• The AI can still word things imperfectly. Check the cards and sources under each answer, and confirm with posted service information.

Privacy

No accounts, no cookies, and no tracking. The conversation is kept only in your browser tab and sent to the server with each question. The server doesn't store it. Questions are sent to Google's Gemini API to produce answers and are subject to Google's Gemini API terms. Please don't include personal information.