Epic - GTFS Schedule to RT Metrics

[tiffanychu90]

After receiving a research request, use this template to plan and track your work. Be sure to also add the appropriate project-level label to this issue (eg gtfs-rt, DLA).

Epic Information - GTFS Schedule to RT

Summary

• All exploratory and analytics metrics related to linking schedule tables to RT
• Use epic to implement metrics in Prof Greg Newmark's papers
• Potential outputs: an RT version of stop_times, spatial accuracy, how many minutes of scheduled service have RT vp or average number of vp per trip, etc
• Do not use this epic for speed-related work, which is a deep-dive on vehicle positions data

Reviewers [Stakeholders]

• @tiffanychu90
• @edasmalchi
• @amandaha8

Issues

Processing

• 1. Research Request - use vehicle positions near stop as actual_stop_arrival #785
• 2. Feature Request: Consolidate the most upstream GTFS schedule or RT preprocessing in gtfs_funnel #930

Tables

• 1. spatial_accuracy: Research Request - Spatial accuracy metric #820
• 2. rt_stop_times: initial rt_stop_times table #954
• 3. trip-level metrics (spatial accuracy, vp pings per minute, vp completeness metric): Research Request - RT vs Schedule Trip Level Metrics (using vp_usable) #936
• 4. aggregate trip-level to route-direction metrics Research Request - Trip Level to Route Level Metrics  #966

Exploratory

• 1. Research Request - RT v Scheduled Exploratory  #968

[tiffanychu90]

• Closing because exploratory work is captured in Epic - GTFS Digest (exploratory portfolio) #989