Compare stop arrivals

[tiffanychu90]

daskify RT segment speeds

• Continue work for Research Request - stop-to-stop segments, does stop_sequence vary? #648
• with stop-to-stop segments, bring in scheduled stop_times and calculate delay as a stop-level metric (difference in actual vs scheduled stop time)
• with data processing steps being the same for joining vehicle positions to some kind of segments, generalize scripts so that it can take the different params needed to get stop-segment-speeds or route-segment-speeds.
  • use scripts/config.yml to set these parameters to pass through
  • add scripts/Makefile for the order to run scripts
  • steps are very similar from A3_sjoin_vp_to_segments -> A4_valid_vehicle_positions -> A5_calculate_speeds_by_segment_trip
  • use helper and gtfs_schedule_wrangling to assemble schedule tables to get ready for cutting segments
  • route_segments and stop_segments are cut rather differently, and take different inputs. leave these as their own steps
  • use dask.arrays to help speed up arrowizing geometry and attaching to segments
• update catalog.yml, which matches config.yml to get all the parquets from each processing stage

calitp_data_analysis

• update imports from calitp to calitp_data or calitp_data_analysis

[github-actions]

nbviewer URLs for impacted notebooks:

• open_data/check_exported_data.ipynb

[github-actions]

nbviewer URLs for impacted notebooks:

• open_data/check_exported_data.ipynb

[github-actions]

nbviewer URLs for impacted notebooks:

• open_data/check_exported_data.ipynb

[github-actions]

nbviewer URLs for impacted notebooks:

• open_data/check_exported_data.ipynb

[github-actions]

nbviewer URLs for impacted notebooks:

• open_data/check_exported_data.ipynb

[github-actions]

nbviewer URLs for impacted notebooks:

• open_data/check_exported_data.ipynb