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 - Route identification over time #924

Closed
tiffanychu90 opened this issue Oct 5, 2023 · 0 comments · Fixed by #986
Closed

Research Request - Route identification over time #924

tiffanychu90 opened this issue Oct 5, 2023 · 0 comments · Fixed by #986
Assignees
Labels
research request Issues that serve as a request for research (summary and handoff)

Comments

@tiffanychu90
Copy link
Member

tiffanychu90 commented Oct 5, 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: We want to identify the same route over time, despite small changes in route_id, route_long_name, route_short_name, and route_description.

Detailed description: Using GTFS schedule routes, we have route_id, route_long_name, route_short_name, and route_description. Once we started aggregating for the month, and even across months, route_id in itself is not that stable (if suffixes change).

How will this research be used?

  • We want some logic implemented to identify similar enough characteristics across the 4 route columns to know that they are indeed the same route.
  • Update this function in portfolio_utils and rt_utils later

Data sources

  • Cal-ITP data sources:
  • Either cached trips data that is already downloaded or mart_gtfs.dim_routes and just grab it all at once
  • Start with {COMPILED_CACHED_VIEWS}trips_{analysis_date}.parquet and concatenate a couple days from shared_utils.rt_dates together

Deliverables:

Notebook, and/or script or function

@tiffanychu90 tiffanychu90 added the research request Issues that serve as a request for research (summary and handoff) label Oct 5, 2023
@csuyat-dot csuyat-dot linked a pull request Dec 19, 2023 that will close this issue
@tiffanychu90 tiffanychu90 linked a pull request Dec 30, 2023 that will close this issue
@tiffanychu90 tiffanychu90 self-assigned this Dec 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
research request Issues that serve as a request for research (summary and handoff)
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants