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

Handling subsequent trip delay notifications after the first notification is sent #139

Open
binh-dam-ibigroup opened this issue Mar 1, 2021 · 0 comments

Comments

@binh-dam-ibigroup
Copy link
Collaborator

Observed behavior

When a monitored transit trip is reported as delayed by OTP, and the first trip delay notification is sent by OTP middleware, the new "reference" time for the trip is the delayed departure/arrival time. Subsequent trip delays and notifications are calculated based on the new "reference" time. If a transit vehicle recovers from a delay and the change is less than the defined variance, then no notification is sent, and the user could miss their transit trip.

Expected behavior

Notifications should be sent if a transit vehicle recovers from a delay.

Steps to reproduce the problem

TBD

Any special notes on configuration used

NA

Version of otp-middleware and/or OpenTripPlanner if applicable (exact commit hash or branch name)

Latest dev branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant