HSLdevcom / transitdata-tripupdate-processor

Generates GTFS-RT TripUpdates from Transitdata source data

HSLdevcom/transitdata-tripupdate-processor Issues

Publish the observed value as the last prediction and lock the stop time event
Closed 3 years ago
Add integration tests
Updated 5 years ago2
Refactor Stop Events to a independent component
Closed 5 years ago6
Enable cancellation of cancellation
Closed 5 years ago
Bug: Read message key from somewhere else than DVJ_ID-property
Closed 5 years ago1
Parse TripId from Cancellation-payload, not from Pulsar message key
Closed 5 years ago
Directions with trip cancellations are in wrong format
Closed 5 years ago1
filter cancellations for trains
Closed 5 years ago
Some cancellations from HSL-Alert-source are not sent forward
Closed 5 years ago3
Refactor: Put more logic to TripCancellationProcessor
Updated 5 years ago
Don't log via-point-filtering as error
Closed 6 years ago1
Remove last symbol from route id when it is a number
Closed 6 years ago3
Filter premature predictions from the feed
Closed 6 years ago1
Don't send old TripUpdates
Closed 6 years ago1
Ack consumed messages only after receiving ack for produced messages
Updated 6 years ago1
Read cancellations from separate topic
Closed 6 years ago
Send cancellations as TripUpdates
Closed 6 years ago
StopTimeEvent timestamps are in wrong time zone
Closed 6 years ago
Make sure StopTimeEvent timestamps are in POSIX time
Closed 6 years ago1
Handle via points in StopTimeUpdates
Closed 6 years ago2
Ensure that arrival time for StopTimeUpdate is not later than the departure time
Closed 6 years ago
Error handling on Pulsar-errors
Closed 6 years ago1
Tripupdates always contain only a single StopTimeUpdate
Closed 6 years ago