User Story: Check whether schedule changes provide at least one week of lead time

[owades]

Summary

As a Cal-ITP team member, I want to know whether a given agency has provided at least 7 days' notice for recent schedule changes, so I can understand their compliance with the GTFS Guidelines (draft v3).

As the draft guidelines state, Changes to the base schedule should be published at least one week in advance of every service change.

We are making an effort to automatically measure as much of the GTFS Guidelines as possible, so we can understand very easily where a given agency stands, and what support they need.

Acceptance Criteria

1. I can see an overview of all GTFS schedule changes made in the last month* by the agency, showing:

• The minimum "lead time" in days (if a schedule update was made on a Monday, to go into effect the following Wednesday, that would be a 2-day lead time.
• The average lead time for all updates

2. In implementing User Story: Data structure and/or dashboard to support GTFS Guideline check-level reporting #1688 an analyst/engineer should be able to use the output of this ticket to create the "check" defined as: "All schedule changes in the last month have provided at least 7 days of lead time".

*I wrote "in the last month" above, but we may find a shorter or longer window to be more useful.

Notes

I imagine this is blocked by the schedule pipeline v2, so it would be helpful to confirm with Laurie whether this would be possible post-launch.

Tester [Stakeholder]

1. Scott O

Sprint Ready Checklist

1. • Acceptance criteria defined
2. • Team understands acceptance criteria
3. • Team has defined solution / steps to satisfy acceptance criteria
4. • Acceptance criteria is verifiable / testable
5. • External / 3rd Party dependencies identified