OTP / Delays Analysis Use Case Profile #233
Draft
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.
Add Use Case Profiles Directory with OTP/Delays Analysis Profile
This PR introduces a new documentation structure for TIDES use case profiles by creating the
docs/use-cases/profiles/
directory hierarchy and adding the first profile documentotp_delay_analysis.md
.The OTP/Delays Analysis profile, which received the highest priority vote at the April Contributors Group meeting, provides comprehensive guidance on using TIDES data for transit delay analysis, covering required tables/fields, data relationships, implementation considerations, extension points, and validation approaches.
This documentation helps transit agencies, software developers, and analysts effectively implement standardized delay analysis using TIDES data, based on feedback from transit technologists across multiple agencies through GitHub issue #231.
By contributing to this project, all contributors certify to the Developer Certificate of Origin in CONTRIBUTING.md.