Darwin (push feed) not planning platforms as far ahead as previously?

[Brandon Randle]

Hi all,

I've been using the Darwin Push Port feed to analyse how hectic things are at the London terminals - specifically by looking at the (non-public-facing) platforms given to trains and seeing how much they change leading up to their departure. Some days a train from Euston will have its platform decided many hours before departure and won't change, and sometimes it'll jump about pretty considerably before being announced publicly.

I've noticed that since a month or so ago, Darwin seems to be planning nowhere near as far ahead as before - often only announcing platforms for the first time at the same time that they appear on public station boards. Has anybody else noticed this, and was it a deliberate change? I can see how the platform data could be misused to beat the station boards and board trains early at Euston or Waterloo for example! 

[WantStuff]

I don’t use the platform details so can’t really comment, but have you check the NROD data? This will confirm if it is just a Darwin’ism and decide if you need to switch.
If you don’t have the NROD data in a usable format you can see it on Real Time Trains,
e.g. http://www.realtimetrains.co.uk/search/basic/kgx

Regards
Martin

[Rail Delivery Group]

Hi,

Darwin doesn't control when platforms are unsuppressed, this is in the hands of the local station controller and in the case of Euston this will be Network Rail.

Platforms will be included in Darwin sourced originally from the Network Rail timetable. When a train is 'activated' in Darwin (usually at around 0230 on the day it runs) by the local station controller the platform may or may not be updated and is then suppressed until they choose to release it for public consumption. Assuming the station controller doesn't blank the platform it will be included in the Darwin Push Port and LDBSV channels with an appropriate suppression marker (it will not be returned in the public LDB API)

So if everything is functioning as it should Darwin will be tied in to the station board so that platforms are unsuppressed in Darwin only when the local station controller publishes them on the board, so this is expected behaviour.

RDG