NRG (National Routeing Guide) Changes

[infobleep]

A most interesting change was made to the NRG yesterday.

The heading of Section E, the easements list, used to read:

"Easements are relaxations of Routeing Guide rules to allow journeys that strict adherence to the rules would forbid. Some previously published easements are no longer exceptions to Routeing Guide rules and have therefore been deleted as unnecessary."​

Yesterday, the easements list was split in two (the first half now comprising 'positive easements', and the second half comprising 'negative easements') and the heading was changed to read:

"An easement which extends permission is a positive easement. An easement which narrows permission is a negative easement. Map, double-back and fare route easements are always positive. Circuitous route easements are always negative. Other kinds of easements can be positive or negative. A journey which follows a route otherwise permitted by the Routeing Guide may be forbidden by a negative easement."​

The explanation of easements in Section F (the 'more information' instructions, which has been frequently amended over the years with no oversight by the DfT), has also been reworded, although there is no change of substance. Section A (the main instructions) has not changed, and still doesn't refer to negative easements.

The ATOC website describes this change as "Changes have been made to Section E - The list of Easements".

The new text is far clearer. Is is legally correct in what it says?

 

[kieron]

Leaving aside the layout of the easement list and the NRG in detail file, there have been a number of other changes. I've indented text from the summary and the easement list below.

Following a review of the use of map BY, the following changes have been deployed. Replacing map BY with map BB for routes from Derby Group.​

... means that you can no longer travel via Narborough en route to Lichfield, Rugeley or Walsall, only via Burton-on-Trent.

A new Local easement has been required to compliment the Routeing Point easement 700546. This was necessary as Journey Planners interpret the Routeing Guide data sets differently.

Added

700551: Customers travelling from Frodsham to Winsford may travel via Chester and Crewe. This easement applies in both directions.​

This seems to say exactly the same thing 700546 did when that was introduced last month. I wonder why both are still around.

To correct the interpretation of Routeing Guide data by Journey Planners the following changes to easements have been required.

Deleted

030157: WO3951 Journeys from Sheffield to Buxton line - allow double back between Hazel Grove and Stockport

Amended

030192: Customers travelling via Sheffield to stations on the Buxton line may doubleback between Stockport and Hazel Grove. This easement applies in both directions.​

30192 used to just be "to Buxton", so this should have no effect on validity.

 

[RailLurker]

Kieron, I think there's something wrong with your comparison - the listed easements have not changed.

 

[adrock1976]

Leaving aside the layout of the easement list and the NRG in detail file, there have been a number of other changes. I've indented text from the summary and the easement list below.

Following a review of the use of map BY, the following changes have been deployed. Replacing map BY with map BB for routes from Derby Group.​

... means that you can no longer travel via Narborough en route to Lichfield, Rugeley or Walsall, only via Burton-on-Trent.

A new Local easement has been required to compliment the Routeing Point easement 700546. This was necessary as Journey Planners interpret the Routeing Guide data sets differently.

Added

700551: Customers travelling from Frodsham to Winsford may travel via Chester and Crewe. This easement applies in both directions.​

This seems to say exactly the same thing 700546 did when that was introduced last month. I wonder why both are still around.

To correct the interpretation of Routeing Guide data by Journey Planners the following changes to easements have been required.

Deleted

030157: WO3951 Journeys from Sheffield to Buxton line - allow double back between Hazel Grove and Stockport

Amended

030192: Customers travelling via Sheffield to stations on the Buxton line may doubleback between Stockport and Hazel Grove. This easement applies in both directions.​

30192 used to just be "to Buxton", so this should have no effect on validity.

Meanwhile, they have made a lot of other changes without any explanation.
The following have lost the statement "This easement applies in both directions":

030005 Customer travelling to or from Gatwick Airport to the north may travel via Earlswood. I assume this refers to the Earlswood in Sussex and not the one in Warwickshire/West Midlands.
030031 Journeys from Wellingborough to Luton and beyond may travel via Bedford (Midland). This has left me puzzled as both Wellingborough and Luton are on the main line of the Midland Railway, and you already pass through Bedford on the way to Luton from points north of Bedford.
030152 WO 4258 Error 16 journey around Barry and Bridgend via Cardiff.
030213 Customers travelling from Martins Heron to Reading and beyond may travel via Wokingham. Ditto. You pass through Wokingham on the way to Reading anyway.
030246 Customers travelling from Aylesford, New Hythe and Snodland to London Terminals may not travel via Ashford International.
700220 Customers travelling via Audley End to Stansted Airport amy double back between Stansted Mountfitchet and Bishops Stortford.
700241 Customers travelling from or via Barton On Humber to Hessle, Ferriby, Brough and beyond may not travel via Hull. Is this to prevent a doubleback? As both Barton on Humber and Hull are on opposite sides of the mighty Humber, there is no requirement to double back via Hull as you will already be passing through or calling at Hessle, Ferriby, and Brough.
700250 Customers travelling from Bury St Edmunds to Ipswich and beyond may travel via Stowmarket.
700255 Customers travelling from or via Bury St Edmunds to Norwich and beyond may double back between Stowmarket and Ipswich.
700305 Customers travelling from Loughborough to Langley Mill or Alfreton may travel via Nottingham.
700306 On 26th December 2012 customers travelling from Reading to London Terminals may not travel on the Railair bus via Gatwick Airport. 2012? I'm puzzled. Unless it's a typo which should be 2014?
700364 Customers travelling from Cholsey or Didcot Parkway to London Waterloo may not travel via Winchester. The sensible route would be via Basingstoke and Woking, or Reading and Wokingham/the 2 Windsor & Eton stations and Staines.
700514 Passengers travelling from or via Peterborough to Hitchin may doubleback at Stevenage.
700521 Passengers travelling from Newington via Sole Street may travel via Gillingham (Kent).
700522 Passengers travelling from Frimley to or via London Waterloo may travel via Ascot.
700525 Passengers travelling from Margate; Broadstairs and Dumpton Park via Canterbury West may travel via Ramsgate.
700526 Passengers travelling from Bracknell via Reading may travel via Wokingham.
700546 To allow travel from Frodsham to Winsford via Chester and Crewe, this easement overrides the fares checking rules.
700548 To allow Skipton to Inverness & beyond via East Coast using fare route EC &Connections (00430) or XC & Connections (00439) this positive Routeing Point easement has been deployed to over rule fares checking in Journey planning systems.​

These each had a list of route codes, but don't now:

700013 Tickets with the following route codes may be used to double back between Clapham Junction and London Victoria.
700014 Tickets with the following route codes may be used to double back between Clapham Junction and London Waterloo.​

And these have been made more restrictive:

700303 Customers travelling from or via London Kings Cross to Carlisle and beyond using fares routed "Any Permitted" may not travel via Newcastle. This easement applies in both directions.
700432 Customers travelling from or via London Kings X to Carlisle and beyond using fares routed "Any Permitted" may not travel via Newcastle.​

The first of these used to apply Monday-Friday, the second on Saturday and Sunday, but only until just over a year ago. Now they're identical.

My comments in red above.

Cheers

Adam

 

[kieron]

Kieron, I think there's something wrong with your comparison - the listed easements have not changed.

Sorry, I don't know what happened there (other than me not checking against the PDFs before I posted, I mean). I've removed them now.

 

[tsr]

I'm a bit confused about Easement 030005. Why would you not be able to travel from Gatwick to "the North" via Earlswood (Surrey)? It's realistically the only route which you would probably want to use in normal circumstances (notwithstanding the three or so journeys I have EVER come across where it obscurely happened to be quicker - yes, I know, special timetables - to change at Horsham, Dorking and Reading) and people have done it for decades without hassle. I can only assume it is to fix an issue clearly and concisely with some sort of electronic system.

P.S. Earlswood is in Surrey (and basically an outer suburb of Redhill, one of the largest towns in East Surrey).

 

[Paul Kelly]

I suspect Gatwick Airport was not always a routeing point in itself as it is now. Easement 30005's effect would be to have confirmed Redhill group (of which Earlswood is a member) as an appropriate routeing point even if the fares check failed.

Not sure why it might have failed - maybe due to special promotional fares to Gatwick being cheaper than those to Redhill, back in the days when the fares check had to be done using the ticket type being travelled on?

 

[tsr]

I suspect Gatwick Airport was not always a routeing point in itself as it is now. Easement 30005's effect would be to have confirmed Redhill group (of which Earlswood is a member) as an appropriate routeing point even if the fares check failed---which it likely might have done, given that fares to/from Gatwick were likely to have been pumped up beyond those to surrounding stations given its status as a popular destination.

Interesting stuff - thanks - I hadn't thought of it that way!

 

[Paul Kelly]

I got my logic with the fares check the wrong way round, hence the edit to my post, but I still think it could be something along those lines. I also think the easement is redundant now that Gatwick is a routeing point.

 

[Greeby]

Latest data dump

New Dataset RJRG0328 published 19/11/2014

Map sequences removed or amended following the end of the FTPE club 55 promotion, (see easements for deletion of controlling easement associated with these map sequences)
Map Sequences Added
Barnetby (BTB) and Carlisle (CAR) - added sequence 'DO+GN'
Barnetby (BTB) and Carlisle (CAR) - added sequence 'DO+NP+GP'
Barnetby (BTB) and Carlisle (CAR) - added sequence 'EE+NP+GP'
Carlisle (CAR) and Habrough (HAB) - added sequence 'GN+DO'

Map sequences removed
Barnetby (BTB) and Carlisle (CAR) - removed sequence 'DS+NP+GP'
Barnetby (BTB) and Carlisle (CAR) - removed sequence 'GD+HX'
Barnetby (BTB) and Newcastle (NCL) - removed sequence 'DW+MN'
Carlisle (CAR) and Darlington (DAR) - removed sequence 'MG+MT'
Carlisle (CAR) and Habrough (HAB) - removed sequence 'HX+GD'
Carlisle (CAR) and SCARBOROUGH GROUP (G48) - removed sequence 'MG+MN'
Habrough (HAB) and Newcastle (NCL) - removed sequence 'DW+MN'

To remove map sequences that generated circuitous routes the following amendments have been made between London Group and Routeing Points on the Trent Valley route and North Wales coast route.
Map sequences added
Crewe (CRE) and LONDON GROUP (G01) - added sequence 'BV+BG+MM'
Crewe (CRE) and LONDON GROUP (G01) - added sequence 'BV+GC'
LONDON GROUP (G01) and Rugeley Trent Valley (RGL) - added sequence 'GC+BP'
LONDON GROUP (G01) and Rugeley Trent Valley (RGL) - added sequence 'GC+TL'
LONDON GROUP (G01) and Stoke On Trent (SOT) - added sequence 'GC+BV+TL'
LONDON GROUP (G01) and Stoke On Trent (SOT) - added sequence 'SF+TL'
Map sequences removed
Chester (CTR) and LONDON GROUP (G01) - removed sequence 'JO+LC'
Crewe (CRE) and LONDON GROUP (G01) - removed sequence 'BJ+GC'
Crewe (CRE) and LONDON GROUP (G01) - removed sequence 'LC+BG+MM'
Crewe (CRE) and LONDON GROUP (G01) - removed sequence 'WS+GC'
LONDON GROUP (G01) and Llandudno Junction (LLJ) - removed sequence 'LC+JO'
LONDON GROUP (G01) and Rugeley Trent Valley (RGL) - removed sequence 'GC+WS'
LONDON GROUP (G01) and Stoke On Trent (SOT) - removed sequence 'GC+BV'
LONDON GROUP (G01) and Stoke On Trent (SOT) - removed sequence 'GC+TM'
LONDON GROUP (G01) and Stoke On Trent (SOT) - removed sequence 'LC'

To reinstate routes to Richmond (London) from Crewkerne that were removed in error when maps were redrawn in 2013, the following changes have been made.
Map sequences added
EXETER GROUP (G12) and Richmond London (RMD) - added sequence 'LE'
Richmond London (RMD) and Salisbury (SAL) - added sequence 'TW+WW'

EASEMENTS
24 Easements have been deleted. These have been deleted as their WEU (week effective until) dates had expired (many because they were created for engineering works), and therefore the data was ignored by Journey Planning systems.
Removed 030070: Journeys between Durham, Chester-le-Street and Northallerton may travel via Eaglescliffe. This easement applies in both directions.
Removed 030081: Services between Manchester Piccadilly and Manchester Airport routed TPE only and AP TPE only, may travel on replacement bus services operated by Nothern Rail. This easements applies in both directions.
Removed 040001: Journeys to and from the Burnley area via Doncaster may not use the SVS/SVR routed Any Permitted when travelling towards Stevenage and London
Removed 700019: During Wimbledon Tennis Tournament, customers in possession of tickets routed AP London Woking, AP London Honiton and London Not Underground may travel via Wimbledon.
Removed 700081: During the period 27th December 2010 to 03rd January 2011 inclusive, customers travelling from Pewsey, Bedwyn, Hungerford, Kintbury, Newbury, Newbury Racecourse, Thatcham, Midgham, Aldermaston and Theale to Salisbury and beyond may travel via Westbury. This easement applies in both directions.
Removed 700110: Customers travelling between Redhill and Tonbridge may travel via East Croydon. This easement applies during periods of Engineering Work Operations only.
Removed 700158: Customers travelling from Adwick to Brighouse in possession of tickets routed 'Any Permitted' may not travel via Leeds. This easement applies in both directions.
Removed 700183: During the period 14th - 27th August 2011 customers travelling from Bicester North,Haddenham, Princes Risborough, Saunderton, High Wycombe, Beaconsfield, Seer Green, Gerrards Cross, Denham Golf Club, Denham, West Ruislip and South Ruislip via London Paddington, may travel via Greenford. This easement applies in both directions.
Removed 700184: During the period 06-22 August 2011 customers travelling from Malvern Link, Great Malvern, Colwall or Ledbury via Abergavenny, Newport and Bristol Parkway may travel via Hereford. This easement applies in both directions.
Removed 700298: During the period 29/10/12 to 03/11/12 inclusive, customers travelling from Huddersfield via Sowerby Bridge may double back between Mirfield, Ravensthorpe and Dewsbury. This easement applies in both directions.
Removed 700302: During Engineering Works (weekends up to 21/10/12 inclusive) customers travelling from Laindon and Basildon via Grays may travel via Pitsea. This easement applies in both directions.
Removed 700306: On 26th December 2012 customers travelling from Reading to London Terminals may not travel on the Railair bus via Gatwick Airport. This easement applies in both directions
Removed 700364: Customers travelling from Cholsey or Didcot Parkway to London Waterloo may not travel via Winchester. This easement applies in both directions
Removed 700384: During the period 12 April to 15 April 2014 inclusive, customers in possession of tickets with the following route codes "LONDN STRD/EVSHM", "RDG STRD INC LDN", " VIA STROUD", "EVESHAM/STROUD", "AP KEMBL NOT LDN" and "AP KEMBLE SLOUGH" may travel via Bristol Parkway. This easement applies in both directions.
Removed 700395: During the period 09 August to 02 September 2013 (inclusive), customers in possession of tickets with the following route codes "LONDN STRD/EVSHM", "RDG STRD INC LDN", "VIA STROUD", "EVESHAM/STROUD", "AP KEMBL NOT LDN" and "AP KEMBLE SLOUGH" may travel via Birmingham New Street. This easement applies in both directions.
Removed 700422: During Engineering weeks at weekends (14 Sept - 19 Oct 2013 inclusive). Customers travelling via Reading to Reading West and beyond may double back between Reading and Tilehurst. This easement applies in both directions.
Removed 700432: Customers travelling from or via London Kings X to Carlisle and beyond using fares routed "Any Permitted" may not travel via Newcastle. This easement applies Saturdays and Sundays inclusive until 03 November 2013
Removed 700443: During the period 27th December 2013 to 01 January 2014 (inclusive), customers in possession of tickets routed "Newbury" may travel via Swindon.
Removed 700455: Customers travelling from stations Bishop Stortford to Broxbourne inclusive to London Liverpool Street and beyond may not travel via Stansted Airport.This easement applies in both directions.
Removed 700456: During the period 18/1/14 to 9/2/14 customers in possession of fares routed "via Taunton" may travel via Honiton and Yeovil Junction, Yeovil Pen Mill. This is due to Engineering works.
Removed 700468: During the period 22/12/13 to 5/1/14 (inclusive) customers travelling from Higham to Hither Green and beyond may travel via Strood. This easement applies in both directions.
Removed 700517: During Engineering Works on Sundays 08/06/2014 to 27/07/2014, journeys routed 'Via Newbury' may go via Swindon.
Removed 700518: During engineering works from 02/08/2014 to 03/08/2014, customers travelling with tickets routed 'Not Via Reading' may travel via Reading. This easement excludes journeys between London and the Thames Valley area and also excludes journeys between Pewsey - Newbury and the West (Devon and Cornwall).
Removed 700535: Customers travelling from Newcastle and stations south of Newcastle to stations North West of Manchester or Newcastle to stations in the South Pennines or South Humberside may travel via Manchester on 'Club 55' promotion tickets routed 00085 'TPE ONLY'. This easement applies in both directions.

Easement total 628 easement(s) (previously: 652)
Circuitous Route: 258 (previously 265)
Doubleback: 86 (previously 88)
Fare route: 10 (previously 18)
Local: 57 (previously 58)
Manual: 15 (previously 15)
Map: 0 (previously 1)
Routeing Point: 202 (previously 207)

Currently fishing through the West Coast stuff, as what actual routes are now prohibited isn't easy to see

 

[krus_aragon]

Interesting to see that changes have been made to the (relatively) new Llandudno Jn routeing point, but not Shotton.

I really must pull my finger out some point and work out what difference the introduction of the LLJ routeing point made....

 

[John @ home]

I really must ... work out what difference the introduction of the LLJ routeing point made.

It seems to me that, prior to the introduction of Llandudno Jn routeing point, a Holyhead - Llandudno ticket was permitted via Shotton on direct Holyhead - Shotton and Shotton - Llandudno trains.

Finding a permitted route when the origin and destination stations have a routeing point in common.

If there is a common routeing point, the permitted route is the shortest route or a route which is longer by no more than 3 miles. Also permitted is the route followed by direct trains to and from the common routeing point if the journey is made on those trains.

http://iblocks-rg-publication.s3-website-eu-west-1.amazonaws.com/nrg_detail.pdf

 

[Bletchleyite]

It seems to me that, prior to the introduction of Llandudno Jn routeing point, a Holyhead - Llandudno ticket was permitted via Shotton on direct Holyhead - Shotton and Shotton - Llandudno trains.

Why would that be the case? It's a clear double-back.

Neil

 

[Paul Kelly]

Why would that be the case? It's a clear double-back.

The "direct trains to and from a common routeing point" rule. Page 7 of Section F of the Routeing Guide. It's also in the instructions on how to implement the routeing guide issued to developers of computerised booking engines.
Edit: as already quoted by John@Home above (I didn't notice!)

 

[Bletchleyite]

The "direct trains to and from a common routeing point" rule. Page 7 of Section F of the Routeing Guide. It's also in the instructions on how to implement the routeing guide issued to developers of computerised booking engines.
Edit: as already quoted by John@Home above (I didn't notice!)

Common Routeing Points
If the origin and destination have a common routeing point, the permitted route is direct via the
shortest distance from the origin to the destination over which a regular scheduled passenger
train service operates. No doubling back (passing through the same station twice on a single
journey) is allowed which may require customers to change trains short of the routeing point,
unless an easement allows a longer alternative route.

http://iblocks-rg-publication.s3-website-eu-west-1.amazonaws.com/nrg_instructions.pdf

That said, that rather conflicts with this:
http://iblocks-rg-publication.s3-website-eu-west-1.amazonaws.com/nrg_detail.pdf

to which you refer, on which the page 7 example indeed suggests a double-back as acceptable via Birmingham rather than changing at Tyseley.

So you appear to be correct.

Neil

 

[Greeby]

Having looked through it now, the gist seems to be:

Chester and North Wales line no longer valid via Warrington
Stoke-on-Trent no longer valid via Crewe
The Crewe and Rugeley bits, I can't see what's prohibited, which probably means it's some circular journey in the West Midlands that few, if any, passengers would actually bother to do.

 

[kieron]

Interesting to see that changes have been made to the (relatively) new Llandudno Jn routeing point, but not Shotton.

I really must pull my finger out some point and work out what difference the introduction of the LLJ routeing point made....

There are 4 routeing points with different routes listed from/to each (Crewe, London, Salisbury and Woking), as well as another 119 points which can be accessed via London. Llandudno Junction-Salisbury is valid going into London via Clapham Junction, but Shotton has more journey options otherwise.

Map sequences removed or amended following the end of the FTPE club 55 promotion, (see easements for deletion of controlling easement associated with these map sequences)

Barnetby (BTB) and Newcastle (NCL) - removed sequence 'DW+MN'
Habrough (HAB) and Newcastle (NCL) - removed sequence 'DW+MN'​

No longer valid via Manchester, or on trains via Guide Bridge and Stalybridge.

There are a few other changes which were put in the same section of the summary, but have nothing to do with the temporary changes made last month.

Barnetby (BTB) and Carlisle (CAR) - added sequence 'DO+GN'
Barnetby (BTB) and Carlisle (CAR) - added sequence 'DO+NP+GP'
Barnetby (BTB) and Carlisle (CAR) - added sequence 'EE+NP+GP'
Barnetby (BTB) and Carlisle (CAR) - removed sequence 'DS+NP+GP'
Barnetby (BTB) and Carlisle (CAR) - removed sequence 'GD+HX'​

Lose validity via Scotland, Goole and Yarm. Gain via Barnsley and on Grand Central's route between Doncaster and Pontefract (although you can't use the train as far as Mirfield).

Carlisle (CAR) and Habrough (HAB) - added sequence 'GN+DO'
Carlisle (CAR) and Habrough (HAB) - removed sequence 'HX+GD'​

No extra routes, but you can't go via Scotland or Yarm anyway.

Carlisle (CAR) and Darlington (DAR) - removed sequence 'MG+MT'
Carlisle (CAR) and SCARBOROUGH GROUP (G48) - removed sequence 'MG+MN'​

No longer valid via Manchester.

To remove map sequences that generated circuitous routes the following amendments have been made between London Group and Routeing Points on the Trent Valley route and North Wales coast route.

Crewe (CRE) and LONDON GROUP (G01) - added sequence 'BV+BG+MM'
Crewe (CRE) and LONDON GROUP (G01) - added sequence 'BV+GC'
Crewe (CRE) and LONDON GROUP (G01) - removed sequence 'BJ+GC'
Crewe (CRE) and LONDON GROUP (G01) - removed sequence 'LC+BG+MM'
Crewe (CRE) and LONDON GROUP (G01) - removed sequence 'WS+GC'​

No longer valid via Cheadle Hulme, Rugby-Nuneaton (the "wrong" way) or Coventry-Nuneaton-Leicester. A few other routes in the West Midlands have been gained and lost, but they're the main changes.

LONDON GROUP (G01) and Stoke On Trent (SOT) - added sequence 'GC+BV+TL'
LONDON GROUP (G01) and Stoke On Trent (SOT) - added sequence 'SF+TL'
LONDON GROUP (G01) and Stoke On Trent (SOT) - removed sequence 'GC+BV'
LONDON GROUP (G01) and Stoke On Trent (SOT) - removed sequence 'GC+TM'
LONDON GROUP (G01) and Stoke On Trent (SOT) - removed sequence 'LC'​

No longer valid via Cheadle Hulme. Again, there are a few other West Midlands routes gained and lost.

LONDON GROUP (G01) and Rugeley Trent Valley (RGL) - added sequence 'GC+BP'
LONDON GROUP (G01) and Rugeley Trent Valley (RGL) - added sequence 'GC+TL'
LONDON GROUP (G01) and Rugeley Trent Valley (RGL) - removed sequence 'GC+WS'​

No longer valid via Stafford. Instead, valid both ways through Coleshill Parkway and between Coventry and Rugby, as well as a few other routes in the West Midlands.

Chester (CTR) and LONDON GROUP (G01) - removed sequence 'JO+LC'
LONDON GROUP (G01) and Llandudno Junction (LLJ) - removed sequence 'LC+JO'​

No longer valid via Warrington.

To reinstate routes to Richmond (London) from Crewkerne that were removed in error when maps were redrawn in 2013, the following changes have been made.

EXETER GROUP (G12) and Richmond London (RMD) - added sequence 'LE'​

No effect (although it's not relevant to a Richmond-Crewkerne journey anyway).

Richmond London (RMD) and Salisbury (SAL) - added sequence 'TW+WW'​

Allows journeys via Clapham Junction avoiding London, as well as journeys via Hounslow.

EASEMENTS

24 Easements have been deleted. These have been deleted as their WEU (week effective until) dates had expired (many because they were created for engineering works), and therefore the data was ignored by Journey Planning systems.​

I'm not convinced of the logic behind "they're not in our electronic routeing guide, so they shouldn't be in the public one". Most of these do have an end date in the text which has passed, anyway (indeed, some passed before they were first published). Those which don't have an end date are:

Removed 030070: Journeys between Durham, Chester-le-Street and Northallerton may travel via Eaglescliffe. This easement applies in both directions.

Removed 030081: Services between Manchester Piccadilly and Manchester Airport routed TPE only and AP TPE only, may travel on replacement bus services operated by Nothern Rail. This easements applies in both directions.

Removed 040001: Journeys to and from the Burnley area via Doncaster may not use the SVS/SVR routed Any Permitted when travelling towards Stevenage and London

Removed 700019: During Wimbledon Tennis Tournament, customers in possession of tickets routed AP London Woking, AP London Honiton and London Not Underground may travel via Wimbledon.

Removed 700110: Customers travelling between Redhill and Tonbridge may travel via East Croydon. This easement applies during periods of Engineering Work Operations only.

Removed 700158: Customers travelling from Adwick to Brighouse in possession of tickets routed 'Any Permitted' may not travel via Leeds. This easement applies in both directions.

Removed 700364: Customers travelling from Cholsey or Didcot Parkway to London Waterloo may not travel via Winchester. This easement applies in both directions

Removed 700455: Customers travelling from stations Bishop Stortford to Broxbourne inclusive to London Liverpool Street and beyond may not travel via Stansted Airport.This easement applies in both directions.​

Apart from this, they've also changed a number of easements to look more like English sentences. These include:

30152: WO 4258 Error 16 journey around Barry and Bridgend via Cardiff. For fares route Any Permitted​

to

30152: To allow journeys, for fares route Any Permitted, between Cardiff to Bridgend and beyond to travel via Dinas Powys (not the shortest route). This easement applies in both directions​

,

30154: WO4350 to allow doubleback when the error is 74 or 75 Dilton Marsh to Westbury via Warminster​

to

30154: to allow the doubleback Dilton Marsh to Westbury via Warminster, even though the fare for the doubleback through the origin/destination is higher than the overall fare. this easement applies in both directions.​

,

30155: WO 4334 Shipley to Runcorn, double back via Liverpool Lime Street.​

to

30155: Shipley to Runcorn, double back via Liverpool Lime Street.​

(I suppose one of the benefits of the new style easements file is that you can tell whether this is allowing you to double back or preventing you from doing so simply by looking at the page header),

30156: WO4475 journey to/from Pokesdown allowing a doubleback from Bournmouth.​

to

30156: For journeys to Pokesdown and Christchurch via Southampton Central may doubleback from Bournmouth. This easement applies in both directions​

, and

30160: WO4333 Error 16 at Romsey and Eastleigh for journeys Romsey to Winchester​

to

30160: For journeys, Romsey to Winchester, to be shown in Journey Planners which do not follow the shortest route​

(I suppose you'd have to check a Journey Planners to find out which routes which do not follow the shortest route are permitted by this easement).​