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

Research Request - RT trip diagnostics: thresholds for usable trips #604

Closed
tiffanychu90 opened this issue Jan 11, 2023 · 0 comments · Fixed by #652, #637 or #678
Closed

Research Request - RT trip diagnostics: thresholds for usable trips #604

tiffanychu90 opened this issue Jan 11, 2023 · 0 comments · Fixed by #652, #637 or #678
Assignees
Labels
gtfs-rt Work related to GTFS-Realtime research request Issues that serve as a request for research (summary and handoff)

Comments

@tiffanychu90
Copy link
Member

tiffanychu90 commented Jan 11, 2023

Complete the below when receiving a research request, and continue to add to this issue as you receive additional details and produce deliverables. Be sure to also add the appropriate project-level label to this issue (eg gtfs-rt, DLA).

Research Question

Single sentence description: Exploratory work to find which RT trips have enough usable vehicle positions.

Detailed description:

(1) For each operator, what's the % of RT trip_ids that would remain after those thresholds are used? Make a chart function that takes a single operator. Produce charts for all operators. Is the time or geographic coverage that's driving this excluding of trips? What is the distribution by route? What is a recommended threshold to use?
(2) Using GTFS schedule data, by route_id-shape_id, calculate how many the route_length of each shape_id as a proportion of the longest shape_id. For short trips, do they tend to be 50% of the longest route length? 40% 30%? What is the distribution? Have this handy to inform question 1.

How will this research be used?

Stakeholders & End-Users

Metrics

Data sources

  • Cal-ITP data sources: GCS
    analysis_date = '2023-01-18' --> shared_utils.rt_dates["jan2023"]

  • rt_segment_speeds/longest_shape_segment_{analysis_date}.parquet

  • rt_segment_speeds/segments_route_direction_crosswalk_{analysis_date}.parquet

  • rt_delay/compiled_cached_views/routelines_{analysis_date}.parquet or rt_delay/compiled_cached_views/trips_{analysis_date}.parquet

  • rt_segment_speeds/trip_diagnostics_{analysis_date}.parquet

  • External data sources:

  • Remaining data source questions:

Deliverables:

Notebook(s) with charts/tables to support recommendations

Timeline of deliverables:

@tiffanychu90 tiffanychu90 added the research request Issues that serve as a request for research (summary and handoff) label Jan 11, 2023
@tiffanychu90 tiffanychu90 added the gtfs-rt Work related to GTFS-Realtime label Jan 11, 2023
This was referenced Jan 11, 2023
@amandaha8 amandaha8 mentioned this issue Feb 3, 2023
This was linked to pull requests Feb 17, 2023
@amandaha8 amandaha8 linked a pull request Mar 14, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gtfs-rt Work related to GTFS-Realtime research request Issues that serve as a request for research (summary and handoff)
Projects
None yet
2 participants