National Routeing Guide update

[kieron]

Adding mapped shortest journeys? Does that come with a later proposal to allow only mapped routes and remove the other rules?

As they've added the shortest route between one additional pair of routeing points, I think they've got a long way to go before they can think about that sort of thing.

The fastest route is to go to West Croydon and then East Croydon. National Rail Enquiries App doesn't give a price for that as it wants to put you on the tram, even though your point to point ticket isn't valid on a tram.

I'm not sure that's the entire reason. There are "via Tramlink 1" tickets defined for Ashtead-Gatwick, but I've checked a few web sites (although not the NRE app) and haven't found anywhere which actually offers them.

But there is no specific ban on travelling via Mitcham Junction; rather maps HR+LB have been removed as a valid combination for the journey.

Yes, sorry, that's all it is. They replaced the SWT Epsom-Clapham Junction-Gatwick map combination with a more restrictive one, and removed the Southern one altogether.

 

[kieron]

Some more changes were published on Wednesday.

New data set 0528 published 18/07/18

Comparing revision RJRG0528 to RJRG0527

Amending map sequences to Hull and Gilberdyke from Northallerton and Darlington

Sequences added

Darlington (DAR) and Hull (HUL) - added sequence 'HT+AH'

Sequences removed

Darlington (DAR) and Hull (HUL) - removed sequence 'DT'
Darlington (DAR) and Hull (HUL) - removed sequence 'HT'​

This journey no longer has mapped routes which go through both Middlesbrough group and Doncaster.

Gilberdyke (GBD) and Northallerton (NTR) - added sequence 'DS'
Gilberdyke (GBD) and Northallerton (NTR) - added sequence 'HA'
Gilberdyke (GBD) and Northallerton (NTR) - added sequence 'HM+MN'
Gilberdyke (GBD) and Northallerton (NTR) - added sequence 'YA'
Gilberdyke (GBD) and Northallerton (NTR) - removed sequence 'DT'
Gilberdyke (GBD) and Northallerton (NTR) - removed sequence 'HT'
Gilberdyke (GBD) and Northallerton (NTR) - removed sequence 'YM'​

Adding HM+MN means that this journey now has mapped routes via Leeds.
Unless this affects the way web sites interpret some easements, the other changes do nothing.

Hull (HUL) and Northallerton (NTR) - added sequence 'HM+MN'
Hull (HUL) and Northallerton (NTR) - removed sequence 'HT'​

This journey now has mapped routes via Leeds.
It no longer has mapped routes via Doncaster which don't go through Goole.

A review to reduce variation of map sequences and to remove unintended routes where maps join at Guildford; Horsham from Epsom Routeing Point -

Sequences added
Epsom (EPS) and CROYDON GROUP (G08) - added sequence 'DK+FC+LP'
Epsom (EPS) and CROYDON GROUP (G08) - added sequence 'XE+TK+LP'
Epsom (EPS) and CROYDON GROUP (G08) - removed sequence 'DK+TN'
Epsom (EPS) and CROYDON GROUP (G08) - removed sequence 'XE+SD'​

This journey no longer has mapped routes via Norwood Junction.

Epsom (EPS) and BRIGHTON GROUP (G04) - added sequence 'AR+VB'
Epsom (EPS) and BRIGHTON GROUP (G04) - added sequence 'DK+HR+VB'
Epsom (EPS) and BRIGHTON GROUP (G04) - added sequence 'HR+VB'
Epsom (EPS) and EASTBOURNE GROUP (G84) - added sequence 'AR+VB'
Epsom (EPS) and EASTBOURNE GROUP (G84) - added sequence 'DK+HR+VB'
Epsom (EPS) and EASTBOURNE GROUP (G84) - added sequence 'HR+VB'
Epsom (EPS) and Gatwick Airport (GTW) - added sequence 'DK+HR+VB'
Epsom (EPS) and Gatwick Airport (GTW) - added sequence 'HR+VB'
Epsom (EPS) and Haywards Heath (HHE) - added sequence 'AR+VB'
Epsom (EPS) and Haywards Heath (HHE) - added sequence 'DK+HR+VB'
Epsom (EPS) and Haywards Heath (HHE) - added sequence 'HR+VB'
Epsom (EPS) and Lewes (LWS) - added sequence 'AR+VB'
Epsom (EPS) and Lewes (LWS) - added sequence 'DK+HR+VB'
Epsom (EPS) and Lewes (LWS) - added sequence 'HR+VB'
Epsom (EPS) and REDHILL GROUP (G60) - added sequence 'DK+HR+VB'
Epsom (EPS) and REDHILL GROUP (G60) - added sequence 'HR+VB'
Epsom (EPS) and Three Bridges (TBD) - added sequence 'AR+VB'
Epsom (EPS) and Three Bridges (TBD) - added sequence 'DK+HR+VB'
Epsom (EPS) and Three Bridges (TBD) - added sequence 'HR+VB'
Epsom (EPS) and Wivelsfield (WVF) - added sequence 'AR+VB'
Epsom (EPS) and Wivelsfield (WVF) - added sequence 'DK+HR+VB'
Epsom (EPS) and Wivelsfield (WVF) - added sequence 'HR+VB'
Epsom (EPS) and BRIGHTON GROUP (G04) - removed sequence 'DK+LB'
Epsom (EPS) and BRIGHTON GROUP (G04) - removed sequence 'DK+XB'
Epsom (EPS) and BRIGHTON GROUP (G04) - removed sequence 'HR+LB'
Epsom (EPS) and EASTBOURNE GROUP (G84) - removed sequence 'DK+LB'
Epsom (EPS) and EASTBOURNE GROUP (G84) - removed sequence 'DK+XB'
Epsom (EPS) and EASTBOURNE GROUP (G84) - removed sequence 'HR+LB'
Epsom (EPS) and Gatwick Airport (GTW) - removed sequence 'DK+LP'
Epsom (EPS) and Haywards Heath (HHE) - removed sequence 'DK+LB'
Epsom (EPS) and Haywards Heath (HHE) - removed sequence 'DK+XB'
Epsom (EPS) and Haywards Heath (HHE) - removed sequence 'HR+LB'
Epsom (EPS) and Lewes (LWS) - removed sequence 'DK+LB'
Epsom (EPS) and Lewes (LWS) - removed sequence 'DK+XB'
Epsom (EPS) and Lewes (LWS) - removed sequence 'HR+LB'
Epsom (EPS) and REDHILL GROUP (G60) - removed sequence 'DK+TN'
Epsom (EPS) and REDHILL GROUP (G60) - removed sequence 'XE+SD'
Epsom (EPS) and Three Bridges (TBD) - removed sequence 'DK+LB'
Epsom (EPS) and Three Bridges (TBD) - removed sequence 'DK+XB'
Epsom (EPS) and Three Bridges (TBD) - removed sequence 'HR+LB'
Epsom (EPS) and Wivelsfield (WVF) - removed sequence 'DK+LB'
Epsom (EPS) and Wivelsfield (WVF) - removed sequence 'DK+XB'
Epsom (EPS) and Wivelsfield (WVF) - removed sequence 'HR+LB'​

Quite a few routes have been gained and lost by these changes, but to me it's more important in terms of what we're left with.

A journey from Epsom to somewhere between Redhill, Hove and Eastbourne has one of two sets of map combinations it can use.

One set (- below) is as follows (all with the same routes south of Redhil):

AR: Epsom-Dorking-Redhill;
DK+HR+VB: Epsom-Wimbledon-Clapham Junction-Streatham-Croydon-Redhill
: Epsom-Wimbledon-Clapham Junction-London-Tulse Hill-Crystal Palace-Croydon-Redhill
: Epsom-Wimbledon-Clapham Junction-London-Tulse Hill-Streatham-Croydon-Redhill
HR+VB: Epsom-Mitcham Junction-Streatham-Croydon-Redhill
: Epsom-Mitcham Junction-Clapham Junction-London-Tulse Hill-Crystal Palace-Croydon-Redhill
: Epsom-Mitcham Junction-Clapham Junction-London-Tulse Hill-Streatham-Croydon-Redhill
XE: Epsom-Sutton-Croydon-Redhill

The other (+ below) is the same, except that routeing points also has LONDON as a route. In these cases, LONDON means DK or HR from Epsom to London, and LB or VB beyond London.

DK: Epsom-Wimbledon-Clapham Junction-London
HR: Epsom-Mitcham Junction-Clapham Junction-London
: Epsom-Mitcham Juntion-Streatham-Clapham Junction-London
: Epsom-Mitcham Junction-Tulse Hill-Elephant & Castle-London

LB includes a number of routes between London and Croydon. These include ones via Clapham Junction, via Elephant & Castle, via Peckham Rye and via New Cross Gate.
VB includes routes via Brixton.

In terms of routeing points, the pattern is:
Redhill Group: -
Gatwick Airport: +
Three Bridges: +
Haywards Heath: -
Wivelsfield: -
Brighton Group: +
Lewes: +
Eastbourne: -

None of these cover the shortest route (or, at least, what I believe to be the shortest route by train) between Epsom and Redhill (and, indeed, Epsom and Eastbourne). XE comes close, but the shortest route goes by train between West Croydon and East Croydon via Selhurst. Selhurst is part of Streatham Group, and not on XE. You'd need something like XE+LP to go that way.

For engineering diversions - easements added

Added 700805: Due to engineering works Cross Country Services will be diverted via Newport (South Wales) and Chepstow between the 15 September and 12 October 2018. This map easement will create temporary permitted routes via Newport (South Wales) for connecting destinations that use a journey leg using these diverted Cross Country services. It will operate in both directions.

Added 700806: Due to engineering works between 15 September and 12 October 2018, Cross Country services are diverted via Newport (South Wales) . This doubleback easement will allow journey planners to accept journeys passing Severn Tunnel Junction twice, and will operate in both directions.​

Crosscountry trains are calling at Gloucester, Newport and Patchway between Cheltenham and Bristol Temple Meads then. Some other trains are shown as going through Yate, but this is still quite some distance in the future.

Easement removed as tickets no longer poriced on (00001) DIRECT

Removed 700312: Customers travelling from Marsden or Slaithwaite to/from Manchester Piccadilly in possession of tickets routed "Direct" may not travel via Huddersfield. This easement applies in both directions.​

The "direct" fares went in January, so this easement hasn't had any effect since then. We now have "any permitted", "not Huddersfield", "via Hebden Bridge", "TPE only" and advance tickets.

Removed 700791: During engineering works from 16/06/2018 to 07/07/2018 ,this local easement allows customers to travel from Bristol Stations and Yate to Chepstow and Lydney, via Gloucester or Cheltenham. This local easement applies in both directions​

The dates have gone now.

For additional dates of diversions, easement amended
2 change(s) in 700796: During engineering works on Saturday and Sunday from 07/07/2018 to 15/07/2018, and 13/10/2018 to 14/10/2018 and all days 27/10/2018 to 18/11/2018 diversions between Bristol and Cheltenham will be permitted via Swindon. This map easement is applies in both directions.​

The October and November dates are new here.

 

[kieron]

Some more changes were made to the routeing guide on Wednesday. There isn't a summary on the RDG web site yet, but the changes are as follows:

Station Association changes:

Ashchurch (ASC) has lost an association with Bromsgrove (BMV).​

Crosscountry no longer call at Bromsgrove. This means that there is only 1 train a week which goes between the two stations, and that goes through Worcester anyway.

There probably are benefits from doing this, but it does mean that a train between Ashchurch and Birmingham New Street doesn't pass through any routeing points associated with Ashchurch on the way, and so mapped routes (such as any route from Ashchurch to Perth via Edinburgh) are not available. I haven't been able to reproduce this on a ticket site yet, so I don't know what the current situation is with those.

As a piece of trivia, Bromsgrove is now a routeing point which has no other stations associated with it. Ebbsfleet and Raynes Park are the only other two.

Permitted Route changes:

Ashford International (AFK) to Salisbury (SAL) gain CW+SS lose CW+SN
Brighton Group (G04) to Salisbury (SAL) gain CW+SS lose SN
Hastings Group (G15) to Salisbury (SAL) gain CW+SS lose CW+SN
Havant (HAV) to Salisbury (SAL) gain SS lose SN
​

These journeys now have mapped routes via Botley.

Dover Priory (DVP) to Salisbury (SAL) gain CW+SS
Ramsgate Group (G68) to Salisbury (SAL) gain DE+KA+CW+SS KA+CW+SS
​

These journeys now have mapped routes via Brighton.

Eastbourne Group (G84) to Salisbury (SAL) gain CW+SS lose XE+SN
​

This journey no longer has mapped routes which go through both Wivelsfield and Southampton.
It now has mapped routes via Botley.

Ford Group (G61) to Salisbury (SAL) gain CW+SS lose CW+CE​

This journey no longer has mapped routes via Westbury.

Leeds Group (G16) to Pontefract Group (G22) gain NP​

This journey now has mapped routes via Wakefield.

Map changes:

NP: Lose Leeds Group to/from Pontefract Group
This map is used in 2480 routes.​

This means that someone going between Accrington and Chesterfield can no longer catch a train which goes through Castleford. I don't know if it has any more troublesome effects.

Easement changes:

Added:

700807 (Circuitous Route) Customers travelling from Spondon and Long Eaton on journeys via Tamworth may not interchange at Beeston. this circuitous route easement applies in both directions.​

Easement 700799 from June allows trains to pass between Tamworth and Nottingham without going through Derby. I suspect this new easement is there to encourage people to use the bus.

 

[bnm]

Crosscountry no longer call at Bromsgrove

Do they not? Four booked calls (2 each way) per weekday. Those calls are a franchise Service Level Commitment. After the 2016 Direct Award the SLCs were unchanged. There has been no recent DfT mandated change to remove the XC Bromsgrove SLC and the calls remain in the timetable.

 

[OwlMan]

There probably are benefits from doing this, but it does mean that a train between Ashchurch and Birmingham New Street doesn't pass through any routeing points on the way, and so mapped routes (such as any route from Ashchurch to Perth via Edinburgh) are not available. I haven't been able to reproduce this on a ticket site yet, so I don't know what the current situation is with those.

It does - Barnt Green

 

[OwlMan]

Do they not? Four booked calls (2 each way) per weekday. Those calls are a franchise Service Level Commitment. After the 2016 Direct Award the SLCs were unchanged. There has been no recent DfT mandated change to remove the XC Bromsgrove SLC and the calls remain in the timetable.

They were withdrawn recently when the Cross City line was extended to Bromsgrove

 

[Paul Kelly]

Ashchurch (ASC) has lost an association with Bromsgrove (BMV).Crosscountry no longer call at Bromsgrove. This means that there is only 1 train a week which goes between the two stations, and that goes through Worcester anyway.

There probably are benefits from doing this, but it does mean that a train between Ashchurch and Birmingham New Street doesn't pass through any routeing points on the way, and so mapped routes (such as any route from Ashchurch to Perth via Edinburgh) are not available.

Or to be more precise, the first routeing point it passes through isn't associated with the origin station, so puffs of smoke come out of the routeing guide. This is a very strange change; it's almost as if whoever is making all these changes to the routeing guide doesn't realise that a train doesn't necessarily need to call at its origin or destination routeing point. Leaving aside the debate about whether a through train from Ashchurch to Birmingham calls at Bromsgrove, it certainly still passes through it, and so Bromsgrove should still be the origin routeing point for the journey - but now can't be. Well spotted; very interesting analysis as always, kieron.

 

[infobleep]

Or to be more precise, the first routeing point it passes through isn't associated with the origin station, so puffs of smoke come out of the routeing guide. This is a very strange change; it's almost as if whoever is making all these changes to the routeing guide doesn't realise that a train doesn't necessarily need to call at its origin or destination routeing point. Leaving aside the debate about whether a through train from Ashchurch to Birmingham calls at Bromsgrove, it certainly still passes through it, and so Bromsgrove should still be the origin routeing point for the journey - but now can't be. Well spotted; very interesting analysis as always, kieron.

Are there any reasonable journeys no longer permitted by this change? Anyone know?

 

[swt_passenger]

They were withdrawn recently when the Cross City line was extended to Bromsgrove

The removal was also foreseen in the 2016 XC consultation, for the then anticipated Dec 2017 timetable. I expect DfT will definitely be onboard with this.

 

[Skymonster]

Added:

700807 (Circuitous Route) Customers travelling from Spondon and Long Eaton on journeys via Tamworth may not interchange at Beeston. this circuitous route easement applies in both directions.​

Easement 700799 from June allows trains to pass between Tamworth and Nottingham without going through Derby. I suspect this new easement is there to encourage people to use the bus.

That's pretty mean-spirited. Long Eaton to Tamworth during the Derby blockade potentially requires a bus from Long Eaton to Derby, another bus from Derby to Burton, and then a train from Burton to Tamworth (whereas outside the blockade it would be a single through train journey). Its far easier at present to get a train to Beeston and then use Cross Country to Tamworth (via Sheet Stores / Stenson). The railway has caused this inconvenience to passengers, so it's very poor that the journey is being made more convoluted than needs be.

 

[Paul Kelly]

Are there any reasonable journeys no longer permitted by this change? Anyone know?

There are bound to be plenty. Ashchurch to York is one. The fastest journey opportunities for this involve a single change at Birmingham. But this is no longer a permitted route, so booking engines will send you on a longer journey via Cheltenham or Worcester.

 

[ForTheLoveOf]

There are bound to be plenty. Ashchurch to York is one. The fastest journey opportunities for this involve a single change at Birmingham. But this is no longer a permitted route, so booking engines will send you on a longer journey via Cheltenham or Worcester.

Yes, although even legally speaking you don't have to follow the itinerary as long as you can justify not doing so as a 'start late' (i.e. break of journey) on the validity of the ticket between Worcester or Cheltenham RPs and your destination. Practically speaking there is no chance you would have any problems!

 

[crosscity]

Do they not? Four booked calls (2 each way) per weekday. Those calls are a franchise Service Level Commitment. After the 2016 Direct Award the SLCs were unchanged. There has been no recent DfT mandated change to remove the XC Bromsgrove SLC and the calls remain in the timetable.

Looking at realtimetrains the trains do stop at Bromsgrove in the working timetable, but not in the public timetable. Can a Bromsgrove passenger use these trains at all? If not what is the SLC for, because it can't be to benefit Bromsgrove passengers? See http://www.realtimetrains.co.uk/sea.../0000-2359?stp=WVS&show=call&order=wtt&toc=XC

 

[swt_passenger]

The timetable changed on 30th. XC no longer stop at Bromsgrove. Why’s that so complicated?

Link to the WMR announcement from one of the other Bromsgrove threads:
https://www.westmidlandsrailway.co.uk/about-us/news-desk/three-extra-trains-hour-bromsgrove

 

[kieron]

Or to be more precise, the first routeing point it passes through isn't associated with the origin station, so puffs of smoke come out of the routeing guide.

Yes, sorry. I've amended the post now to say that. As you don't go through any routeing points associated with Ashchurch, you're left with through trains, easements, and whatever is allowed under the shortest route rule.

Journeys which don't pass through a routeing point associated with one end or the other aren't a new thing, as (for example) Chorley hasn't been associated with Wigan since the routeing guide was created.

I don't know if having a trains from a station which goes to a routeing point, but not to any of the ones associated with that station, is a new thing. There are certainly lots where the obvious routeing point fails the fare check, though, which gives a similar effect.

This is a very strange change; it's almost as if whoever is making all these changes to the routeing guide doesn't realise that a train doesn't necessarily need to call at its origin or destination routeing point.

It could just be that it started as a "Crosscountry will no longer stop at Bromsgrove, so we should do something" thing and somehow got into the routeing guide without anyone thinking too much about it.

There are bound to be plenty. Ashchurch to York is one. The fastest journey opportunities for this involve a single change at Birmingham. But this is no longer a permitted route, so booking engines will send you on a longer journey via Cheltenham or Worcester.

Yes, that one works, with the shortest route going via Pontefract Baghill. At least you can pick Cheltenham as the associated routeing point and start short at Ashchurch, even if a booking engine will never suggest it. I somehow failed to spot the "via Lancaster" fares to Stirling.

 

[kieron]

Some more updates were published this afternoon. There's no summary of it on the RDG web site, but the changes are as follows:

Changes from 180801 to 180816.

Permitted Route changes:

Dorking Group (G10) to Effingham Junction (EFF) gain AR lose AR+DK DK+AR​

No effect.

Newcastle (NCL) to Warrington Group (G31) gain MN+NO​

This journey now has mapped routes via Newton-le-Willows.

Map changes:
AR: Gain Edenbridge to/from Godstone
AR: Gain Redhill Group to/from Godstone
AR: Lose Edenbridge to/from Redhill Group
TN: Gain Edenbridge to/from Godstone
TN: Gain Redhill Group to/from Godstone
TN: Lose Edenbridge to/from Redhill Group
XE: Gain Edenbridge to/from Godstone
XE: Gain Redhill Group to/from Godstone
XE: Lose Edenbridge to/from Redhill Group​

In other words, every map which includes Edenbridge (a station between the Tonbridge and Redhill Group routeing points) now includes Godstone between Edenbridge and Redhill Group. This means that someone following a mapped route can't travel via Edenbridge Town instead.

Easement changes:

Removed:

700042 (Circuitous Route) Customers travelling from Castle Cary to Bristol Temple Meads and beyond may not travel via Taunton. This easement applies in both directions.​

I can't see anything which would be affected by this easement, just from looking at the maps. That's not a bad reason to delete something, but I suspect there's more to it.

700797 (Routeing Point) During engineering works from 16/06/2018 to 07/07/2018 ,this local easement allows customers to travel from Bristol Stations and Yate to Chepstow and Lydney, via Gloucester or Cheltenham. This routeing point easement applies in both directions

700802 (Fare route) Due to engineering diversions operational until 22 July 2018, journeys from Worcester to London Paddington with tickets priced on fare route (00805) VIA EVESHAM, will be valid via Stroud (Glos). This fare route easement applies in both directions​

These temporary easements have no effect now.

 

[WelshBluebird]

700042 (Circuitous Route) Customers travelling from Castle Cary to Bristol Temple Meads and beyond may not travel via Taunton. This easement applies in both directions.I can't see anything which would be affected by this easement, just from looking at the maps. That's not a bad reason to delete something, but I suspect there's more to it.

Really? I'm quite surprised at that.
I don't know if it was a legitimate route before this change (it may already not have been, in which case what is the point of adding the easement!), but just from knowing the services in the area I can tell you that going via Taunton and changing can easily be quicker than the direct train via Westbury for that journey. Google Maps also suggests that as a route if you try to ask for public transport directions from Castle Cary to Bristol, and it is also a handy alternative route if the route via Westbury is disrupted.

 

[ForTheLoveOf]

Really? I'm quite surprised at that.
I don't know if it was a legitimate route before this change (it may already not have been, in which case what is the point of adding the easement!), but just from knowing the services in the area I can tell you that going via Taunton and changing can easily be quicker than the direct train via Westbury for that journey. Google Maps also suggests that as a route if you try to ask for public transport directions from Castle Cary to Bristol, and it is also a handy alternative route if the route via Westbury is disrupted.

No, this easement was removed. It's unclear why it ever came into existence in the first place.

 

[Mag_seven]

Removed:

700042 (Circuitous Route) Customers travelling from Castle Cary to Bristol Temple Meads and beyond may not travel via Taunton. This easement applies in both directions.

Can you now travel via Taunton as you are removing something that states that you can't!

 

[island]

That is correct. You previously could not travel that way, and now you can.

 

[JB_B]

That is correct. You previously could not travel that way, and now you can.

It's a reasonable route but I don't think Castle Cary -> Taunton -> Bristol is a permitted route, is it?

( I did wonder if the "and beyond" part of 700042 might still have had some relevance but I can't immediately spot any destinations from CLC to beyond Bristol with mapped routes via Taunton.)

 

[kieron]

I had a look for mapped routes from Castle Cary via Taunton and Bristol. For there to be a route on a map, you need something which includes the Bridgwater-Taunton section of line. This appears on the following maps:

CZ GW MP OP PB PE PH PJ PL PM PO PP PV PW PX PY SP WR

No route from Castle Cary includes any of these maps.

There are some "via Taunton", "AP Taunton" and "via Bristol" tickets from Castle Cary, but none have a suitable destination for this to mean a route which involves Taunton-Bridgwater-Bristol.

The shortest route and through train rules don't help, and I couldn't see a relevant easement, so I don't think easement 700042 actually prevented anything at the end.

 

[kieron]

An easement was amended this afternoon:

Changes from 180816 (224) to 180820 (225).

Easement changes:

Changed:
< 700804 (Map) ... 25 - 27 August 2018 ...
> 700804 (Map) Due to the closure of London Euston station over the weekends of the 18 - 19 August 2018; 26 - 27 August 2018 and 01 - 02 September 2018. Journeys between London and Manchester, Wilmslow and Stockport will be permitted via London Kings Cross, Leeds and onward on Trans Pennine Express services via Huddersfield and Manchester Piccadilly. This map easement applies in both directions​

Easement 700804 has had its dates amended to remove this Saturday (26 August). There isn't much scheduled to leave London Euston on Saturday at the moment, but perhaps they're working on it.

Easement 700803 (which has similar wording) hasn't been altered.

Now I think about it, this easement does make it sound as though you would need to wait at Manchester Piccadilly for a TPE train to Stockport or Wilmslow. TPE don't call at Wilmslow even when they're sent that way.

 

[kieron]

Two temporary easements had extra dates added to them this afternoon. Some past dates were removed at the same time.

Changes from 180820 to 180830:​

700788 has had Sunday 21 October and Sunday 25 November added, making it:

Due to engineering work diversions via Cosham, affecting journeys from and via Southampton to destinations using journey legs on Cross Country services on the weekends 01/02, 08/09, 15/16, and Saturday 22 September 2018, and Sundays the 21 October 2018 and 25 November 2018. This map easement will allow journey planners to see journeys via Cosham and Havant, and applies in both directions.​

700796 has had the weekend 1-2 December added. It's now:

During engineering works on the weekend of 13/10/2018 - 14/10/2018, between 27/10/2018 to 18/11/2018 and the weekend of the 01/12/2018 - 02/12/2018 diversions between Bristol and Cheltenham will be permitted via Swindon. This map easement is applies in both directions.​

 

[kieron]

Some more changes were made on Wednesday. Sorry for the delay.

Changes from 180830 (226) to 180912 (227).

Map changes:
WG: Gain Wigan Group to/from Earlestown Group​

There's a commuter train each way between Newton-le-Willows and Liverpool which happens to start from Wigan North Western rather than Manchester. This change means that someone going (say) from Newton-le-Willows to Falkirk can take one of these trains but still go via Glasgow or Edinburgh.

Easement changes:

Added:
700808 (Fare route) Due to engineering works between Crewkerne and Exeter from 15 to 23 September 2018, there will be fast rail replacement buses calling at Crewkerne, Exeter Central and Exeter St Davids. As the bus does not call/pass Honiton, this fare route easement is required to allow tickets routed (00840) Via Honiton to be valid on these rail replacement services.​

You can confirm that this easement is needed, as journeys which use some of the other "via Honiton" routes are not shown as valid using the buses. There are a few of these:
Exeter-Hastings has "London Honiton", "Honiton Clapm Jn" and "Honiton Shampton" ones;
Exeter-Poole has "Dorchstr Honiton" and "Honiton Shampton" ones;
Exeter-Southampton has "Honiton Salisbry" ones;
Exeter-Weymouth has "Thornfrd Honiton" ones.
Exeter-Winchester has "Honiton Basingst" and "Honiton Shampton" ones; and
Exeter-Woking has "Honiton not Ldn" tickets.

This probably wouldn't be an issue once you got to the bus, but it's harder to get that far if you look on a web site which doesn't show the itinerary you need.

700809 (Circuitous Route) Due to engineering works between Crewkerne and Exeter from 15 to 23 September 2018, rail replacement bus services will be in operation. This circuitous route easement is to ensure that the normal routeing to London Paddington is maintained, and to prevent journeys from Axminster and Honiton to be valid via Exeter St Davids. This negative easement applies in both directions.​

I think this just affects Axminster-London and Honiton-London tickets, which aren't normally valid that way.

700810 (Doubleback) On Sundays passengers travelling from redditch, Alvechurch and Barnt Green to Bromsgrove, Droitwich Spa, Worcester Foregate Street and Worcester Shrub Hill may doubleback by changing at Longbridge. This doubleback easement applies in both directions​

The Barnt Green-Bromsgrove service is hourly 7 days a week, so I don't know why this new easement only applies on Sundays. Luckily it doesn't matter.

The tickets for the above routes are all either "any permitted" or "not via Birmnghm" ones. Easement 700444 lets you double back to Birmingham with the former and easement 700445 permits the latter as far as University. As you can double back that far, and none of the tickets stop you from breaking your journey, you can just use the tickets as far as Longbridge in each direction.

Removed:

700803 (Fare route) Due to the closure of London Euston station over the weekends of the 18 - 19 August 2018; 25 - 27 August 2018 and 01 - 02 September 2018. Journeys between London and Manchester, Wilmslow and Stockport will be permitted via London Kings Cross, Leeds and onward on Trans Pennine Express services via Huddersfield and Manchester Piccadilly. Tickets priced on fare route (00452) Virgin West Coast & Connections will be permitted to travel via Peterborough. This fare route easement applies in both directions

700804 (Map) Due to the closure of London Euston station over the weekends of the 18 - 19 August 2018; 26 - 27 August 2018 and 01 - 02 September 2018. Journeys between London and Manchester, Wilmslow and Stockport will be permitted via London Kings Cross, Leeds and onward on Trans Pennine Express services via Huddersfield and Manchester Piccadilly. This map easement applies in both directions​

These dates are all in the past.

 

[kieron]

An easement was removed from the routeing guide this afternoon.

It was:

700197 (Circuitous Route) Customers travelling via Melton Mowbray to/from Leicester, Market Harborough and Kettering may not travel via Loughborough. This easement applies in both directions.​

There are a lot of tickets which could be affected by this easement, but the effects are generally minor as as taking advantage means using either a Corby-Oakham train or a Melton Mowbray-Loughborough one avoiding Leicester, both infrequent.

It did mean that you couldn't start short on a Kettering-Grimsby Town ticket at Melton Mowbray. Doing this avoids the problem of all flexible Melton Mowbray-Grimsby Town tickets having a "via Peterborough" route,

This is quite an old easement, though, and there was once a Loughborough group which included the stations as far as Sileby. This meant that Leicester-Loughborough-Melton Mowbray wouldn't have been invalidated by the double back. Perhaps this easement was created to prevent something using that route.

 

[kieron]

Some more changes were published today, as follows:

Changes from 180917 (228) to 180926 (229).

Permitted Route changes:
Ash Vale (AHV) to Bridgend (BGN) gain BB+SB
Ash Vale (AHV) to Cardiff Central (CDF) gain BB+SB
Ash Vale (AHV) to Chippenham (CPM) gain BB
Ash Vale (AHV) to Didcot Parkway (DID) gain BB
Ash Vale (AHV) to Maidenhead (MAI) gain BB
Ash Vale (AHV) to Newport (Gwent) (NWP) gain BB+SB
Ash Vale (AHV) to Pontypridd (PPD) gain BB+SB
Ash Vale (AHV) to Reading Group (G24) gain BB
Ash Vale (AHV) to Swansea Group (G38) gain BB+SB
Ash Vale (AHV) to Swindon (SWI) gain BB
Ash Vale (AHV) to Twyford (TWY) gain BB
Ash Vale (AHV) to Westbury Group (G46) gain BB+WP​

These journeys now have mapped routes via Sandhurst.

Ash Vale (AHV) to Bristol Group (G05) gain BB+SB
Ash Vale (AHV) to Slough (SLO) gain BB lose MW
London Group (G01) to Salisbury (SAL) gain WW WX+BU+WW lose LE WX+BU+LE​

No effect.

Easement changes:

Removed:

700783 (Map) Due to Sunday trains from Glasgow Central being diverted via Mount Florida from 13 May to 09 September 2018, connecting services require this map easement to ensure journey opportunities are presented to customers. This easement will apply in both directions
700794 (Fare route) Due to engineering works between 12/06/2018 and 14/06/2018, customers travelling on route ' VIA TAUNTON' may travel via Castle Cary
700808 (Fare route) Due to engineering works between Crewkerne and Exeter from 15 to 23 September 2018, there will be fast rail replacement buses calling at Crewkerne, Exeter Central and Exeter St Davids. As the bus does not call/pass Honiton, this fare route easement is required to allow tickets routed (00840) Via Honiton to be valid on these rail replacement services.
700809 (Circuitous Route) Due to engineering works between Crewkerne and Exeter from 15 to 23 September 2018, rail replacement bus services will be in operation. This circuitous route easement is to ensure that the normal routeing to London Paddington is maintained, and to prevent journeys from Axminster and Honiton to be valid via Exeter St Davids. This negative easement applies in both directions.​

These are all temporary easements for which the dates have passed.

Added:

700811 (Map) Due to engineering works, Cross Country services on Sundays 21 October 2018 and 25 November 2018 will be diverted via Ash and North Camp. this map easement will allow connecting services to be shown in journey planners.​

Crosscountry trains to Guildford go this way anyway, but at least some Bournemouth trains are being diverted via Guildford on those dates as the line between Reading and Basingstoke is closed.

 

[kieron]

Some more temporary easements were published on Friday. Sorry for the delay. They read as follows:

700812 (Map) Due to engineering diversions on the 14 October 2018 via Normanton; this map easement will create temporary permitted routes for TransPennine Express trains only between Leeds and Huddersfield for journeys between Hull and Manchester/Liverpool. This easement applies in both directions.​

The line through Dewsbury is shut then, so trains are being diverted between Leeds and Huddersfield via Wakefield. I don't know the significance of Hull-Manchester and Hull-Liverpool in this description, as nationalrail.co.uk shows (as an example) Selby-Chester as being valid using the diverted trains.

700813 (Fare route) Tickets routed (00803) EVESHAM/STROUD and (00805) VIA EVESHAM will be valid via Stroud between 17 and 25 November 2018 due to station improvement works between Pershore and Morten in the Marsh. This fare route easement applies in both directions​

If I look at Basingstoke-Worcester journeys on those dates, nationalrail.co.uk only offers "via Evesham/Stroud" tickets via Stroud rather than the cheaper "via Evesham" ones. There is no mapped route between Basingstoke and Worcester via Stroud, so perhaps it's not following the "an easement lets me go via Stroud, so I can check Basingstoke-Stroud and Stroud-Worcester routes" logic.

700814 (Fare route) During engineering works affecting journeys into London Paddington between 23 and 30 December 2018 and 01 January 2019, tickets routed (00803) EVESHAM/STROUD, (00805) VIA EVESHAM and (00807) VIA STROUD will be valid on journeys to London Euston and London Marylebone via Birmingham and Oxford. This fare route easement applies in both directions

700815 (Map) During engineering works affecting journeys into London Paddington between 23 and 30 December 2018 and 01 January 2019, tickets routed (00803) EVESHAM/STROUD, (00805) VIA EVESHAM and (00807) VIA STROUD will be valid on routes to London Euston and London Marylebone via Birmingham and Oxford. This map easement applies in both directions​

There are no service changes in the timetable for those dates, but there must be engineering works somewhere between Gloucester and London then.

 

[Paul Kelly]

700813 (Fare route) Tickets routed (00803) EVESHAM/STROUD and (00805) VIA EVESHAM will be valid via Stroud between 17 and 25 November 2018 due to station improvement works between Pershore and Morten in the Marsh. This fare route easement applies in both directionsIf I look at Basingstoke-Worcester journeys on those dates, nationalrail.co.uk only offers "via Evesham/Stroud" tickets via Stroud rather than the cheaper "via Evesham" ones. There is no mapped route between Basingstoke and Worcester via Stroud, so perhaps it's not following the "an easement lets me go via Stroud, so I can check Basingstoke-Stroud and Stroud-Worcester routes" logic.

Correct. I don't think any journey planners are smart enough to know they can do a split route check at Stroud on a VIA EVESHAM fare because of the easement allowing it to be used via Stroud. Maybe they should be, though.

 

[_toommm_]

I see my dodgy ticket still hasn't been removed, even after having it reported twice now