Time between receiving schedule and the service running.

47 views
Skip to first unread message

Ben Short

unread,
Apr 12, 2018, 9:30:38 AM4/12/18
to A gathering place for the Open Rail Data community
Hi,

What is the expected time between receiving the schedule messages from the STOMP queue and the service actually running? 

Regards

Ben

George Goldberg

unread,
Apr 12, 2018, 9:36:59 AM4/12/18
to Ben Short, A gathering place for the Open Rail Data community
On 12 April 2018 at 14:30, Ben Short <b...@benshort.co.uk> wrote:
What is the expected time between receiving the schedule messages from the STOMP queue and the service actually running?

Anything from a few minutes up to about 48 hours. The reason for this is that late entered changes are sent out "live" as they are entered, and Darwin is aware of planned schedules for "today" and "tomorrow".

--
George
 
 

Ben Short

unread,
Apr 12, 2018, 10:14:27 AM4/12/18
to A gathering place for the Open Rail Data community
Hi George,

So for a base timetable you could expect to get a schedule message 48 hours in advice, like what is in the 20180412020734_v8.xml.gz. Then any updates, or services created on the fly would be pushed as they are entered?

Ben

Allan Blundell

unread,
Apr 12, 2018, 10:26:30 AM4/12/18
to A gathering place for the Open Rail Data community
That is true, however you don't need to download the timetable everyday as it will also be pushed out via the PushPort roughly between 2 and 6AM everyday. 
Reply all
Reply to author
Forward
0 new messages