Skip to content

[Realtime] Clarify Trip Update precedence for consumer routing decisions #630

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.

Sign up for GitHub

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

Open
tzujenchanmbd wants to merge 2 commits into
base: master
Choose a base branch
from
Open

[Realtime] Clarify Trip Update precedence for consumer routing decisions #630

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e2baf14
Add interaction between TU and SA
tzujenchanmbd May 4, 2026
92ef0e8
change wording
tzujenchanmbd May 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions gtfs-realtime/spec/en/feed-entities.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,13 @@ A service alert will usually consist of some text which will describe the
problem, and we also allow for URLs for more information as well as more
structured information to help us understand who this service alert affects.

#### Interaction between Trip Updates and Service Alerts

If data consumers use Service Alerts to affect routing decisions, and both Trip Updates
and Service Alerts apply but provide conflicting information, consumers should
give precedence to Trip Updates for routing decisions, unless there is clear
evidence that the Trip Updates is incorrect.

[More about Service Alerts...](service-alerts.md)

## Vehicle Positions
Expand Down
Loading