search

peter-mount / opendata

Latest & first public version of my code that monitors the UK Rail Network in real time using Open Data feeds
Other
12 stars 2 forks source link

Some entries for a train are appearing twice #46

Closed peter-mount closed 9 years ago

peter-mount commented 9 years ago

Some trains show an entry duplicated. From issue #33 we have:

image

Here Martin Mill appears twice. For others some entries appear as both a pass and a stop.

This is actually down to Darwin actually sending us multiple entries, and apparently it's a known bug with Darwin. No eta on when this will be fixed other than "the next release".

When I redid the SQL this then appeared, but it's minor on uktra.in. On deparureboards however it can show some weirdness if the boards are being shown. Depending on the entries, the train could either appear cancelled, delayed or even vanish (when it thinks its a pass) or worse shown twice.

So this issue is a marker just to acknowledge the issue but it's not our bug, and showing all of the entries is the safest as then we are keeping in line with the NRE licensing.

External example from the Open Rail Data group:

What we show for the external example: image

In the above example there's another oddity, Linlithgow shows that the train actually stopped there at 07:50 & departed at 07:52, 20 minutes late. However it's showing as cancelled so we show it as bypassing that station at the same time as going through it.

The extra stop icons in the track flow at Glasgow Queen St and Edinburgh also appear to be related, they don't appear on any other train.

For now I'm putting these two down to this issue.

peter-mount commented 9 years ago

A new version of this:RID 201509160824700

image

here signalling meant that CHX & WAE were blocked so train to HGS was started from CST instead.

Problem is that due to 2 entries for LBG due to this bug we still showed LBG in the calling point list even though it was cancelled. It looks like from below LBG should have been a pass.

image

peter-mount commented 9 years ago

Just heard this is due to be fixed in Darwin 3.7 - but no date on when that's due to be released yet.

Ref: https://groups.google.com/d/msg/openraildata-talk/hQ4oRH2hv-Q/PU3oh5ZRCgAJ

peter-mount commented 9 years ago

Just had confirmation that this was resovled in Darwin 3.7 released 2 days ago:

https://groups.google.com/d/msg/openraildata-talk/S2uWcEMPKU8/3fR7X0r5DwAJ