National Routeing Guide update

[kieron]

According to NRE, Farnborough North to Streatham Common via Redhill requires 2 tickets. This route is also disallowed by FGW's Mixing Deck.

Sorry; I thought you realised I was talking about buying a ticket which would allow you to make that journey, rather than a ticket with those specific stations written on it.

In any case, they added that bit back in for Streatham-Guildford (but not for Streatham-Dorking) on Friday.

I am looking into moving half way between Brockenhurst and Salisbury. Am I right in thinking that as a result of these changes, there is now no annual season ticket that I can get that would allow me to go from London and choose either destination without paying an excess?

What about Dorchester ? Have not got the fares to compare with Salisbury

Sorry, I really don't understand what you're asking. What would you like to do with Dorchester?
--- old post above --- --- new post below ---
There was another update on Friday.

New Dataset RJRG0365 published 03 July 2015

Following customer comment the following changes have been made to permitted routes.


Map sequence added

Ash Vale (AHV) and Hounslow (HOU) - added sequence 'BU'​

There was already a mapped route via West Byfleet, Staines and Feltham.
This adds one via West Byfleet, Staines, Feltham and Barnes.

Basingstoke (BSK) and Hounslow (HOU) - added sequence 'BU'
Basingstoke (BSK) and Hounslow (HOU) - added sequence 'BU+WX'
Basingstoke (BSK) and Hounslow (HOU) - added sequence 'WW+WX'

Map sequence removed

Basingstoke (BSK) and Hounslow (HOU) - removed sequence 'LE'​

This removes mapped routes via London which also went via Feltham or Twickenham.
It removes mapped routes avoiding London which go via Ash Vale and Weybridge.
It adds mapped routes avoiding London going via Ascot and Kingston.

DORKING GROUP (G10) and Hounslow (HOU) - added sequence 'DK+TW'
DORKING GROUP (G10) and Hounslow (HOU) - added sequence 'SD+VH+TW'​

This adds a mapped route via Earlsfield, and a few extra ones via Redhill.

Guildford (GLD) and Hounslow (HOU) - added sequence 'EF+TW'
Guildford (GLD) and Hounslow (HOU) - added sequence 'PU'
Guildford (GLD) and Hounslow (HOU) - removed sequence 'PD+TW'​

This removes mapped routes via Feltham which also went via London or Effingham Junction. The only mapped routes via Feltham are now via Woking on maps WX or PU.

Hounslow (HOU) and Woking (WOK) - added sequence 'PU'​

This adds mapped routes via Chertsey, including the shortest route between the routeing points.

Following customer comment; to provide alternative permitted routes via Redhill. the following amendment has been published

STREATHAM GROUP (G29) and Guildford (GLD) - added sequence 'LP+CS'​

This adds a mapped route via Redhill, one of the ones removed a fortnight ago.

To ensure XC Train services that travel via the Tyseley Routeing Point to Gloucester have map permissions, a review has rsulted in the following amendments


Map sequence added

BANBURY GROUP (G58) and Gloucester (GCR) - added sequence 'BB+BL'
BANBURY GROUP (G58) and Gloucester (GCR) - added sequence 'LH'
BANBURY GROUP (G58) and Gloucester (GCR) - added sequence 'XB+CB+HP'

Map sequence removed

BANBURY GROUP (G58) and Gloucester (GCR) - removed sequence 'RB+PB'​

This adds mapped routes via Evesham and via Stroud.
It removes mapped routes via Bristol, Nuneaton, Stratford upon Avon
It also removes mapped routes which go via Stourbridge, Droitwich and Bromsgrove.

BIRMINGHAM GROUP (G02) and Gloucester (GCR) - added sequence 'BL'
BIRMINGHAM GROUP (G02) and Gloucester (GCR) - added sequence 'CB+HP+BL'
BIRMINGHAM GROUP (G02) and Gloucester (GCR) - removed sequence 'PB'​

This removes mapped routes which go via Stourbridge, Droitwich and Bromsgrove.

Gloucester (GCR) and Oxford (OXF) - removed sequence 'BL+SM'​

They added BL+HP+CB+XB, HP+WR+BE+PG and WR+XB at the same time.

Altogether, these changes add mapped routes via Tyseley, via Stourbridge, and via the line between Bromsgrove and Droitwich.

Gloucester (GCR) and Tyseley (TYS) - removed sequence 'PB+BI'​

As this was the only map combination available in the previous version, they added BL+BI and BL+HP+CB+BI to replace it.

This removes a route via Stourbridge, Droitwich and Bromsgrove.

Easements added for GWNML engineering works


700579: During Engineering Works in July and August, affecting the railway route through Box Tunnel, tickets routed 00618 is Via Salisbury, 00438 AP Salisbury and 00831 Via Bath Spa will be permitted to travel via Swindon and Westbury on First Great Western services.


700580: Due to engineering works in August 2015, affecting the route to the east of Bath Spa station, journeys from South Wales to Hampshire and Dorset will require to take alternative routes. For example Cardiff to Portsmouth direct trains will not operate. Journeys between S Wales and Hampshire/Dorset will be allowed to go via Swindon where interchange to connecting services will be permitted for the duration of this easement. this map easement will operate in both directions.​

As neither easement lists any dates, should I assume that these are active until the end of August, and for the length of August, respectively? Or are you required to find out if train A is cancelled before you board train B?

There were some updates which weren't included in the summary. Perhaps someone was looking at the effects of easement 700580, noticed that some journeys from stations in South Wales to ones in Hampshire or Dorset were already allowed on that sort of route, and made a half-hearted attempt to get rid of them.

Or maybe they just forgot to include the section which explained these changes.

Cardiff Central (CDF) to Brockenhurst (BCU) lose SB+LA+XR​

Cardiff Central (CDF) to Eastleigh (ESL) lose SB+LA+XR​

Cardiff Central (CDF) to Southampton Group (SDN etc.) lose SB+LA+XR​

These each remove a mapped route via Swindon, Trowbridge and Reading.

 

[FenMan]

Sorry; I thought you realised I was talking about buying a ticket which would allow you to make that journey, rather than a ticket with those specific stations written on it.

In any case, they added that bit back in for Streatham-Guildford (but not for Streatham-Dorking) on Friday.

Following customer comment; to provide alternative permitted routes via Redhill. the following amendment has been published

STREATHAM GROUP (G29) and Guildford (GLD) - added sequence 'LP+CS'​

This adds a mapped route via Redhill, one of the ones removed a fortnight ago.

Good to see positive customer service in action. It's almost as if someone is reading this thread.

 

[kieron]

There were some more changes to the routeing guide on Monday.

New Dataset RJRG0366 published 03 August 2015

To allow journeys from Huddersfield to Blackpool via Brighouse, led to a mini review of map permissions for Huddersfield Group, the following changes have been made.

Map sequence added

HUDDERSFIELD GROUP (G40) and Kirkham And Wesham (KKM) - added sequence 'MS+NP'
HUDDERSFIELD GROUP (G40) and LANCASTER GROUP (G64) - added sequence 'MS+NP+GP'
HUDDERSFIELD GROUP (G40) and Preston (Lancs) (PRE) - added sequence 'MS+NP'​

This turns the shortest route between the stations in each routeing point into a mapped route. This does mean you can now leave the direct route to sample the wonders of Halifax or Todmorden en route.

To allow a Journey from Shepperton to Hoxton to travel via Kingston and Wimbledon, the following change has been made.

Map sequence added

Kingston (KNG) and Surrey Quays (SQE) - added sequence 'SU+EL'​

There are now mapped routes via Peckham Rye and via Elephant & Castle.

To allow journeys from Guildford to Shoreham on Sea to travel via Ockley, the following changes have been made.

Map sequence added

BRIGHTON GROUP (G04) and Guildford (GLD) - added sequence 'XC+SD'​

Adds mapped routes via Horsham.

FORD GROUP (G61) and Guildford (GLD) - added sequence 'XC+SD'​

​

Adds mapped routes via Gatwick.

To ensure that permissions from Routeing Points on the West Coast Main Line to Liverpool Group are consistent, the following changes have been made.

Map sequence added

Bletchley (BLY) and LIVERPOOL GROUP (G18) - added sequence 'LC+GV'
LIVERPOOL GROUP (G18) and Milton Keynes Central (MKC) - added sequence 'GV+LC'
LIVERPOOL GROUP (G18) and Northampton (NMP) - added sequence 'GV+LC'
LIVERPOOL GROUP (G18) and Rugby (RUG) - added sequence 'GV+LC'

Map sequence removed

Bletchley (BLY) and LIVERPOOL GROUP (G18) - removed sequence 'LC+NO'
Bletchley (BLY) and LIVERPOOL GROUP (G18) - removed sequence 'LC+NR'
Bletchley (BLY) and LIVERPOOL GROUP (G18) - removed sequence 'MA+NR'
LIVERPOOL GROUP (G18) and Milton Keynes Central (MKC) - removed sequence 'NO+LC'
LIVERPOOL GROUP (G18) and Milton Keynes Central (MKC) - removed sequence 'NO+MA'
LIVERPOOL GROUP (G18) and Milton Keynes Central (MKC) - removed sequence 'NR+LC'
LIVERPOOL GROUP (G18) and Milton Keynes Central (MKC) - removed sequence 'NR+MA'
LIVERPOOL GROUP (G18) and Northampton (NMP) - removed sequence 'NO+LC'
LIVERPOOL GROUP (G18) and Northampton (NMP) - removed sequence 'NO+MA'
LIVERPOOL GROUP (G18) and Northampton (NMP) - removed sequence 'NR+LC'
LIVERPOOL GROUP (G18) and Northampton (NMP) - removed sequence 'NR+MA'
LIVERPOOL GROUP (G18) and Rugby (RUG) - removed sequence 'NO+LC'
LIVERPOOL GROUP (G18) and Rugby (RUG) - removed sequence 'NR+LC'​

Removes mapped routes via Manchester, via Widnes and via Wilmslow.
Adds routes via both Bedworth and Runcorn.

LIVERPOOL GROUP (G18) and Watford Junction (WFJ) - added sequence 'GV+LC'
LIVERPOOL GROUP (G18) and Watford Junction (WFJ) - removed sequence 'NO+LC'
LIVERPOOL GROUP (G18) and Watford Junction (WFJ) - removed sequence 'NO+MA'
LIVERPOOL GROUP (G18) and Watford Junction (WFJ) - removed sequence 'NR+LC'
LIVERPOOL GROUP (G18) and Watford Junction (WFJ) - removed sequence 'NR+MA'
LIVERPOOL GROUP (G18) and Willesden Junction (WIJ) - added sequence 'GV+LC'
LIVERPOOL GROUP (G18) and Willesden Junction (WIJ) - removed sequence 'NO+LC'
LIVERPOOL GROUP (G18) and Willesden Junction (WIJ) - removed sequence 'NO+MA'
LIVERPOOL GROUP (G18) and Willesden Junction (WIJ) - removed sequence 'NR+LC'
LIVERPOOL GROUP (G18) and Willesden Junction (WIJ) - removed sequence 'NR+MA'​

Removes mapped routes via Manchester, via Widnes and via Wilmslow.
Adds some extra mapped routes which go through Runcorn and Bedworth (there were some previously, although only ones which went south though Bedworth on a southbound journey, where you can now go either way).

LIVERPOOL GROUP (G18) and Nuneaton (NUN) - removed sequence 'NO+BM+BP'
LIVERPOOL GROUP (G18) and Nuneaton (NUN) - removed sequence 'NR+BM'
LIVERPOOL GROUP (G18) and Nuneaton (NUN) - removed sequence 'NR+BM+BP'​

Removes mapped routes via Widnes.
Also removes a few more obscure routes (such as ones which go from Stoke to Rugeley avoiding Stafford, and then via Birmingham).

Following TOC report that journeys between Alton and Bath Spa were only shown in Journey Planners via London, the following changes have been made.

Map sequence added

Ash Vale (AHV) and Bath Spa (BTH) - added sequence 'BB'
Ash Vale (AHV) and Bath Spa (BTH) - added sequence 'BB+LA'
Ash Vale (AHV) and Bath Spa (BTH) - added sequence 'BU'​

This adds mapped routes which go via Farnborough and Wokingham, although I'm not exactly sure what routes a journey planner would show with these.

A review of map permissions between Lancashire and Finsbury Park and Highbury & Islington Routeing Points; to remove permissions via the East Coast Main Line, (created in error in April 2013), the following changes have been made.


Map sequence added

Accrington (ACR) and Finsbury Park (FPK) - added sequence 'EP+OV+KP'
Accrington (ACR) and Highbury And Islington (HHY) - added sequence 'EP+OV'
Blackburn (BBN) and Finsbury Park (FPK) - added sequence 'EP+OV+KP'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - added sequence 'KP+OV+EP'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - added sequence 'KP+OV+EX'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - added sequence 'KP+OV+EP'
WIGAN GROUP (G34) and Highbury And Islington (HHY) - added sequence 'EP+OV'


Map sequence removed

Accrington (ACR) and Finsbury Park (FPK) - removed sequence 'BK+BP+KP'
Accrington (ACR) and Finsbury Park (FPK) - removed sequence 'CU+AC'
Accrington (ACR) and Finsbury Park (FPK) - removed sequence 'CU+AS'
Accrington (ACR) and Finsbury Park (FPK) - removed sequence 'DP+EE'
Accrington (ACR) and Finsbury Park (FPK) - removed sequence 'KM+AC'
Accrington (ACR) and Finsbury Park (FPK) - removed sequence 'KM+AM'
Accrington (ACR) and Finsbury Park (FPK) - removed sequence 'KM+AS'
Accrington (ACR) and Finsbury Park (FPK) - removed sequence 'KM+MN+EC'
Accrington (ACR) and Finsbury Park (FPK) - removed sequence 'NP+EC'
Accrington (ACR) and Finsbury Park (FPK) - removed sequence 'NP+ER'
Accrington (ACR) and Highbury And Islington (HHY) - removed sequence 'BK+BP+KP'
Accrington (ACR) and Highbury And Islington (HHY) - removed sequence 'CU+AC'
Accrington (ACR) and Highbury And Islington (HHY) - removed sequence 'CU+AS'
Accrington (ACR) and Highbury And Islington (HHY) - removed sequence 'DP+EE'
Accrington (ACR) and Highbury And Islington (HHY) - removed sequence 'KM+AC'
Accrington (ACR) and Highbury And Islington (HHY) - removed sequence 'KM+AM'
Accrington (ACR) and Highbury And Islington (HHY) - removed sequence 'KM+AS'
Accrington (ACR) and Highbury And Islington (HHY) - removed sequence 'KM+MN+EC'
Accrington (ACR) and Highbury And Islington (HHY) - removed sequence 'NP+EC'
Accrington (ACR) and Highbury And Islington (HHY) - removed sequence 'NP+ER'
Blackburn (BBN) and Finsbury Park (FPK) - removed sequence 'BK+BP+KP'
Blackburn (BBN) and Finsbury Park (FPK) - removed sequence 'CU+AC'
Blackburn (BBN) and Finsbury Park (FPK) - removed sequence 'CU+AS'
Blackburn (BBN) and Finsbury Park (FPK) - removed sequence 'DP+EE'
Blackburn (BBN) and Finsbury Park (FPK) - removed sequence 'KM+AC'
Blackburn (BBN) and Finsbury Park (FPK) - removed sequence 'KM+AM'
Blackburn (BBN) and Finsbury Park (FPK) - removed sequence 'KM+AS'
Blackburn (BBN) and Finsbury Park (FPK) - removed sequence 'KM+DB+EE'
Blackburn (BBN) and Finsbury Park (FPK) - removed sequence 'KM+DW+EE'
Blackburn (BBN) and Finsbury Park (FPK) - removed sequence 'KM+MN+EC'
Blackburn (BBN) and Finsbury Park (FPK) - removed sequence 'NP+EC'
Blackburn (BBN) and Finsbury Park (FPK) - removed sequence 'NP+ER'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'AC+CU'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'AC+KM'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'AM+KM'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'AM+XW'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'AS+CU'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'AS+KM'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'EC+MN+KM'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'EC+MN+XW'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'EC+NP'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'EE+DB+KM'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'EE+DB+XW'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'EE+DP'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'EE+DW+KM'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'EE+DW+XW'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'ER+NP'
Finsbury Park (FPK) and Kirkham And Wesham (KKM) - removed sequence 'KP+BP+BK'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'AC+CU'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'AC+MX'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'AM+MX'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'AM+XW'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'AS+CU'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'AS+MX'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'EC+MN+MX'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'EC+MN+XW'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'EC+NP+XP'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'EE+DB+MX'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'EE+DB+XW'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'EE+DP+XP'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'EE+DW+MX'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'EE+DW+XW'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'ER+LX'
Finsbury Park (FPK) and LANCASTER GROUP (G64) - removed sequence 'KP+BP+BX'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'AC+CU'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'AC+KM'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'AM+KM'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'AM+XW'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'AS+CU'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'AS+KM'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'EC+MN+KM'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'EC+MN+XW'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'EC+NP'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'EE+DB+KM'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'EE+DB+XW'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'EE+DP'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'EE+DW+KM'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'EE+DW+XW'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'ER+NP'
Finsbury Park (FPK) and Preston (Lancs) (PRE) - removed sequence 'KP+BP+BK'
WIGAN GROUP (G34) and Highbury And Islington (HHY) - removed sequence 'BS+BP+KP'
WIGAN GROUP (G34) and Highbury And Islington (HHY) - removed sequence 'DB+EE'
WIGAN GROUP (G34) and Highbury And Islington (HHY) - removed sequence 'DW+EE'
WIGAN GROUP (G34) and Highbury And Islington (HHY) - removed sequence 'NC+AC'
WIGAN GROUP (G34) and Highbury And Islington (HHY) - removed sequence 'NC+AS'
WIGAN GROUP (G34) and Highbury And Islington (HHY) - removed sequence 'NN+AC'
WIGAN GROUP (G34) and Highbury And Islington (HHY) - removed sequence 'NN+AM'
WIGAN GROUP (G34) and Highbury And Islington (HHY) - removed sequence 'NN+AS'
WIGAN GROUP (G34) and Highbury And Islington (HHY) - removed sequence 'NN+MN+EC'
WIGAN GROUP (G34) and Highbury And Islington (HHY) - removed sequence 'XW+AM'
WIGAN GROUP (G34) and Highbury And Islington (HHY) - removed sequence 'XW+MN+EC'​

These remove mapped routes via Peterborough.
They add routes via Gospel Oak instead (for instance, someone going from Preston to Finsbury Park could go into London on the WCML as far as Willesden Junction, take the Overground to Highbury and Islington, travelling into Moorgate, use the Undergound to King Cross St. Pancras and catch a final train from Kings Cross to Finsbury Park).

Accrington (ACR) and HUDDERSFIELD GROUP (G40) - added sequence 'NP+MS'​

No effect.

Blackburn (BBN) and HUDDERSFIELD GROUP (G40) - added sequence 'NP+MS'​

This adds a mapped route using the shortest route via Brighouse. This may have fit better in another part of the summary.

Bolton (BON) and Finsbury Park (FPK) - added sequence 'MA+OV+KP'
Bolton (BON) and Highbury And Islington (HHY) - added sequence 'MA+OV'​

These add mapped routes via Gospel Oak. They weren't valid valid via Peterborough before this.

Finsbury Park (FPK) and WIGAN GROUP (G34) - added sequence 'KP+OV+EP'
Finsbury Park (FPK) and WIGAN GROUP (G34) - removed sequence 'AC+NC'
Finsbury Park (FPK) and WIGAN GROUP (G34) - removed sequence 'AC+NN'
Finsbury Park (FPK) and WIGAN GROUP (G34) - removed sequence 'AM+NN'
Finsbury Park (FPK) and WIGAN GROUP (G34) - removed sequence 'AM+XW'
Finsbury Park (FPK) and WIGAN GROUP (G34) - removed sequence 'AS+NC'
Finsbury Park (FPK) and WIGAN GROUP (G34) - removed sequence 'AS+NN'
Finsbury Park (FPK) and WIGAN GROUP (G34) - removed sequence 'EC+MN+NN'
Finsbury Park (FPK) and WIGAN GROUP (G34) - removed sequence 'EC+MN+XW'
Finsbury Park (FPK) and WIGAN GROUP (G34) - removed sequence 'EE+DB'
Finsbury Park (FPK) and WIGAN GROUP (G34) - removed sequence 'EE+DW'
Finsbury Park (FPK) and WIGAN GROUP (G34) - removed sequence 'KP+BP+BS'​

These remove mapped routes via Peterborough.
They add routes via Gospel Oak and via Preston.

Blackburn (BBN) and Highbury And Islington (HHY) - removed sequence 'BK+BP+KP'
Blackburn (BBN) and Highbury And Islington (HHY) - removed sequence 'CU+AC'
Blackburn (BBN) and Highbury And Islington (HHY) - removed sequence 'CU+AS'
Blackburn (BBN) and Highbury And Islington (HHY) - removed sequence 'DP+EE'
Blackburn (BBN) and Highbury And Islington (HHY) - removed sequence 'KM+AC'
Blackburn (BBN) and Highbury And Islington (HHY) - removed sequence 'KM+AM'
Blackburn (BBN) and Highbury And Islington (HHY) - removed sequence 'KM+AS'
Blackburn (BBN) and Highbury And Islington (HHY) - removed sequence 'KM+DB+EE'
Blackburn (BBN) and Highbury And Islington (HHY) - removed sequence 'KM+DW+EE'
Blackburn (BBN) and Highbury And Islington (HHY) - removed sequence 'KM+MN+EC'
Blackburn (BBN) and Highbury And Islington (HHY) - removed sequence 'NP+EC'
Blackburn (BBN) and Highbury And Islington (HHY) - removed sequence 'NP+ER'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'AC+CU'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'AC+KM'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'AM+KM'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'AM+XW'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'AS+CU'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'AS+KM'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'EC+MN+KM'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'EC+MN+XW'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'EC+NP'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'EE+DB+KM'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'EE+DB+XW'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'EE+DP'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'EE+DW+KM'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'EE+DW+XW'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'ER+NP'
Highbury And Islington (HHY) and Kirkham And Wesham (KKM) - removed sequence 'KP+BP+BK'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'AC+CU'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'AC+KM'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'AM+KM'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'AM+XW'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'AS+CU'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'AS+KM'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'EC+MN+KM'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'EC+MN+XW'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'EC+NP'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'EE+DB+KM'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'EE+DB+XW'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'EE+DP'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'EE+DW+KM'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'EE+DW+XW'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'ER+NP'
Highbury And Islington (HHY) and Preston (Lancs) (PRE) - removed sequence 'KP+BP+BK'
​

These remove mapped routes via Peterborough.

LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'BX+BP+KP'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'CU+AC'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'CU+AS'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'LX+ER'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'MX+AC'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'MX+AM'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'MX+AS'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'MX+DB+EE'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'MX+DW+EE'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'MX+MN+EC'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'XP+DP+EE'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'XP+NP+EC'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'XW+AM'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'XW+DB+EE'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'XW+DW+EE'
LANCASTER GROUP (G64) and Highbury And Islington (HHY) - removed sequence 'XW+MN+EC'​

This removes a lot of mapped routes via Peterborough, but not all of them.
This does include all of the mapped routes via Bingham, Cambridge, Halifax, Huddersfield and Stamford, amongst others.

Easements

Following a review of easements the following was removed.

Easement removed Removed 700068: Customers travelling from Chester Le Street to/via Durham may not travel via Newcastle. This easement applies in both directions.​

And it works (at least, on journeys long enough for this not to be forbidden anyway).

Following a review of easements the following was amended (to make this Local easement effective). Public text amended to list affected stations.

Easement changed 700478: Customers travelling via Berwick Upon Tweed to stations Musselburgh, Wallyford, Prestonpans, Longniddry, Drem, North Berwick and Dunbar in possession of tickets routed "Any Permitted" or "EC & Connections" may double back via Edinburgh. This easement applies in both directions.​

The stations this easement previously listed after "to" were "Dunbar and Drem".

They've also replaced the semi-colon in easement 700575 with a comma.

 

[MKB]

LIVERPOOL GROUP (G18) and Nuneaton (NUN) - removed sequence 'NO+BM+BP'
LIVERPOOL GROUP (G18) and Nuneaton (NUN) - removed sequence 'NR+BM'
LIVERPOOL GROUP (G18) and Nuneaton (NUN) - removed sequence 'NR+BM+BP'​

I'm very upset at this. It explains why most of the booking engines are today refusing to sell me my preferred journey back from Liverpool to Nuneaton on a weekday morning, which is a perfectly reasonable route, namely:

Liverpool Lime Street - depart 06:22
Manchester Piccadilly - arrive 07:10
Manchester Piccadilly - depart 07:35
Nuneaton - arrive 0844

This journey is not overtaken by any other journey options from Liverpool to Nuneaton at that time.

Yet, bizarrely, LIV-MAN-NUN is still valid (on maps NO+BM) provided you take the much longer journey via Earlestown.

Is there any way I can challenge this change to get it reversed?

 

[Merseysider]

I'm very upset at this. It explains why most of the booking engines are today refusing to sell me my preferred journey back from Liverpool to Nuneaton on a weekday morning, which is a perfectly reasonable route, namely:

Liverpool Lime Street - depart 06:22
Manchester Piccadilly - arrive 07:10
Manchester Piccadilly - depart 07:35
Nuneaton - arrive 0844

This journey is not overtaken by any other journey options from Liverpool to Nuneaton at that time.

Yet, bizarrely, LIV-MAN-NUN is still valid (on maps NO+BM) provided you take the much longer journey via Earlestown.

Is there any way I can challenge this change to get it reversed?

Personally I'd just continue using the route.

If challenged, explain it's the fastest way to make the journey at this time. Most guards would let it go at that. You can't be prosecuted for being off-route, the worst that can happen is that you would have to pay an excess for the Warrington Central - Stoke bit (where you leave the official permitted route and rejoin it).

If that happened, just split your tickets at Warrington (the SOR WAC-NUN is £41.60 and valid via Manc). If the lovely people at ATOC try and remove validity via Manchester on that one then it will be argued.

 

[MKB]

If that happened, just split your tickets at Warrington (the SOR WAC-NUN is £41.60 and valid via Manc). If the lovely people at ATOC try and remove validity via Manchester on that one then it will be argued.

£41.60 is with railcard discount, which is not valid on my Two-Together one at that time of day. In any case, my outbound is not via WAC, so doesn't help.

Currently, SVR NUN-LIV is £42.50 before discount and travel is valid any time after 04:15 and gives me flexibility if my plans change.

This routeing change represents a significant cost increase for me.

Interestingly, the overnight maintenance on LM's website has not yet removed the LIV-MAN-NUN 06:22 option:

Dep Arr Ch Duration
03:38 06:17 1 2:39hrs
05:26 07:06 1 1:40hrs
06:05 08:18 1 2:13hrs
06:22 08:44 1 2:22hrs
06:30 09:22 1 2:52hrs
07:04 09:27 1 2:23hrs
07:34 10:23 1 2:49hrs
07:47 10:23 2 2:36hrs
08:34 10:35 1 2:01hrs
08:47 10:35 1 1:48hrs

 

[Merseysider]

Oops, hadn't realised I'd put the rc discount in. I'm used to querying with YNG discount so it was automatic.

This routeing change doesn't represent a significant cost increase for you. Just book your tickets through the TPE/LM website and select 0622-0844 as your return itinerary.

If you can get an itinerary, it's valid.

 

[clagmonster]

Is there any way I can challenge this change to get it reversed?

From the NRG:
"DISPUTED ROUTEINGS
The permitted routes shown in the Routeing Guide precisely define the various routes that a
customer may use to make a particular journey. These routes have been included to reflect all
the travel options that were previously legitimately available to customers when travel was
deemed to be valid via ‘any reasonable route’. A lengthy consultation process has been
undertaken involving the Train Operating Companies, Central Rail User’s Consultative
Committee, Office of the Rail Regulator and Office of Passenger Rail Franchising aimed at
defining precisely what these permitted routes should be.
It is appreciated that on occasions customers may claim that the National Routeing Guide now
prevents them from travelling via a route that was previously valid for them to travel on under
the ‘any reasonable route’ ruling. In such instances the following procedures should be
followed.
1. Inform the customer that travel is now only valid via the permitted routes shown within
the National Routeing Guide.
2. Advise the customer that a ‘disputed routeing procedure’ exists whereupon
consideration will be given to whether the route disputed by the customer can be
included as an easement and included as a permitted route in the future.
3. Take details of the disputed route which the customer now claims to be prevented from
using and forward to the Customer Relations Office of any Train Operator providing
services along the disputed route. Remember to record the customer’s name and
address.
4. Advise the customer that a ruling will be sought through the Association of Train
Operating Companies (ATOC) in liaison with the Department for Transport, to ascertain
whether the disputed route should be allowed or declined. A written reply will be sent
by ATOC direct to the customer advising them of the adjudication as soon as possible.
5. Upon receipt of a disputed routeing from a customer the Customer Relations Office
should arrange to forward details to ATOC as soon as possible to allow for a prompt
adjudication.
6. Should a disputed route be conceded the customer will be entitled to a refund of fare
for any additional payment that may have been necessary to have allowed them to
make their journey via the disputed route. In this event, the customer will be
compensated.
7. Where a disputed route is conceded, ATOC will arrange for an additional easement to be
published."
http://iblocks-rg-publication.s3-website-eu-west-1.amazonaws.com/nrg_instructions.pdf

The instructions assume you are stopped whilst using the ticket on the invalid route, which is something I wouldn't want to do as it would surely be a byelaw 18 matter. I'd suggest contacting the customer relations departments of the relevant TOCs; VTWC and however operates your preferred Liverpool-Manchester service.
--- old post above --- --- new post below ---

If challenged, explain it's the fastest way to make the journey at this time. Most guards would let it go at that. You can't be prosecuted for being off-route, the worst that can happen is that you would have to pay an excess for the Warrington Central - Stoke bit (where you leave the official permitted route and rejoin it).

Surely you could be prosecuted under byelaw 18, and if it could be proved that you knew it was invalid and deliberately avoided paying the excess up to a valid combination of tickets, the RoRA. Am I missing something?

 

[MKB]

Oops, hadn't realised I'd put the rc discount in. I'm used to querying with YNG discount so it was automatic.

This routeing change doesn't represent a significant cost increase for you. Just book your tickets through the TPE/LM website and select 0622-0844 as your return itinerary.

If you can get an itinerary, it's valid.

The Webtis sites won't let me combine a 2TR discount on the outbound with the full fare on the return.
--- old post above --- --- new post below ---
Thanks for those links Clagmonster.

 

[Merseysider]

Surely you could be prosecuted under byelaw 18, and if it could be proved that you knew it was invalid and deliberately avoided paying the excess up to a valid combination of tickets, the RoRA. Am I missing something?

That is one way of looking at it. But in my opinion as long as you don't refuse to pay an excess when requested I don't think a RoRA would stick.

After all, the Routeing Guide isn't the only thing that determines validity. As I mentioned, a ticket purchased in conjunction with an itinerary automatically validates the route.

I have an inkling tickets were accepted via this route at privatisation, before the RG was implemented (Any reasonable route allowed as long as it doesn't undercut an intermediate fare). If so, the route would thus be protected. NFM64 data shows the following:

0435-1077 £20
0455-1077 £16.50
0438-1077 £19

for the Standard Open Single, where 0435 is Liverpool Stations, 0455 is Warrington stations and 0438 is Manchester Stations.

In my opinion the route is valid even though the NRG says otherwise. But I can understand there are also arguments to the contrary.

 

[kieron]

The Webtis sites won't let me combine a 2TR discount on the outbound with the full fare on the return.

I suppose you could use an itinerary from one site, together with tickets you couldn't possibly have bought from there. If you're not going the same way in each direction, you probably don't want to get reservations on-line anyway.

If they do disappear, there are stations near Liverpool and Nuneaton such that a ticket from one to the other is valid via Manchester using the same trains, going by the routeing guide. I don't know if there are any that are as cheap as the one you're using, though.

Probably the first thing you could do would be to contact Virgin (who price the flow) about it, and explain how this change affects you. As the reason given for this in the summary was "consistency", this may not be a ticket they're especially worried about how people use.

 

[MKB]

Oddly, the 06:22 LIV-NUN option has made a re-appearance in trainline.com booking engines today.

Checking further, I can see that NR+TM has been added back to the list of permitted routes. And it's referenced here: http://www.atoc.org/about-atoc/rail-settlement-plan/routeing-guide/

Following customer comment, permitted routes between Liverpool and Nuneaton have been amended to create a mapped route via Hunts Cross and Warrington central.
Map sequence added
LIVERPOOL GROUP (G18) and Nuneaton (NUN) - added sequence 'NR+TM'

So thanks to whoever in ATOC reads this forum and sorted that out!

I hope there will be no more tinkering. Typical journey times on this route are already longer than LIV-EUS despite it being half the distance, so removing an option that is 30 minutes quicker than the next service was not helpful!

 

[kieron]

I hadn't noticed that there'd been another update or two since I last looked. I've set my computer to keep an eye on it now. It does seem that Liverpool-Nuneaton wasn't the only route where they've adjusted their position.

In any case, there were apparently two more sets of changes last week. The first was:

New dataset RJRG0367 published 04 August 2015
This data release is to accomodate changes to a map easement published in RJRG0365. The easement data sent to journey planners has been amended to provide greater flexibility. The primary purpose is to allow journeys to/from Bath Spa to show options which involve interchange at Bristol Temple Meads (normally prohibited for such journeys). the easement text has been amended

700580: Due to engineering works in August 2015, affecting the route to the east of Bath Spa station, journeys from South Wales to Hampshire and Dorset will require to take alternative routes. For example Cardiff to Portsmouth direct trains will not operate. Journeys between S Wales and Hampshire/Dorset will be allowed to go via Swindon where interchange to connecting services will be permitted for the duration of this easement. In addition journeys to Bath Spa will be allowed to interchange at Bristol Temple Meads. This positive map easement will operate in both directions.​

The new bit is the "anyone going to Bath can change trains in Bristol" sentence.

The second, on Wednesday, was:

New dataset RJRG0368 published 06 august 2015

New Stations

Stations added

Bermuda Park (BEP) has been added
Coventry Arena (CAA) has been added
Eskbank (EKB) has been added
Galashiels (GAL) has been added
Gorebridge (GBG) has been added
Newtongrange (NEG) has been added
Shawfair (SFI) has been added
Stow (SOI) has been added
Tweedbank (TWB) has been added​

All fairly straightforward.

Bermuda Park and Coventry Arena are associated with Coventry and Nuneaton.
Shawfair, Eskbank, Newtongrange, Gorebridge, Stow, Galashiels and Tweedbank are associated with Edinburgh Group.

None are open yet, as far as I know.

"STO" is, of course, the CRS code for South Tottenham.

Following customer comment, permitted routes between Liverpool and Nuneaton have been amended to create a mapped route via Hunts Cross and Warrington central.

Map sequence added

LIVERPOOL GROUP (G18) and Nuneaton (NUN) - added sequence 'NR+TM'​

This allows various routes via Widnes and Rugeley. The routes which went via Widnes and Birmingham or Wolverhampton were not replaced.

A review of map permissions between Lancashire and London; between Lancashire and Finsbury Park and Alexandra Palace Routeing Points; to remove permissions via the East Coast Main Line north of Grantham, (created in error in April 2013), the following changes have been made.​

I suppose April 2013 must be the date of a routeing guide version used internally by ATOC (and maybe journey planners). There wasn't anything in the public domain which listed Alexandra Palace as a routeing point at the time.

Map sequences added

Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - added sequence 'LN+AM+KM'

Map sequences removed

Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'AC+CU'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'AC+KM'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'AM+KM'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'AM+XW'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'AS+CU'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'AS+KM'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'EC+MN+KM'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'EC+MN+XW'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'EC+NP'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'EE+DB+KM'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'EE+DB+XW'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'EE+DP'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'EE+DW+KM'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'EE+DW+XW'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'ER+NP'
Alexandra Palace (AAP) and Kirkham And Wesham (KKM) - removed sequence 'KP+BP+BK'​

This removes mapped routes via Lincoln, Newark, Uttoxeter and Narborough, and ones which go through both Sheffield and Warrington (with the only mapped routes through Sheffield and Wigan being on the TPE trains via Eccles and Golborne).

Alexandra Palace (AAP) and LANCASTER GROUP (G64) - added sequence 'LN+AM+MX'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'AC+CU'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'AC+MX'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'AM+MX'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'AM+XW'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'AS+CU'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'AS+MX'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'EC+MN+MX'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'EC+MN+XW'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'EC+NP+XP'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'EE+DB+MX'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'EE+DB+XW'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'EE+DP+XP'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'EE+DW+MX'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'EE+DW+XW'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'ER+LX'
Alexandra Palace (AAP) and LANCASTER GROUP (G64) - removed sequence 'KP+BP+BX'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - added sequence 'LN+AM+MX'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'AC+CU'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'AC+MX'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'AM+MX'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'AM+XW'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'AS+CU'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'AS+MX'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'EC+MN+MX'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'EC+MN+XW'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'EC+NP+XP'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'EE+DB+MX'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'EE+DB+XW'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'EE+DP+XP'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'EE+DW+MX'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'EE+DW+XW'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'ER+LX'
Alexandra Palace (AAP) and Oxenholme Lake District (OXN) - removed sequence 'KP+BP+BX'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'AC+CU'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'AC+MX'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'AM+XW'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'AS+CU'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'AS+MX'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'EC+MN+MX'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'EC+MN+XW'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'EC+NP+XP'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'EE+DB+MX'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'EE+DB+XW'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'EE+DP+XP'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'EE+DW+MX'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'EE+DW+XW'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'ER+LX'
Finsbury Park (FPK) and Oxenholme Lake District (OXN) - removed sequence 'KP+BP+BX'​

These removes mapped routes via Lincoln, Newark, Uttoxeter and Narborough.
They also remove mapped routes via Warrington which also go via Grantham or Oakham.

Finsbury Park (FPK) and LANCASTER GROUP (G64) - added sequence 'AM+MX'
LONDON GROUP (G01) and Kirkham And Wesham (KKM) - added sequence 'LN+AM+KM'​

These add mapped routes via Peterborough. These all either go via Oakham or Bingham.

LONDON GROUP (G01) and LANCASTER GROUP (G64) - added sequence 'LN+AM+MX'
LONDON GROUP (G01) and LANCASTER GROUP (G64) - removed sequence 'ER+LX'
LONDON GROUP (G01) and Oxenholme Lake District (OXN) - added sequence 'LN+AM+MX'
LONDON GROUP (G01) and Oxenholme Lake District (OXN) - removed sequence 'ER+LX'​

These add mapped routes via Stamford and via Bingham.
They remove mapped routes via Lincoln and via Newark.

Alexandra Palace (AAP) and Accrington (ACR) - removed sequence 'AC+CU'
Alexandra Palace (AAP) and Accrington (ACR) - removed sequence 'AC+KM'
Alexandra Palace (AAP) and Accrington (ACR) - removed sequence 'AM+KM'
Alexandra Palace (AAP) and Accrington (ACR) - removed sequence 'AS+CU'
Alexandra Palace (AAP) and Accrington (ACR) - removed sequence 'AS+KM'
Alexandra Palace (AAP) and Accrington (ACR) - removed sequence 'EC+MN+KM'
Alexandra Palace (AAP) and Accrington (ACR) - removed sequence 'EC+NP'
Alexandra Palace (AAP) and Accrington (ACR) - removed sequence 'EE+DP'
Alexandra Palace (AAP) and Accrington (ACR) - removed sequence 'ER+NP'
Alexandra Palace (AAP) and Accrington (ACR) - removed sequence 'KP+BP+BK'
Alexandra Palace (AAP) and Blackburn (BBN) - removed sequence 'AC+CU'
Alexandra Palace (AAP) and Blackburn (BBN) - removed sequence 'AC+KM'
Alexandra Palace (AAP) and Blackburn (BBN) - removed sequence 'AM+KM'
Alexandra Palace (AAP) and Blackburn (BBN) - removed sequence 'AS+CU'
Alexandra Palace (AAP) and Blackburn (BBN) - removed sequence 'AS+KM'
Alexandra Palace (AAP) and Blackburn (BBN) - removed sequence 'EC+MN+KM'
Alexandra Palace (AAP) and Blackburn (BBN) - removed sequence 'EC+NP'
Alexandra Palace (AAP) and Blackburn (BBN) - removed sequence 'EE+DB+KM'
Alexandra Palace (AAP) and Blackburn (BBN) - removed sequence 'EE+DP'
Alexandra Palace (AAP) and Blackburn (BBN) - removed sequence 'EE+DW+KM'
Alexandra Palace (AAP) and Blackburn (BBN) - removed sequence 'ER+NP'
Alexandra Palace (AAP) and Blackburn (BBN) - removed sequence 'KP+BP+BK'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'AC+CU'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'AC+KM'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'AM+KM'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'AM+XW'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'AS+CU'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'AS+KM'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'EC+MN+KM'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'EC+MN+XW'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'EC+NP'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'EE+DB+KM'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'EE+DB+XW'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'EE+DP'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'EE+DW+KM'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'EE+DW+XW'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'ER+NP'
Alexandra Palace (AAP) and Preston (Lancs) (PRE) - removed sequence 'KP+BP+BK'
Alexandra Palace (AAP) and WIGAN GROUP (G34) - removed sequence 'AC+NC'
Alexandra Palace (AAP) and WIGAN GROUP (G34) - removed sequence 'AC+NN'
Alexandra Palace (AAP) and WIGAN GROUP (G34) - removed sequence 'AM+NN'
Alexandra Palace (AAP) and WIGAN GROUP (G34) - removed sequence 'AM+XW'
Alexandra Palace (AAP) and WIGAN GROUP (G34) - removed sequence 'AS+NC'
Alexandra Palace (AAP) and WIGAN GROUP (G34) - removed sequence 'AS+NN'
Alexandra Palace (AAP) and WIGAN GROUP (G34) - removed sequence 'EC+MN+NN'
Alexandra Palace (AAP) and WIGAN GROUP (G34) - removed sequence 'EC+MN+XW'
Alexandra Palace (AAP) and WIGAN GROUP (G34) - removed sequence 'EE+DB'
Alexandra Palace (AAP) and WIGAN GROUP (G34) - removed sequence 'EE+DW'
Alexandra Palace (AAP) and WIGAN GROUP (G34) - removed sequence 'KP+BP+BS'​

These each remove all mapped routes via Peterborough.

Some of the routes changed last Monday were further changed on Wednesday as the permitted routes between one end and London changed. The total effect of these changes for these is:

Finsbury Park (FPK) - Kirkham And Wesham (KKM)​

Finsbury Park is in on the newly added route north, so this isn't affected by the Kirkham-London changes (unless there's a way to avoid passing through Finsbury Park so much en route that I haven't thought of).
The routes via Peterborough are still gone, with routes via Gospel Oak added.

Finsbury Park (FPK) - LANCASTER GROUP (G64)​

The maps for this route were changed directly on Monday and Wednesday, as well as the changes to the London-Lancaster routes.
In total, mapped routes have been removed via Lincoln, Newark, Narborough and Uttoxeter, as well as routes which go both through Peterborough and Warrington.
And mapped routes have been added via Gospel Oak.

Highbury And Islington (HHY) - Kirkham And Wesham (KKM)​

Highbury And Islington (HHY) - LANCASTER GROUP (G64)​

These changes remove all mapped routes via Lincoln, Newark, Uttoxeter and Narborough.
They also remove mapped routes which go via both Peterborough and Warrington, and those which started by going up the ECML as far as Alexandra Palace.
They add some routes which go via London, Peterborough and Chesterfield.

 

[MKB]

At some point the route Nuneaton to London Euston via Coventry has been removed. I can't see any reference to this in the changes log, and I suspect this was an unintentional change.

The Webtis booking engines are still offering this route, but NRE says two tickets are needed.

There are times of day when NUN-COV-EUS is quicker than waiting for the next direct NUN-EUS. Via Cov was valid previously as far back as I can remember.

Shouldn't map EB have a line linking NUN and COV? That would solve the problem.

 

[kieron]

Shouldn't map EB have a line linking NUN and COV? That would solve the problem.

The way they did it a couple of years ago was by having TV as a valid map for the journey. That would still work today.

ATOC's response to this concern was included in a set of updates published on Thursday:

New Dataset RJRG0369 published 13 August 2015

New Stations

Station added

Cranbrook (CBK) has been added
​

This is associated with Exeter Group and Salisbury. The station itself isn't that far from Exeter.

Review of permissions from Lancashire/Greater Manchester to Stansted via south end of ECML has led to these changes

Map sequence removed

Accrington (ACR) and STANSTED GROUP (G66) - removed sequence 'DP+AD'
Accrington (ACR) and STANSTED GROUP (G66) - removed sequence 'KM+MN+AL'
Accrington (ACR) and STANSTED GROUP (G66) - removed sequence 'NP+AY'
Bolton (BON) and STANSTED GROUP (G66) - removed sequence 'DB+AD'
Bolton (BON) and STANSTED GROUP (G66) - removed sequence 'DB+EE+KE'
Bolton (BON) and STANSTED GROUP (G66) - removed sequence 'DW+AD'
Bolton (BON) and STANSTED GROUP (G66) - removed sequence 'DW+EE+KE'
Bolton (BON) and STANSTED GROUP (G66) - removed sequence 'MN+AL'
Bolton (BON) and STANSTED GROUP (G66) - removed sequence 'MN+AY'
Bolton (BON) and STANSTED GROUP (G66) - removed sequence 'MN+EC+KE'
LANCASTER GROUP (G64) and STANSTED GROUP (G66) - removed sequence 'LX+AL'
LANCASTER GROUP (G64) and STANSTED GROUP (G66) - removed sequence 'MX+DB+AD'
LANCASTER GROUP (G64) and STANSTED GROUP (G66) - removed sequence 'MX+DW+AD'
LANCASTER GROUP (G64) and STANSTED GROUP (G66) - removed sequence 'MX+MN+AL'
LANCASTER GROUP (G64) and STANSTED GROUP (G66) - removed sequence 'MX+MN+AY'
LANCASTER GROUP (G64) and STANSTED GROUP (G66) - removed sequence 'XP+DP+AD'
LANCASTER GROUP (G64) and STANSTED GROUP (G66) - removed sequence 'XP+NP+AY'
LANCASTER GROUP (G64) and STANSTED GROUP (G66) - removed sequence 'XW+DB+AD'
LANCASTER GROUP (G64) and STANSTED GROUP (G66) - removed sequence 'XW+DW+AD'
LANCASTER GROUP (G64) and STANSTED GROUP (G66) - removed sequence 'XW+MN+AL'
LANCASTER GROUP (G64) and STANSTED GROUP (G66) - removed sequence 'XW+MN+AY'
STANSTED GROUP (G66) and Kirkham And Wesham (KKM) - removed sequence 'AD+DB'
STANSTED GROUP (G66) and Kirkham And Wesham (KKM) - removed sequence 'AD+DP'
STANSTED GROUP (G66) and Kirkham And Wesham (KKM) - removed sequence 'AD+DW'
STANSTED GROUP (G66) and Kirkham And Wesham (KKM) - removed sequence 'AL+MN+KM'
STANSTED GROUP (G66) and Kirkham And Wesham (KKM) - removed sequence 'AL+MN+KW'
STANSTED GROUP (G66) and Kirkham And Wesham (KKM) - removed sequence 'AY+MN+KM'
STANSTED GROUP (G66) and Kirkham And Wesham (KKM) - removed sequence 'AY+MN+KW'
STANSTED GROUP (G66) and Kirkham And Wesham (KKM) - removed sequence 'AY+NP'
STANSTED GROUP (G66) and Oxenholme Lake District (OXN) - removed sequence 'AD+DB+MX'
STANSTED GROUP (G66) and Oxenholme Lake District (OXN) - removed sequence 'AD+DB+XW'
STANSTED GROUP (G66) and Oxenholme Lake District (OXN) - removed sequence 'AD+DP+XP'
STANSTED GROUP (G66) and Oxenholme Lake District (OXN) - removed sequence 'AD+DW+MX'
STANSTED GROUP (G66) and Oxenholme Lake District (OXN) - removed sequence 'AD+DW+XW'
STANSTED GROUP (G66) and Oxenholme Lake District (OXN) - removed sequence 'AL+LX'
STANSTED GROUP (G66) and Oxenholme Lake District (OXN) - removed sequence 'AL+MN+MX'
STANSTED GROUP (G66) and Oxenholme Lake District (OXN) - removed sequence 'AL+MN+XW'
STANSTED GROUP (G66) and Oxenholme Lake District (OXN) - removed sequence 'AY+MN+MX'
STANSTED GROUP (G66) and Oxenholme Lake District (OXN) - removed sequence 'AY+MN+XW'
STANSTED GROUP (G66) and Oxenholme Lake District (OXN) - removed sequence 'AY+NP+XP'
STANSTED GROUP (G66) and Preston (Lancs) (PRE) - removed sequence 'AD+DB'
STANSTED GROUP (G66) and Preston (Lancs) (PRE) - removed sequence 'AD+DP'
STANSTED GROUP (G66) and Preston (Lancs) (PRE) - removed sequence 'AD+DW'
STANSTED GROUP (G66) and Preston (Lancs) (PRE) - removed sequence 'AL+MN+KM'
STANSTED GROUP (G66) and Preston (Lancs) (PRE) - removed sequence 'AL+MN+KW'
STANSTED GROUP (G66) and Preston (Lancs) (PRE) - removed sequence 'AY+MN+KM'
STANSTED GROUP (G66) and Preston (Lancs) (PRE) - removed sequence 'AY+MN+KW'
STANSTED GROUP (G66) and Preston (Lancs) (PRE) - removed sequence 'AY+NP'
​

These remove mapped routes via Newark and Lincoln.

Blackburn (BBN) and STANSTED GROUP (G66) - removed sequence 'DB+AD'
Blackburn (BBN) and STANSTED GROUP (G66) - removed sequence 'DW+AD'
Blackburn (BBN) and STANSTED GROUP (G66) - removed sequence 'KM+MN+AL'
Blackburn (BBN) and STANSTED GROUP (G66) - removed sequence 'KW+MN+AL'
Blackburn (BBN) and STANSTED GROUP (G66) - removed sequence 'NP+AY'​

This removes mapped routes via York, Selby and Todmorden.
It also removes ones which go via Peterborough and also go through either Selby or Meadowhall (Stansted-Peterborough-Sheffield-Chinley-Blackburn is still fine).

Following customer report, it has been discovered that in February 2014 new map permissions were created between Nuneaton (NUN) and LONDON Group (G01) Routeing Points. The new map sequences did not include a location link between Nuneaton and Coventry for onward journeys via Rugby to London. There is no documented reason why this link should have been removed and it is now reinstated with the following change.

Map sequence added

LONDON GROUP (G01) and Nuneaton (NUN) - added sequence 'EB+MW'​

And so this adds mapped routes via Rugby and Bedworth.

A Retailer reported that journeys between Sheffield and Disley were denied when a doubleback was required at Stockport and Hazel Grove. These doublebacks are allowed by easements. The journeys were denied because the only mapped permissions were map SH. This map does not include links to Stockport and therefore the journey planner could not provide a journey plan which included travel via Stockport. Subsequently a review of the use of map SH, including on journeys between Lincolnshire/Derbyshire/Nottinghamshire/South Yorks and Hazel Grove/Chinley/Stockport Routeing Points has led to the following changes

Map sequence added

Barnetby (BTB) and Hazel Grove (HAZ) - added sequence 'HO'
Chesterfield (CHD) and Hazel Grove (HAZ) - added sequence 'HO'
Habrough (HAB) and Hazel Grove (HAZ) - added sequence 'HO'
Hazel Grove (HAZ) and Meadowhall (MHS) - added sequence 'HO'
Hazel Grove (HAZ) and Retford (RET) - added sequence 'SO+SH'
Hazel Grove (HAZ) and Sheffield (SHF) - added sequence 'HO'
Hazel Grove (HAZ) and Swinton (South Yorks) (SWN) - added sequence 'HO'
Hazel Grove (HAZ) and Worksop (WRK) - added sequence 'SO+SH'
Meadowhall (MHS) and Swinton (South Yorks) (SWN) - added sequence 'HO'
Sleaford (SLR) and Swinton (South Yorks) (SWN) - added sequence 'DL+NB'

Map sequences removed

Barnetby (BTB) and Hazel Grove (HAZ) - removed sequence 'HD'
Chesterfield (CHD) and Hazel Grove (HAZ) - removed sequence 'SH'
Habrough (HAB) and Hazel Grove (HAZ) - removed sequence 'HD'
Hazel Grove (HAZ) and Meadowhall (MHS) - removed sequence 'SH'
Hazel Grove (HAZ) and Sheffield (SHF) - removed sequence 'SH'
Hazel Grove (HAZ) and Swinton (South Yorks) (SWN) - removed sequence 'SH'
Meadowhall (MHS) and Sleaford (SLR) - removed sequence 'JL+SH'
Meadowhall (MHS) and Swinton (South Yorks) (SWN) - removed sequence 'YL'
Sleaford (SLR) and Swinton (South Yorks) (SWN) - removed sequence 'DL+PR+YL'​

No effect (although I can't speak for journey planners).

Cheadle Hulme (CHU) and NEWARK GROUP (G47) - added sequence 'HD+NS'
Cheadle Hulme (CHU) and NEWARK GROUP (G47) - added sequence 'SO+SH+NS'
Cheadle Hulme (CHU) and NEWARK GROUP (G47) - removed sequence 'HO+NS'
Cheadle Hulme (CHU) and NEWARK GROUP (G47) - removed sequence 'MH+EM'
Cheadle Hulme (CHU) and NEWARK GROUP (G47) - removed sequence 'MN+ER'
Cheadle Hulme (CHU) and NEWARK GROUP (G47) - removed sequence 'MS+EM'
Cheadle Hulme (CHU) and NEWARK GROUP (G47) - removed sequence 'PR+DG'​

This removes mapped routes via Manchester, Nottingham and Wakefield.
It adds the shortest route between Cheadle Hulme and Newark, which goes via Worksop.
The only other remaining mapped route is similar, but goes via Doncaster between Sheffield and Retford.

Chinley (CLY) and NEWARK GROUP (G47) - added sequence 'HD+NS'
Chinley (CLY) and NEWARK GROUP (G47) - added sequence 'SH+NS'
Chinley (CLY) and NEWARK GROUP (G47) - removed sequence 'MS+MM+EM'
Chinley (CLY) and NEWARK GROUP (G47) - removed sequence 'PS+ER'
Chinley (CLY) and NEWARK GROUP (G47) - removed sequence 'SH+ER'​

This removes mapped routes via Chesterfield, Lincoln, Wakefield and Barnetby.
Again, this leaves just the shortest route between Chinley and Newark, and a route via Doncaster.

Chinley (CLY) and Sleaford (SLR) - added sequence 'HO+NB+DL'
Chinley (CLY) and Sleaford (SLR) - added sequence 'HO+NH+JL'
Chinley (CLY) and Sleaford (SLR) - added sequence 'SH'
Chinley (CLY) and Sleaford (SLR) - removed sequence 'HO+GH'
Chinley (CLY) and Sleaford (SLR) - removed sequence 'HO+GH+DL'
Chinley (CLY) and Sleaford (SLR) - removed sequence 'PS'
Chinley (CLY) and Sleaford (SLR) - removed sequence 'PS+JL'
Chinley (CLY) and Sleaford (SLR) - removed sequence 'SH+JL'​

This removes mapped routes via Loughborough, Newark and Barnetby.

Hazel Grove (HAZ) and Lincoln (LCN) - added sequence 'HO+NH'
Hazel Grove (HAZ) and Lincoln (LCN) - added sequence 'SH'
Hazel Grove (HAZ) and Lincoln (LCN) - added sequence 'SO+SH'
Hazel Grove (HAZ) and Lincoln (LCN) - removed sequence 'MS+SH'
Hazel Grove (HAZ) and Lincoln (LCN) - removed sequence 'MS+SH+JL'​

This removes mapped routes via Manchester.

Hazel Grove (HAZ) and Sleaford (SLR) - added sequence 'HO+NB+DL'
Hazel Grove (HAZ) and Sleaford (SLR) - added sequence 'HO+NH+JL'
Hazel Grove (HAZ) and Sleaford (SLR) - added sequence 'SH'
Hazel Grove (HAZ) and Sleaford (SLR) - added sequence 'SO+SH'
Hazel Grove (HAZ) and Sleaford (SLR) - removed sequence 'MH+EM'
Hazel Grove (HAZ) and Sleaford (SLR) - removed sequence 'PS'
Hazel Grove (HAZ) and Sleaford (SLR) - removed sequence 'PS+JL'
Hazel Grove (HAZ) and Sleaford (SLR) - removed sequence 'SH+JL'​

This ticket no longer has mapped routes via Stockport (although there are still a few easements), Loughborough or Barnetby.
There are mapped routes along the ECML now, albeit only between Doncaster and Retford.

Lincoln (LCN) and Stockport (SPT) - added sequence 'NH+HO'
Lincoln (LCN) and Stockport (SPT) - added sequence 'SH+SO'
Lincoln (LCN) and Stockport (SPT) - removed sequence 'DG+PR'
Lincoln (LCN) and Stockport (SPT) - removed sequence 'JL+HO'
Lincoln (LCN) and Stockport (SPT) - removed sequence 'JL+MN'
Lincoln (LCN) and Stockport (SPT) - removed sequence 'SH+PR'​

This removes mapped routes via Manchester, Newark and Wakefield.

NEWARK GROUP (G47) and Hazel Grove (HAZ) - added sequence 'NS+HD'
NEWARK GROUP (G47) and Hazel Grove (HAZ) - added sequence 'NS+SH'
NEWARK GROUP (G47) and Hazel Grove (HAZ) - added sequence 'NS+SH+SO'
NEWARK GROUP (G47) and Hazel Grove (HAZ) - removed sequence 'EM+MH'
NEWARK GROUP (G47) and Hazel Grove (HAZ) - removed sequence 'ER+PS'
NEWARK GROUP (G47) and Hazel Grove (HAZ) - removed sequence 'ER+SH'​

This removes mapped routes via Barnetby, Grantham, Lincoln, Sleaford, Stockport and Wakefield.

Retford (RET) and Stockport (SPT) - added sequence 'SH+SO'
Retford (RET) and Stockport (SPT) - removed sequence 'NS+HO'
Retford (RET) and Stockport (SPT) - removed sequence 'SH+PR'
Stockport (SPT) and Worksop (WRK) - added sequence 'SO+SH'
Stockport (SPT) and Worksop (WRK) - removed sequence 'HO+NS'
Stockport (SPT) and Worksop (WRK) - removed sequence 'PR+SH'​

These removes mapped routes via Doncaster and via Manchester.
This leaves only the shortest route between each pair of stations.

Sheffield (SHF) and Sleaford (SLR) - added sequence 'JL'
Sheffield (SHF) and Sleaford (SLR) - added sequence 'NB+DL'
Sheffield (SHF) and Sleaford (SLR) - added sequence 'SH'
Sheffield (SHF) and Sleaford (SLR) - removed sequence 'JL+SH'
Sheffield (SHF) and Sleaford (SLR) - removed sequence 'PR+DL'
Sheffield (SHF) and Sleaford (SLR) - removed sequence 'SH+JL'
Sheffield (SHF) and Sleaford (SLR) - removed sequence 'YL+GS+DL'​

This removes mapped routes via Newark.

Sleaford (SLR) and Stockport (SPT) - added sequence 'DL+NB+HO'
Sleaford (SLR) and Stockport (SPT) - added sequence 'JL+NH+HO'
Sleaford (SLR) and Stockport (SPT) - added sequence 'SH+SO'
Sleaford (SLR) and Stockport (SPT) - removed sequence 'DL+GH+HO'
Sleaford (SLR) and Stockport (SPT) - removed sequence 'DL+PR'
Sleaford (SLR) and Stockport (SPT) - removed sequence 'GH+HO'
Sleaford (SLR) and Stockport (SPT) - removed sequence 'JL+HO'
Sleaford (SLR) and Stockport (SPT) - removed sequence 'JL+MN'
Sleaford (SLR) and Stockport (SPT) - removed sequence 'SH+PR'​

This removes mapped routes via Manchester, Newark and Wakefield.

Easements removed

This routeing point easement is not relevant as easement 700447 permits the journeys

700209: Customers travelling from Disley via Stockport may travel via Hazel Grove. This easement applies in both directions.​

Easement 70447 reads:

Customers travelling from Buxton, Dove Holes, Chapel en le Frith, Whaley Bridge, Furness Vale, New Mills Newtown, Disley, Middlewood and Hazel Grove to Sheffield and beyond in possession of tickets routed "Any Permitted" may double back between Hazel Grove and Stockport. This easement applies in both directions​

The connection between these two easements is not at all clear to me.

Then again, I don't know what journeys 700209 affected in the first place. Are there journeys from Disley for which Hazel Grove fails the fare check?

ATOC also made the following changes to the station association tables:

Ebbw Vale Town (EBB) and Rogerstone (ROR) are now associated with Newport (South Wales) (NWP).​

This means that every station on the Ebbw Vale line is asssociated with Newport and Cardiff Central apart from Pye Corner, which is only associated with Cardiff.

 

[Merseysider]

As ATOC are being rather 'proactive' in removing redundant easements, perhaps they would consider removing the following, which was drawn to their attention last year...

Customers travelling from Southport to Bryn and beyond in possession of fares routed "Liverpool" or "Any Permitted" may not travel via Wigan North Western. This easement applies in both directions.

This is despite the shortest route from Southport to Bryn/Garswood being via Wigan North Western.

Any Permitted and Via Wigan fares (both in the region of £12) are twice the price of Via Liverpool anyway, so it's not like there's a revenue risk. What Merseyrail/Northern were hoping to achieve by requesting this useless easement can only be speculated upon.

 

[Hadders]

I wonder if this forum gets a fee from ATOC for the advice we provide...

 

[kieron]

There was another set of updates on Thursday.

New Dataset RJRG0370 published 20 August 2015

A review of map permissions between Carlisle to and via East Coast mainline routes to eastern England has resulted in the following changes.

Map sequence added

Carlisle (CAR) and Cambridge (CBG) - added sequence 'GN+AT'​

Adds mapped routes which go through both Newcastle and Ely.

Carlisle (CAR) and Cheshunt (CHN) - added sequence 'GN+AT'
Carlisle (CAR) and Colchester. (COL) - added sequence 'GN+AT+AP'
Carlisle (CAR) and Doncaster. (DON) - added sequence 'GN+NT'
Carlisle (CAR) and Ely (ELY) - added sequence 'GN+AT'
Carlisle (CAR) and Ipswich (IPS) - added sequence 'GN+AT+AP'
Carlisle (CAR) and Manningtree (MNG) - added sequence 'GN+AT+AP'
Carlisle (CAR) and Marks Tey (MKT) - added sequence 'GN+AT+AP'
Carlisle (CAR) and Norwich (NRW) - added sequence 'GN+AT'
Carlisle (CAR) and Retford (RET) - added sequence 'GN+NT'
Carlisle (CAR) and Selby (SBY) - added sequence 'GN+YM'
Carlisle (CAR) and Shenfield (SNF) - added sequence 'GN+AT+AP'
Carlisle (CAR) and STANSTED GROUP (G66) - added sequence 'GN+AT'
Carlisle (CAR) and Stowmarket (SMK) - added sequence 'GN+AT+AB'
Carlisle (CAR) and Wickford (WIC) - added sequence 'GN+AT+AP'
Carlisle (CAR) and Witham (WTM) - added sequence 'GN+AT+AP'
Carlisle (CAR) and Worksop (WRK) - added sequence 'GN+NT'

Map sequence removed

Carlisle (CAR) and Cheshunt (CHN) - removed sequence 'HX+AA'
Carlisle (CAR) and Colchester. (COL) - removed sequence 'GN+AA+AP'
Carlisle (CAR) and Doncaster. (DON) - removed sequence 'HX+NS'
Carlisle (CAR) and Ely (ELY) - removed sequence 'GN+AA'
Carlisle (CAR) and Ipswich (IPS) - removed sequence 'GN+AA+AP'
Carlisle (CAR) and Manningtree (MNG) - removed sequence 'GN+AA+AP'
Carlisle (CAR) and Marks Tey (MKT) - removed sequence 'GN+AA+AP'
Carlisle (CAR) and Norwich (NRW) - removed sequence 'GN+AA'
Carlisle (CAR) and Retford (RET) - removed sequence 'HX+NS'
Carlisle (CAR) and Selby (SBY) - removed sequence 'HX+YA'
Carlisle (CAR) and Shenfield (SNF) - removed sequence 'GN+AA+AP'
Carlisle (CAR) and STANSTED GROUP (G66) - removed sequence 'HX+AA'
Carlisle (CAR) and Stowmarket (SMK) - removed sequence 'GN+AA+AP'
Carlisle (CAR) and Wickford (WIC) - removed sequence 'GN+AA+AP'
Carlisle (CAR) and Witham (WTM) - removed sequence 'GN+AA+AP'
Carlisle (CAR) and Worksop (WRK) - removed sequence 'HX+NS'
​

Remove mapped routes via Edinburgh.

Carlisle (CAR) and Grantham (GRA) - added sequence 'GN+GT'
Carlisle (CAR) and Grantham (GRA) - removed sequence 'HX+GS'
Carlisle (CAR) and Grantham (GRA) - removed sequence 'HX+GS+DL'​

Removes mapped routes via Edinburgh.
Also removes mapped routes which go through both Newcastle and Sleaford.

Carlisle (CAR) and Lincoln (LCN) - added sequence 'GN+NT'
Carlisle (CAR) and Lincoln (LCN) - removed sequence 'HX+NS'
Carlisle (CAR) and Lincoln (LCN) - removed sequence 'HX+NS+DG'
Carlisle (CAR) and Lincoln (LCN) - removed sequence 'HX+NS+JL'​

Removes mapped routes:
via Edinburgh; and
via both Newcastle and Retford.

Carlisle (CAR) and NEWARK GROUP (G47) - added sequence 'GN+NT'
Carlisle (CAR) and NEWARK GROUP (G47) - added sequence 'WG+WY+NT'
Carlisle (CAR) and NEWARK GROUP (G47) - removed sequence 'GP+DB+NH'
Carlisle (CAR) and NEWARK GROUP (G47) - removed sequence 'GP+NP+NS'
Carlisle (CAR) and NEWARK GROUP (G47) - removed sequence 'HX+NS'
Carlisle (CAR) and NEWARK GROUP (G47) - removed sequence 'HX+NS+DG'
Carlisle (CAR) and NEWARK GROUP (G47) - removed sequence 'TC+ER'​

Removes mapped routes:
via Edinburgh, Harrogate, Lincoln, Nottingham, Peterborough, Stalybridge or Todmorden;
via Halifax, Selby and Doncaster; and
via Halifax, York and Doncaster.
It also removes a direct map link between Pontefract Group and Doncaster (as used by Grand Central), although there are still mapped routes from Carlisle to Newark via Pontefract, Wakefield and Doncaster.
Adds mapped routes:
via Skipton and Selby;
via Skipton and York; and
via Skipton, Pontefract and Wakefield.

Carlisle (CAR) and Sleaford (SLR) - added sequence 'GN+AT'
Carlisle (CAR) and Sleaford (SLR) - removed sequence 'HX+GS+DL'​

Removed mapped routes via both Edinburgh and Grantham (this doesn't affect the routes via Edinburgh and Lincoln, of course).
Adds mapped routes via both Newcastle and Peterborough.

A review of map permissions to Stevenage from Lancashire has resulted in the following changes

Map sequence added

Accrington (ACR) and Stevenage (SVG) - added sequence 'DP+HU+KP'
Accrington (ACR) and Stevenage (SVG) - added sequence 'MH+MS+HU+KP'

Map sequence removed

Accrington (ACR) and Stevenage (SVG) - removed sequence 'DP+EE'
Accrington (ACR) and Stevenage (SVG) - removed sequence 'KM+MN+EC'
Accrington (ACR) and Stevenage (SVG) - removed sequence 'NP+EC'
Accrington (ACR) and Stevenage (SVG) - removed sequence 'NP+ER'​

Removes mapped routes:
via Stalybridge, Todmorden or York;
via Peterborough and Selby;
and via the direct link between Pontefract and Doncaster.
It adds mapped routes which go via both Doncaster and either Chinley or Ely.

Blackburn (BBN) and Stevenage (SVG) - added sequence 'DP+HU+KP'
Blackburn (BBN) and Stevenage (SVG) - added sequence 'MH+MS+HU+KP'
Blackburn (BBN) and Stevenage (SVG) - removed sequence 'DP+EE'
Blackburn (BBN) and Stevenage (SVG) - removed sequence 'KM+DB+EE'
Blackburn (BBN) and Stevenage (SVG) - removed sequence 'KM+DW+EE'
Blackburn (BBN) and Stevenage (SVG) - removed sequence 'KM+MN+EC'
Blackburn (BBN) and Stevenage (SVG) - removed sequence 'NP+EC'
Blackburn (BBN) and Stevenage (SVG) - removed sequence 'NP+ER'
Blackburn (BBN) and Stevenage (SVG) - removed sequence 'XW+DB+EE'
Blackburn (BBN) and Stevenage (SVG) - removed sequence 'XW+DW+EE'
Blackburn (BBN) and Stevenage (SVG) - removed sequence 'XW+MN+EC'​

Removes mapped routes:
via Stalybridge, Todmorden or York;
via Barnsley or Selby and Peterborough;
via Preston and Doncaster; and
via the direct map link between Pontefract Group and Doncaster.
It adds mapped routes which go via both Doncaster and either Chinley or Ely.

Kirkham And Wesham (KKM) and Stevenage (SVG) - added sequence 'DP+HU+KP'
Kirkham And Wesham (KKM) and Stevenage (SVG) - added sequence 'KM+MS+HU+KP'
Kirkham And Wesham (KKM) and Stevenage (SVG) - removed sequence 'DP+EE'
Kirkham And Wesham (KKM) and Stevenage (SVG) - removed sequence 'KM+DB+EE'
Kirkham And Wesham (KKM) and Stevenage (SVG) - removed sequence 'KM+DW+EE'
Kirkham And Wesham (KKM) and Stevenage (SVG) - removed sequence 'KM+MN+EC'
Kirkham And Wesham (KKM) and Stevenage (SVG) - removed sequence 'NP+EC'
Kirkham And Wesham (KKM) and Stevenage (SVG) - removed sequence 'NP+ER'
Kirkham And Wesham (KKM) and Stevenage (SVG) - removed sequence 'XW+DB+EE'
Kirkham And Wesham (KKM) and Stevenage (SVG) - removed sequence 'XW+DW+EE'
Kirkham And Wesham (KKM) and Stevenage (SVG) - removed sequence 'XW+MN+EC'​

Removes mapped routes:
via Lancaster, Selby, Stalybridge, Todmorden or York;
via Chinley and Wakefield or Hindley;
via Doncaster and Warrington; and
via the link from Pontefract Group to Doncaster, then either going directly to Retford or going later on to Lincoln.
Adds mapped routes via Chinley and either Cheadle Hulme or Ely.

LANCASTER GROUP (G64) and Stevenage (SVG) - added sequence 'LX+HU+KP'
LANCASTER GROUP (G64) and Stevenage (SVG) - added sequence 'MX+MS+HU+KP'
LANCASTER GROUP (G64) and Stevenage (SVG) - added sequence 'XP+DP+HU+KP'
LANCASTER GROUP (G64) and Stevenage (SVG) - removed sequence 'LX+ER'
LANCASTER GROUP (G64) and Stevenage (SVG) - removed sequence 'MX+DB+EE'
LANCASTER GROUP (G64) and Stevenage (SVG) - removed sequence 'MX+DW+EE'
LANCASTER GROUP (G64) and Stevenage (SVG) - removed sequence 'MX+MN+EC'
LANCASTER GROUP (G64) and Stevenage (SVG) - removed sequence 'XP+DP+EE'
LANCASTER GROUP (G64) and Stevenage (SVG) - removed sequence 'XP+NP+EC'
LANCASTER GROUP (G64) and Stevenage (SVG) - removed sequence 'XW+DB+EE'
LANCASTER GROUP (G64) and Stevenage (SVG) - removed sequence 'XW+DW+EE'
LANCASTER GROUP (G64) and Stevenage (SVG) - removed sequence 'XW+MN+EC'​

Removes mapped routes:
via Selby, Stalybridge, Todmorden or York;
via Manchester and Wakefield;
via Warrington and Doncaster; and
via Skipton and Pontefract.
Adds mapped routes via Chinley and either Cheadle Hulme or Ely.

Oxenholme Lake District (OXN) and Stevenage (SVG) - added sequence 'LX+HU+KP'
Oxenholme Lake District (OXN) and Stevenage (SVG) - added sequence 'MX+MS+EC+KP'
Oxenholme Lake District (OXN) and Stevenage (SVG) - added sequence 'MX+MS+HU+KP'
Oxenholme Lake District (OXN) and Stevenage (SVG) - added sequence 'XP+DP+HU+KP'
Oxenholme Lake District (OXN) and Stevenage (SVG) - removed sequence 'LX+ER'
Oxenholme Lake District (OXN) and Stevenage (SVG) - removed sequence 'MX+DB+EE'
Oxenholme Lake District (OXN) and Stevenage (SVG) - removed sequence 'MX+DW+EE'
Oxenholme Lake District (OXN) and Stevenage (SVG) - removed sequence 'MX+MN+EC'
Oxenholme Lake District (OXN) and Stevenage (SVG) - removed sequence 'XP+DP+EE'
Oxenholme Lake District (OXN) and Stevenage (SVG) - removed sequence 'XP+NP+EC'
Oxenholme Lake District (OXN) and Stevenage (SVG) - removed sequence 'XW+DB+EE'
Oxenholme Lake District (OXN) and Stevenage (SVG) - removed sequence 'XW+DW+EE'
Oxenholme Lake District (OXN) and Stevenage (SVG) - removed sequence 'XW+MN+EC'​

Removes mapeed routes:
via Selby, Stalybridge, Todmorden or York;
via Manchester and Wakefield;
via Warrington, Manchester and Doncaster; and
via Skipton, Pontefract and Peterborough.
Adds mapped routes via Chinley and either Cheadle Hulme or Ely.

Preston (Lancs) (PRE) and Stevenage (SVG) - added sequence 'DP+HU+KP'
Preston (Lancs) (PRE) and Stevenage (SVG) - added sequence 'KM+MS+HU+KP'
Preston (Lancs) (PRE) and Stevenage (SVG) - removed sequence 'DP+EE'
Preston (Lancs) (PRE) and Stevenage (SVG) - removed sequence 'KM+DB+EE'
Preston (Lancs) (PRE) and Stevenage (SVG) - removed sequence 'KM+DW+EE'
Preston (Lancs) (PRE) and Stevenage (SVG) - removed sequence 'KM+MN+EC'
Preston (Lancs) (PRE) and Stevenage (SVG) - removed sequence 'NP+EC'
Preston (Lancs) (PRE) and Stevenage (SVG) - removed sequence 'NP+ER'
Preston (Lancs) (PRE) and Stevenage (SVG) - removed sequence 'XW+DB+EE'
Preston (Lancs) (PRE) and Stevenage (SVG) - removed sequence 'XW+DW+EE'
Preston (Lancs) (PRE) and Stevenage (SVG) - removed sequence 'XW+MN+EC'​

Removes mapped routes:
via Lancaster, Selby, Stalybridge, Todmorden or York;
via Chinley and Barnsley or Hindley;
via Warrington and Doncaster;
via Accrington and Ely; and
via the link from Pontefract Group to Doncaster for routes also going via Peterborough.

Due to Sunday diversions of services between london and Brighton on 27 September 2015

Easement added

700581: On Sunday 27 September 2015 trains from London Victoria to Brighton are diverted via Horsham, Littlehampton and Worthing. This is not the normal permitted route between London and Brighton. As a result journey planners would not be able to show journeys to/from Brighton that involve changing trains in London. This map easement adds in the diversion and will operate in both directions.​

The easement says that it adds in the diversion. I don't know if this means that the a train which follows the (unstated) actual route of the diverted trains on the day would be valid on a ticket like this, or that you can follow any reasonable route between Brighton and London if your destination is beyond London, so long as it goes via Worthing, Littlehampton, Horsham and London Victoria.

In any case, it appears that anyone going to Hove or Moulsecoomb is just left to their own devices (or rather, to the rail replacement 'buses on some other route).

 

[Starmill]

Some of these changes are absolutely mind-boggling. Where exactly do they want people travelling from Lancashire to Hertfordshire to go? Via The Moon? :roll:

 

[kieron]

Most of the changes seem to have been to reduce the number of ways in which you can cross the Pennines and then go down the ECML. There are still plenty left, and more further south.

For instance, the shortest route from Preston to Stevenage is via Bolton and Worksop according to bukitlawang.com. There hasn't been a mapped route via Worksop since 2013.
--- old post above --- --- new post below ---
A new version has been released over the last couple of days.

New Dataset RJRG0371 published 26 August 2015

In addition to the changes listed below, a new section A of the Routeing Guide text has been published. Primarily to accomodate a new Routeing Point Calculator search tool (Step 4 Fares Check) using NFM64 Fares. To be made available on the Routeing Guide Help and instructions web pages between Section B (pink pages) and Section C (yellow pages).​

They uploaded a new version of the Instructions document yesterday, and updated the main page with yesterday's date this afternoon. They also added links to the routeing point calculator and a "NFM64 Fares" file.

The latter appears to be a text file with fixed width fields in it, and comes with no documentation of any sort. The former is a web app, with documentation only to explain its basic purpose.

There is nothing to explain what it means to say that a ticket is (say) "allowed on any route on NFM 64 by route 00600". There is also nothing to indicate what algorithm the web app uses to reach its decisions.

There are a few other changes:

Following a customer comment on the impact of deleting map AS in autumn 2011, (removing map links between Leeds Group (G16) and Hellifield Group (G53) for a journey between London Kings Cross and Glasgow Central. the following changes have been made.

Map sequence added

LONDON GROUP (G01) and GLASGOW GROUP (G13) - added sequence 'WA+EC+EG'
LONDON GROUP (G01) and GLASGOW GROUP (G13) - added sequence 'WA+ER+GY'
LONDON GROUP (G01) and GLASGOW GROUP (G13) - added sequence 'WA+ER+GY+WN'

Map sequence removed

LONDON GROUP (G01) and GLASGOW GROUP (G13) - removed sequence 'EC+GN'
LONDON GROUP (G01) and GLASGOW GROUP (G13) - removed sequence 'ER+GB'
LONDON GROUP (G01) and GLASGOW GROUP (G13) - removed sequence 'ER+GB+GK'​

This removes mapped routes via Stevenage and Pontefract or Bradford.
It also removes mapped routes which use a link between London and Highbury and Islington which doesn't show it going via Essex Road. You could, apparently, have caught the DLR from Limehouse to Shadwell en route if you'd really wanted.
It adds mapped routes via Cambridge, and ones via both Sheffield and Bradford.

LONDON GROUP (G01) and TROON GROUP (G81) - added sequence 'WA+TY+GN+KK'
LONDON GROUP (G01) and TROON GROUP (G81) - removed sequence 'EC+GN+AG'​

Removes mapped routes:
which go London-Edinburgh-Carlisle-Troon;
via Stevenage, Newcastle and Dumfries; and
via Limehouse and Selby or Newcastle;
Adds mapped routes via Cambridge (but not via Ely).

To accomodate temporary permitted routes via Carlisle during engineering works on the ECML north of Newcastle. The following changes have been made.

Easements removed1 easement(s) removed

700433: Customers travelling from or via London Kings Cross to Carlisle and beyond using fares routed "Any Permitted" may travel via Newcastle on Saturday and Sunday during Engineering Works from 04/10/2014 to 19/10/2014.​

Defunct, of course.

Easements added.

700581: Due to engineering works on the 14th November, 21st November, 28th November and 5th December 2015, north of Newcastle. Permitted routes will be amended via Carlisle to allow travel to/via Newcastle. This positive map easement applies in both directions.​

​

So does this allow travel via Carlisle or via Newcastle? I can't help feeling the old version was a lot clearer.

Incidentally, they haven't actually added an easement here. In creating this, they've replaced the engineering easement they created last week. I don't know if the engineering work has been cancelled, or if they're going to have another go at it later on or what the plan is. In any case, the first easement 700581 was:

On Sunday 27 September 2015 trains from London Victoria to Brighton are diverted via Horsham, Littlehampton and Worthing. This is not the normal permitted route between London and Brighton. As a result journey planners would not be able to show journeys to/from Brighton that involve changing trains in London. This map easement adds in the diversion and will operate in both directions.​

--- old post above --- --- new post below ---
There were some more changes yesterday:

New Dataset RJRG0372 published 28 August 2015

In dataset RJRG0371 - the original easement 700781 was deleted, (see text below), because on testing the day after publication, it was noted that the TOC Train Plan had changed overnight and train services were no longer diverted; but instead trains will now terminate at Three Bridges with replacement bus service to Brighton. The eassement was therefore redundant. The easement number was subsequently reissued to a new 700581 (see reference below)

700581: On Sunday 27 September 2015 trains from London Victoria to Brighton are diverted via Horsham, Littlehampton and Worthing. This is not the normal permitted route between London and Brighton. As a result journey planners would not be able to show journeys to/from Brighton that involve changing trains in London. This map easement adds in the diversion and will operate in both directions.​

That's one question answered.

To allow journeys between London Group (G01) and Crystal Palace (CYP) via New Cross Gate, (without the use of a map combination that created a circuitous route via Surrey Quays), the following changes have been published.

Map changed

Map BR - LONDON BRIDGE - LOCAL ROUTES changed (2 added links)​

This adds a link between Croydon and New Cross Gate.
No effect.

Map sequence added

Crystal Palace (CYP) and LONDON GROUP (G01) - added sequence 'BR'

Map sequence removed

Crystal Palace (CYP) and LONDON GROUP (G01) - removed sequence 'EL+BR'​

This removes mapped routes via New Cross Gate.

To accomodate Journey Planner needs for engineering disruption 29-31 August 2015 the following changes have been made.

Map sequence added

Hooton (HOO) and Lichfield Trent Valley (LTV) - added sequence 'BV'
HUNTS CROSS GROUP (G70) and Lichfield Trent Valley (LTV) - added sequence 'BV'
Huyton (HUY) and Lichfield Trent Valley (LTV) - added sequence 'BV'
LIVERPOOL GROUP (G18) and Lichfield Trent Valley (LTV) - added sequence 'BV'

Map sequence removed

Hooton (HOO) and Lichfield Trent Valley (LTV) - removed sequence 'BV+WM'
HUNTS CROSS GROUP (G70) and Lichfield Trent Valley (LTV) - removed sequence 'BV+WM'
Huyton (HUY) and Lichfield Trent Valley (LTV) - removed sequence 'BV+WM'
LIVERPOOL GROUP (G18) and Lichfield Trent Valley (LTV) - removed sequence 'BV+WM'​

These add mapped routes via Tamworth.
There are a few other additions, such as one where a northbound journey would start Lichfield-Rugeley-Walsall, but I don't know if the engineering works would make any of them useful.

Hooton (HOO) and Tamworth (TAM) - removed sequence 'BV+WM'
HUNTS CROSS GROUP (G70) and Tamworth (TAM) - removed sequence 'BV+WM'
Huyton (HUY) and Loughborough (Leics) (LBO) - added sequence 'BV+BP'
Huyton (HUY) and Loughborough (Leics) (LBO) - removed sequence 'BV+BP+MI'
Huyton (HUY) and Tamworth (TAM) - removed sequence 'BV+WM'
LIVERPOOL GROUP (G18) and Tamworth (TAM) - removed sequence 'BV+WM'​

No effect.

Easements added

700583: Due to engineering works, 29-31 August 2015, the normal permitted routes from Birmingham International to Liverpool are not available to journey planners. This map easement will create temporary permitted routes via Rugby during the period of the works. This easement applies in both directions​

I don't know if this is anything to do with the NFM64 changes, as Coventry-Liverpool isn't valid via Rugby either.

700585: During engineering works 29-31 August 2015, fares from the West Midlands priced on fare route 'Via Crewe' 00287 may travel via Shrewsbury. This Fare Route easement operates in both directions.​

Another engineering easement. Last bank holiday for a while...

For engineering work in December 2015 the following easement has been published.

Easement added

700582: Due to engineering works between Stafford and Crewe on the 27-28 December 2015, services between Birmingham and Scotland will be diverted via Shrewsbury and Chester. this positive map easement will create temporary permitted routes to facilitate this diversion. this easement applies in both directions.​

There are quite a few routes you could take between Birmingham and Scotland which go via Shrewsbury and Chester, even if not all of them are cleared for Voyagers.

Following comments the following easement text has been rewritten

700581 Customers travelling from or via London Kings Cross to Edinburgh and beyond may travel via Carlisle during engineering works on the 14th November, 21st November, 28th November and 5th December 2015, north of Newcastle. This positive map easement applies in both directions.​

That was quick!

The following easement has been published to accomodate the needs of a Journey planning system that was unable to show some services between Lockerbie and Milton Keynes.

Easement added

700584: This positive Routeing Point easement will override the Fare Checking rule which is preventing a Journey Planning system from finding journeys between Lockerbie and Milton Keynes Central. This easement will apply in both directions​

This doesn't say which routeing points you are allowed to use for Lockerbie, but it doesn't matter too much as both Milton Keynes-Carlisle and Milton Keynes-Carstairs (the two options) use the LM map, which only offers the route to Carstairs via Lockerbie anyway.

You get the same issue with other similar journeys such as ones from Northampton and Bletchley to Lockerbie.

To allow a journey planner to show journeys between Stoneleigh and Farnborough North utilising a doublback easement through Wimbledon and travel via Clapham Junction the following changes have been published.

Map sequence added

Motspur Park (MOT) and Woking (WOK) - added sequence 'WV'

Map sequence removed

Motspur Park (MOT) and Woking (WOK) - removed sequence 'WU'​

No effect, if you go by the published rules.
--- old post above --- --- new post below ---
There were a few more changes yesterday:

New Dataset RJRG0373 published 03 September 2015

To ensure Journey Plannwers can plan journeys Elgin to Glasgow Central via Cumbernauld the following changes have been published.

Map sequence added

Aberdeen (ABD) and GLASGOW GROUP (G13) - added sequence 'GA+GF'
Aberdeen (ABD) and GLASGOW GROUP (G13) - added sequence 'GA+WN'​

I'm not exactly sure how much this helps someone going from Elgin to Glasgow Central via Cumbernauld, but you can still go that way.
It does appear to add routes from Aberdeen (and Elgin) to Glasgow via Falkirk and Stirling, anyway.

For Christmas engineering works and the closure of the route between Slough and London Paddington the following changes have been published.

Easement added

700586: During engineering works between Slough and London Paddington on the 27 and 28 December 2015, services will be diverted at Reading via Basingstoke and Woking to London Waterloo. This map easement will create temporary permitted routes to allow for this diversion. the easement operates in both directions.​

I wonder if this applies to all tickets valid between Slough and London on the day, or just some of them.

700587: During engineering works between Slough and London Paddington on the 27 and 28 December 2015, services will be diverted via Banbury and High Wycombe to London Marylebone. This map easement will create temporary permitted routes to allow for this diversion. the easement operates in both directions.​

I'm a bit surprised to see an easement for this given that this is a route trains take every day. It would probably be less surprising if I knew where the temporary routes were going from and to.

I suppose things will be a bit clearer once the train timetable is confirmed, anyway.

Easements removed due to no longer required after end of engineering works

700580: Due to engineering works in August 2015, affecting the route to the east of Bath Spa station, journeys from South Wales to Hampshire and Dorset will require to take alternative routes. For example Cardiff to Portsmouth direct trains will not operate. Journeys between S Wales and Hampshire/Dorset will be allowed to go via Swindon where interchange to connecting services will be permitted for the duration of this easement. In addition journeys to Bath Spa will be allowed to interchange at Bristol Temple Meads. This positive map easement will operate in both directions.

700583: Due to engineering works, 29-31 August 2015, the normal permitted routes from Birmingham International to Liverpool are not available to journey planners. This map easement will create temporary permitted routes via Rugby during the period of the works. This easement applies in both directions

700585: During engineering works 29-31 August 2015, fares from the West Midlands priced on fare route 'Via Crewe' 00287 may travel via Shrewsbury. This Fare Route easement operates in both directions.​

All finished, as stated.

For engineering works, new easement (reusing the number 700585) to allow diversions via Severn Tunnel Junction and Newport (S Wales).

Easement added

700585: During Sunday engineering works 27 September and 04 October 2015, when Cross Country services from the West Country to Birmingham New Street and beyond are diverted via Severn Tunnel Junction, Newport (South Wales) and Lydney, this map easement will create temporary permitted routes that will allow Journey Planners to show journeys that include travel through Bristol Temple Meads and Birmingham New Street involving more than one service, (other than those on the shortest route or solely on a through train). This positive map easement operates in both directions.​

While this looks a lot like 700232 to me, things may seem different to Journey Planners.

 

[button_boxer]

For instance, the shortest route from Preston to Stevenage is via Bolton and Worksop according to bukitlawang.com.

Though for this route you'd have to take the Hope Valley stopper from Manchester to Sheffield via Marple rather than the fast trains (which go via Hazel Grove, a route that it says is within three miles of the shortest, but as pointed out on another thread that three mile allowance no longer seems to apply to a long distance journey...).

 

[kieron]

There doesn't always seem to be a clear relationship between what journey planners allow and what the Routeing Guide says is allowed.

In any case, there was another update released yesterday.

New Dataset RJRG0374 published 09 September 2015

Stansted Air Bus was added to the Routeing Guide in 2005. Currently there are no flows for it and Journey Planners do not offer it as an Origin/Destination. As result the following changes have been published.

Station removed

Stansted Air Bus (XTH)

Routeing groups changed

Routeing group contractedSTANSTED GROUP (G66) has removed member: Stansted Air Bus (XTH)
​

I wonder what happened to them all.

Following an investigation into permitted routes Folkestone to Melesham, it was noted that the map sequences between routeing point AFK and Croydon Group (G08) included a sequence that included a circuitous route via Hastings and brighton. The following changes have therefore been published.

Map sequence added

Ashford International. (AFK) and CROYDON GROUP (G08) - added sequence 'VH+SD'

Map sequence removed

Ashford International. (AFK) and CROYDON GROUP (G08) - removed sequence 'VH+LB'​

This removes mapped routes via Hastings, as you would expect.
It also removes ones which go via Paddock Wood, Beckenham Junction and either Elephant and Castle or Tulse Hill.
It adds mapped routes via Sutton.

For Christmas engineering works on the GWML the following positive easements have been published. 700588 & 700589 create temporary map links and therefore expanded map permissions; 700591 overrides geographic restrictions for the fare routes so that they may use the new map permissions in 700588.

700588: During Engineering works, the railway between Slough and Paddington will be closed on 27/28th December. Due to the level of disruption that customers from the Gloucester / Worcester / Hereford areas would face; tickets on routes 00200 VIA LONDON; 00201 NOT VIA BIRMNGHM; 00411 AP SLOUGH; 00412 AP NEWPT NOT LDN; 00413 AP SLOUGH NEWPRT; 00417 AP KEMBL NOT LDN; 00418 AP KEMBLE SLOUGH; 00433 AP EVESHAM; 00462 AP READING; 00473 AP LONDN READING; 00807 VIA STROUD; 00808 RDG STRD INC LDN, will be permitted to travel via Birmingham and onward to reach London Euston. This positive map easement will create the necessary temporary permitted routes in journey planners. this easement will operate in both directions​

As the text talks about "necessary temporary permitted routes" without giving any detail, I would hope that someone using one of the flexible tickets affected on a route via Birmingham would be accepted.

700589: Due to a total engineering work closure between Slough and Paddington on 27th/28th December 2015. This map easement is required to allow train services to be shown in journey planners in combination with two bus services that will run: Maidenhead - High Wycombe non-stop. And Maidenhead - all stations to Marlow - High Wycombe. Tickets to/via 'London Terminals' will thus be valid to/from London Marylebone from/to First Great Western origins on these dates only. This positive map easement applies in both directions.​

Seems simple enough.

700591: During Engineering works, the railway between Slough and Paddington will be closed on 27/28th December. Due to the level of disruption that customers from the Gloucester / Worcester / Hereford areas would face; tickets on routes 00200 VIA LONDON; 00201 NOT VIA BIRMNGHM; 00411 AP SLOUGH; 00412 AP NEWPT NOT LDN; 00413 AP SLOUGH NEWPRT; 00417 AP KEMBL NOT LDN; 00418 AP KEMBLE SLOUGH; 00433 AP EVESHAM; 00462 AP READING; 00473 AP LONDN READING; 00807 VIA STROUD; 00808 RDG STRD INC LDN, will be permitted to travel via Birmingham and onward to reach London Euston. This Fare Route easement will override the routeing restrictions of the quote fare routes. This easement will operate in both directions​

It seems a bit silly to have this separate from 700588, but at least this easement says what it does (even if it does nothing for "via London" tickets).

Following an investigation that revealed that Eaglescliffe - York route 'not Darlington' does not allow via double back at Thornaby, the following change has been published.

Easement added

700590: To allow journeys between Eaglescliff and York using tickets on fare route 00099 Not Via Darlington to Doubleback at Thornaby. This positive doubleback easement will operate in both directions.​

Eaglsecliffe and Thornaby are part of Middlesbrough routeing group, and Grand Central run a few trains a day between Eaglescliffe and Northallerton (and beyond). I feel the results of this investigation shouldn't have come as too much of a surprise.

This easement does not yet appear to have been adopted everywhere.

700592: To allow journeys Allens West - York on fare route 00000 'Any Permitted' to travel via Darlington; this routeing point easement will override the fares check. This easement will operate in both directions.​

This is another place where they're slowly putting permissions back from before the 1996 fare check thing.

Tees-side Airport-York (as well as Allens West-Poppleton and the like) is affected in the same way, but Allens West-York is probably the only route anyone has complained about so far.

Engineering works completed

Easement removed

700579: During Engineering Works in July and August, affecting the railway route through Box Tunnel, tickets routed 00618 is Via Salisbury, 00438 AP Salisbury and 00831 Via Bath Spa will be permitted to travel via Swindon and Westbury on First Great Western services.​

Expired, as stated.

They've also replaced "services" with "First Great Western services" in easement 700586.
They've done the same with easement 700587, and also changed "diverted via Banbury" to "diverted at Didcot Parkway via Banbury".

I think this does make it clearer what the easements relate to.

 

[greatkingrat]

Following an investigation into permitted routes Folkestone to Melesham, it was noted that the map sequences between routeing point AFK and Croydon Group (G08) included a sequence that included a circuitous route via Hastings and brighton. The following changes have therefore been published.​

Where is Melesham? At first I thought it was a typo for Melksham, but not sure what Croydon Group has to do with that?​

 

[MikeWh]

Where is Melesham? At first I thought it was a typo for Melksham, but not sure what Croydon Group has to do with that?

Looking at stations with Croydon Group as a routeing point, I'd say Merstham is most likely.

 

[WelshBluebird]

Grrrr typical they had to be doing work on the GWML around Christmas didn't they! (sorry off topic I know, but interesting that the routing guide has been updated before the works have been announced!)

 

[kieron]

Looking at stations with Croydon Group as a routeing point, I'd say Merstham is most likely.

They've since changed it to Merstham on the summary.

There was another update yesterday (Friday).

New dataset RJRG0375 published 18 september 2015

Withthe introduction of the Todmorden curve, a new routeing link has been created in the Routeing Guide data between Todmorden and Burnley Manchester Road. A number of changes have had to be made to accomodate this new link.

Map sequence removed

Accrington (ACR) and Retford (RET) - removed sequence 'KW+DP+NH'

Accrington (ACR) and Worksop (WRK) - removed sequence 'KW+DP+NH'​

No effect.

Maps changed

DP - DONCASTER TO PRESTON changed (2 added links)
NP - NORTH PENNINES ROUTE changed (2 added links)​

Adds Todmorden, with links to Burnley Manchester Road and Hebden Bridge.
These could conceivably have an effect on a route where you now switch to the map at Todmorden, but this seems unlikely to me as you could normally switch at Burnley or Hebden Bridge instead in the same situation. Otherwise it does nothing.

There are 28 different maps which have been used before or after NP in various sequences (some may no longer be used - I haven't checked), and 12 used before or after DP. None of them include Todmorden, so these changes have no effect.

MP - MANCHESTER TO PLYMOUTH VIA SHREWSBURY changed (1 added links)​

Adds Burnley Manchester Road, with a link to Todmorden.
None of the maps used before or after MP include Burnley, so this has no effect.

Obviously, these may have an effect on some easement or other, but as there's no public documentation on how maps affect easements it's hard to guess.

Easements added

700593: Customers from Colne, Nelson, Briefield, Burnley Central, Burnley Barracks, Rose Grove, Hapton and Huncoat travelling to or via Burnley Manchester Road may doubleback between Accrington and Rose Grove. This positive doubleback easement operates in both directions​

There are currently no fares between stations on the Colne branch and Burnley Manchester Road, although there are ones going beyond it.

Christmas engineering between stafford and Crewe. The planned train service diversions for Virgin Trains have been cancelled and the supporting map easement has now been deleted as it is not required.

Easement removed

700582: Due to engineering works between Stafford and Crewe on the 27-28 December 2015, services between Birmingham and Scotland will be diverted via Shrewsbury and Chester. this positive map easement will create temporary permitted routes to facilitate this diversion. this easement applies in both directions.​

So if you've bought a ticket on the strength of this, you'll have to find your own trains.

 

[Sacro]

So if you've bought a ticket on the strength of this, you'll have to find your own trains.

If you bought a ticket on the strength of this they have to honour it as you have a contract between yourself and the TOC to carry you with the rules / restrictions that applied when you booked.

 

[Andrew1395]

No virgin only tickets available yet and no journey planner has journeys for those dates. More significantly sounds like it wil be bus replacements or alternative routeing via Stoke on permitted routes instead of the diversions via Shrewsbury.

 

[kieron]

There was another update on Wednesday.

New dataset RJRG0376 published 23 September 2015

Following an enquiry from a retailer regarding permitted routes between Birmingham and Swindon a review (to remove circuitous routes via Taunton and via Bath) has led to the publication of the following changes

Map sequence added

Barnt Green (BTG) and Swindon (Wilts) (SWI) - added sequence 'BI+HP'
BIRMINGHAM GROUP (G02) and Swindon (Wilts) (SWI) - added sequence 'CB+HP'
Coventry (COV) and Swindon (Wilts) (SWI) - added sequence 'BI+CB+HP'

Map sequence removed

Barnt Green (BTG) and Swindon (Wilts) (SWI) - removed sequence 'WO'
Barnt Green (BTG) and Swindon (Wilts) (SWI) - removed sequence 'WR'
BIRMINGHAM GROUP (G02) and Swindon (Wilts) (SWI) - removed sequence 'BW'
Coventry (COV) and Swindon (Wilts) (SWI) - removed sequence 'BI+BW'
Swindon (Wilts) (SWI) and Wolverhampton (WVH) - added sequence 'HP+CB'
Swindon (Wilts) (SWI) and Wolverhampton (WVH) - removed sequence 'BW+WM'
WALSALL GROUP (G59) and Swindon (Wilts) (SWI) - added sequence 'CB+HP'
WALSALL GROUP (G59) and Swindon (Wilts) (SWI) - removed sequence 'BW'​

These remove mapped routes via Bath.
They add mapped routes via both Worcester and Stroud.

Bromsgrove (BMV) and Swindon (Wilts) (SWI) - added sequence 'BI+HP'
Bromsgrove (BMV) and Swindon (Wilts) (SWI) - removed sequence 'WO+WR'
Bromsgrove (BMV) and Swindon (Wilts) (SWI) - removed sequence 'WR'
Bromsgrove (BMV) and Swindon (Wilts) (SWI) - removed sequence 'WR+WO'​

This removes mapped routes via Bristol.
It adds ones via Worcester.

Lichfield Trent Valley (LTV) and Swindon (Wilts) (SWI) - added sequence 'BB'
Lichfield Trent Valley (LTV) and Swindon (Wilts) (SWI) - added sequence 'CB+HP'
Lichfield Trent Valley (LTV) and Swindon (Wilts) (SWI) - removed sequence 'PB+SB'
Lichfield Trent Valley (LTV) and Swindon (Wilts) (SWI) - removed sequence 'RB'
Lichfield Trent Valley (LTV) and Swindon (Wilts) (SWI) - removed sequence 'TL+BW'
Lichfield Trent Valley (LTV) and Swindon (Wilts) (SWI) - removed sequence 'WM+BW'​

This removes mapped routes via Bristol and via Stratford upon Avon.
It also removes mapped routes via Nuneaton and Oxford (which go Lichfield-Birmingham-Nuneaton-...).
It adds mapped routes via Tamworth and Oxford (which go Lichfield-Tamworth-Birmingham-...).
It also adds mapped routes via Worcester and Stroud.

Nuneaton (NUN) and Swindon (Wilts) (SWI) - added sequence 'BP+CB+HP'
Nuneaton (NUN) and Swindon (Wilts) (SWI) - removed sequence 'BP+BW'
Nuneaton (NUN) and Swindon (Wilts) (SWI) - removed sequence 'BP+PB+SB'
Rugby (RUG) and Swindon (Wilts) (SWI) - added sequence 'BI+CB+HP'
Rugby (RUG) and Swindon (Wilts) (SWI) - removed sequence 'BI+BW'
Rugby (RUG) and Swindon (Wilts) (SWI) - removed sequence 'BI+PB+SB'
Rugeley Trent Valley (RGL) and Swindon (Wilts) (SWI) - added sequence 'BP+CB+HP'
Rugeley Trent Valley (RGL) and Swindon (Wilts) (SWI) - added sequence 'WM+CB+HP'
Rugeley Trent Valley (RGL) and Swindon (Wilts) (SWI) - removed sequence 'BP+BW'
Rugeley Trent Valley (RGL) and Swindon (Wilts) (SWI) - removed sequence 'BP+PB+SB'
Rugeley Trent Valley (RGL) and Swindon (Wilts) (SWI) - removed sequence 'TL+PB+SB'
Rugeley Trent Valley (RGL) and Swindon (Wilts) (SWI) - removed sequence 'WM+BW'
Rugeley Trent Valley (RGL) and Swindon (Wilts) (SWI) - removed sequence 'WM+PB+SB'
STAFFORD GROUP (G65) and Swindon (Wilts) (SWI) - added sequence 'BV+CB+HP'
STAFFORD GROUP (G65) and Swindon (Wilts) (SWI) - removed sequence 'BV+BW'
STAFFORD GROUP (G65) and Swindon (Wilts) (SWI) - removed sequence 'BV+PB+SB'​

These removes mapped routes via Bristol.
They add mapped routes via both Worcester and Stroud.

Shrewsbury (SHR) and Swindon (Wilts) (SWI) - added sequence 'CA+CB+HP'
Shrewsbury (SHR) and Swindon (Wilts) (SWI) - removed sequence 'CA+BW'
Shrewsbury (SHR) and Swindon (Wilts) (SWI) - removed sequence 'CA+PB+SB'​

This removes mapped routes via Yate, via Taunton, and via both Bristol and Cheltenham.
It adds mapped routes via both Worcester and Stroud.

SMETHWICK GROUP (G63) and Swindon (Wilts) (SWI) - added sequence 'AB+BL'
SMETHWICK GROUP (G63) and Swindon (Wilts) (SWI) - added sequence 'CB+HP'
SMETHWICK GROUP (G63) and Swindon (Wilts) (SWI) - removed sequence 'WM+BL'
SMETHWICK GROUP (G63) and Swindon (Wilts) (SWI) - removed sequence 'WM+BW'​

This removes mapped routes via Bath, and via both Wolverhampton and Stroud.
It adds mapped routes via both Worcester and Stroud.

Swindon (Wilts) (SWI) and Tamworth (TAM) - added sequence 'BB'
Swindon (Wilts) (SWI) and Tamworth (TAM) - added sequence 'HP+CB'
Swindon (Wilts) (SWI) and Tamworth (TAM) - removed sequence 'BW'
Swindon (Wilts) (SWI) and Tamworth (TAM) - removed sequence 'BW+TL'
Swindon (Wilts) (SWI) and Tamworth (TAM) - removed sequence 'RB'
Swindon (Wilts) (SWI) and Tamworth (TAM) - removed sequence 'SB+PB'
Swindon (Wilts) (SWI) and Tamworth (TAM) - removed sequence 'SB+PB+TL'​

This removes mapped routes via Bristol.
It also removes a mapped route which goes via Stratford and then Birmingham to Tamworth.
It adds mapped routes via both Worcester and Stroud.

Swindon (Wilts) (SWI) and Tyseley (TYS) - added sequence 'WR+SM'
Swindon (Wilts) (SWI) and Tyseley (TYS) - removed sequence 'RB'​

This removes all but one mapped route.
In doing so, it removes mapped routes via Coventry and via Stratford upon Avon.
There are no mapped routes via Cheltenham, although it seems to me to be easier to find on a journey planner if you go that way.

To help Journey Planners to show journeys avoiding the use of bus replacement services, when train services are available, during the engineering works on the LSW Mainline a map easement will create temporary permitted routes via Veovil.

Easement added

700594: On Sunday 27 September 2015, engineering work will see trains from London Waterloo to Exeter diverted between Salisbury and Yeovil Junction via Westbury, Warminster and Castle Cary. This positive map easement will create temporary permitted routes for this diversionary route. This easement applies in both directions​

Nice and straightforward.

One other thing which was changed at the same time, but which wasn't included in the summary, was:

Sherburn-in-Elmet (SIE) has gained an association with Selby (SBY).​

This association was removed last December.

There are separate "any permitted" and "direct" tickets for Selby-Sherburn-in-Elmet, but the dearer version doesn't give any extra validity based on 1996 fares.

 

[bb21]

No doubt XC have been hard at it again trying to protect their rip-off flows. :roll:

What's wrong with Bristol being on a permitted route for these flows?