Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Epic - GTFS analytics pipeline - stop + operator grains #1232

Open
2 of 3 tasks
tiffanychu90 opened this issue Sep 26, 2024 · 0 comments · Fixed by #1259
Open
2 of 3 tasks

Epic - GTFS analytics pipeline - stop + operator grains #1232

tiffanychu90 opened this issue Sep 26, 2024 · 0 comments · Fixed by #1259
Assignees
Labels
epic Representing research requests - large segments of work and their dependencies gtfs-rt Work related to GTFS-Realtime

Comments

@tiffanychu90
Copy link
Member

tiffanychu90 commented Sep 26, 2024

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 analytics pipeline - stop + operator grains

Summary

  • GTFS digest shows mostly operator and route-direction stats across schedule, speeds, rt vs schedule.
    • The operator section shows GTFS schedule stats + NTD
  • Make concerted effort to develop our tables supporting visualizations in coherent way
    • Additional operator tables (Juan Matute) for work within rt vs schedule (operator grain)
    • Current research on transit bunching rt vs schedule (stop grain)
    • Evan's request for stop map to be included in GTFS digest (stop grain) can be combined with Julian's work related to stops

Tables

operator route-dir stop
schedule operator_ scheduled_stats schedule_stats_by_ route_direction TODO: schedule_stats_by_ stop
segment speeds N/A average_segment_speeds average_speedmap_ segment_speeds N/A
summary speeds TODO? how would we average this if routes are different lengths? would simple average be ok? average_summary_speeds N/A
rt vs schedule rt_v_scheduled_operator rt_v_scheduled_routes TODO: transit bunching work

gtfs_analytics_data

  • Similar to sched_route_direction_metrics: "schedule_route_dir/schedule_route_direction_metrics" and vp_route_direction_metrics: "vp_route_dir/route_direction_metrics", we want
    • sched_stop_metrics: capture any stop-level metric we can calculate (n_trips, n_arrivals, n_routes, n_hours_in_service
    • vp_stop_metrics: transit bunching

Issues

Deliverables

@tiffanychu90 tiffanychu90 added epic Representing research requests - large segments of work and their dependencies gtfs-rt Work related to GTFS-Realtime labels Sep 26, 2024
@amandaha8 amandaha8 linked a pull request Oct 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Representing research requests - large segments of work and their dependencies gtfs-rt Work related to GTFS-Realtime
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants