You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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
The text was updated successfully, but these errors were encountered:
tiffanychu90
added
epic
Representing research requests - large segments of work and their dependencies
gtfs-rt
Work related to GTFS-Realtime
labels
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
schedule
,speeds
,rt vs schedule
.rt vs schedule
(operator grain)rt vs schedule
(stop grain)Tables
gtfs_analytics_data
sched_route_direction_metrics: "schedule_route_dir/schedule_route_direction_metrics"
andvp_route_direction_metrics: "vp_route_dir/route_direction_metrics"
, we wantsched_stop_metrics
: capture any stop-level metric we can calculate (n_trips, n_arrivals, n_routes, n_hours_in_service
vp_stop_metrics
: transit bunchingIssues
Deliverables
The text was updated successfully, but these errors were encountered: