Research Request - Migrate quarterly performance metrics to v2

[tiffanychu90]

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: Migrate this workflow to produce aggregate service metrics to v2. Also, clean up the logic more so the workflow is simpler to follow.

Detailed description: Why are service hours magnitudes different in aggregate?

• If Q1-Q4 2022 look similar quarter to quarter, then jump when we switch to v2, what is happening?
• Go back to Q3/Q4 2022 and download the v2 versions of those dates and debug

How will this research be used?

What will be achieved or informed? What is the intended impact?

Stakeholders & End-Users

Who is asking the question, and who is the audience?

Metrics

• any specific calculations
• you think will be needed

Data sources

• Cal-ITP data sources:

• External data sources:

• Remaining data source questions:

Deliverables:

Notebook, dashboard, narrative, presentation details.

Timeline of deliverables:

Estimated completion date

[tiffanychu90]

for the most part, this is done. We have some delay calculated now, but will aggregate endpoint delay to operator after other stop segments cutting is fixed (loops, etc).

[tiffanychu90]

• Quarterly metrics #746
• some TODOs related to endpoint delay after running for Q2 2023