National Routeing Guide update

[kieron]

Some more changes were made to the routeing guide this week. The following changes were published on Tuesday:

New data set 0516 published 15/05/18

Comparing RJRG0516 to RJRG0515

Map sequence added to match Scotrail local instructions

Aberdeen (ABD) and EDINBURGH GROUP (G11) - added sequence 'IP+FD'​

This now has mapped routes via Perth.

GLASGOW GROUP (G13) and Inverness (INV) - added sequence 'GA+IP'​

This now has mapped routes via Aberdeen.

Simplified map permission additions using single map

READING GROUP (G24) and Lewes (LWS) - added sequence 'XC'
BRIGHTON GROUP (G04) and READING GROUP (G24) - added sequence 'XC'

Simplified map permissions sequences removed

READING GROUP (G24) and Lewes (LWS) - removed sequence 'RG+XC'
BRIGHTON GROUP (G04) and READING GROUP (G24) - removed sequence 'XC+RG'​

These journeys now have mapped routes using the North Downs line via Guildford.

EALING BROADWAY GROUP (G77) and Staines (SNS) - removed sequence 'WR'
Feltham (FEL) and Slough (SLO) - removed sequence 'WU+WR'
HAYES & HARLNGTN GP (G75) and Staines (SNS) - removed sequence 'WR'
Slough (SLO) and Staines (SNS) - removed sequence 'WR'​

These journeys no longer have mapped routes via Windsor.

Local easement added to match Scotrail local instructions

700784: Holders of tickets from Kyle of Lochalsh to either Glasgow or Edinburgh, may join trains at Mallaig. They will need to make their own arrangements to travel between Kyle of Lochalsh and Mallaig, as railway tickets are not valid on bus and ferry connections between the two locations.

This manual easement will not operate in online journey planning systems.​

That sounds fairly straightforward (or, at least, it would be if I knew how much of "Glasgow" this covers), but why would it not be incorporated into journey planners? Particularly when the National Routeing Guide is supposed to be incorporated into the data used to support the Journey Planner on the National Rail website?

easement(s) changed for the opening of Kenilworth station

030038: Journeys routed (00211) VIA COVENTRY may travel via Dorridge, with the exception of journeys to and from Kenilworth. This fare route easement applies in both directions.​

This has had the Kenilworth bit added. I think this is saying that the easement doesn't give you any special privileges if you're going to Kenilworth, rather than that you can't go via Dorridge at all.

I don't know what tickets this affects at the moment, though. There were no VIA COVENTRY fares to Kenilworth in the January fare list, and the May one hasn't been made available to the public yet.

In addition to the above changes, there were a number of changes to maps which weren't included in the RDG's summary:

CO: Lose London Group to/from Witham
CO: Lose Stratford London Gp to/from Witham
EA: Lose London Group to/from Witham
EA: Lose Stratford London Gp to/from Witham​

These were added to support rail replacement buses which ran to Ingatestone. There should always be something published about ticket acceptance for when that happens, so that these links aren't needed.

FW: Lose Dalmuir to/from Glasgow Group
FW: Lose Glasgow Group to/from Westerton​

Dalmuir-Glasgow is another route which was added to cover for engineering works. These ones have long since finished.

Glasgow-Westerton is a bit odd, as that covers the main route between Glasgow Queen Street High Level and Dalmuir (and further west). I'm not saying that a ticket from Glasgow to Oban isn't valid with one change at Crianlarich, but it isn't clear to me that it should be a valid route.

GK: Lose Glasgow Group to/from Westerton
GO: Lose Glasgow Group to/from Westerton
SR: Lose Glasgow Group to/from Westerton
WN: Lose Glasgow Group to/from Westerton​

The Glasgow-Westerton link has been removed from every map which included it.

RA: Lose Swanley to/from Sevenoaks
SV: Lose Swanley to/from Sevenoaks​

This was added last year for some engineering works, as ticket sites treated trains which went non-stop through Otford as if they hadn't gone there. This diversion has since finished.

WR: Lose Slough to/from Staines​

This removes Staines from the map. There are no longer any maps which include a route through Windsor, so someone with (say) an Ash Vale-Worcester ticket can't go that way.

YK: Lose Leeds Group to/from Hellifield Group​

Hellifield was added to the map in December 2015, and has now been removed again. I don't know if anything ever used this section.
:
The following changes were published this afternoon:

New data set 517 published 18/05/18

Comparing revision RJRG0517 to RJRG0516

To ensure journeys are valid via Wigan after the 20 May Timetable change the following map sequences have been changed

3 sequence(s) added
Barnetby (BTB) and Preston (Lancs) (PRE) - added sequence 'DW+KM'
Habrough (HAB) and Kirkham And Wesham (KKM) - added sequence 'DW+KM'
Habrough (HAB) and Preston (Lancs) (PRE) - added sequence 'DW+KM'

3 sequence(s) removed
Barnetby (BTB) and Preston (Lancs) (PRE) - removed sequence 'DW+KW'
Habrough (HAB) and Kirkham And Wesham (KKM) - removed sequence 'DW+KW'
Habrough (HAB) and Preston (Lancs) (PRE) - removed sequence 'DW+KW'​

These routes no longer have mapped routes via Warrington.
They now have mapped routes via Eccles.

They still don't have any mapped routes via Walkden, even though a few Manchester-Blackpool trains will go that way.

To add a link between Wakefield Group and Doncaster routeing points on Map PY

Map PY - PLYMOUTH TO YORK changed (1 added/ 0 removed links)​

I can think of a few routes where this could be used, but none where it would be particularly useful. Routes from Leeds and Wakefield use PL instead, so it's no good for those. I'm sure there's something out there, though.

2 easement(s) added for engineering works

Added 700785: During engineering works between 04-07 June 2018, 09-12 July 2018, 16 July to 05 August 2018, 08-11 October 2018 and 19-22 November 2018, journeys from Warminster, Frome, Dilton Marsh and Westbury to Reading and London Paddington priced on fare route (00063) VIA NEWBURY are permitted on journeys via Swindon. This fare route easement applies in both directions​

The line between Theale and Pewsey will be closed then, so this allows people to use cheaper tickets on the diverted trains.

Added 700786: During engineering works between 04-07 June 2018, 09-12 July 2018, 16 July - 05 August 2018, 08-11 October 2018 and 19-22 November 2018 passengers from Pewsey to Reading and London Paddington on tickets routed (00000) ANY PERMITTED, may travel via Westbury, Bath Spa, Chippenham and Swindon. This map easement applies in both directions.​

Looking at the dates in June, all that's running from Pewsey are buses to Newbury, Swindon and Westbury, with the Newbury ones just connecting to other buses further down the line. Given the choice, you probably wouldn't catch a Westbury one. It may be more appealing on other dates, though.

 

[adrock1976]

easement(s) changed for the opening of Kenilworth station

030038: Journeys routed (00211) VIA COVENTRY may travel via Dorridge, with the exception of journeys to and from Kenilworth. This fare route easement applies in both directions.This has had the Kenilworth bit added. I think this is saying that the easement doesn't give you any special privileges if you're going to Kenilworth, rather than that you can't go via Dorridge at all.

I don't know what tickets this affects at the moment, though. There were no VIA COVENTRY fares to Kenilworth in the January fare list, and the May one hasn't been made available to the public yet.

I had purchased a Tile Hill - Kenilworth Day Return a couple of weeks ago and noticed that it had "Route: via Coventry" in that section of the ticket. Perhaps the "via Coventry" fares are already loaded on the machines that the guards use on the former London Midland routes?

 

[kieron]

I had purchased a Tile Hill - Kenilworth Day Return a couple of weeks ago and noticed that it had "Route: via Coventry" in that section of the ticket. Perhaps the "via Coventry" fares are already loaded on the machines that the guards use on the former London Midland routes?

The fares have been added to the systems used by train companies, as they can be changed from one day to the next. The fares made available to download by the general public are updated less frequently.

All I would have liked to have done was to bring up a map showing where has "via Coventry" fares defined to Kenilworth, and see if there are any for which expecting someone to actually go via Coventry would cause any hardship. They weren't in the data I had, so I couldn't.

I notice that the list on brfares.com was updated this morning, and the number of places it had fares defined to from Kenilworth went from 1666 to 2664. From the list, it looks as though this include almost everywhere, the exceptions being to stations in Ireland and a few locations used for advance fares in the north of England.

 

[kieron]

A few more changes were published yesterday.

New data set 0518 published 21/05/18

Comparing revision RJRG0518 to RJRG0517

Changes to map permissions, and Map KM as a result of changes to timetables in May 2018

Barnetby (BTB) and Kirkham And Wesham (KKM) - added sequence 'DW+KM'
Barnetby (BTB) and Kirkham And Wesham (KKM) - removed sequence 'DW+KW'
​

This journey no longer has mapped routes via Warrington.
It now has mapped routes which go through Atherton and Ince.

Map KM - KIRKHAM & WESHAM TO MANCHESTER VIA PRESTON changed (1 added link between Wigan Group G34 and Salford Crescent SLD routeing points)
​

This map already contained a route between Manchester and Wigan via Eccles.

The change means that (for example) a Salford-Preston ticket is now valid using the line between Salford Crescent and Wigan.

Easement changed to clarify that Scotrail local instructions only apply to Scotrail services.

2 change(s) in 700784: Holders of tickets from Kyle of Lochalsh to either Glasgow or Edinburgh, may join Scotrail only operated trains at Mallaig. They will need to make their own arrangements to travel between Kyle of Lochalsh and Mallaig, as railway tickets are not valid on bus and ferry connections between the two locations. This manual easement will not operate in online journey planning systems.
​

This has had "Scotrail only operated" added to it.

 

[Bletchleyite]

I assume the latter makes it clear they don't give validity on the Jacobite. (Or CS?)

 

[yorkie]

This has had "Scotrail only operated" added to it.

So no getting the Jacobite then

At least it's consistent with the restrictions of tickets from Mallaig
http://www.brfares.com/#faredetail?orig=MLG&dest=FTW&rte=1000&tkt=CDR

Not valid on 'The Jacobite',
steam service operated by West
Coast Railways

Of course it's not really necessary as the Jacobite isn't a National Rail service, but it's inclusion in the National Rail Timetable may cause confusion, hence the clarification.

 

[kieron]

Some more changes were published yesterday, as below:

New data set 0519 published 24/05/18
Comparing revision RJRG0519 to RJRG0518
To add permitted routes via Stoke on Trent and to simplify the number of sequemnces, the following changes have been made.
BIRMINGHAM GROUP (G02) and Llandudno Junction (LLJ) - added sequence 'RJ'
Chester (CTR) and BIRMINGHAM GROUP (G02) - added sequence 'RJ'
Chester (CTR) and BIRMINGHAM GROUP (G02) - removed sequence 'BJ'
BIRMINGHAM GROUP (G02) and Llandudno Junction (LLJ) - removed sequence 'BJ'
BIRMINGHAM GROUP (G02) and Llandudno Junction (LLJ) - removed sequence 'BP+NJ'
Chester (CTR) and BIRMINGHAM GROUP (G02) - removed sequence 'NJ+BP'
​

These journeys now have mapped routes via Stoke.
If you're going to Birmingham (rather than from it), there were already some mapped routes using a Wolverhampton-Walsall train which avoids Birmingham (they run early on a Saturday morning), and then going to Birmingham via Rugeley and Lichfield. This change adds ones which go via Rugeley and Nuneaton.

To create routes via Mirfield (G40) Huddersfield Routeing Group
HALIFAX GROUP (G39) and MIDDLESBROUGH GROUP (G42) - added sequence 'MS+YT'
HALIFAX GROUP (G39) and Newcastle (NCL) - added sequence 'MS+YN'​

These journeys now have mapped routes via Huddersfield Group.

To create routes via Leeds
HUDDERSFIELD GROUP (G40) and HELLIFIELD GROUP (G53) - added sequence 'WY'​

There were already some mapped routes via Leeds, but this creates ones which don't oblige you to go through Bradford City Centre on the way.

To allow doublebacks within (G20) Manchester Routeing Group, which are preventing interchange at Manvchester Victoria easement added
700787: Services to or via Deansgate, Manchester Oxford Road or Manchester Piccadilly station that involve an interchange at Manchester Victoria, will involving passing Salford Central station twice. This doubleback easement will permit journey planners displaying journeys that involve this doubleback.​

While trains using the Ordsall Curve don't go through the platforms at Salford Central, they are treated by ticket sites as having gone through the station. This means that there is plenty of scope for a site to declare that a route doubles back through Salford Central.
The rules for station groups mean that this doesn't matter for most journeys which don't start or end at a station within Manchester Routeing Group, but this extends it to most of the stations within the group. Journeys to and from Salford Central itself do not benefit from this easement, even if a change at Manchester Victoria is sometimes faster than one at Salford Crescent.

 

[Bletchleyite]

These journeys now have mapped routes via Stoke.

I expect this is to allow for the new Crewe-Birmingham(-Euston) via Stoke service coming up in the December timetable which will replace the "wobble" in the Trent Valley service.

 

[yorkie]

It's more reactionary I think. It should have always been mapped! There were problems with journeys from Trent Valley to places like Chester, which came up as either requiring an additional unnecessary change (and tighter connection at Crewe than should have been the case) or a higher fare for the privilege of remaining on the train to Crewe.

I can't remember if there was a thread on this forum or not, but if there was, I can't seem to find it now.

 

[kieron]

New data set 0520 published 29/05/18

Map MM - LONDON TO THE EAST MIDLANDS AND SCOTLAND VIA THE PENNINES changed (1 added/ 0 removed links)In preparation for Derby diversions link direct between Loughborough and Chesterfield Routeing Points

Map SY - MIDLAND MAINLINE TO YORKSHIRE changed (1 added/ 0 removed links) In preparation for Derby diversions link direct between Loughborough and Chesterfield Routeing Points​

These maps (as well as PR) have had a Loughborough-Chesterfield link added. AM and PS already included this link, leaving 16 maps which include Leicester-Derby-Chesterfield but don't include this this diversion.

Naturally, this affects a large number of routes. As an example, Leicester-York is valid on BP+KY and EY. EY includes the line between London and Sheffield, but doesn't include this diverted route.

Easements for Engineering diversions - added

Added 700788: 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 of the 2-3, 9-10, 16-17, 23-24 June and 30 June - 01 July 2018. This map easement will allow journey planners to see journeys via Cosham and Havant, and applies in both directions.​

On the 3rd June (for instance), Crosscountry are going between Southampton and Reading via Havant and Guildford, not calling at Winchester or Basingstoke. Southampton-Reading (for one) isn't normally valid this way.

Easements for Engineering diversions - removed

Removed 700758: On Sunday 01 April 2018, customers travelling to or via London Marylebone may not travel on Cross Country services from the North West to interchange at Leamington Spa or Banbury for onward travel to London. Instead they should change at Birmingham New Street and use Chiltern services from Birmingham Moor Street. This circuitous route easement has been introduced during the engineering works closure of London Euston, and is to prevent overcrowding on Cross Country services south of Birmingham.

Removed 700759: During engineering works affecting the route through Newbury on 12 March to 15 March 2018; 23 April to 26 April 2018 and 14 May to 18 May 2018, tickets priced on route (00063) VIA NEWBURY will be valid for journeys via Swindon and Didcot Parkway. This positive fare route easement will apply in both directions

Removed 700760: During engineering works affecting Great Western services on 17 to 18 March and 25 to 28 May 2018, tickets priced on fare route (00810) NOT VIA READING will be valid via Reading.

Removed 700761: Due to engineering works affecting journeys via Cheltenham Spa and Bristol. Cross Country services will be diverted via Kemble, Swindon and Bath Spa on Saturdays 12, 19 and Sundays 13, 20 May 2018. This map easement will create temporary permitted routes and will apply in both directions.

Removed 700779: During engineering works on the 26 and 27 May 2018, Cross Country services between the South West and North East will be subject to diversions that will entail passing Selly Oak and Birmingham New Street stations more than once. This doubleback easement will operate in both directions to permit journeys to be found.

Removed 700781: Due to engineering works on the 26 and 28 May 2018 affecting journeys on Virgin Trains to or via Birmingham New Street; this map easement will create temporary permitted routes via Tamworth, Stafford and Smethwick Galton Bridge. It will operate in both directions​

The dates for these have all passed now.

 

[kieron]

Some more changes were published this afternoon.

New data set 0521published 31/05/18
Comparing RJRG0521 to RJRG0520

To create permissions via Staylebridge from Hull to Guide Bridge

Sequence(s) added
Gilberdyke (GBD) and Guide Bridge (GUI) - added sequence 'WY+CM'
Guide Bridge (GUI) and Hull (HUL) - added sequence 'CM+WY'​

As it said, this creates routes via Stalybridge.

To review maps use of map KM

Sequence(s) removed
Bolton (BON) and Kirkham And Wesham (KKM) - removed sequence 'KM'
Bolton (BON) and Preston (Lancs) (PRE) - removed sequence 'KM'

Sequence(s) added
Bolton (BON) and Kirkham And Wesham (KKM) - added sequence 'CL+DB'
Bolton (BON) and Kirkham And Wesham (KKM) - added sequence 'DB'
Bolton (BON) and Preston (Lancs) (PRE) - added sequence 'CL'
Bolton (BON) and Preston (Lancs) (PRE) - added sequence 'DB'​

These journeys no longer have mapped routes which go via Salford Crescent.
They now have mapped routes which go through Wigan but not Salford Crescent.

Changes due to rationalisation of maps used to create sequences for map permissions - use of map CL

Bolton (BON) and Chester (CTR) - added sequence 'CL'
Bolton (BON) and Llandudno Junction (LLJ) - added sequence 'CL'
Bolton (BON) and Shotton (SHT) - added sequence 'CL'
Bolton (BON) and WREXHAM GROUP (G49) - added sequence 'CL'​

These journeys now have mapped routes which go through Wigan and Warrington.

Bolton (BON) and Hooton (HOO) - added sequence 'CL'
Hooton (HOO) and Preston (Lancs) (PRE) - added sequence 'CL'​

These journeys now have mapped routes via Chester.

Bolton (BON) and LANCASTER GROUP (G64) - added sequence 'CL+XP'
Bolton (BON) and LANCASTER GROUP (G64) - added sequence 'DB+XP'
Bolton (BON) and Oxenholme Lake District (OXN) - added sequence 'CL+XP'
Bolton (BON) and Oxenholme Lake District (OXN) - added sequence 'DB+XP'

15 sequence(s) removed

Bolton (BON) and LANCASTER GROUP (G64) - removed sequence 'MX'
Bolton (BON) and Oxenholme Lake District (OXN) - removed sequence 'MX'​

These journeys no longer has mapped routes via Manchester.

Chester (CTR) and Hooton (HOO) - added sequence 'CL'
Chester (CTR) and Hooton (HOO) - removed sequence 'CH'
Chester (CTR) and Hooton (HOO) - removed sequence 'CP'
Chester (CTR) and Llandudno Junction (LLJ) - added sequence 'CL'
Chester (CTR) and Llandudno Junction (LLJ) - removed sequence 'CH'
Chester (CTR) and Preston (Lancs) (PRE) - added sequence 'CL'
Chester (CTR) and Shotton (SHT) - added sequence 'CL'
Chester (CTR) and Shotton (SHT) - removed sequence 'CH'
Chester (CTR) and WREXHAM GROUP (G49) - added sequence 'CL'
Chester (CTR) and WREXHAM GROUP (G49) - removed sequence 'CH'
WARRINGTON GROUP (G31) and Hooton (HOO) - added sequence 'CL'
WARRINGTON GROUP (G31) and Hooton (HOO) - removed sequence 'JG'
WARRINGTON GROUP (G31) and Llandudno Junction (LLJ) - added sequence 'CL'
WARRINGTON GROUP (G31) and Llandudno Junction (LLJ) - removed sequence 'GJ'
WARRINGTON GROUP (G31) and Shotton (SHT) - added sequence 'CL'
WARRINGTON GROUP (G31) and Shotton (SHT) - removed sequence 'JK'
WARRINGTON GROUP (G31) and WREXHAM GROUP (G49) - added sequence 'CL'
WARRINGTON GROUP (G31) and WREXHAM GROUP (G49) - removed sequence 'JK'
WIGAN GROUP (G34) and Hooton (HOO) - added sequence 'CL'
WIGAN GROUP (G34) and Hooton (HOO) - removed sequence 'GJ'
WIGAN GROUP (G34) and Llandudno Junction (LLJ) - added sequence 'CL'
WIGAN GROUP (G34) and Llandudno Junction (LLJ) - removed sequence 'GJ'
WREXHAM GROUP (G49) and Preston (Lancs) (PRE) - added sequence 'CL'
Llandudno Junction (LLJ) and Preston (Lancs) (PRE) - added sequence 'CL'
Preston (Lancs) (PRE) and Shotton (SHT) - added sequence 'CL'​

No effect.

To ensure tickets from Wigan to Preston are not valid via Burscough Bridge, negative easement created

Added 700789: Journeys from Wigan to Preston are not valid via Burscough Bridge. This negative easement applies in both directions.​

A Wigan-Preston season ticket is slightly cheaper than a Wigan-Burscough Bridge one. Maybe that's why.

To overcome rules relating to journeys where origin and destination share more than one common routeing point, and to ensure journeys are valid following timetable changes. Positive local easement created
Added 700790: Journeys from Greenfield to Slaithwaite via Stalybridge (which is not a shortest route for the common routeing points shared by these local stations) will be permitted by this local easement.​

I'm not exactly sure which rules this refers to (it's one of those places in the routeing guide where you can't follow all of the rules at the same time), but easement 700769 (from March) permits travel via Huddersfield with a first class Greenfield-Slaithwaite ticket. You need a first class ticket because the standard class ones have all had a "not Huddersfield" route since January. First class offers "TPE only" instead.

 

[Paul Kelly]

To overcome rules relating to journeys where origin and destination share more than one common routeing point, and to ensure journeys are valid following timetable changes. Positive local easement created
Added 700790: Journeys from Greenfield to Slaithwaite via Stalybridge (which is not a shortest route for the common routeing points shared by these local stations) will be permitted by this local easement.I'm not exactly sure which rules this refers to (it's one of those places in the routeing guide where you can't follow all of the rules at the same time), but easement 700769 (from March) permits travel via Huddersfield with a first class Greenfield-Slaithwaite ticket. You need a first class ticket because the standard class ones have all had a "not Huddersfield" route since January. First class offers "TPE only" instead.

It's almost amusing how disjointed this all is. Easement 700769 is superfluous because via Huddersfield would be permitted anyway, due to the common routeing point rule. I say would be, due to the "NOT HUDDERSFIELD" routeing, which can't be overridden by an easement. But in fact route 00258 NOT HUDDERSFIELD does not have any restrictions applied in the electronic data anyway, so it has no effect in journey planners and travel is allowed via Huddersfield without a need for any easements at all.

On the other hand, the new easement 700790 on its own is still not enough to allow travel via Stalybridge, at least in journey planners which comply with RDG's instructions for implementing the electronic routeing guide, which say:

Positive easements can be applied to a journey which has failed the ENRG rules, in order to change its validity. Where a journey contains several "errors", an easement is required for each in order to make the journey valid.

The route via Stalybridge contains two such "errors" in this context. Firstly, it contains a doubleback through Mossley (and Greenfield), which would need a doubleback easement to cover it. Secondly it fails the local journey rules, since it's neither a through train, the shortest route nor within 3 miles. It is to and from a common routeing point, but not the closest common routeing point, which again is a rule that electronic journey planners must implement, and thus it can't be allowed by virtue of the common routeing point rule.

So the current situation is that a local easement has been added to cover the second "error", but it still needs a doubleback easement to cover the doubleback through Mossley/Greenfield before it will be allowed by compliant journey planners.

 

[kieron]

Some more easements were published yesterday, although no summary has been uploaded to the RDG web site yet. They are:

700791 (Local) During engineering works from 16/06/2018 to 07/07/2018 ,this local easement allows customers to travel from Bristol Stations and Yale to Chepstow and Lydney, via Gloucester. This easement applies in both directions​

​

Bristol Stations? And Yale?

Anywaay, there are no trains through Patchway for some of this period. The replacement buses will still typically be faster than a trek to Gloucester, but they're not for everyone.

700792 (Routeing Point) This routeing point easement overrides the Fare Check to allow customers to travel via West Hampstead to stations beyond West Hampstead from St Albans City. This easement applies in both directions.​

​

As anyone who's familiar with the "pink pages" station list knows, "West Hampstead" is the name of a routeing point which covers solely the station named "West Hampstead Thameslink". It's not immediately obvious which station "beyond West Hampstead" refers to in this context, though.

700793 (Doubleback) Customers travelling via Yeovil to Taunton and beyond may doubleback between Castle Cary and Westbury. This easement applies in both directions.​

​

This easement doesn't affect as many journeys as it might appears on first reading as so many journeys in the area only have tickets via Exeter, Salisbury, Taunton or the like. This easement is there for the trains which don't stop between Westbury and Taunton, of course.

 

[kieron]

An easement was added to the routeing guide yesterday (8 June). It reads:

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​

The line is closed then between Tiverton Parkway and Exeter, and GWR are running a few trains via Castle Cary and Honiton to compensate.

As far as I can tell, there is no permitted route from Castle Cary to Exeter or beyond via Honiton (through trains aside), meaning a Torquay-London ticket isn't valid on these trains.

 

[Andy1066]

Thanks so much , may explain why it's impossible to buy online a ticket from Avonmouth to pilning return , even though it is possible .
Also correct via Newport is not the shortest or fastest option to change for pilning .

 

[Paul Kelly]

As far as I can tell, there is no permitted route from Castle Cary to Exeter or beyond via Honiton (through trains aside), meaning a Torquay-London ticket isn't valid on these trains.

Yes indeed. Strange that a map easement hasn't been added for this. As it stands, it's a half-done job.

 

[kieron]

Some more easements were added to the routeing guide yesterday (12 June). They are:

700795 (Map) During engineering workings between 22/07/2018 and 02/10/2018 trains will be diverted between Burton and Chesterfield via Langley Mill. This map easement allows travel between Tamworth and Chesterfield without passing through Derby.

700798 (Map) During engineering works between 22/07/2018 and 07/10/2018 trains will be diverted via Langley Mills.This map easement allows travel between Loughborough and Chesterfield without passing through Derby.

700799 (Map) During engineering works between Tamworth and Nottingham, trains will be diverted This map easement allows travel between Tamworth and Nottingham without passing through Derby.​

That's Loughborough and Chesterfield, Tamworth and Chesterfield, and Tamworth and Nottingham with additional routes avoiding Derby. The trains don't have any extra stops to help people who are going to or through Derby, but with Tamworth-Chesterfield trains (for one) not passing any stations between Alfreton and Willington, there isn't an obvious station to choose.

700796 (Map) During engineering works on Saturday and Sunday from 07/07/2018 to 15/07/2018, diversions between Bristol and Cheltenham will be permitted via Swindon. This map easement is applies in both directions.​

Crosscountry are going via Bath and Swindon between Bristol Temple Meads and Cheltenham. Those trains don't go to Gloucester, and this easement doesn't cover 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​

This is a "routeing point" version on 700791.

In addition to this, 700791 has also had "or Cheltenham" added to it in the same way.

 

[kieron]

Some more changes were published this morning.

New dataset 0525 published 27/06/18

Impact Assessment - comparing revision RJRG0525 to RJRG0521

2 sequence(s) added to provide routes to Guide Bridge not via Manchester

Gilberdyke (GBD) and Guide Bridge (GUI) - added sequence 'TP'
Guide Bridge (GUI) and Hull (HUL) - added sequence 'TP'​

These journeys now have mapped routes:
via Wakefield; and
ones via Stalybridge which avoid Manchester.

None via Knottingley, though.

The summary lists a few easements which were added during the last month:

New easements (temporary and permanent) as a result of engineering diversions

Added 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

Added 700792: This routeing point easement overrides the Fare Check to allow customers to travel via West Hampstead to stations beyond West Hampstead from St Albans City. This easement applies in both directions.

Added 700793: Customers travelling via Yeovil to Taunton and beyond may doubleback between Castle Cary and Westbury. This easement applies in both directions.

Added 700794: Due to engineering works between 12/06/2018 and 14/06/2018, customers travelling on route ' VIA TAUNTON' may travel via Castle Cary

Added 700795: During engineering workings between 22/07/2018 and 02/10/2018 trains will be diverted between Burton and Chesterfield via Langley Mill. This map easement allows travel between Tamworth and Chesterfield without passing through Derby.

Added 700796: During engineering works on Saturday and Sunday from 07/07/2018 to 15/07/2018, diversions between Bristol and Cheltenham will be permitted via Swindon. This map easement is applies in both directions.

Added 700797: 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

Added 700798: During engineering works between 22/07/2018 and 07/10/2018 trains will be diverted via Langley Mills.This map easement allows travel between Loughborough and Chesterfield without passing through Derby.

Added 700799: During engineering works between Tamworth and Nottingham, trains will be diverted This map easement allows travel between Tamworth and Nottingham without passing through Derby.​

It then finishes with a couple of new changes.

To correct fare anomaly where travel to Glasgow is cheaper than to Edinburgh new circuitous route negative easement

Added 700800: Customers travelling from Perth with a Cheap Day Single or return tickets to Glasgow Central or Glasgow Queen Street may not travel via Haymarket or Edinburgh. This circuitous route easement applies in both directions.​

There isn't a Cheap Day Single (or whatever they're called) between Glasgow and Perth, but there are some returns. This doesn't seem to have been implemented by nationalrail.co.uk yet, so I can't check which tickets are actually affected at the moment.

Additional dates added to existing easement for engineering work diversions
5 change(s) in 700788: 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 of the 2-3, 9-10, 16-17, 23-24 June and 30 June - 01 July, 28/29 July; 11, 19, 26 August and the 01/02, 08/09, 15/16, 22 September 2018. This map easement will allow journey planners to see journeys via Cosham and Havant, and applies in both directions.​

This was created on 29th May, and it originally only had the dates until 1st July.

 

[kieron]

Some more easements were published on Tuesday. Sorry about the delay. The published summary is as follows:

New data set 0526 published 03/07/18

Comparing revision RJRG0526 to RJRG0525

To provide routes via Leeds; this additional sequence has been published HALIFAX GROUP (G39) and HELLIFIELD GROUP (G53) - added sequence 'MS+WY'​

If easement 300329 isn't relevant, this only had mapped routes with a walk across Bradford beforehand.
It now also has mapped routes via Mirfield and Leeds.
There are at least two shorter routes between Halifax and Hellifield (one via Clitheroe, and a more useful one via Bradford and Leeds) which aren't covered.

For routine diversions and Sunday timetables for Cross Country services, a link between Wakefield (G30) and Doncaster routeing points has been added to five maps

Map BY - BIRMINGHAM TO YORK changed (1 added/ 0 removed links)
Map CY - CARDIFF TO YORK changed (1 added/ 0 removed links)
Map DY - DERBY TO YORK changed (1 added/ 0 removed links)
Map RY - ROUTES VIA READING TO YORK changed (1 added/ 0 removed links)
Map SY - MIDLAND MAINLINE TO YORKSHIRE changed (1 added/ 0 removed links)​

You do not, of course, have to wait for a Crosscountry train to use one of these routes.

This affects a lot of different routes. For example, there are now mapped routes between London and Bradford via Chesterfield and Doncaster.

To ensure journeys are not denied by the fare check rule. This easement has been published

Added 700801: Customers from Falkirk High, Larbet, Falkirk Grahamston, Camelon, Polmont or Linlithgow travelling to Airbles, Hamilton Central, Chatelherault, Merryton or Larkhall are prevented from getting journey planning itineraries due to NFM64 fares checking. This routeing point easement will allow journeys via Newton (Lanarkshire) and operate in both directions.​

The problem with the fare check may be due to the fact that there are no suitable fares on any of these journeys in the NFM64 list. This fact also means that Motherwell Group fails the fare check. There are still valid routes as there are mapped routes which go via Newton, Motherwell and Glasgow, and the shortest route for each journey goes via Motherwell and Cumbernauld.

 

[kieron]

Some more changes were published on Wednesday, as follows:

New data set 0527 published 11/07/18
Comparing revision RJRG0527 to RJRG0526

Review of map permissions from Accrington

Accrington (ACR) and DERBY GROUP (G09) - added sequence 'DP+BB+DY'
Accrington (ACR) and DERBY GROUP (G09) - added sequence 'DP+SY'​

This journey now has mapped routes:
via Brighouse and Leeds; and
via the line between Mirfield and Wakefield.

Review of Epsom to ensure that (00700) Not Via London priced tickets are valid via Clapham Junction and Balham for journeys to or via (G08) Croydon Routeing Point

Added sequences to priovide routes via Clapham Junction

Epsom (EPS) and CROYDON GROUP (G08) - added sequence 'DK+TN'​

This now has mapped routes via Clapham Junction.

Epsom (EPS) and Gatwick Airport (GTW) - added sequence 'DK+LP'

Removed sequences following review and addition of EPS to GTW addition of DK+LP

Epsom (EPS) and Gatwick Airport (GTW) - removed sequence 'DK+LB'
Epsom (EPS) and Gatwick Airport (GTW) - removed sequence 'HR+LB'​

This no longer has mapped routes:
via Brighton;
via Peckham Rye, London and New Cross Gate;
via Clapham Junction, Herne Hill, London and New Cross Gate;
ones via Crystal Palace which don't go via London; or
ones via Mitcham Junction which don't go via London.

Review of York to East Yorkshire routeing points. To add where possible additional permitted routes or mapped shortest journeys

Goole (GOO) and York (YRK) - added sequence 'HO+YM'​

This journey now has mapped routes via Gilberdyke.

Hull (HUL) and York (YRK) - added sequence 'NP'​

This journey now has mapped routes via Leeds.

Review of map permissions from Lincolnshire and Nottinghamshire routeing points

Sequences added

Barnetby (BTB) and Kettering (KET) - added sequence 'NB+NM'
Barnetby (BTB) and Kettering (KET) - added sequence 'NB+SY'
BIRMINGHAM GROUP (G02) and Grantham (GRA) - added sequence 'DG+DL'
BIRMINGHAM GROUP (G02) and Grantham (GRA) - added sequence 'DL'
BIRMINGHAM GROUP (G02) and NEWARK GROUP (G47) - added sequence 'DL+DG'
BIRMINGHAM GROUP (G02) and Sleaford (SLR) - added sequence 'DG+DL'
BIRMINGHAM GROUP (G02) and Sleaford (SLR) - added sequence 'DL'

Sequences removed

Barnetby (BTB) and Kettering (KET) - removed sequence 'YL+SY'​

No effect.

Barnetby (BTB) and Leicester (LEI) - added sequence 'NB+NM'
Barnetby (BTB) and Leicester (LEI) - removed sequence 'YL+SY'​

This journey no longer has mapped routes via Wakefield.

Barnetby (BTB) and Tamworth (TAM) - added sequence 'BG+DG'
Barnetby (BTB) and Tamworth (TAM) - added sequence 'DG'
Barnetby (BTB) and Tamworth (TAM) - removed sequence 'BG+WM'
Barnetby (BTB) and Tamworth (TAM) - removed sequence 'DG+WM'​

This journey no longer has mapped routes via Lincoln and Coventry.
It now has mapped routes:
via Lincoln and Lichfield Trent Valley; and
via Lincoln and Burton-upon-Trent.

Habrough (HAB) and Tamworth (TAM) - added sequence 'DG'
Habrough (HAB) and Tamworth (TAM) - removed sequence 'DG+WM'​

This now has mapped routes via Lincoln and Burton-upon-Trent.

Lincoln (LCN) and Lichfield Trent Valley (LTV) - added sequence 'BG+DG'
Lincoln (LCN) and Lichfield Trent Valley (LTV) - added sequence 'BG+TL'
Lincoln (LCN) and Lichfield Trent Valley (LTV) - added sequence 'DG'
Lincoln (LCN) and Lichfield Trent Valley (LTV) - removed sequence 'EM'
NEWARK GROUP (G47) and Lichfield Trent Valley (LTV) - added sequence 'BG+DG'
NEWARK GROUP (G47) and Lichfield Trent Valley (LTV) - added sequence 'BG+TL'
NEWARK GROUP (G47) and Lichfield Trent Valley (LTV) - added sequence 'DG'
NEWARK GROUP (G47) and Lichfield Trent Valley (LTV) - removed sequence 'EM'​

These journeys no longer have mapped routes via Melton Mowbray.
They now have mapped routes via Birmingham.

Lincoln (LCN) and Rugeley Trent Valley (RGL) - added sequence 'BG+DG+TL'
Lincoln (LCN) and Rugeley Trent Valley (RGL) - added sequence 'BG+TL'​

This journey now has mapped routes:
via Atherstone; and
via Loughborough and Lichfield Trent Valley.

Lincoln (LCN) and Tamworth (TAM) - added sequence 'BG+DG'
Lincoln (LCN) and Tamworth (TAM) - added sequence 'BG+TL'
Lincoln (LCN) and Tamworth (TAM) - removed sequence 'EM'​

This journey no longer has mapped routes via Melton Mowbray.

NEWARK GROUP (G47) and Tamworth (TAM) - added sequence 'BG+DG'
NEWARK GROUP (G47) and Tamworth (TAM) - added sequence 'BG+TL'
NEWARK GROUP (G47) and Tamworth (TAM) - added sequence 'DG'
NEWARK GROUP (G47) and Tamworth (TAM) - removed sequence 'BG+WM'
NEWARK GROUP (G47) and Tamworth (TAM) - removed sequence 'DG+CE'
NEWARK GROUP (G47) and Tamworth (TAM) - removed sequence 'EM'​

This no longer has mapped routes:
via Sheffield;
via Melton Mowbray; or
via Coventry.
It now has mapped routes via Lichfield Trent Valley.

NOTTINGHAM GROUP (G43) and Lichfield Trent Valley (LTV) - added sequence 'BG+DG'
NOTTINGHAM GROUP (G43) and Lichfield Trent Valley (LTV) - added sequence 'BG+TL'
NOTTINGHAM GROUP (G43) and Lichfield Trent Valley (LTV) - added sequence 'DG'
NOTTINGHAM GROUP (G43) and Lichfield Trent Valley (LTV) - removed sequence 'BG+WM'
NOTTINGHAM GROUP (G43) and Lichfield Trent Valley (LTV) - removed sequence 'DG+WM'​

This no longer has mapped routes via Coventry.
It now has mapped routes which go via both Leicester and Tamworth.

NOTTINGHAM GROUP (G43) and Tamworth (TAM) - added sequence 'BG+HB'
NOTTINGHAM GROUP (G43) and Tamworth (TAM) - added sequence 'BG+TL'
NOTTINGHAM GROUP (G43) and Tamworth (TAM) - added sequence 'DG'
NOTTINGHAM GROUP (G43) and Tamworth (TAM) - added sequence 'DG+XL'
NOTTINGHAM GROUP (G43) and Tamworth (TAM) - added sequence 'TV'
NOTTINGHAM GROUP (G43) and Tamworth (TAM) - removed sequence 'BG+WM'
NOTTINGHAM GROUP (G43) and Tamworth (TAM) - removed sequence 'DG+WM'
NOTTINGHAM GROUP (G43) and Tamworth (TAM) - removed sequence 'TL'​

This no longer has mapped routes via Rugby
It now has mapped routes via Nuneaton which don't go through Rugby.

New temporary easements added to mitigate impacts of engineering works

Added 700802: 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​

There are rail replacement buses for parts of the line through Evesham. I suspect this actually covers more than just Worcester-London Terminals tickets, but I'm not sure of the details.

Added 700803: 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

Added 700804: 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. This map easement applies in both directions​

These are a "map" and "fare route" easement; I assume to let tickets be used to go through Leeds when it isn't normally on a permitted route, and to let "via Chesterfield" tickets be used via Leeds instead.

Additional locations added to easement

700287: Customers travelling from Cuxton, Halling, Snodland, New Hythe or Aylesford to London Terminals Stations in possession of tickets routed "Not Valid on HS1" may not travel via Paddock Wood. This easement applies in both directions.​

This restriction has been extended to cover Cuxton and Halling (so it affects everywhere between Strood and Maidstone Barracks exclusive.

 

[Bletchleyite]

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

 

[Peter Mugridge]

Epsom (EPS) and Gatwick Airport (GTW) - removed sequence 'DK+LB'
Epsom (EPS) and Gatwick Airport (GTW) - removed sequence 'HR+LB'​

This no longer has mapped routes:
via Brighton;
via Peckham Rye, London and New Cross Gate;
via Clapham Junction, Herne Hill, London and New Cross Gate;
ones via Crystal Palace which don't go via London; or
ones via Mitcham Junction which don't go via London.

Doesn't that create an anomaly in that you can go on a South Western Railway service Epsom to Clapham Junction and change there for Gatwick, but you cannot now use a Southern service to do exactly the same simply because the Southern one goes via Mitcham Junction?

 

[infobleep]

Doesn't that create an anomaly in that you can go on a South Western Railway service Epsom to Clapham Junction and change there for Gatwick, but you cannot now use a Southern service to do exactly the same simply because the Southern one goes via Mitcham Junction?

That is indeed the case and it's a minute quicker via Mitcham Junction. Not that TOCs would always consider that to necessarily be a reason why they would continue to allow it. It should be of course.

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.

There was a separate discussion on here recently about train tickets and trams.

 

[Paul Kelly]

The removal of the "Southern" route to Clapham Junction seems even more peculiar because an easement exists specifically to allow the doubleback through Balham and Wandsworth Common:

Customers travelling from Epsom to Redhill and beyond in possession of tickets routed "Not via London" may double back between Balham and Clapham Junction. This easement applies in both directions.

If I understand correctly this easement is now superfluous for this journey, since the mapped route this way has been deleted.

 

[Peter Mugridge]

Very curious... so has someone made a blunder somewhere? Is this one of those famous instances of "unintended consequences" in which case there would presumably have to be an easement added to re-instate the route?

A further point; it's not just a minute quicker to reach Clapham Junction - it's also easier on the outbound as it would offer a cross-platform connection at Clapham Junction...

 

[infobleep]

The removal of the "Southern" route to Clapham Junction seems even more peculiar because an easement exists specifically to allow the doubleback through Balham and Wandsworth Common:

If I understand correctly this easement is now superfluous for this journey, since the mapped route this way has been deleted.

Now it's been raised on here, perhaps they will amend the easement so it better reflects the fact travel is no longer valid via Mitcham Junction in this case.

 

[infobleep]

Just had a other thought with regard to the essmemet. Would one be allowed to walk to Balham from Earlsfield? Why you'd want to I know not but would it be allowed? Then the easement still holds true.

I know it's silly and clearly not intended but legally woild it stand? I'm trying to think of tenuous reasons as to how the easement could still be used by passengers

 

[MikeWh]

Now it's been raised on here, perhaps they will amend the easement so it better reflects the fact travel is no longer valid via Mitcham Junction in this case.

Just had a other thought with regard to the essmemet. Would one be allowed to walk to Balham from Earlsfield? Why you'd want to I know not but would it be allowed? Then the easement still holds true.

I know it's silly and clearly not intended but legally woild it stand? I'm trying to think of tenuous reasons as to how the easement could still be used by passengers

I don't think you quite understand. If you travel by Southern from Epsom to Clapham Junction and then Clapham Junction to Gatwick, both legs use the stretch between Balham and Clapham Junction. Without the easement you would have had to change at Balham, and thus use slow trains. The easement has no effect on the SWR route via Wimbledon as there is no doubleback.

 

[infobleep]

I don't think you quite understand. If you travel by Southern from Epsom to Clapham Junction and then Clapham Junction to Gatwick, both legs use the stretch between Balham and Clapham Junction. Without the easement you would have had to change at Balham, and thus use slow trains. The easement has no effect on the SWR route via Wimbledon as there is no doubleback.

I do understand that but as passengers are not allowed via Mitcham Junction, l wondered if passengers could get out at Earlsfield. Make their own way to Balham. Travel from there to Clapham on a slow train and then back down to Gatwick Airport on a fast train.

I'm not saying anyone would want to do that but would it still technically allow the easement to be made use of, whilst travel via Mitcham Junction is barred?

The question is it valid to walk between Earlsfield and Balham in this circumstances. This is hyperthetical as who would do it. I can start a new thread if this js considered inappropriate here?

 

[Paul Kelly]

No, there still seems to be a misunderstanding here. There is no specific prohibition on travelling via Mitcham Junction. What has actually happened is that maps HR+LB have been removed as a valid map combination for an Epsom to Gatwick Airport journey. Describing this change as consisting of, amongst other things, there no longer being any permitted routes via Mitcham Junction which don't go via London. was simply kieron's very helpful interpretation of the change to the permitted routes in more human-readable terms. 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.