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

Transitdata-omm-alert-source: Disruption routes data to existing bulletins #36

Open
ahjyrkia opened this issue Apr 5, 2022 · 1 comment · May be fixed by #35
Open

Transitdata-omm-alert-source: Disruption routes data to existing bulletins #36

ahjyrkia opened this issue Apr 5, 2022 · 1 comment · May be fixed by #35

Comments

@ahjyrkia
Copy link
Contributor

ahjyrkia commented Apr 5, 2022

No description provided.

@teemu8655 teemu8655 linked a pull request Apr 5, 2022 that will close this issue
@ahjyrkia ahjyrkia changed the title test ticket Selvitystyö, työmääräarvio: OMMista poikkeusreitti Reittilokiin #385 + Poikkeuspysäkki tilanne #231 Apr 5, 2022
@ahjyrkia ahjyrkia changed the title Selvitystyö, työmääräarvio: OMMista poikkeusreitti Reittilokiin #385 + Poikkeuspysäkki tilanne #231 Transitdata-omm-alert-source and merge data to existing bulletins Apr 5, 2022
@ahjyrkia ahjyrkia changed the title Transitdata-omm-alert-source and merge data to existing bulletins Transitdata-omm-alert-source: Disruption routes data to existing bulletins Apr 5, 2022
@mjaakko
Copy link
Contributor

mjaakko commented Jun 16, 2022

Disruption routes are included in INTERNAL type bulletins instead of PASSENGER_INFORMATION and thus they have different bulletin IDs. It is not possible to add disruption route data to existing bulletins. Maybe internal bulletins should also be stored to the DB?

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

Successfully merging a pull request may close this issue.

2 participants