Cancellation map - what it's showing

[whole diary]

[grahame]

We have another,,,, would it be Weston Milton?

An additional train service has been planned to operate as shown 09:30 Weston Milton to Bristol Temple Meads due 10:00.

It probably was ... I have added Weston Milton to the terminations our maps know about.

[grahame]

There seems to be some problems with the JourneyCheck feeds at present - they're sometimes correct and at other times saying there are on cancellations or changes when we know that there are.   It look to me as if there's a problem with one of a series of parallel back-office servers feeding out zeros rather than real data.

An unfortunate consequence, as well as Journey Check failures, is that out map at the top left is sometimes saying "n o problems" when it should be reporting issues.   As far as I can tell, the problem does NOT effect the feed that I'm using for "next departure" links at the top of these pages.

[grahame]

Additional service - 22:08 Parson Street to Bristol Temple Meads.   Map didn't know where Parson Street was and guessed it was somewhere near the Fastnet Rock.  I have told out server otherwise, however ...

There seems to be some problems with the JourneyCheck feeds at present - they're sometimes correct and at other times saying there are on cancellations or changes when we know that there are.   It look to me as if there's a problem with one of a series of parallel back-office servers feeding out zeros rather than real data.

An unfortunate consequence, as well as Journey Check failures, is that out map at the top left is sometimes saying "n o problems" when it should be reporting issues.   As far as I can tell, the problem does NOT effect the feed that I'm using for "next departure" links at the top of these pages.

That problem still persists and I'm pretty sure it's at "their" end ... as I have tried multiple locations and multiple methods to get the data, including manual browsing, and they all exhibit the issue.

[Southernman]

Additional service - 22:08 Parson Street to Bristol Temple Meads.   Map didn't know where Parson Street was and guessed it was somewhere near the Fastnet Rock.  I have told out server otherwise, however ...

There seems to be some problems with the JourneyCheck feeds at present - they're sometimes correct and at other times saying there are on cancellations or changes when we know that there are.   It look to me as if there's a problem with one of a series of parallel back-office servers feeding out zeros rather than real data.

An unfortunate consequence, as well as Journey Check failures, is that out map at the top left is sometimes saying "n o problems" when it should be reporting issues.   As far as I can tell, the problem does NOT effect the feed that I'm using for "next departure" links at the top of these pages.

That problem still persists and I'm pretty sure it's at "their" end ... as I have tried multiple locations and multiple methods to get the data, including manual browsing, and they all exhibit the issue.

Certainly get that issue as well!

[grahame]

Langley and Iver added to our train start and end locations for the cancellation map at the top of these pages - sorry about the misleading lines to the Fastnet Rock a few minutes ago!

[grahame]

Langley and Iver added to our train start and end locations for the cancellation map at the top of these pages - sorry about the misleading lines to the Fastnet Rock a few minutes ago!

And this morning we have a train failing to start at Cam & Dursley ... also added to the map!

[rogerw]

Cam & Dursley only required because of the Gloucester closure this week

[grahame]

Cam & Dursley only required because of the Gloucester closure this week

Indeed. But also because even having made changes to the timetables to cope with engineering works, further changes are being made on the morning to cope with other problems too!

[grahame]

14:45 Mortimer to Basingstoke due 15:02
Additional 14:45 Mortimer to Basingstoke due 15:02 has been delayed at Mortimer and is now 23 minutes late.
This is due to a broken down train earlier today.

Mortimer added to map!

[TonyK]

Has someone drawn a nit comb on the map?

[grahame]

Has someone drawn a nit comb on the map?

It's the effect of crude offsetting where multiple services on a flow are to mapped; it effects service between points that are diagonally offset from each other (SW, NW, SE, NE) rather than between points above / below or left / right of each other (N, S, E, W).

[TonyK]

Has someone drawn a nit comb on the map?

It's the effect of crude offsetting where multiple services on a flow are to mapped; it effects service between points that are diagonally offset from each other (SW, NW, SE, NE) rather than between points above / below or left / right of each other (N, S, E, W).

Of course, silly me. 

[TonyK]

It's getting bigger!

[grahame]

22:50 London Paddington to Worcestershire Parkway Hl due 01:06
Facilities on the 22:50 London Paddington to Worcestershire Parkway Hl due 01:06.
Will be formed of 5 coaches instead of 9.

I will tell our "applet" where WOP is ... in. few minutes ... currently showing at Fastnet Rock - sorry.

EDIT TO ADD^▸ (Automatic Dropping Device) ... fixed:

For newcomers to this thread and our map, it shows trains that are cancelled, running short, or have formation of other changes as currently notified on Journey Check. The "Train Running" link shown just below the map on our pages will take you to journey check so that you can "knife and fork" through data for your area.

For simplicity, the lines shown on the map are drawn as the crow flies for the entire journey - so very much diagrammatic!  Lines thickened where multiple services concerned. It's a great way to spot quickly if there are issues in or near your area - looking at the example above, Devon and Cornwall clean except for one Plymouth / London service.  Couple of modified services to  / from Cardiff - Westbury and London.  Few problems on the North Cotswold by the look of it, and something going on with Reading / Didcot / Oxford / Banbury.   No "blue-out" catastrophes.

Readers please bear in mind that a "service change" can be anything from a delay of a few minutes to a cancellation and (for those who have been around for many years) that the reason it can look far worse than it used to is that this modern electronic age brings news from far places to our eyes where 20 years ago we wouldn't  have known, living in Wiltshire, that there was a problem at Paignton ...

[GBM]

As we've read on this thread, it can also be notoriously incorrect at times as well as changes are not always updated as the day goes on (or has that problem been addressed perhaps?).