Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add communication_period and impact_period to GTFS Service Alerts #521

Open
skalexch opened this issue Nov 25, 2024 · 0 comments
Open

Add communication_period and impact_period to GTFS Service Alerts #521

skalexch opened this issue Nov 25, 2024 · 0 comments
Labels
Change: Addition New function proposed to the specification. GTFS Realtime Issues and Pull Requests that focus on GTFS Realtime Status: Discussion Issues and Pull Requests that are currently being discussed and reviewed by the community. Support: Needs Feedback

Comments

@skalexch
Copy link
Collaborator

skalexch commented Nov 25, 2024

Describe the problem

In the GTFS Realtime Alert spec, active_period is defined as: Time when the alert should be shown to the user. If missing, the alert will be shown as long as it appears in the feed. If multiple ranges are given, the alert will be shown during all of them.

However, there still is an ambiguity of interpretation of the active_period field; whether it is intended for the period of showing the alert or for the period of the related service disruption itself.

Use cases

We need to distinguish:

  1. The period when the alert is shown -> Communication period of the alert
  2. The period when the alert is actually in effect -> Impact period of the alert

Proposed solution

We propose the addition of two fields, communication_period and impact_period, to disambiguate active_period.

The detailed proposal is found here: communication_period and impact_period proposal

Additional information

More information regarding the extent of this issue can be found in PR#482

@skalexch skalexch added GTFS Realtime Issues and Pull Requests that focus on GTFS Realtime Status: Discussion Issues and Pull Requests that are currently being discussed and reviewed by the community. Change: Addition New function proposed to the specification. Support: Needs Feedback labels Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Change: Addition New function proposed to the specification. GTFS Realtime Issues and Pull Requests that focus on GTFS Realtime Status: Discussion Issues and Pull Requests that are currently being discussed and reviewed by the community. Support: Needs Feedback
Projects
None yet
Development

No branches or pull requests

1 participant