Scheduled Trips ETL
Consumes this source in its data lineage graph.
Table
Route dimension table. Produced by Data Ingestion.
Owner: Produced by Data Ingestion. · Freshness: Updated when the producing pipeline step is rerun.
Built 2026-06-15 11:52 UTC · Commit e5cf673
flowchart LR src["routes"] src --> c1["Scheduled Trips ETL"] src --> c2["01 - System-Wide OTP Trend"] src --> c3["02 - Mode Comparison"] src --> c4["03 - Route Ranking"] src --> c5["04 - Tract Equity"] src --> c6["05 - Anomaly Investigation"] src --> c7["06: Seasonal Patterns"] src --> c8["07: Stop Count vs OTP"] src --> c9["08: Hot-Spot Map"] src --> c10["09: Incline Investigation"] src --> c11["10: Trip Frequency vs OTP"] src --> c12["11: Directional Asymmetry"] src --> c13["12: Route Geographic Span vs OTP"] src --> c14["13: Cross-Route Correlation Clustering"] src --> c15["14: COVID Recovery Trajectories"] src --> c16["15: Municipal/County Equity"] src --> c17["16: Transfer Hub Performance"] src --> c18["17: Weekend vs Weekday Service Profile"] src --> c19["18: Multivariate OTP Model"] src --> c20["21 - COVID Ridership vs OTP Recovery"] src --> c21["22 - Passenger-Weighted Delay Burden"] src --> c22["23 - Garage-Level Performance"] src --> c23["25 - Ridership Concentration & Equity"] src --> c24["26 - Ridership in Multivariate OTP Model"] src --> c25["27 - Traffic Congestion and OTP"] src --> c26["28 - Weather Impact"] src --> c27["30 - Service Level vs OTP Longitudinal"] src --> c28["31 - Stop Consolidation Candidates"] src --> c29["34 - Ridership Concentration (Pareto)"] src --> c30["44 - Route Population Reach"] src --> c31["45 - Population-Weighted System OTP"] src --> c32["49 - Transit Service & Boardings vs Population Density"] src --> c33["51 - Traffic Signals and OTP"] src --> c34["55 - Road Classification and OTP"] src --> c35["56 - City Centerline and OTP"] src --> c36["57 - Pavement Condition and OTP"]
| Why It Matters | Caveat |
|---|---|
| Primary analytical table used in this page's computations. | Coverage depends on upstream source availability and ETL assumptions. |
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.
Consumes this source in its data lineage graph.