Reliability
On-time share and bus spacing by route, stop and hour of day.
“Which hours have the most late arrivals on route 15?”
From RTD GTFS schedules and GTFS-Realtime
Ask about Denver-area bus and rail service in plain English. WhyLine writes the SQL, shows it to you before it runs, and gives you a table, chart or map to download. Free and open source.
Each topic is a line on the map. Ask within one, or ask a question that rides across several.
On-time share and bus spacing by route, stop and hour of day.
“Which hours have the most late arrivals on route 15?”
From RTD GTFS schedules and GTFS-Realtime
How on-time performance shifts on days with rain or snow.
“Do snowy days lower on-time performance on route 0?”
From NOAA daily observations at Denver International Airport
Reported traffic crashes within 250 meters of each stop.
“Which stops have the most crashes nearby?”
From Denver Open Data crash records
Where weak service overlaps with neighborhoods that rely on transit, and how much sidewalk is near each stop.
“Which high-need stops have the least sidewalk around them?”
From U.S. Census ACS 2023 and Denver’s sidewalk inventory
Nothing runs until you’ve seen the query.
Type a question, or pick a ready-made one. Date, route and stop filters narrow it down.
WhyLine writes the query and shows it to you. Edit it if you like. Only read-only queries on approved tables can run.
See the result as a table, chart or map. Download it as CSV, or download a whole table.
SELECT route_id, AVG(pct_on_time) AS avg_pct_on_time
FROM mart_reliability_by_route_day
WHERE service_date_mst >= DATE_SUB(CURRENT_DATE, INTERVAL 30 DAY)
GROUP BY route_id
ORDER BY avg_pct_on_time ASC
LIMIT 10Read these before you quote a result.
Reliability comes from sampled realtime observations, not every scheduled arrival. Treat on-time shares as estimates.
Realtime data is collected through the day, but the dashboard reads a nightly snapshot. It’s not a live arrivals board.
Crashes near a stop don’t mean transit caused them. Census figures describe areas, not individual riders.
WhyLine Denver is not an official RTD or City of Denver service. Read the metric definitions
Public sources, collected on a schedule and joined in one warehouse.
No. Open the dashboard and start asking.
It’s built from RTD’s public feeds, but WhyLine Denver is an independent project, not an RTD service.
No. WhyLine is for looking at how service has performed. It has no trip planner, live arrivals, passenger counts, fares, crowding or service alerts.
It’s sent to Google’s Gemini service to write the SQL. Our logs keep only a one-way hash of it, not the text, and your browser remembers your last question and query until you clear them. The privacy policy has the details.
Yes. Download any result, or a whole table, as CSV. The code is MIT-licensed on GitHub. Check each source’s terms before redistributing its data.