Create SIRI rides report

[cjer]

This Epic defines the steps required for reaching the final goal of creating a bus trip report on SIRI trips in comparison to GTFS trips.

This has two main motivations: (a) we need a common ground for all our SIRI analyses and comparisons to GTFS, given SIRI noisy data, (b) we want to find recurring issues and "bugs" in SIRI data, in order to know how to work with them and hopefully work with MOT on improving them.

• [x] Define a SIRI trip? #174
• [x] Get the necessary data to identify SIRI trip #182 #183 #184
• [ ] Create function for identifying SIRI trips, and tagging them with valuable information (fullness, route correct label, route deviation, actual departure time, etc.) #173
• [ ] Create a SIRI trip table using function (also export in GTFS format)
• [ ] Join SIRI trips to GTFS trips
• [ ] Create a daily report which summarizes SIRI trips and compares them to GTFS
• [ ] Analyze long term trip trends (create notebook and blog post)

[EyalBerger]

Looks great!

I think that between steps 2 & 3 we will need to add a small step of building a siri2trip_index function. We also will need to build parallel function for GTFS.

As for the third step, we will need to define priorities (fullness & route correct label will be our first goal in my opinion)

[AvivSela]

we (me and Dan) talked about it yesterday evening. let's change the term "SIRI trip" to "SIRI ride". More about the differences in #174