Open machow opened 3 years ago
add to this list (or maybe a part 2) for level of delay
cal-itp/data-infra#232 seems related to this too / seems to duplicate some of what is in cal-itp/data-infra#205
@holly-g Looking into this a bit more, wanted to note that:
To expand on last comment, re: cal-itp/data-analyses#260 -- the "what" (goal) described relates to GTFS RT data (checking how far in advance GTFS RT predictions are useful/needed). But the proposed "how" (method) laid out in the issue body refers to actually conducting an analysis on the schedule data (what are the typical gaps between services at the same stop & what is the frequency of services) which would then be used to inform that RT analysis.
So that issue as currently written is a bit hard to categorize - perhaps should be split out into two issues, one (perhaps that existing issue) for the initial GTFS Schedule analysis and a second (perhaps new) issue for the subsequent RT work?
cc @holly-g
I appreciate the enthusiasm of looking into various issues like this. This particular issue is tagged as "epic" which the author of this issue liked to use to contain information about large tasks that could have numerous subcomponents to them. Also, in the greater scheme of things, this issue is rather old and not something I'd like to prioritize until the GTFS-RT pipeline is built out completely. So this is blocked by cal-itp/data-infra#221.
To go over with @chriscardillo next week, to sanity check the views we are creating. Below is a list of many questions which have been asked of GTFS RT data.
Depencies
These questions all depend on the availability of a built-out RT pipeline which is being tracked in:
Issues
Misc
Metrics proposed from the outcomes section of this doc