RT vs Schedule

[amandaha8]

• Added in schedule gtfs key route_id dir_id time_of_day and offpeak_onpeak columns to routes and trips.
• Separated workstream between routes and trips. Metrics are always generated on a trip level. Routes is calculated with a weighted average and any metrics from trip are deleted before added back in.
• Saved outputs to the correct folder in GCS's rt_v_schedule folders.
• New function that adds in time_of_day in segment_speed_utils based on vp positions instead of schedule. If the trip is only found in vp_usable and not in both vp_usable and schedule, we can determine now the time_of_day based on vp.

[github-actions]

nbviewer URLs for impacted notebooks:

• rt_scheduled_v_ran/07_vp_usable_v3.ipynb
• rt_scheduled_v_ran/scripts/route_aggregation.ipynb

[amandaha8]

@tiffanychu90 Can you tell me if I added too many columns in the group_cols list?

[tiffanychu90]

I think you just need group_cols = ["schedule_gtfs_dataset_key", "route_id", "direction_id"].
I think peak_offpeak and time_of_day are going to force the granularity to be more fine than we want. It'll leave rows like route A - direction 0- AM_peak - peak, route A-direction 0 - Midday-offpeak. which is too granular. We want route A - direction 0 - peak, route A - direction 0 - offpeak, route A - direction 0 - all_day

[tiffanychu90]

• Research Request - RT vs Schedule Trip Level Metrics (using vp_usable) #936
• Research Request - Trip Level to Route Level Metrics  #966