National Routeing Guide update

[FenMan]

Easement removed

700235: Customers travelling from Alton, Bentley, Farnham, Aldershot and Ash Vale to or via Fleet may double back between Brookwood and Woking. This easement applies in both directions.​

​

I don't know if this means that they were only interested in shortish journeys (i.e. ones not as far as Basingstoke, which is still a routeing point), or if there's something else there which duplicates it for those journeys.

Well, if passengers from Aldershot to, say, Southampton are now barred from going to Woking to pick up a fast service then their journey times would be badly affected. Until now, there's a decent hourly connection at Woking with an end to end journey time of 1h15m, which is reasonable. If they're only permitted to travel to Brookwood then the same journey would take 1h37m.

For reference, Google Maps reports the same journey by car would take 55 minutes.

Given that (1) SWT are the sole operator for both legs of this journey, and (2) fares from Aldershot etc to points west of Basingstoke are more expensive than equivalent fares where Woking is the origin, I'm not sure what is being attempted here, apart from making travel by train significantly less attractive.

 

[Paul Kelly]

When Cross Country services are diverted vi Romsey on route to Weynmouth a Journey Planner system is currently confusing the routeing; in that when doubleback easement 30263 is applied the doubleback is stripped out of the route check and therefore for journeys beyond Brockenhurst from Origins not on a direct train are failing. The solution is to add a map link between ROM and BCU. This will be removed once the diversions are concluded.

Map changed

Map RM - ROUTES VIA READING TO MANCHESTER changed (1 added links)​

I don't know which journey planner it refers to, but it seems badly broken and it stands to reason that such a bug in its routeing guide implementation would affect lots of other journeys in other parts of the country as well - surely special hacks shouldn't be being put into the routeing guide for this, rather any TOCs who use that journey planner should be demanding that it's fixed and claiming damages for lost revenue due to passengers being unable to book valid itineraries on it!

Easement 30263 only affects journeys from and to Redbridge, so I can only assume that a new easement will be added for longer distance journeys before Crosscountry go to Weymouth.

The electronic version of easement 30263 doesn't require Redbridge to be the origin or the destination of the journey, so it also applies to journeys that pass through there (it is a compulsory timing point, so will show up in all schedules).

And if we're going to be hacking the routeing guide to allow journeys to Weymouth on the diverted CrossCountry trains via Romsey, what about Reading to Weymouth? None of the maps for that journey allow you to take that route, so journey planners force you onto a replacement bus between Basingstoke and Winchester instead. E.g. search for a journey from Reading to Weymouth tomorrow evening at 20:45; you'll be given a journey with 3 changes including a bus, when there is in fact a perfectly good itinerary available with a single change in Southampton (or Brockenhurst or Bournemouth).

 

[embers25]

Well, if passengers from Aldershot to, say, Southampton are now barred from going to Woking to pick up a fast service then their journey times would be badly affected. Until now, there's a decent hourly connection at Woking with an end to end journey time of 1h15m, which is reasonable. If they're only permitted to travel to Brookwood then the same journey would take 1h37m.

For reference, Google Maps reports the same journey by car would take 55 minutes.

Given that (1) SWT are the sole operator for both legs of this journey, and (2) fares from Aldershot etc to points west of Basingstoke are more expensive than equivalent fares where Woking is the origin, I'm not sure what is being attempted here, apart from making travel by train significantly less attractive.

This is a massive inconvenience to lots of people and due to Woking barrier staff complaining about it. I thought easements couldn't be removed if they make journeys worse? It's been removed not for the reason they state but because Ash Vale fares are normally MUCH cheaper than Woking ones and SWT don't like it but can't do anything other than this as Ash Vale ones are usually set by GWR.

 

[infobleep]

This is a massive inconvenience to lots of people and due to Woking barrier staff complaining about it. I thought easements couldn't be removed if they make journeys worse? It's been removed not for the reason they state but because Ash Vale fares are normally MUCH cheaper than Woking ones and SWT don't like it but can't do anything other than this as Ash Vale ones are usually set by GWR.

To get from Clapham Junction to Poole during evening peak rush hour there are no direct services. One must travel to Woking on a stopping service.

Alternatively one can travel via Waterloo but that's more expensive. Perhaps South West Trains would prefer the same to apply to passengers who wish for faster journey via Woking.

Of course for that to happen, wouldn't South West Trains need to petition to have a higher fare via Woking available. Then you could get a faster service if you pay more.

It may be that they feel there is nothing wrong with passengers spending an extra 22 minutes travelling. Perhaps they could run an advertising campaign on how passengers must not travel via Woking any more and your journeys have just got slower. I'm sure it would be popular. Lol.

 

[embers25]

To get from Clapham Junction to Poole during evening peak rush hour there are no direct services. One must travel to Woking on a stopping service.

Alternatively one can travel via Waterloo but that's more expensive. Perhaps South West Trains would prefer the same to apply to passengers who wish for faster journey via Woking.

Of course for that to happen, wouldn't South West Trains need to petition to have a higher fare via Woking available. Then you could get a faster service if you pay more.

It may be that they feel there is nothing wrong with passengers spending an extra 22 minutes travelling. Perhaps they could run an advertising campaign on how passengers must not travel via Woking any more and your journeys have just got slower. I'm sure it would be popular. Lol.

I thought removing/adding easements that made journeys previously possible much harder required DfT approval? Also with such a big change as this one they should put up some publicity as it is likely to catch many out.

I also love the ridiculous reason they gave for removing it when we all know it's because Woking barrier staff complained people were using them to travel to Woking as the fare to Woking is so much more expensive. Rather than fix the MASSIVE fare anomally that is Woking where SWT add a huge supplement to almost all tickets compared to fares to surrounding stations they'd rather keep ripping us off and make journeys more inconvenient.

 

[infobleep]

I thought removing/adding easements that made journeys previously possible much harder required DfT approval? Also with such a big change as this one they should put up some publicity as it is likely to catch many out.

I also love the ridiculous reason they gave for removing it when we all know it's because Woking barrier staff complained people were using them to travel to Woking as the fare to Woking is so much more expensive. Rather than fix the MASSIVE fare anomally that is Woking where SWT add a huge supplement to almost all tickets compared to fares to surrounding stations they'd rather keep ripping us off and make journeys more inconvenient.

Of course perhaps GWR are under charging? I don't know.

 

[embers25]

Of course perhaps GWR are under charging? I don't know.

True but this overcharging applies to SWT set fares too where Woking is way more expensive than Guildford or Brookwood or Clapham. One reason is because Woking is a railhead for Heathrow. Also by pumping up Woking fares and keeping all those around lower they can claim that they increased fares less as it's only 1 fare and yet they make larger profits as more people use that fare. Other TOC's do this at some stations but Woking is extreme.

 

[kieron]

surely special hacks shouldn't be being put into the routeing guide for this, rather any TOCs who use that journey planner should be demanding that it's fixed and claiming damages for lost revenue due to passengers being unable to book valid itineraries on it!

I think it's reasonable for Crosscountry to take steps to limit the cost and inconvenience of this problem for their customers when a problem arises, however it happens.

The electronic version of easement 30263 doesn't require Redbridge to be the origin or the destination of the journey, so it also applies to journeys that pass through there (it is a compulsory timing point, so will show up in all schedules).

Does it at least mention Bournemouth? For that matter, does 700516 (the "local" version of this easement) specify stations? I had wondered why it was quite hard to find a route which wasn't valid with a double-back through Redbridge.

And if we're going to be hacking the routeing guide to allow journeys to Weymouth on the diverted CrossCountry trains via Romsey, what about Reading to Weymouth?

I suspect a TOC (not necessarily Crosscountry) received a complaint, and have done what it takes to address that complaint. The wider issue can wait, maybe until after the engineering works finish.

Incidentally, there are only 3 maps (SW, WU and XR) which have a route from Basingstoke to Brockenhurst via Winchester and Southampton, but don't have one via Romsey. This seems pretty remarkable to me given the lack of trains on that route. Unfortunately, Reading-Weymouth relies on XR for its route via Southampton.

 

[Paul Kelly]

Does it at least mention Bournemouth? For that matter, does 700516 (the "local" version of this easement) specify stations? I had wondered why it was quite hard to find a route which wasn't valid with a double-back through Redbridge.

30263 doesn't no; it applies equally well to a journey from Totton to Romsey as to one from Weymouth to Reading.

700516 requires Brockenhurst to be in the itinerary - but that's OK as it's not needed for journeys from Beaulieu Road, Ashurst or Totton to Redbridge via Southampton, as in that case the "through trains to and from common routeing point rule" will apply (although easement 30263 still applies here).

Local journeys from Brockenhurst and stations west thereof to Redbridge have Brockenhurst as their common routeing point, so the local easement 700516 will be needed to justify the longer journey via Southampton and the doubleback easement 30263 needed to justify the doubleback.

 

[kieron]

I'd noticed that NRE didn't feel it was only valid to catch a train which called at Redbridge when going from Totton to Romsey. This only happens in that direction and I haven't been able to reproduce it on any other booking engine, so there could be something else going on.
--- old post above --- --- new post below ---
Some more changes were made yesterday.

new dataset RJRG0401 published 04 March 2016

A review of Warwick Group Routeing Point permissions has resulted in the following changes.

Map sequence added

BIRMINGHAM GROUP (G02) and WARWICK GROUP (G73) - added sequence 'BH'
SMETHWICK GROUP (G63) and WARWICK GROUP (G73) - added sequence 'BH'
WALSALL GROUP (G59) and WARWICK GROUP (G73) - added sequence 'BH'

Map sequences removed

BIRMINGHAM GROUP (G02) and WARWICK GROUP (G73) - removed sequence 'BI'
SMETHWICK GROUP (G63) and WARWICK GROUP (G73) - removed sequence 'BI'
WALSALL GROUP (G59) and WARWICK GROUP (G73) - removed sequence 'BI'​

These removes the mapped routes via Stratford-upon-Avon.

Coventry (COV) and STAFFORD GROUP (G65) - added sequence 'SM+BJ'
Coventry (COV) and STAFFORD GROUP (G65) - removed sequence 'TL'​

This removes the mapped routes via Stoke and adds some via Birmingham.

STAFFORD GROUP (G65) and WARWICK GROUP (G73) - added sequence 'WM'
STAFFORD GROUP (G65) and WARWICK GROUP (G73) - removed sequence 'TL+BB'​

This removes the mapped routes via Rugeley, to leave only ones via Wolverhampton.

WARWICK GROUP (G73) and Rugeley Trent Valley (RGL) - added sequence 'BH+BP'
WARWICK GROUP (G73) and Rugeley Trent Valley (RGL) - removed sequence 'BB+TL'
WARWICK GROUP (G73) and Rugeley Trent Valley (RGL) - removed sequence 'WM+BP'​

This removes all of the mapped routes via Stratford-upon-Avon, via Lichfield and via Wolverhampton.
This includes the shortest rail-only route from Warwick to Rugeley Trent Valley, which goes via Leamington, Coventry, Nuneaton and Lichfield.

It states on the National Rail web site that the distance by foot between Birmingham Moor Street and Birmingham New Street is 240 metres long. There's no reference to this journey in the National Rail Timetable, so I have not considered it further.

On an unrelated note, the sole remaining mapped route goes via Birmingham and Walsall.

WARWICK GROUP (G73) and Lichfield Trent Valley (LTV) - removed sequence 'MW+TL'​

This removes all of the mapped routes via Rugeley or via Nuneaton. These again include the shortest rail-only route (also via Leamington, Coventry and Nuneaton).
There are a number of mapped routes left via Birmingham, however.

WARWICK GROUP (G73) and Tyseley (TYS) - added sequence 'BH'
WARWICK GROUP (G73) and Tyseley (TYS) - removed sequence 'WM'
WARWICK GROUP (G73) and Wolverhampton (WVH) - added sequence 'BH'
WARWICK GROUP (G73) and Wolverhampton (WVH) - removed sequence 'BI'​

Thes remove mapped routes via Stratford-upon-Avon group, to leave only routes via Dorridge.

WARWICK GROUP (G73) and Tamworth (TAM) - removed sequence 'MW'​

This removes mapped routes via Stratford-upon-Avon group, and also ones which use the direct route from Birmingham New Street to Tamworth.
The shortest rail-only route remains a mapped route on BB+TL.

Due to the closure of Glasgow Queen Street High Level tunnel from the 21 March 2016, some serrvices will start from the Low Level platforms and pass the Springburn Routeing Point to then rejoin the normal routeing. To accomodate this change the following maps have been amended to provide a link between the Springburn and Westerton Routeing Points.

Map changed

Map EG - EDINBURGH TO GLASGOW LOCAL ROUTES changed (1 added/ 0 removed links)
Map FW - GLASGOW AREA TO FORT WILLIAM changed (1 added/ 0 removed links)
Map GF - ROUTES BETWEEN GLASGOW AND FALKIRK changed (1 added/ 0 removed links)
Map SR - STRATHCLYDE LOCAL SERVICES changed (1 added/ 0 removed links)​

There are a lot of service changes connected with this closure, with (for example) direct trains between Bishopbriggs and Springburn, but I haven't found any evidence of trains which travel between Westerton and Springburn without passing through the routeing points at Ashfield, Hyndburn, Partick or Glasgow Queen Street en route.

Map sequence added

Fort William (FTW) and Springburn (SPR) - added sequence 'FW'​

This adds a few routes involving the Westerton-Springburn link referred to above.

During to Engineering works affecting the route at Stafford to Crewe, the following easements have been published. It also led to a change in map permissions as itemised below

Easement added

700626: During the closure of the line between Stafford and Crewe over the weekend of the 25-28 March 2016, customers for Wilmslow will be permitted to travel via Stoke on Trent and Stokport, and then from Stockport to Wilmslow. This positive map easement will apply in both directions


700627: During engineering works over the Easter weekend of the 25 - 28 March, permitted routes to Wilmslow have been amended to allow travel via Stockport. However that will involve journeys passing through Cheadle Hume twice. Normally journey planners would deny these journeys due to the repeated location being shown in timetable data. This positive doubleback easement will resolve this problem and will apply in both directions.​

The National Rail web site, for one, doesn't normally deny journeys like this Wilmslow via Stockport. These easement may have been created to allow something which was already permitted.

Map sequence added

STAFFORD GROUP (G65) and WILMSLOW GROUP (G69) - added sequence 'BV+MC'
STAFFORD GROUP (G65) and WILMSLOW GROUP (G69) - added sequence 'EM+OP'

Map sequence removed

STAFFORD GROUP (G65) and WILMSLOW GROUP (G69) - removed sequence 'MH'​

This removes mapped routes via Manchester.
It adds ones via Crewe.

For engineering works that will close the route via Newbury the following easement of the Via Newbury Fare route has been published,

Easement added

700628: During engineering works over the weekend of the 14 and 15 May 2016, tickets on fare route 00063 VIA NEWBURY to the West Country will be valid on journeys via Swindon. This easement applies in both directions.​

I don't know what tickets you get with this fare route, but I feel "to the West Country" is vague enough for it to apply to all of them anyway.

 

[kieron]

A new version of the Routeing Guide was released today.

New dataset RJRG0402 published 18 March 2016

To accomodate routine train service diversions for engineering works, the following map sequence change has been made.

Map sequence added

LONDON GROUP (G01) and GLASGOW GROUP (G13) - added sequence 'LM+IN+GO'​

This adds lots of routes via Newton-Mount Florida-Glasgow.

Review of Slough Routeing Point has resulted in the following amendments.

Map sequence added

Feltham (FEL) and Slough (SLO) - added sequence 'WU+WR'​

This adds a mapped route via Windsor.

Ascot (Berks) (ACT) and Slough (SLO) - added sequence 'XR+BL'

Map sequence removed

Ascot (Berks) (ACT) and Slough (SLO) - removed sequence 'WX+RG'​

This removes mapped routes via London.
I haven't checked the stations related to these routeing points, but Ascot-Slough tickets are sold with a route of either "+Any Permitted" or "via Windsor", the latter costing less.
"Via Windsor" tickets are only valid on the shortest route from Ascot to Windsor, and then from Windsor to Slough.
"+Any Permitted" tickets are also valid via Reading (the route via Windsor isn't on any maps, but it is valid as a "route not listed in the Routeing Guide for which a lower priced route specific fare exists". The tickets were also valid via London, but this is no longer the case.

Review of the Weymouth and Brockenhurst Routeing Points has resulted in the following changes

Map sequence added

SOUTHAMPTON GROUP (G26) and Taunton (TAU) - added sequence 'BW+WE'​

No effect.

WEYMOUTH GROUP (G33) and Salisbury (SAL) - added sequence 'EU'​

This adds a mapped route via Yeovil, to go with the existing ones via Bournemouth. The added route would be the shortest route if the national timetable listed a distance between Yeovil Pen Mill and Yeovil Junction. As only Table 160 lists both stations, and this doesn't give a distance to or from Yeovil Pen Mill, it's less clear which route is the shortest.

Brockenhurst (BCU) and Taunton (TAU) - added sequence 'BW+WE'

Map sequence removed

Brockenhurst (BCU) and Taunton (TAU) - removed sequence 'SS'​

This removes mapped routes via Portsmouth, and ones via Romsey and Exeter.

Review of the use of maps has resulted in the following changes

Map sequence added

Chester (CTR) and Runcorn (RUN) - added sequence 'BJ'
Chester (CTR) and Runcorn (RUN) - added sequence 'CP'

Map sequence removed

Chester (CTR) and Runcorn (RUN) - removed sequence 'CH+CV'​

This adds mapped routes via Huyton.

Loughborough (Leics) (LBO) and Tamworth (TAM) - added sequence 'NM+WS'
Loughborough (Leics) (LBO) and Tamworth (TAM) - removed sequence 'BG+TL'​

No effect.

Review of map permissions in Yorkshire has resulted in the following changes

Map sequence added

Grantham (GRA) and Selby (SBY) - added sequence 'ED+YL'
Grantham (GRA) and Selby (SBY) - added sequence 'GH'

Map sequence removed

Grantham (GRA) and Selby (SBY) - removed sequence 'ER+HL'
Grantham (GRA) and Selby (SBY) - removed sequence 'GS'​

This removes mapped routes via Leeds and via York.
It adds mapped routes via Gilberdyke.

HALIFAX GROUP (G39) and Guide Bridge (GUI) - added sequence 'MR'
HALIFAX GROUP (G39) and Guide Bridge (GUI) - added sequence 'TP'
HALIFAX GROUP (G39) and Guide Bridge (GUI) - removed sequence 'MS'​

This removes mapped routes via Stockport.
It adds ones via Leeds, and ones using the direct route between Stalybridge and Guide Bridge (which is, co-incidentally, only served by trains from Stockport) where the route also goes via Huddersfield.

HUDDERSFIELD GROUP (G40) and Guide Bridge (GUI) - added sequence 'GU+BM'
HUDDERSFIELD GROUP (G40) and Guide Bridge (GUI) - added sequence 'MR'
HUDDERSFIELD GROUP (G40) and Guide Bridge (GUI) - removed sequence 'MS'
HUDDERSFIELD GROUP (G40) and Guide Bridge (GUI) - removed sequence 'WK+MR'​

This removes mapped routes via Stockport.
It adds ones via Rochdale.

LEEDS GROUP (G16) and Grantham (GRA) - added sequence 'GG'
LEEDS GROUP (G16) and Grantham (GRA) - added sequence 'GY+GH'
LEEDS GROUP (G16) and Grantham (GRA) - removed sequence 'LS+GS'​

This removes mapped routes:
via Pontefract;
via South Milford and York; and
via Sherburn-in-Elmet and York, but not via Harrogate.
It adds some:
via Gilberdyke; and
via Wakefield and Lincoln.

PONTEFRACT GROUP (G22) and Guide Bridge (GUI) - added sequence 'TP'
PONTEFRACT GROUP (G22) and Guide Bridge (GUI) - removed sequence 'WY+MR'
PONTEFRACT GROUP (G22) and Stalybridge (SYB) - removed sequence 'WK'
AKEFIELD GROUP (G30) and Guide Bridge (GUI) - added sequence 'TP'
WAKEFIELD GROUP (G30) and Stalybridge (SYB) - added sequence 'TP'
WAKEFIELD GROUP (G30) and Stalybridge (SYB) - removed sequence 'WY'​

No effect.

Carlisle (CAR) and York (YRK) - removed sequence 'MG+MN'​

This removes mapped routes via Manchester.

Review of map permissions from North East England to Scotland (removing circuitous routes via Manchester)

Map sequence removed

Bellgrove (BLG) and SCARBOROUGH GROUP (G48) - removed sequence 'GO+MG+MN'
Carstairs (CRS) and SCARBOROUGH GROUP (G48) - removed sequence 'MG+MN'
Carstairs (CRS) and York (YRK) - removed sequence 'MG+MN'
Crianlarich (CNR) and SCARBOROUGH GROUP (G48) - removed sequence 'FW+EG+MG+MN'
Dalmuir (DMR) and SCARBOROUGH GROUP (G48) - removed sequence 'FW+EG+MG+MN'
Darlington (DAR) and EDINBURGH GROUP (G11) - removed sequence 'MT+MG'
Darlington (DAR) and GLASGOW GROUP (G13) - removed sequence 'MT+MG'
EDINBURGH GROUP (G11) and MIDDLESBROUGH GROUP (G42) - removed sequence 'MG+MT'
EDINBURGH GROUP (G11) and Newcastle (NCL) - removed sequence 'MG+MN'
EDINBURGH GROUP (G11) and SCARBOROUGH GROUP (G48) - removed sequence 'MG+MN'
EDINBURGH GROUP (G11) and York (YRK) - removed sequence 'MG+MN'
Fort William (FTW) and SCARBOROUGH GROUP (G48) - removed sequence 'FW+EG+MG+MN'
GLASGOW GROUP (G13) and SCARBOROUGH GROUP (G48) - removed sequence 'GK+MG+MN'
GLASGOW GROUP (G13) and SCARBOROUGH GROUP (G48) - removed sequence 'MG+MN'
SCARBOROUGH GROUP (G48) and DUMBARTON GROUP (G80) - removed sequence 'MN+MG+EG+FW'
SCARBOROUGH GROUP (G48) and Hyndland (HYN) - removed sequence 'MN+MG+GO'
SCARBOROUGH GROUP (G48) and Kilmarnock (KMK) - removed sequence 'MN+MG'
SCARBOROUGH GROUP (G48) and Kilmarnock (KMK) - removed sequence 'MN+MG+GK'
SCARBOROUGH GROUP (G48) and Kilwinning (KWN) - removed sequence 'MN+MG+GO'
SCARBOROUGH GROUP (G48) and MOTHERWELL GROUP (G67) - removed sequence 'MN+MG'
SCARBOROUGH GROUP (G48) and Mount Florida (MFL) - removed sequence 'MN+MG+GO'
SCARBOROUGH GROUP (G48) and Newton Lanark (NTN) - removed sequence 'MN+MG'
SCARBOROUGH GROUP (G48) and Paisley Gilmour Street (PYG) - removed sequence 'MN+MG+GO'
SCARBOROUGH GROUP (G48) and Partick (PTK) - removed sequence 'MN+MG+GO'
SCARBOROUGH GROUP (G48) and Pollokshaws West (PWW) - removed sequence 'MN+MG+KK'
SCARBOROUGH GROUP (G48) and Port Glasgow (PTG) - removed sequence 'MN+MG+GO'
SCARBOROUGH GROUP (G48) and Springburn (SPR) - removed sequence 'MN+MG+SG'
SCARBOROUGH GROUP (G48) and TROON GROUP (G81) - removed sequence 'MN+MG+AG'
SCARBOROUGH GROUP (G48) and Westerton (WES) - removed sequence 'MN+MG+WN'​

In each case, these remove all of the mapped routes via Manchester.

Journey Planners are failing to find services from Lockerbie to Euston when services are routed via Stoke on trent due to failing the fares check. A routeing point easement has been required to resolve this incident.

Easement added

700629: Journeys from Lockerbie to London are failing the NFM64 Fares Check when the journey includes travel via Stoke On Trent. this positive routeing point easement will enable journey planners to show these journeys. The easement applies in both directions.​

There are also easements between Lockerbie and Carstairs, Motherwell, Edinburgh and Milton Keynes. There are plenty of other places without one, however.

To prevent journeys via Oxford Parkway from Worcester to London

Easement added

700630: Journeys to and via London Marylebone on fare routes AP EVESHAM (00402); CHILTERN & CONNECTIONS (00402); EVESHAM/STROUD (00803) and VIA EVESHAM (00805) are not permitted to travel via Oxford and Oxford Parkway. This negative easement applies in both directions.​

Just looking at Worcester-London fares, this covers all of the Great Western fares, to leave only "via Birmingham", "via High Wycombe & Birmingham" and "London Midland only" tickets. There are no mapped routes via High Wycombe, and it isn't on the shortest Worcester-London route.

I don't know if ATOC have confirmed what a traveller should do in the situation where a route restriction involving two locations is not on any permitted route between origin and destination, but Oxford Parkway is on mapped routes from Worcester to High Wycombe, and from Birmingham to High Wycombe.

Due to service plan diversions because of the Glasgow Queen Street High Level closure, journey planners arre denying services due to repeat locations in the timetable data for journeys via Glasgow Queen street (Low Level platforms)

Easements added

700631: During the closure of the Glasgow Queen Street High Level Tunnel between the 20 March and 08 August 2016, services are diverted from their normal routes. Journey planners are failing to find services via Glasgow Queen Street due to journey plans including Anniesland as a repeated station in the journey. This doubleback easement will resolve this incident and will apply in both directions.


700632: During the closure of the Glasgow Queen Street High Level Tunnel between the 20 March and 08 August 2016, services are diverted from their normal routes. Journey planners are failing to find services via Glasgow Queen Street due to journey plans including Bellgrove as a repeated station in the journey. This doubleback easement will resolve this incident and will apply in both directions.​

Or "Passengers can double back between Glasgow Queen Street and Anniesland and between Glasgow Queen Street and Bellgrove between 20/3 and 8/8". I don't know on which routes passengers are likely to benefit from this, though.

To resolve incident with journey planners unable to display services from Rainham (Kent) to Pitlochery

Easement added

700633: Fares checking rules are preventing journey planners finding services from Rainham (Kent) via Gillingham to Pitlochery. To resolve this incident this positive routeing point easement will apply in both directions.​

Fare checking rules don't allow it because there are no prices for Rainham-Pitlochry tickets. The same applies to journeys between most stations in Kent and either Pitlochry and Blair Atholl.

Deletions - engineering works completed

Easement removed

700605: Due to engineering works the London bound platform at Roydon (Essex) will be closed between 02 January 2016 and 28 February 2016. this positive local easement will allow journeys to Roydon from the Cambridge direction to doubleback between Roydon and Broxbourne. The platform for journeys toward Cambridge is not affected by these works, and therefore this easement applies in only the London bound direction.​

All in the past now.

 

[Merseysider]

The Chester to Runcorn changes have no effect. Permitted routes were via Liverpool or via Crewe. Originally on one map, the two routes have now been split onto two different maps.

 

[kieron]

Some more updates were released yesterday (Wednesday), but ATOC haven't yet provided a summary of them.

The changes from 18/3/16 to 23/3/16 are:

Bletchley to Wolverhampton gain EB+WM lose EB
London Group to Wolverhampton gain EB+WM
Milton Keynes Central to Wolverhampton gain EB+WM lose EB
Watford Junction to Wolverhampton gain EB+WM lose EB​

No effect.

PO: Gain Birmingham Group to/from Walsall Group​

This map already contained Walsall-Rugeley Trent Valley (as well as Wolverhampton-Walsall), but I haven't looked into the effects of this change.

 

[kieron]

A few more easements were added or removed today.

New Dataset RJRG0404 published 01 April 2016

Easements removed - time expired engineering diversions

700603: Due to engineering works the London bound platform at Roydon (Essex) will be closed between 02 January 2016 and 28 February 2016. This positive local easement will allow journeys in the London direction from Roydon to or via Broxbourne to doubleback between Roydon and Harlow Town. The platform for journeys to Roydon from London is not affected by these works, and therefore the easement applies in only the London bound direction

700610: Due to flood damage, sleeper services to Aberdeen, Inverness and Fort William during January 2016 are subject to diversions in Scotland. This map easement will aid journey planners find journeys and will apply in both directions.

700612: During Engineering works on Sundays 7 and 28 February and 06,13, 20, 27 March 2016 the line between Radley, Didcot and Tilehurst will be closed. Services will use the diversionary route via Newbury. This map easement will allow Customers travelling with tickets on Fare Routes ANY PERMITTED (00000), Via EVESHAM (00805), Via AP EVESHAM (00433), Via LONDON/EVESHAM Fare (00799), Via EVESHAM/STROUD Fare Route (00803), Via LONDON/STROUD/EVESHAM (00827), on journeys that would normally only be permitted to travel along the closed route to travel via Bristol, Swindon, Chippenham and Newbury to and via Reading. This easement will apply in both directions

700613: During engineering works on Sundays 7 and 28 February and 06,13, 20, 27 March 2016 the line between Radley, Didcot and Tilehurst will be closed. Customers travelling on journeys that would normally be routed on this closed line using tickets on Fare Route NOT VIA READING (00810) may do so to utilise bus rail replacement services. This easement applies in both directions.

700626: During the closure of the line between Stafford and Crewe over the weekend of the 25-28 March 2016, customers for Wilmslow will be permitted to travel via Stoke on Trent and Stokport, and then from Stockport to Wilmslow. This positive map easement will apply in both directions

700627: During engineering works over the Easter weekend of the 25 - 28 March, permitted routes to Wilmslow have been amended to allow travel via Stockport. However that will involve journeys passing through Cheadle Hume twice. Normally journey planners would deny these journeys due to the repeated location being shown in timetable data. This positive doubleback easement will resolve this problem and will apply in both directions.​

All temporary easements which have now expired, as stated.

Easement amended - New dates

700608 During engineering works on Sundays 08, 15, 22 and 04 June 2016, affecting the line between Romsey & Warminster, journeys on the route between Portsmouth and South Wales using fare routes 00618 VIA SALISBURY and 00837 VIA WESTBURY & SALISBURY will be valid for journeys via Reading. This easement applies in both directions.​

This had said "13 & 14 February 2016; 08 May 2016 and 15 May 2016", so this may reflect the work taking longer than originally planned. The first 3 dates aren't Sundays, so the person who wrote this may have intended to refer to May at some point.

 

[kieron]

Some more updates were published yesterday.

New dataset RJRG0405 published 13 April 2016

As part of a review of Routeing Groups the following amendment to the Derby Group has been made.

Routeing groups changed

DERBY GROUP (G09) has removed member: Peartree (PEA)​

If anyone is wondering, Peartree is a station in the suburbs of Derby which lies on the lines from Derby to Stoke-on-Trent and to Tamworth, but is only served by a small number of trains on the line to Stoke-on-Trent.

This means that this change does not create a route between Tamworth and Stoke which doesn't go through an intermediate routeing point (not that any maps show this anyway).

I don't think it prevents you from using mapped routes via Tamworth, Derby and Stoke either, simply because I don't think there are any mapped routes like that.

It does mean that someone travelling from Peartree to Tamworth (and beyond) can go via Derby, even when not using the shortest route. Peartree-Ancaster via Grantham is right out, though. At least, it is based on the output of ATOC's routeing point calculator and the distance tables in the national rail timetable.

Review of permissions to Swindon the following changes have been made. Adding permissions via Evesham.​

The only journey in the following section I could see with valid routes via Evesham is Worcester-Swindon. This is an addition, at least.

Map sequence added

BIRMINGHAM GROUP (G02) and Swindon (Wilts) (SWI) - added sequence 'RW'

Map sequence removed

BIRMINGHAM GROUP (G02) and Swindon (Wilts) (SWI) - removed sequence 'RB'​

This removes all of the mapped routes via Nuneaton, except for ones which go via Reading and London.

Bromsgrove (BMV) and Swindon (Wilts) (SWI) - added sequence 'BC+RW'​

This adds mapped routes via Birmingham, to go with the existing ones via Cheltenham.

SMETHWICK GROUP (G63) and Swindon (Wilts) (SWI) - added sequence 'MW'
SMETHWICK GROUP (G63) and Swindon (Wilts) (SWI) - removed sequence 'BI+MW'​

No effect.

WORCESTER GROUP (G35) and Swindon (Wilts) (SWI) - added sequence 'CB+BB'
WORCESTER GROUP (G35) and Swindon (Wilts) (SWI) - added sequence 'LH+BB'
WORCESTER GROUP (G35) and Swindon (Wilts) (SWI) - removed sequence 'CE'​

This adds routes via Didcot; some via Birmingham, and some via Evesham.
It removes the ones via Bromsgrove and Cheltenham.

Review of permissions from Hastings and Tonbridge the following changes have been made; creating permissions via Otford and reducing/harmonising maps used to describe map permissions.

Map sequence added

Beckenham Junction (BKJ) and Sevenoaks (SEV) - added sequence 'VH'
BROMLEY SOUTH GROUP (G06) and Sevenoaks (SEV) - added sequence 'VH'
Sevenoaks (SEV) and Shortlands (SRT) - added sequence 'VH'

Map sequence removed

Beckenham Junction (BKJ) and Sevenoaks (SEV) - removed sequence 'FO'
Beckenham Junction (BKJ) and Sevenoaks (SEV) - removed sequence 'FS'
Beckenham Junction (BKJ) and Tonbridge (TON) - removed sequence 'VA'
BROMLEY SOUTH GROUP (G06) and Sevenoaks (SEV) - removed sequence 'FO'
BROMLEY SOUTH GROUP (G06) and Sevenoaks (SEV) - removed sequence 'FS'
Crystal Palace (CYP) and HASTINGS GROUP (G15) - removed sequence 'VA'
Crystal Palace (CYP) and Sevenoaks (SEV) - removed sequence 'VA'
Crystal Palace (CYP) and Tonbridge (TON) - removed sequence 'VA'
Sevenoaks (SEV) and Shortlands (SRT) - removed sequence 'FO'
Sevenoaks (SEV) and Shortlands (SRT) - removed sequence 'FS'​

No effect.

BROMLEY SOUTH GROUP (G06) and HASTINGS GROUP (G15) - added sequence 'VH'
BROMLEY SOUTH GROUP (G06) and HASTINGS GROUP (G15) - removed sequence 'HC'
BROMLEY SOUTH GROUP (G06) and Tonbridge (TON) - added sequence 'VH'
BROMLEY SOUTH GROUP (G06) and Tonbridge (TON) - removed sequence 'FS'
HASTINGS GROUP (G15) and Shortlands (SRT) - added sequence 'VH'
HASTINGS GROUP (G15) and Shortlands (SRT) - removed sequence 'HC'
Shortlands (SRT) and Tonbridge (TON) - added sequence 'VH'
Shortlands (SRT) and Tonbridge (TON) - removed sequence 'FS'​

These add mapped routes via Otford.

Engineering works easements

Easement added

700634: During engineering works on Sunday 24 April 2016 the line between Radley, Didcot and Tilehurst will be closed. Customers travelling on journeys using tickets on Fare Route NOT VIA READING (00810) may travel via Reading. This easement applies in both directions.​

And to think that it was only a couple of weeks ago that the last easement which allowed "not via Reading" tickets to be used via Reading was removed...

700635: During engineering diversions from 15 May 2016 when evening services via York to Leeds are diverted through Church Fenton and Castleford, this positive map easement will allow journeys from beyond York to Leeds follow a permitted route. This easement will apply in both directions​

As the 22:30 from York to Manchester goes this way 6 days a week, it's probably a good thing that this is already a mapped route for journeys which only go as far as York.

And, for that matter, journeys which end up somewhere between York and Edinburgh.

Easements removed - time expired

700606: During weekend engineering works, from the 09 January 2016 to 03 April 2016, journeys to Cardiff from stations on the line to Ebbw Vale will need to go via Newport (S Wales). This positive Local easement will permit a doubleback between Pye Corner and Newport (S Wales). This easement applies in both directions​

And so it goes. Oddly enough, 700607 is still there.

 

[MKB]

I need to get from Northampton to Nuneaton late tomorrow (Saturday) evening, and I was surprised that the only available route at that time (via Coventry) is not actually a permitted route according to the booking engines. Is this a mistake?

 

[Romilly]

MKB - which trains were you looking at for tomorrow?

 

[sonic2009]

I need to get from Northampton to Nuneaton late tomorrow (Saturday) evening, and I was surprised that the only available route at that time (via Coventry) is not actually a permitted route according to the booking engines. Is this a mistake?

I don't think this is a mistake the last LM Trent Valley service from Rugby to Nuneaton is 1942 on a Saturday evening, so after this time the journey planner must automatically send journeys via Coventry, where the last train from Coventry to Nuneaton departs at 2142.

But i agree with you that its not a permitted route according the the routeing guide.

 

[infobleep]

Could they introduce easements that allow travel on particular timed services so that people could use services that otherwise they wouldn't want them to travel on?

Sent from my SM-G925F using Tapatalk

 

[bb21]

Could they introduce easements that allow travel on particular timed services so that people could use services that otherwise they wouldn't want them to travel on?

Yes they can.

 

[Paul Kelly]

Yes they can.

Well I hope not; there haven't been any of those types of easements added for many years - possibly because they are incredibly difficult for electronic journey planners to deal with. It seems like a reasonable route anyway; would be better in my opinion if it was permitted permanently.

 

[furlong]

Could they introduce easements that allow travel on particular timed services so that people could use services that otherwise they wouldn't want them to travel on?

I don't think those would constitute valid easements in terms of the National Routeing Guide. (And the system is quite complicated enough already!)

13. The route you are entitled to take
(a) You may travel between the stations shown on the ticket you hold in:
...
(iii) trains which take the routes shown in the National Routeing Guide.

First you find the routes available for the ticket you hold, then you select trains that follow those routes. Several problems with journey planners can be traced to the way they tend to search for trains first (for performance reasons) and then only check routes afterwards, while the contract is specified the other way around.

Time and train restrictions are covered by

12. Restrictions on when you can travel

which of course makes no reference to the NRG.

 

[All Line Rover]

I need to get from Northampton to Nuneaton late tomorrow (Saturday) evening, and I was surprised that the only available route at that time (via Coventry) is not actually a permitted route according to the booking engines. Is this a mistake?

Many (MANY) questionable changes have been made to permitted routes to/from Trent Valley stations, Northampton and Milton Keynes. Until such time as they are rectified, I recommend travelling on whichever route you consider to be a reasonable route (whether that involves a change at Rugby and Nuneaton or Tamworth, or a change at Coventry, or a change at Birmingham New Street). You will not encounter any problems with guards, because guards, unlike ATOC, actually apply some common sense when considering whether a route is reasonable (which travel via Coventry is for any journey, and travel via Birmingham New Street is for any medium or long-distance journey).

 

[kieron]

Some more changes were made to the routeing guide yesterday.

New dataset RJRG0406 published 20 April 2016

To ensure map permissions (in addition to via London Only LO) are in place for fare routes not via London the following changes have been made.

Map sequence added

Basingstoke (BSK) and Kingston (KNG) - added sequence 'WU+WX'
Basingstoke (BSK) and Kingston (KNG) - added sequence 'WW'​

This adds some mapped routes avoiding London. The shortest route from Basingstoke to Kingston (via Woking and New Malden) is on map WW.
WU+WX provides routes via Twickenham: some via Woking and Staines; the rest via Clapham Junction.

To remove circuitous routes from Salisbury to Kingston via Peckham Rye

Map sequence added

Kingston (KNG) and Salisbury (SAL) - added sequence 'WX+EU'

Map sequence removed

Kingston (KNG) and Salisbury (SAL) - removed sequence 'WW+LE'​

If travelling via London, this removes all mapped routes which go between Kingston and London via Tulse Hill, leaving only those via Clapham Junction.
If avoiding London, this removes mapped routes via Clapham Junction and Chertsey, and adds ones via Hampton Wick.

A review of permissions from south of Rugby to routeing points along the Trent Valley has been undertaken. This will harmonise routeings by adding routes where absent via Coventry and remove those via Birmingham where fare anomalies create circuitous routes.

Map sequence added

Bletchley (BLY) and Nuneaton (NUN) - added sequence 'TV'
Milton Keynes Central (MKC) and Nuneaton (NUN) - added sequence 'TV'

Map sequence removed

Bletchley (BLY) and Nuneaton (NUN) - removed sequence 'EB'
Milton Keynes Central (MKC) and Nuneaton (NUN) - removed sequence 'EB'​

These add mapped routes via Bedworth.
They remove the ones via Birmingham.

Bletchley (BLY) and Lichfield Trent Valley (LTV) - removed sequence 'TV+TL'
Bletchley (BLY) and Lichfield Trent Valley (LTV) - removed sequence 'TV+WM'
Bletchley (BLY) and Lichfield Trent Valley (LTV) - removed sequence 'WM+TV'
Lichfield Trent Valley (LTV) and Northampton (NMP) - added sequence 'TV+TL'
Lichfield Trent Valley (LTV) and Northampton (NMP) - removed sequence 'TV+WM'
Lichfield Trent Valley (LTV) and Northampton (NMP) - removed sequence 'WM'
Lichfield Trent Valley (LTV) and Northampton (NMP) - removed sequence 'WM+TV'
Lichfield Trent Valley (LTV) and Milton Keynes Central (MKC) - removed sequence 'TL+TV'
Lichfield Trent Valley (LTV) and Milton Keynes Central (MKC) - removed sequence 'TV+WM'
Lichfield Trent Valley (LTV) and Milton Keynes Central (MKC) - removed sequence 'WM+TV'​

These removes all mapped routes via Birmingham.

Lichfield Trent Valley (LTV) and Rugby (RUG) - added sequence 'TV'
Lichfield Trent Valley (LTV) and Rugby (RUG) - removed sequence 'TL'
Northampton (NMP) and Nuneaton (NUN) - added sequence 'SM'
Northampton (NMP) and Tamworth (TAM) - added sequence 'TL+TV'
Rugby (RUG) and Tamworth (TAM) - added sequence 'TV'
Rugby (RUG) and Tamworth (TAM) - removed sequence 'TL'​

These add mapped routes via Coventry.

Milton Keynes Central (MKC) and Rugeley Trent Valley (RGL) - added sequence 'TV+EB+AB'
Milton Keynes Central (MKC) and Rugeley Trent Valley (RGL) - removed sequence 'TV+BP'​

This adds mapped routes via Birmingham International.

Northampton (NMP) and Rugeley Trent Valley (RGL) - added sequence 'SM+EB+AB'
Northampton (NMP) and Rugeley Trent Valley (RGL) - added sequence 'SM+TV'
Northampton (NMP) and Rugeley Trent Valley (RGL) - removed sequence 'TL'
Northampton (NMP) and Rugeley Trent Valley (RGL) - removed sequence 'TV+CN'
Northampton (NMP) and Rugeley Trent Valley (RGL) - removed sequence 'WM'​

These add mapped routes:
via Wolverton, Weedon (between Wolverton and Rugby) and Bedworth; and
via Bedworth and Armitage (between Rugeley and Lichfield).
They remove mapped routes via Wolverhampton (although these were via Willenhall rather than Birmingham) and via Sutton Coldfield.

Nuneaton (NUN) and Watford Junction (WFJ) - added sequence 'TV'
Nuneaton (NUN) and Willesden Junction (WIJ) - added sequence 'TV'​

These add routes via Bedworth which don't involve going into London and back out again.

Rugeley Trent Valley (RGL) and Rugby (RUG) - added sequence 'CN+EB'
Rugeley Trent Valley (RGL) and Rugby (RUG) - added sequence 'TV'
Rugeley Trent Valley (RGL) and Rugby (RUG) - removed sequence 'TL'
Rugeley Trent Valley (RGL) and Rugby (RUG) - removed sequence 'WM'​

This adds mapped routes via Bedworth and Armitage.

Rugeley Trent Valley (RGL) and Watford Junction (WFJ) - added sequence 'AB+EB'​

This adds mapped routes via Birmingham International which don't go via London.

A review of permissions from Habrough, Barnetby and Retford has resulted in the following changes to remove circuitous routes, via Manchester and via York.

Map sequence added

Bletchley (BLY) and Retford (RET) - added sequence 'EN+EM'
Bletchley (BLY) and Retford (RET) - added sequence 'TV+DY+SH'
Bletchley (BLY) and Retford (RET) - added sequence 'TV+NT'
Milton Keynes Central (MKC) and Retford (RET) - added sequence 'EN+EM'
Milton Keynes Central (MKC) and Retford (RET) - added sequence 'TV+DY+SH'
Milton Keynes Central (MKC) and Retford (RET) - added sequence 'TV+NT'

Map sequence removed

Bletchley (BLY) and Retford (RET) - removed sequence 'TV+CE+EM'
Bletchley (BLY) and Retford (RET) - removed sequence 'TV+CE+SH'
Bletchley (BLY) and Retford (RET) - removed sequence 'TV+EM'
Milton Keynes Central (MKC) and Retford (RET) - removed sequence 'TV+CE+EM'
Milton Keynes Central (MKC) and Retford (RET) - removed sequence 'TV+CE+SH'
Milton Keynes Central (MKC) and Retford (RET) - removed sequence 'TV+EM'
​

This removes mapped routes via Doncaster, via Lichfield and via Narborough.
It adds mapped routes via Alfreton.

Northampton (NMP) and Retford (RET) - added sequence 'EN+EM'
Northampton (NMP) and Retford (RET) - added sequence 'TV+DY+SH'
Northampton (NMP) and Retford (RET) - added sequence 'TV+NT'
Northampton (NMP) and Retford (RET) - removed sequence 'TV+CE+EM'
Northampton (NMP) and Retford (RET) - removed sequence 'TV+CE+SH'
Northampton (NMP) and Retford (RET) - removed sequence 'TV+EM'​

This removes mapped routes via Doncaster, via Lichfield, via Narborough and via both Rugby and Milton Keynes.
It adds mapped routes via Alfreton.

Retford (RET) and Rugby (RUG) - added sequence 'NT+TV'
Retford (RET) and Rugby (RUG) - added sequence 'SH+DY+TV'
Retford (RET) and Rugby (RUG) - removed sequence 'EM+CE+TV'
Retford (RET) and Rugby (RUG) - removed sequence 'EM+TV'
Retford (RET) and Rugby (RUG) - removed sequence 'SH+CE+TV'​

This removes mapped routes via Doncaster, via Lichfield and via Loughborough.
It adds mapped routes via Alfreton.

Accrington (ACR) and Barnetby (BTB) - removed sequence 'NP+DS'
Accrington (ACR) and Habrough (HAB) - removed sequence 'NP+DS'
Barnetby (BTB) and Kirkham And Wesham (KKM) - removed sequence 'DS+NP'
Barnetby (BTB) and LANCASTER GROUP (G64) - removed sequence 'DS+NP+XP'
Barnetby (BTB) and Oxenholme Lake District (OXN) - removed sequence 'DS+NP+XP'
Barnetby (BTB) and Preston (Lancs) (PRE) - removed sequence 'DS+NP'
Blackburn (BBN) and Barnetby (BTB) - removed sequence 'NP+DS'
Blackburn (BBN) and Habrough (HAB) - removed sequence 'NP+DS'
Habrough (HAB) and Kirkham And Wesham (KKM) - removed sequence 'DS+NP'
Habrough (HAB) and Oxenholme Lake District (OXN) - removed sequence 'DS+NP+XP'
Habrough (HAB) and Preston (Lancs) (PRE) - removed sequence 'DS+NP'
LANCASTER GROUP (G64) and Habrough (HAB) - removed sequence 'XP+NP+DS'​

These remove all mapped routes via York and via Selby.

Barnetby (BTB) and Northampton (NMP) - removed sequence 'DW+MA'
Barnetby (BTB) and Rugby (RUG) - removed sequence 'DW+MA'
Barnetby (BTB) and Watford Junction (WFJ) - removed sequence 'DW+MA'
Bletchley (BLY) and Habrough (HAB) - removed sequence 'MA+DW'
Habrough (HAB) and Milton Keynes Central (MKC) - removed sequence 'DW+MA'
Habrough (HAB) and Northampton (NMP) - removed sequence 'DW+MA'
Habrough (HAB) and Rugby (RUG) - removed sequence 'DW+MA'
Habrough (HAB) and Watford Junction (WFJ) - removed sequence 'DW+MA'​

These remove all mapped routes via Chinley.

Removing circuitous routes between Gospel Oak and London Group

Map sequence removed

LONDON GROUP (G01) and Gospel Oak (GPO) - removed sequence 'LB+OV'​

This removes mapped routes via Clapham Junction.

Easements for engineering works

Easement(s) added

700636: During railway improvement works from the 30 July to 14 August 2016 the permitted routes between Oxford and Didcot will be affected. Customers travelling from and via Hereford will be permitted to travel via Newport and Bristol to or via Didcot.​

A new engineering easement published more than 12 weeks before the dates mentioned.

Easement removed

700607: During weekend engineering works, from 09 January 2016 to 03 April 2016, journeys on the line from Ebbw Vale Town to destinations via Cardiff Central will be routed via Newport (S Wales). This positive Routeing Point easement will allow journey planners to show journeys that doubleback between Newport (S Wales) and Pye Corner and onward to Cardiff Central. This easement applies in both directions.

700621: During engineering works 17 April 2016 the route between Bristol Temple Meads and Bath Spa will be closed. Alternative routeings via Chippenham Swindon and Bristol Parkway will be place. For journeys from Portsmouth, Fratton, Cosham, Fareham, Southampton Central, Romsey. Salisbury, Warminster, Dilton Marsh, Weymouth, Dorchester West, Maiden Newton, Chetnole, Yetminster, Thornford, Yeovil Pen Mill, Castle Cary, Bruton, Frome, Westbury, Trowbridge, Bradford on Avon, Avoncliff, Freshfold, Bath Spa, Melksham and Chippenham that would travel to or via Bristol on tickets routed ANY PERMITTED (00000), NOT VIA LONDON (00700), VIA YEOVIL (00829), VIA SALISBURY (00618) may travel via Swindon. this easement applies in both directions.​

The dates for both have gone now.

Easements added for Glastonbury festival for customers using South West Trains services

700637: For the Glastonbury festival between 20 and 28 June 2016 journeys to Castle Cary on Fare routes (00618) SALISBURY and (00800) SALISBURY/WARMINSTER will be permitted to travel via Sherbourne, Yeovil Junction and Yeovil Pin Mill. This positive map easement applies in both directions.

700638: During the Glastonbury Festival, 20 - 28 June 2016, tickets to Castle Cary on fare route WARMINSTER/SALISBURY (00800) will be able to travel via Sherbourne and Yeovil Junction and Yeovil Pin Mill. This easement applies in both directions.​

There's no substantive difference between the text of each. 700637 is a "map" easement, and 700638 a "fare route" one. The latter isn't needed for "via Salisbury" tickets as someone travelling via Sherbourne (sic), Yeovil Junction and Yeovil Pin Mill (sic) will go through Salisbury anyway.

Easements changed to add a further fare route LONDON EVESHAM (00799).

700630: Journeys to and via London Marylebone on fare routes AP EVESHAM (00402); CHILTERN & CONNECTIONS (00402); LONDON EVESHAM (00799); EVESHAM/STROUD (00803) and VIA EVESHAM (00805) are not permitted to travel via Oxford and Oxford Parkway. This negative easement applies in both directions.​

"London Evesham" has been added, as mentioned. I don't know off-hand which tickets would have a valid route via London, Oxford Parkway and Evesham without this easement, but I suspect there aren't too many.

 

[All Line Rover]

The changes removing permitted routes via Birmingham are unacceptable.

 

[adrock1976]

Removing circuitous routes between Gospel Oak and London Group

Map sequence removed

LONDON GROUP (G01) and Gospel Oak (GPO) - removed sequence 'LB+OV'​

This removes mapped routes via Clapham Junction.

Regarding the above, as it is within Greater London and the zonal fares system (Gospel Oak and Clapham Junction), are Transport for London aware of this recent change?

Does TfL actually have any input into the Routeing Guide at all for routes within London?

Apologies for the above questions - whenever I see any changes in London, it always throws me a bit, as surely it would have no effect for passengers who possess zonal products.

 

[kieron]

Some more changes were published today, although they only affect temporary easements.

New dataset RJRG0407 published 28 April 2016

Engineering works easements for May bank holiday weekend

Easements added

700639: Over the weekend of the 30 April to Monday 2 May 2016, engineering works will affect the line between Exeter St Davids and Crewkerne. Rail replacement bus services will be in operation, and tickets from Honiton to London will not be valid on Great Western services via Exeter, Reading to London Paddington. This negative easement will apply in both directions​

This is, I presume, intended to counteract the effect of 700031, which allows you to go via Exeter so long as you go via Taunton.

Easements changed - added dates

700634: During engineering works on Sundays 24 April, 1 May and Monday 2 May 2016 the line between Radley, Didcot and Tilehurst will be closed. Customers travelling on journeys using tickets on Fare Route NOT VIA READING (00810) may travel via Reading. This easement applies in both directions.​

This just adds next weekend to the easement.

 

[kieron]

Some more changes were made to the routeing guide yesterday.

New dataset RJRG0408 published 05 May 2016

Fares from Bedford to ELy are priced on fare route VIA CAMBRIDGE. The following map sequence is therefore not required as it does not include Cambridge as a via Location

Map sequence removed

Bedford (BDM) and Ely (ELY) - removed sequence 'MI+AB'​

This removes the mapped routes via Leicester, to leave only ones which go through both London and Cambridge.

Tickets from Bedford to Ely are priced on the fare routes "via Cambridge" and "Hatfld/Albns Bus", neither of which uses the route on these maps. Tickets from Wellingborough to Elmswell, by contrast, are valid on "any permitted" route. Travellers may still use the shortest route for this journey, of course. That's similar to the route on MI+AB except that it doesn't include the double back via Bedford, and it goes through Corby rather than Leicester.

Journeys from Hull to Grimsby Town via Goole were reported failing in journey planning systems. A review found that a Manual Easement that would allow journeys to doubleback through Hatfield & Stainforth was not effective and a reoplacement doubleback easement was created to replace it.

Easement removed

000047: When changing between the Goole-Doncaster and Scunthorpe-Doncaster lines passengers may double back between Hatfield & Stainforth and Doncaster. This easement applies in both directions.

Easement added (note this addition reused number of a deleted dated easement)

700639: For journeys from or via Goole to destinations on the route between Doncaster, Scunthorpe and Cleethorpes may doubleback through Hatfield & Stainforth. This positive doubleback easement applies in both directions.​

There's probably a good reason why they reused 700639 rather than 47 for this.
The new easement is similar to the old one, except that it doesn't imply that anyone can double back through Kirk Sandall (the station between Doncaster and Hatfield & Stainforth), and that it makes it clear that it does not cover the Barton-on-Humber branch.

And then there's easement 700261:

Customers travelling from or via Thorne South to or via Thorne North may not travel via Kirk Sandall and/or Doncaster. This easement applies in both directions.​

I don't know what to think.

Easement removed enginering work diversions

700634: During engineering works on Sundays 24 April, 1 May and Monday 2 May 2016 the line between Radley, Didcot and Tilehurst will be closed. Customers travelling on journeys using tickets on Fare Route NOT VIA READING (00810) may travel via Reading. This easement applies in both directions.

700639: Over the weekend of the 30 April to Monday 2 May 2016, engineering works will affect the line between Exeter St Davids and Crewkerne. Rail replacement bus services will be in operation, and tickets from Honiton to London will not be valid on Great Western services via Exeter, Reading to London Paddington. This negative easement will apply in both directions​

The dates for these have all passed now.

 

[CheapAndNerdy]

And then there's easement 700261:

Customers travelling from or via Thorne South to or via Thorne North may not travel via Kirk Sandall and/or Doncaster. This easement applies in both directions.​

I don't know what to think.

Looking at the timetable, for much of the day when travelling from Thorne North to Thorne South, there's a 1 hour plus wait at Hatfield & Stainforth. All I can think is that passengers prefer to travel via Doncaster (although it's no quicker) in order to relieve the tedium of waiting for over an hour.

 

[Bletchleyite]

Looking at the timetable, for much of the day when travelling from Thorne North to Thorne South, there's a 1 hour plus wait at Hatfield & Stainforth. All I can think is that passengers prefer to travel via Doncaster (although it's no quicker) in order to relieve the tedium of waiting for over an hour.

So why stop them?

Why does the railway like to go "ner ner, you can't do that" rather than setting a suitable fare for journey combinations passengers evidently wish to make?

I despair, I really do.