Quarterly performance metrics Q4 2023 + add speed based delay estimation #947
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
quarterly performance metrics
trip_speeds
, a trip-level summary of speeds, and apply a speeds-based delay metric to thishours = distance / speed
. compare actual speed vs target speed, and the difference of that isdelay_hours
, which can be summed up at the route-level and categorized intoon_shn/intersects_shn/other
delay/reliability
metric is sensitive to whatever we choose for target speeds...do more exploratory work to see what should be chosen / just present speeds, or what