National Routeing Guide update

[kieron]

A new easement was added to the routeing guide today, although it hasn't reached the summary yet didn't reach the summary until the following day.

Engineering diversions affecting Cross Country services mean that trains will travel via Guildford rather than Basingstoke and Winchester. The trains will not be travelling over a mapped route and therefore a temporary map easement is required.​

700655 Due to engineering works on 16 October 2016, Cross Country services to/from Southampton and Bournemouth are diverted via North Camp, Haslemere and Fareham (without stopping at those locations). This map easement will create temporary permitted routes and facilitate journey planning. This easement applies in both directions.​

I wonder why the easement refers to a number of places where the trains don't call, but not to mention Guildford, where they are all scheduled to stop.

It's a funny way to get to Basingstoke, anyway.

 

[infobleep]

A new easement was added to the routeing guide today, although it hasn't reached the summary yet.

700655 Due to engineering works on 16 October 2016, Cross Country services to/from Southampton and Bournemouth are diverted via North Camp, Haslemere and Fareham (without stopping at those locations). This map easement will create temporary permitted routes and facilitate journey planning. This easement applies in both directions.​

I wonder why the easement refers to a number of places where the trains don't call, but not to mention Guildford, where they are all scheduled to stop.

It's a funny way to get to Basingstoke, anyway.

Don't remember them having an easement like that before but Cross Country train have certainly travelled this way before. When they do this, is possible to buy many more advance purchase tickets from Guildford to Oxford.

Sent from my SM-G925F using Tapatalk

 

[swt_passenger]

Don't remember them having an easement like that before but Cross Country train have certainly travelled this way before. When they do this, is possible to buy many more advance purchase tickets from Guildford to Oxford.

Sent from my SM-G925F using Tapatalk

Last time they diverted the whole XC service via Andover and Romsey they had to issue a load of new easements, although they hadn't needed to in previous years. I suspect it is another unintended consequence of the increased number of smaller maps that kieron mentioned on the 7th, in response to my earlier question.

 

[infobleep]

Last time they diverted the whole XC service via Andover and Romsey they had to issue a load of new easements, although they hadn't needed to in previous years. I suspect it is another unintended consequence of the increased number of smaller maps that kieron mentioned on the 7th, in response to my earlier question.

Thanks for that.

Sent from my SM-G925F using Tapatalk

 

[kieron]

Some more changes were published yesterday.

New dataset RJRG0421 published 12 August 2016

To reduce the number of maps used the following changes have been made , no impact on mapped rotes.

Map sequence added

Ely (ELY) and Peterborough. (PBO) - added sequence 'AP'
Norwich (NRW) and Peterborough. (PBO) - added sequence 'AP'

Map sequence removed

Ely (ELY) and Peterborough. (PBO) - removed sequence 'AB'
Norwich (NRW) and Peterborough. (PBO) - removed sequence 'AB'​

No effect on mapped routes, as stated - you can still use the shortest route between the routeing points. Both maps are listed thousands of times in the route tables.

To ensure mapped routes via Tamworth and Grantham are in place between Stafford (G65) and Sleaford Routeing Points the following changes have been made.

Map sequence added

STAFFORD GROUP (G65) and Sleaford (SLR) - added sequence 'MH+AS+DL'
STAFFORD GROUP (G65) and Sleaford (SLR) - added sequence 'WS+NT+DL'

Map sequence removed

STAFFORD GROUP (G65) and Sleaford (SLR) - removed sequence 'EM'​

No effect. MH+AS+DL provides the same routes EM did.

WS+NT+DL provides no routes at all. The only stations NT has in common with WS or DL are in Nottingham group. WS and DL only have Derby group-Nottingham group, and NT only has Nottingham Group-Worksop. The only direct route between Derby and Nottingham groups is via Attenborough and Long Eaton.

As you can't get from Derby group to Nottingham group and back, there are no mapped routes at all which use this map combination.

To remove circuitous routes and to align permissions in West Yorkshire the following deletion as been made between Leeds (G16) and Carlisle Routeing Points.

Map sequence removed

Carlisle (CAR) and LEEDS GROUP (G16) - removed sequence 'HX+MN'​

This removes mapped routes via Newcastle. You can still travel via Gargrave, Hebden Bridge or Standedge, though.

To remove circuitous routes and to align permissions in Cheshire and Merseyside, the following deletions have been made between Liverpool (G18) and Stoke on Trent Routeing Points.

Map sequence removed

Hooton (HOO) and Stoke On Trent (SOT) - removed sequence 'CV+EM'Find Item
HUNTS CROSS GROUP (G70) and Stoke On Trent (SOT) - removed sequence 'CV+EM'Find Item
Huyton (HUY) and Stoke On Trent (SOT) - removed sequence 'CV+EM'Find Item​

These remove all mapped routes via Runcorn.

This does not, of course, affect the shortest route, which is via Runcorn in the cases of Hunts Cross-Stoke and Huyton-Stoke.

LIVERPOOL GROUP (G18) and Stoke On Trent (SOT) - removed sequence 'CV+EM'​

This removes all mapped routes via Stafford.

Each of these has a greater choice of routes to Stoke than unaffected Cheshire routeing points such as Chester and Runcorn do.

To ensure that amended map permissions are targetted to the Bristol area the following easement has been rewritten.

Easement changed

700651: During route improvements works 12 September 2016 to 21 October 2016 that will see the closure of the Severn Tunnel, journeys from Bristol Temple Meads, Filton Abbeywood, Stapleton Road, Lawrence Hill, Bristol Parkway to Lydney, Chepstow, Caldicot and Severn Tunnel Junction may travel via Gloucester and Cheltenham Spa. This positive local easement will apply in both directions.​

This is a "local" easement which replaces a "map" easement added in June, which read:

During route improvements works 12 September 2016 to 21 October 2016 that will see the closure of the Severn Tunnel, alternative permitted routes to/from South Wales will be via Gloucester and Lydney. This positive map easement will apply in both directions.​

They're not all that similar.

They've also changed easement 700116 from being a "routeing point" easement to being a "local" one. The easement reads:

Customers travelling from Kennett to or via Ely, may travel via Cambridge. This easement applies in both directions.​

My understanding is that the former means "Cambridge can be a routeing point" in some situations, whereas the latter means "you can go via Cambridge when Ely is the routeing point" in equivalent cases. I assume this would also apply to journeys (such as Kennett-Thetford) where there is a common routeing point.

I think this easement would covers more journeys after the change than before.

 

[infobleep]

STAFFORD GROUP (G65) and Sleaford (SLR) - added sequence 'MH+AS+DL'
STAFFORD GROUP (G65) and Sleaford (SLR) - added sequence 'WS+NT+DL'

Map sequence removed

STAFFORD GROUP (G65) and Sleaford (SLR) - removed sequence 'EM'[/b][/indent]
No effect. MH+AS+DL provides the same routes EM did.

WS+NT+DL provides no routes at all. The only stations NT has in common with WS or DL are in Nottingham group. WS and DL only have Derby group-Nottingham group, and NT only has Nottingham Group-Worksop. The only direct route between Derby and Nottingham groups is via Attenborough and Long Eaton.

As you can't get from Derby group to Nottingham group and back, there are no mapped routes at all which use this map combination.

Why would they need to add WS+NT+DL if there are no mapped routes which use that map combination?

Sent from my SM-G925F using Tapatalk

 

[kieron]

Why would they need to add WS+NT+DL if there are no mapped routes which use that map combination?

The language used suggests they may have been trying to add something along the lines of the shortest route between Stafford and Sleaford, but didn't do it for some reason.

There are only 4 maps which include the Nottingham-Sleaford link, and they all go a lot further west, so I don't know if any combination would let you use this route. KN+KS would work if only it didn't require you to reverse in Grantham (something most of the trains do).
--- old post above --- --- new post below ---
Some more updates were published yesterday.

New dataset RJRG0422 published 19 August 2016

To ensure mapped routes via Tamworth and Grantham are in place between Stafford (G65) and Sleaford Routeing Points the following changes have been made.

Map sequence added

STAFFORD GROUP (G65) and Sleaford (SLR) - added sequence 'WS+AN+DL'

Map sequence removed

STAFFORD GROUP (G65) and Sleaford (SLR) - removed sequence 'WS+NT+DL'​

This allows routes via Tamworth. And I shouldn't underestimate what you can do if you use enough maps.

Engineering works easement Severn Tunnel closure

Easement added

700656: During the closure of the Severn Tunnel for rail enhancement works between 12 September and 21 October 2016, journeys from South Wales to the west country may travel via Gloucester and Swindon. This positive map easement applies in both directions​

West country is a pretty vague term (for example, the EU have two different Protected Geographical Indication areas for it). I think you'd be on fairly safe ground if you're going at least as far as Bristol Temple Meads, though.
There's already easement 700561 for local journeys. There also seems to be an easement which allows longer distance journeys via Gloucester and Bristol, but I don't know which it is at the moment.

700657: During engineering improvement works that will result in the closure of the Severn Tunnel between 12 September and 21 October 2016, journeys to and from South Wales on tickets routed (00616) SALISBURY NOT LONDON and (00618) VIA SALISBURY may travel via Reading. This positive fare route easement applies in both directions​

I haven't checked September's fares, but there aren't any SALISBURY NOT LONDON fares to South Wales in the current set, only to Devon or Cornwall.
There are plenty of "via Salisbury" fares, though.

Easements removed time expired

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

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

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

700641: During overnight engineering works from 23.20 Sunday 14 August 2016 to 05.20 Monday 15 August 2016, the route through Swindon will not be available. Alternative routeing via Newbury and Reading will be used. To destinations such as Oxford journeys on fare route NOT VIA READING (00810) will be permitted to travel via Reading during these times. This positive fare route easement applies in both directions

700642: During rail improvement works from 30 July 2016 to 14 August 2016 the route between Oxford and Didcot Parkway will be closed. Journeys that would normally be routed via Oxford on tickets routed (00000) ANY PERMITTED, (00433) AP EVESHAM, (00799) LONDON EVESHAM, (00803) EVESHAM STROUD, (00805) VIA EVESHAM and (00807) VIA STROUD may travel via Oxford Parkway for onward travel with Chiltern Railways; travel via Swindon to London (Paddington); travel via Birmingham New Street to London (Euston) and beyond is also permitted within this easement. As there will also be works at Banbury between 30 July and 07 August 2016, this easement will only allow travel via Leamington Spa from Warwick Parkway and intermediate stations towards London Marylebone from 08 August to 14 August 2016 inclusive. This positive fare route easement will apply in both directions for the time period stated only.

700643: During railway improvement works 30 July to 15 August 2016 services between Birmingham and Reading will not call at Oxford as bus replacement services will be in operation. This positive fare route easement will allow tickets to be retailed on fare route (00825) VIA OXFORD during this period. This easement applies in both directions.​

All finished now.

They've also changed the text of easement 700630 to remove the reference to engineering work which have (or should have) finished. It now reads:

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

--- old post above --- --- new post below ---
Some more easement changes were made today:

New dataset RJRG0423 published 22 August 2016

For engineering works new easements added

700658: Customers travelling from or via Haymarket to Edinburgh may doubleback through Haymarket during engineering works on Saturdays 17 and 24 September 2016; Sundays 18 and 25 September 2016 and Saturdays 01; 08 and 15 October 2016. This positive doubleback easement applies in both directions​

No trains are set to run between Chathill and Edinburgh (although no extra Chathill trains are scheduled to make up for it), and some trains are non-stop between Carlisle and Edinburgh. I'm struggling to think why someone travelling to Edinburgh would double back through Haymarket, though.

700659: During an engineering blockade at Fareham, from 22 October to 28 October 2016, tickets from South Wales and Bristol to the South Coast priced on route (00616) VIA SALISBURY and (00618) SALISBURY NOT LONDON, will be permitted to travel via ReadingFind Item​

As with South Wales, there don't appear to be any stations associated with Bristol, Bath or Chippenham which have "Salisbury not London" tickets to anywhere, but there are plenty of "via Salisbury" tickets.

Easements removed as time expired

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

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

Both finished. I suppose these are kept around at least until the relevant TOC confirms they don't want them.

Easement expanded and text rewritten

700116 - Local easement

Customers travelling from March, Manea, Kennett,Bury St Edmunds, Thurston and Elmswell to or via Ely, may travel via Cambridge. This positive local easement applies in both directions​

This previously only listed Kennett (which, as far as I know, only has Cambridge trains, not Ely ones). The rest of that line isn't much better, with a train to and from Ely every two hours. Manea only gets a train each way every two hours. March isn't as badly affected.

The "text rewritten" bit just means that "positive local" has been added to the last sentence.

 

[adrock1976]

For engineering works new easements added

700658: Customers travelling from or via Haymarket to Edinburgh may doubleback through Haymarket during engineering works on Saturdays 17 and 24 September 2016; Sundays 18 and 25 September 2016 and Saturdays 01; 08 and 15 October 2016. This positive doubleback easement applies in both directions

I believe this easement is to allow passengers from points west of Edinburgh to connect onto the diverted ICEC services, as the normal route does not double back through Haymarket when connecting onto the London Kings Cross services. This easement is most likely to make the journey planners work for the diversions.

Furthermore, I also believe that there is also a local easement for journeys starting and finishing in Scotland via Edinburgh that allows a doubleback through Haymarket for interchange purposes.

Not sure if I've made sense here or not.

 

[kieron]

I believe this easement is to allow passengers from points west of Edinburgh to connect onto the diverted ICEC services, as the normal route does not double back through Haymarket when connecting onto the London Kings Cross services.

I think that could be useful for some travellers (if you were going to South Gyle, say, which is in the Edinburgh routeing group).

The published easement only affects "Customers travelling from or via Haymarket to Edinburgh", though, which makes it less useful.

- - - - - - - - - - -

An additional easement (easement 700660) was published on Thursday which only affects today. It hasn't yet been added to ATOC's summary:

During enginerering works on 28/08/2016, journeys from and via Lewisham to London and beyond may travel via Denmark Hill and Elephant and Castle. This positive map easement applies in both directions.​

 

[kieron]

Sorry for not updating this sooner; I've had a few issues.

There were three updates to the routeing guide over the last couple of weeks; on the 1st, 7th and 9th of September. I've added what I've got so far below, but I haven't made much progress on the various map changes.

To start with:

New dataset RJRG0425 published 01 September 2016

For engineering works on the Great Western mainline.

Easement added

700661: During engineering works on Sundays 18 September 2016, 30 October 2016 and 06, 13 and 20 November 2016 the route through Swindon will not be available. Alternative routeing via Newbury and Reading will be used to destinations such as Oxford, journeys on fare route NOT VIA READING (00810) will be permitted to travel via Reading . This positive fare route easement applies in both directions.​

I think the last comma makes more sense as a full stop, but I'm not sure if it was intended .

700662: During engineering works that will close the route through Swindon on Sundays 18 September 2016 and the 02, 09, 16 and 23 October 2016, journeys from Hereford, Ledbury, Colwall, Great Malvern, Malvern Link, Worcester Shrub Hill, Worcester Foregate Street, Pershore and Evesham on tickets routed (00805) VIA EVESHAM, may travel via Birmingham New Street and London Euston. This fare route easement to apply in both directions​

I don't have access to the current fare list at the moment, but the last one included no "via Evesham" tickets from Pershore or Evesham. The other stations had quite a few.

700663: During engineering works on Sundays 30 October 2016 and 06, 13 and 20 November 2016, affecting the route through Swindon. Journeys from South Wales and Bristol to Oxford on tickets routed (00810)NOT VIA READING will be permitted to travel via Reading on Great Western services only. This fare route easement to apply in both directions.​

They must have decided that the buses will have enough capacity if they just send Oxford passengers on the trek to Reading.

Easement reworded

700657: During an engineering blockade at Fareham, from 12th September to 21st October 2016, tickets from or via Newport South Wales priced on route (00616) VIA SALISBURY and (00618) SALISBURY NOT LONDON, will be permitted to travel via Reading.This Fare Route Easement applies in both directions.​

The only substantial change here is that "to and from South Wales" has been changed to "from or via Newport South Wales". If you've already bought a ticket, of course, ...

700659: During an engineering blockade at Fareham, from 22 October to 28 October 2016, tickets from or via Newport South Wales priced on route (00616) VIA SALISBURY and (00618) SALISBURY NOT LONDON, will be permitted to travel via Reading.This Fare Route Easement applies in both directions.​

The previous version affected journeys "from South Wales and Bristol to the South Coast" and only with a route of "Salisbury not London", so that's quite a change.

Easement removed

700624: Due to engineering works between the 27 and 29 August 2016, services that travel from or via Cheltenham Spa to Bristol and beyond will be diverted via Kemble and Swindon. This positive map easement will provide temporary permitted routes via Swindon and will apply in both directions.

Timetabled diversion ended- easement no longer required.

Easement removed

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

Both gone. I haven't checked where the trains are going now for 700635.

To override NFM64 fares checking preventing journeys Rochdale line to Cambridge via Leeds the following easement has been published.

Easement added (note reference number reused - Previous use for short term engineering works easementin South London)

700660: For journeys to Cambridge from Moston, Mills Hill (Manchester), Castleton (Manchester), Rochdale, Smithy Bridge, Littleborough and Walsden on tickets routed (00422) PETERBOROUGH & VTEC, (00493) AP XC EMT & CONNS and (00700) NOT VIA LONDON, may travel via Sowerby Bridge and Halifax. This Routeing Point easement overrides the NFM64 fares check and operates in both directions.​

This was previously an easement provided on 25/8/16 for travel 3 days later, one which never reached ATOC's summary.

The new easement seems a bit odd to me. I'd expect Sowerby Bridge to pass a fare check for a ticket from any of those stations to Cambridge.

- -

The next set was:

New dataset RJRG0426 published 07 September 2016

A review of the use of Map LB and its replacement with alternative maps has led to the following changes (part 1)

Map sequence added

CROYDON GROUP (G08) and Leatherhead (LHD) - added sequence 'TN+DK'
CROYDON GROUP (G08) and Leatherhead (LHD) - removed sequence 'LB+DK'

Map sequence removed

CROYDON GROUP (G08) and Leatherhead (LHD) - removed sequence 'LB+HR'​

This removes mapped routes via Crystal Palace, via Mitcham Junction, via Redhill and via Tulse Hill.

Effingham Junction (EFF) and CROYDON GROUP (G08) - added sequence 'EF+TN'
Effingham Junction (EFF) and CROYDON GROUP (G08) - removed sequence 'DK+LB'
Effingham Junction (EFF) and CROYDON GROUP (G08) - removed sequence 'EF+LB'
Effingham Junction (EFF) and CROYDON GROUP (G08) - removed sequence 'HR+LB'​

This removes mapped routes via Crystal Palace, via Mitcham Junction, via Motspur Park, via Redhill and via Tulse Hill.

REDHILL GROUP (G60) and Leatherhead (LHD) - added sequence 'TN+DK'
REDHILL GROUP (G60) and Leatherhead (LHD) - added sequence 'TN+HR'
REDHILL GROUP (G60) and Leatherhead (LHD) - removed sequence 'LB+DK'
REDHILL GROUP (G60) and Leatherhead (LHD) - removed sequence 'LB+HR'​

This remove mapped routes:
via Crystal Palace;
via Peckham Rye;
via Three Bridges; and
via both Herne Hill and Wimbledon.

BRIGHTON GROUP (G04) and Leatherhead (LHD) - added sequence 'VB+HR'
BRIGHTON GROUP (G04) and Leatherhead (LHD) - added sequence 'VB+TN+DK'
BRIGHTON GROUP (G04) and Leatherhead (LHD) - removed sequence 'LB+DK'
BRIGHTON GROUP (G04) and Leatherhead (LHD) - removed sequence 'LB+HR'
EASTBOURNE GROUP (G84) and Leatherhead (LHD) - added sequence 'VB+HR'
EASTBOURNE GROUP (G84) and Leatherhead (LHD) - added sequence 'VB+TN+DK'
EASTBOURNE GROUP (G84) and Leatherhead (LHD) - removed sequence 'LB+DK'
EASTBOURNE GROUP (G84) and Leatherhead (LHD) - removed sequence 'LB+HR'
Effingham Junction (EFF) and BRIGHTON GROUP (G04) - added sequence 'DK+TN+VB'
Effingham Junction (EFF) and BRIGHTON GROUP (G04) - added sequence 'HR+VB'
Effingham Junction (EFF) and BRIGHTON GROUP (G04) - removed sequence 'DK+LB'
Effingham Junction (EFF) and BRIGHTON GROUP (G04) - removed sequence 'HR+LB'
Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - added sequence 'DK+TN+VB'
Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - added sequence 'EF+TN+VB'
Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - added sequence 'HR+VB'
Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - removed sequence 'DK+LB'
Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - removed sequence 'EF+LB'
Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - removed sequence 'HR+LB'
Effingham Junction (EFF) and Gatwick Airport (GTW) - added sequence 'AR+VB'
Effingham Junction (EFF) and Gatwick Airport (GTW) - added sequence 'DK+SC'
Effingham Junction (EFF) and Gatwick Airport (GTW) - removed sequence 'DK+LB'
Effingham Junction (EFF) and Gatwick Airport (GTW) - removed sequence 'HR+LB'
Effingham Junction (EFF) and Haywards Heath (HHE) - added sequence 'DK+TN+VB'
Effingham Junction (EFF) and Haywards Heath (HHE) - added sequence 'HR+VB'
Effingham Junction (EFF) and Haywards Heath (HHE) - removed sequence 'HR+LB'
Effingham Junction (EFF) and Lewes (LWS) - added sequence 'DK+TN+VB'
Effingham Junction (EFF) and Lewes (LWS) - added sequence 'HR+VB'
Effingham Junction (EFF) and Lewes (LWS) - removed sequence 'DK+LB'
Effingham Junction (EFF) and Lewes (LWS) - removed sequence 'HR+LB'
Effingham Junction (EFF) and REDHILL GROUP (G60) - added sequence 'AR'
Effingham Junction (EFF) and REDHILL GROUP (G60) - added sequence 'DK+TN'
Effingham Junction (EFF) and REDHILL GROUP (G60) - added sequence 'HR+TN'
Effingham Junction (EFF) and REDHILL GROUP (G60) - removed sequence 'DK+LB'
Effingham Junction (EFF) and REDHILL GROUP (G60) - removed sequence 'HR+LB'
Effingham Junction (EFF) and Wivelsfield (WVF) - added sequence 'DK+TN+VB'
Effingham Junction (EFF) and Wivelsfield (WVF) - removed sequence 'DK+LB'
Effingham Junction (EFF) and Wivelsfield (WVF) - removed sequence 'HR+LB'
Gatwick Airport (GTW) and Leatherhead (LHD) - added sequence 'SC+DK'
Gatwick Airport (GTW) and Leatherhead (LHD) - removed sequence 'LB+DK'
Gatwick Airport (GTW) and Leatherhead (LHD) - removed sequence 'LB+HR'
Haywards Heath (HHE) and Leatherhead (LHD) - added sequence 'VB+AR'
Haywards Heath (HHE) and Leatherhead (LHD) - added sequence 'VB+SC'
Haywards Heath (HHE) and Leatherhead (LHD) - added sequence 'VB+TN+DK'
Haywards Heath (HHE) and Leatherhead (LHD) - removed sequence 'LB+DK'
Haywards Heath (HHE) and Leatherhead (LHD) - removed sequence 'LB+HR'
Leatherhead (LHD) and Lewes (LWS) - added sequence 'DK+TN+VB'
Leatherhead (LHD) and Lewes (LWS) - added sequence 'HR+VB'
Leatherhead (LHD) and Lewes (LWS) - removed sequence 'DK+LB'
Leatherhead (LHD) and Lewes (LWS) - removed sequence 'HR+LB'
Leatherhead (LHD) and Wivelsfield (WVF) - added sequence 'DK+TN+VB'
Leatherhead (LHD) and Wivelsfield (WVF) - removed sequence 'DK+LB'
Leatherhead (LHD) and Wivelsfield (WVF) - removed sequence 'HR+LB'​

I'm still looking into these, although most of them reduce ticket validity.

To permit journeys denied by NFM64 Fares Checking that are not taking the shortest route the following posirtive easement has been published.

Easement added

700664: For journeys from Ledbury, Colwall, Great Malvern and Malvern Link to Spring Road, Hall Green, Yardley Wood, Shirley (West Midlands), Whitlocks End, Wythall, Earlswood (West Midlands), The Lakes, Wood End, Danzey, Henley in Arden, Wootton Wawen and Wilmcote are permitted via Tysley. This routeing point easement overrides NFM64 fares checking and operates in both directions.​

The Warwickshire stations are the issue here, with fares to the line from Worcester to Hereford higher than those at either end.

Wilmcote is unaffected as it's part of a routeing point anyway.

For enginnering works on the Great Western mainline

Easement added

700665: During the closure of the Severn Tunnel between 12 September 2016 and 20 October 2016, journeys from Bristol Temple Meads, Filton Abbeywood, Stapleton Road, Lawrence Hill and Bristol Parkway to Severn Tunnel Junction, Chepstow, Lydney and Caldicot are allowed to travel via Gloucester (easement 700651). This routeing point easement will override NFM64 fares checking which is preventing easement 700651 working fully and will apply in both directions.​

The description of easement 700651 here matches the original easement. I don't think anyone needs to act differently based on this new easement, but perhaps some retailers are doing.

- -

The last set was:

New dataset RJRG0427 published 09 September 2016

A review of the use of Map LB and its replacement with alternative maps has led to the following changes (part 2 - see RJRG0426 changes from 07 September 2016)


Map sequence added

EASTBOURNE GROUP (G84) and Leatherhead (LHD) - added sequence 'VB+AR'
Leatherhead (LHD) and Wivelsfield (WVF) - added sequence 'AR+VB'

Map sequence removed

EASTBOURNE GROUP (G84) and Leatherhead (LHD) - removed sequence 'CW+VB+AR'
EASTBOURNE GROUP (G84) and Leatherhead (LHD) - removed sequence 'XB+DK'
Leatherhead (LHD) and Wivelsfield (WVF) - removed sequence 'DK+XB'​

These remove mapped routes via Guildford and Horsham.

Leatherhead (LHD) and Lewes (LWS) - added sequence 'AR+VB'​

No effect. The routes it covered were already available on DK+XB.

Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - removed sequence 'DK+XB'​

This removes mapped routes via Dorking.

Effingham Junction (EFF) and Wivelsfield (WVF) - added sequence 'HR+AR+VB'
Effingham Junction (EFF) and Wivelsfield (WVF) - removed sequence 'DK+XB'
Effingham Junction (EFF) and Three Bridges (TBD) - added sequence 'DK+TN+VB'
Effingham Junction (EFF) and Three Bridges (TBD) - added sequence 'HR+AR+VB'
Effingham Junction (EFF) and Three Bridges (TBD) - removed sequence 'DK+LB'
Effingham Junction (EFF) and Three Bridges (TBD) - removed sequence 'DK+XB'
Effingham Junction (EFF) and Three Bridges (TBD) - removed sequence 'HR+LB'
Leatherhead (LHD) and Three Bridges (TBD) - added sequence 'AR+VB'
Leatherhead (LHD) and Three Bridges (TBD) - added sequence 'DK+TN+VB'
Leatherhead (LHD) and Three Bridges (TBD) - added sequence 'HR+VB'
Leatherhead (LHD) and Three Bridges (TBD) - removed sequence 'DK+LB'
Leatherhead (LHD) and Three Bridges (TBD) - removed sequence 'DK+XB'
Leatherhead (LHD) and Three Bridges (TBD) - removed sequence 'HR+LB'
Effingham Junction (EFF) and Haywards Heath (HHE) - removed sequence 'DK+LB'
Effingham Junction (EFF) and Haywards Heath (HHE) - removed sequence 'DK+XB'
Effingham Junction (EFF) and Lewes (LWS) - removed sequence 'DK+XB'
Effingham Junction (EFF) and Lewes (LWS) - removed sequence 'HR+VB'
Haywards Heath (HHE) and Sevenoaks (SEV) - removed sequence 'LB+VH'
Haywards Heath (HHE) and Sevenoaks (SEV) - removed sequence 'LB+VR'
REDHILL GROUP (G60) and Sevenoaks (SEV) - removed sequence 'LB+VH'
REDHILL GROUP (G60) and Sevenoaks (SEV) - removed sequence 'LB+VR'
Sevenoaks (SEV) and Three Bridges (TBD) - removed sequence 'VH+LB'
Sevenoaks (SEV) and Three Bridges (TBD) - removed sequence 'VR+LB'
Three Bridges (TBD) and Tonbridge (TON) - removed sequence 'LB+RA'​

I'm still looking into these, although most of them reduce ticket validity.

Seven routes were changed in different ways on the 7th and the 9th, but I haven't looked into the overall effect. I should have more details shortly.

 

[MikeWh]

Would it surprise you to realise that this thread may explain most of the map changes?

 

[kieron]

The map changes did seem tightly focussed on routes between Effingham/Leatherhead and Eastbourne-Brighton-Croydon, so I expected it to have a single source. It's interesting to know what it was, though.

I have looked a bit further into the map changes, and ended up with the following:

New dataset RJRG0426 published 07 September 2016

A review of the use of Map LB and its replacement with alternative maps has led to the following changes (part 1)

Map sequence added

BRIGHTON GROUP (G04) and Leatherhead (LHD) - added sequence 'VB+HR'
BRIGHTON GROUP (G04) and Leatherhead (LHD) - added sequence 'VB+TN+DK'

Map sequence removed

BRIGHTON GROUP (G04) and Leatherhead (LHD) - removed sequence 'LB+DK'
BRIGHTON GROUP (G04) and Leatherhead (LHD) - removed sequence 'LB+HR'​

This removes mapped routes:
via Worthing;
via Peckham Rye and New Cross Gate; and
via Crystal Palace while avoiding Tulse Hill and London.
The last included routes such as Brighton-Croydon-Crystal Palace-Streatham Hill-Clapham Junction-Wimbledon-Epsom-Leatherhead.

CROYDON GROUP (G08) and Leatherhead (LHD) - added sequence 'TN+DK'
CROYDON GROUP (G08) and Leatherhead (LHD) - removed sequence 'LB+DK'
CROYDON GROUP (G08) and Leatherhead (LHD) - removed sequence 'LB+HR'​

This removes mapped routes via Crystal Palace, via Mitcham Junction, via Redhill and via Tulse Hill.

EASTBOURNE GROUP (G84) and Leatherhead (LHD) - added sequence 'VB+HR'
EASTBOURNE GROUP (G84) and Leatherhead (LHD) - added sequence 'VB+TN+DK'
EASTBOURNE GROUP (G84) and Leatherhead (LHD) - removed sequence 'LB+DK'
EASTBOURNE GROUP (G84) and Leatherhead (LHD) - removed sequence 'LB+HR'​

This removes mapped routes:
via Worthing;
via New Cross Gate and Peckham Rye;
via New Cross Gate, Herne Hill and Clapham Junction; and
ones via Norwood Junction which avoid London and Tulse Hill.

Effingham Junction (EFF) and BRIGHTON GROUP (G04) - added sequence 'DK+TN+VB'
Effingham Junction (EFF) and BRIGHTON GROUP (G04) - added sequence 'HR+VB'
Effingham Junction (EFF) and BRIGHTON GROUP (G04) - removed sequence 'DK+LB'
Effingham Junction (EFF) and BRIGHTON GROUP (G04) - removed sequence 'HR+LB'​

This removes mapped routes:
via Worthing;
via Motspur Park, Tulse Hill, London and New Cross Gate; and
via Sutton, Peckham Rye, London and New Cross Gate.

Effingham Junction (EFF) and CROYDON GROUP (G08) - added sequence 'EF+TN'
Effingham Junction (EFF) and CROYDON GROUP (G08) - removed sequence 'DK+LB'
Effingham Junction (EFF) and CROYDON GROUP (G08) - removed sequence 'EF+LB'
Effingham Junction (EFF) and CROYDON GROUP (G08) - removed sequence 'HR+LB'​

This removes mapped routes via Crystal Palace, via Mitcham Junction, via Motspur Park and via Redhill.

Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - added sequence 'DK+TN+VB'
Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - added sequence 'EF+TN+VB'
Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - added sequence 'HR+VB'
Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - removed sequence 'DK+LB'
Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - removed sequence 'EF+LB'
Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - removed sequence 'HR+LB'​

This removes mapped routes:
via Worthing;
via Peckham Rye and New Cross Gate;
via Clapham Junction, Herne Hill and New Cross Gate; and
ones via Norwood Junction which avoid London and Tulse Hill.

Effingham Junction (EFF) and Gatwick Airport (GTW) - added sequence 'AR+VB'
Effingham Junction (EFF) and Gatwick Airport (GTW) - added sequence 'DK+SC'
Effingham Junction (EFF) and Gatwick Airport (GTW) - removed sequence 'DK+LB'
Effingham Junction (EFF) and Gatwick Airport (GTW) - removed sequence 'HR+LB'​

This removes mapped routes:
via Three Bridges; and
via Leatherhead, Peckham Rye and New Cross Gate.
It adds mapped routes:
via Guildford;
via Tooting;
via New Cross Gate and Crystal Palace; and
via Wimbledon and Sutton.

Effingham Junction (EFF) and Haywards Heath (HHE) - added sequence 'DK+TN+VB'
Effingham Junction (EFF) and Haywards Heath (HHE) - added sequence 'HR+VB'
Effingham Junction (EFF) and Haywards Heath (HHE) - removed sequence 'HR+LB'​

This removes routes:
via Sutton, Peckham Rye and New Cross Gate; and
ones via Norwood Junction which avoid both Clapham Junction and Tulse Hill.

Effingham Junction (EFF) and Lewes (LWS) - added sequence 'DK+TN+VB'
Effingham Junction (EFF) and Lewes (LWS) - added sequence 'HR+VB'
Effingham Junction (EFF) and Lewes (LWS) - removed sequence 'DK+LB'
Effingham Junction (EFF) and Lewes (LWS) - removed sequence 'HR+LB'​

This removes mapped routes:
via Worthing;
via Motspur Park, Streatham and New Cross Gate;
via Sutton, Peckham Rye and New Cross Gate; and
ones via Norwood Junction which avoid London and Tulse Hill.

Effingham Junction (EFF) and REDHILL GROUP (G60) - added sequence 'AR'
Effingham Junction (EFF) and REDHILL GROUP (G60) - added sequence 'DK+TN'
Effingham Junction (EFF) and REDHILL GROUP (G60) - added sequence 'HR+TN'
Effingham Junction (EFF) and REDHILL GROUP (G60) - removed sequence 'DK+LB'
Effingham Junction (EFF) and REDHILL GROUP (G60) - removed sequence 'HR+LB'​

This removes mapped routes:
via Three Bridges;
via Motspur Park, Streatham and New Cross Gate;
via Sutton, Peckham Rye and New Cross Gate; and
ones via Epsom and Norwood Junction which avoid London.
It adds a mapped route via Guildford.

Effingham Junction (EFF) and Wivelsfield (WVF) - added sequence 'DK+TN+VB'
Effingham Junction (EFF) and Wivelsfield (WVF) - removed sequence 'DK+LB'
Effingham Junction (EFF) and Wivelsfield (WVF) - removed sequence 'HR+LB'​

This removes mapped routes:
via Worthing;
via Motspur Park, Streatham and New Cross Gate;
via Mitcham Junction, Peckham Rye and New Cross Gate; and
ones via Mitcham Junction which avoid London.

Gatwick Airport (GTW) and Leatherhead (LHD) - added sequence 'SC+DK'
Gatwick Airport (GTW) and Leatherhead (LHD) - removed sequence 'LB+DK'
Gatwick Airport (GTW) and Leatherhead (LHD) - removed sequence 'LB+HR'​

This removes mapped routes:
via Three Bridges; and
via New Cross Gate and Peckham Rye.
It adds mapped routes:
via South Merton;
via Tooting;
via Crystal Palace and New Cross Gate; and
via Sutton and Motspur Park (roughly Gatwick-West Croydon-Sutton-Clapham Junction-Wimbledon-Motspur Park-Leatherhead).

Haywards Heath (HHE) and Leatherhead (LHD) - added sequence 'VB+AR'
Haywards Heath (HHE) and Leatherhead (LHD) - added sequence 'VB+SC'
Haywards Heath (HHE) and Leatherhead (LHD) - added sequence 'VB+TN+DK'
Haywards Heath (HHE) and Leatherhead (LHD) - removed sequence 'LB+DK'
Haywards Heath (HHE) and Leatherhead (LHD) - removed sequence 'LB+HR'​

This removes mapped routes:
via Worthing;
via New Cross Gate and Peckham Rye;
via New Cross Gate, Herne Hill and Clapham Junction; and
ones via Crystal Palace and Clapham Junction which avoid London and Tulse Rill.
It adds mapped routes:
via South Merton;
via Tooting; and
via Crystal Palace and New Cross Gate.

Leatherhead (LHD) and Lewes (LWS) - added sequence 'DK+TN+VB'
Leatherhead (LHD) and Lewes (LWS) - added sequence 'HR+VB'
Leatherhead (LHD) and Lewes (LWS) - removed sequence 'DK+LB'
Leatherhead (LHD) and Lewes (LWS) - removed sequence 'HR+LB'​

...

Leatherhead (LHD) and Wivelsfield (WVF) - added sequence 'DK+TN+VB'
Leatherhead (LHD) and Wivelsfield (WVF) - removed sequence 'DK+LB'
Leatherhead (LHD) and Wivelsfield (WVF) - removed sequence 'HR+LB'​

This removes mapped routes:
via Worthing;
via Peckham Rye and New Cross Gate;
via Wimbledon, Streatham and New Cross Gate;
routes via Mitcham Junction which avoid London; and
routes via Norwood Junction which avoid both London and Tulse Hill.

REDHILL GROUP (G60) and Leatherhead (LHD) - added sequence 'TN+DK'
REDHILL GROUP (G60) and Leatherhead (LHD) - added sequence 'TN+HR'
REDHILL GROUP (G60) and Leatherhead (LHD) - removed sequence 'LB+DK'
REDHILL GROUP (G60) and Leatherhead (LHD) - removed sequence 'LB+HR'​

This remove mapped routes:
via Crystal Palace;
via Peckham Rye;
via Three Bridges; and
via both Herne Hill and Wimbledon.

To permit journeys denied by NFM64 Fares Checking that are not taking the shortest route the following posirtive easement has been published.

Easement added

700664: For journeys from Ledbury, Colwall, Great Malvern and Malvern Link to Spring Road, Hall Green, Yardley Wood, Shirley (West Midlands), Whitlocks End, Wythall, Earlswood (West Midlands), The Lakes, Wood End, Danzey, Henley in Arden, Wootton Wawen and Wilmcote are permitted via Tysley. This routeing point easement overrides NFM64 fares checking and operates in both directions.​

The Warwickshire stations are the issue, with fares to the line from Worcester to Hereford higher than those at either end.

Wilmcote is unaffected as it's part of a routeing point anyway.

For enginnering works on the Great Western mainline

Easement added

700665: During the closure of the Severn Tunnel between 12 September 2016 and 20 October 2016, journeys from Bristol Temple Meads, Filton Abbeywood, Stapleton Road, Lawrence Hill and Bristol Parkway to Severn Tunnel Junction, Chepstow, Lydney and Caldicot are allowed to travel via Gloucester (easement 700651). This routeing point easement will override NFM64 fares checking which is preventing easement 700651 working fully and will apply in both directions.​

The description of easement 700651 here matches the original easement. I don't think anyone should act differently based on this new easement, but perhaps some retailers are doing.

New dataset RJRG0427 published 09 September 2016

A review of the use of Map LB and its replacement with alternative maps has led to the following changes (part 2 - see RJRG0426 changes from 07 September 2016)

Map sequence added

EASTBOURNE GROUP (G84) and Leatherhead (LHD) - added sequence 'VB+AR'

Map sequence removed

EASTBOURNE GROUP (G84) and Leatherhead (LHD) - removed sequence 'CW+VB+AR'
EASTBOURNE GROUP (G84) and Leatherhead (LHD) - removed sequence 'XB+DK'​

This removes mapped routes:
via Guildford; and
via Horsham.

Effingham Junction (EFF) and Three Bridges (TBD) - added sequence 'DK+TN+VB'
Effingham Junction (EFF) and Three Bridges (TBD) - added sequence 'HR+AR+VB'
Effingham Junction (EFF) and Three Bridges (TBD) - removed sequence 'DK+LB'
Effingham Junction (EFF) and Three Bridges (TBD) - removed sequence 'DK+XB'
Effingham Junction (EFF) and Three Bridges (TBD) - removed sequence 'HR+LB'​

This removes mapped routes:
via Horsham;
via Motspur Park, Streatham and New Cross Gate;
via Sutton, Peckham Rye and New Cross Gate;
ones via Mitcham Junction which avoid London; and
ones via Motspur Park and Crystal Palace which avoid both London and Tulse Hill.

Effingham Junction (EFF) and Wivelsfield (WVF) - added sequence 'HR+AR+VB'
Effingham Junction (EFF) and Wivelsfield (WVF) - removed sequence 'DK+XB'​

This removes mapped routes via Horsham.

Leatherhead (LHD) and Lewes (LWS) - added sequence 'AR+VB'​

No effect. The routes it covered were already available on DK+XB.

Leatherhead (LHD) and Three Bridges (TBD) - added sequence 'AR+VB'
Leatherhead (LHD) and Three Bridges (TBD) - added sequence 'DK+TN+VB'
Leatherhead (LHD) and Three Bridges (TBD) - added sequence 'HR+VB'
Leatherhead (LHD) and Three Bridges (TBD) - removed sequence 'DK+LB'
Leatherhead (LHD) and Three Bridges (TBD) - removed sequence 'DK+XB'
Leatherhead (LHD) and Three Bridges (TBD) - removed sequence 'HR+LB'​

This removes mapped routes:
via Guildford;
via Horsham;
via Peckham Rye and New Cross Gate;
via Wimbledon, Streatham and New Cross Gate; and
ones via Norwood Junction which avoid both London and Tulse Hill.

Leatherhead (LHD) and Wivelsfield (WVF) - added sequence 'AR+VB'
Leatherhead (LHD) and Wivelsfield (WVF) - removed sequence 'DK+XB'​

This removes mapped routes via Guildford and via Horsham.

Effingham Junction (EFF) and EASTBOURNE GROUP (G84) - removed sequence 'DK+XB'​

This removes mapped routes via Dorking.

Effingham Junction (EFF) and Haywards Heath (HHE) - removed sequence 'DK+LB'
Effingham Junction (EFF) and Haywards Heath (HHE) - removed sequence 'DK+XB'​

This removes mapped routes:
via Dorking;
via Motspur Park, Streatham and New Cross Gate; and
ones via Motspur Park and Norwood Junction which avoid both London and Tulse Hill.

Effingham Junction (EFF) and Lewes (LWS) - removed sequence 'DK+XB'
Effingham Junction (EFF) and Lewes (LWS) - removed sequence 'HR+VB'​

This removes mapped routes:
via Dorking; and
ones via Mitcham Junction which avoid London.

Haywards Heath (HHE) and Sevenoaks (SEV) - removed sequence 'LB+VH'
Haywards Heath (HHE) and Sevenoaks (SEV) - removed sequence 'LB+VR'
REDHILL GROUP (G60) and Sevenoaks (SEV) - removed sequence 'LB+VH'
REDHILL GROUP (G60) and Sevenoaks (SEV) - removed sequence 'LB+VR'​

These remove mapped routes:
via Lewes;
via New Cross Gate, Tulse Hill and Crystal Palace;
ones via Beckenham Junction which avoid London; and
ones via London, Tulse Hill and Beckenham Junction which visit them in that order.

Sevenoaks (SEV) and Three Bridges (TBD) - removed sequence 'VH+LB'
Sevenoaks (SEV) and Three Bridges (TBD) - removed sequence 'VR+LB'​

This removes mapped routes:
via Lewes;
via Crystal Palace, Tulse Hill and New Cross Gate;
ones via Beckenham Junction which avoid London; and
ones via Beckenham Junction, Tulse Hill and London which visit them in that order.

Three Bridges (TBD) and Tonbridge (TON) - removed sequence 'LB+RA'​

This removes mapped routes:
via Denmark Hill and New Cross;
via Herne Hill and North Dulwich;
via Elephant & Castle, Clapham High Street and Queens Road Peckham (in any order);
via New Cross Gate, Tulse Hill and Sevenoaks; and
ones via Orpington or Otford which do not go via London.

Several routes were altered on both 7/9 and 9/9:

• Effingham Junction (EFF) and EASTBOURNE GROUP (G84)
• Effingham Junction (EFF) and Haywards Heath (HHE)
• EASTBOURNE GROUP (G84) and Leatherhead (LHD)
• Effingham Junction (EFF) and Lewes (LWS)
• Effingham Junction (EFF) and Wivelsfield (WVF)
• Leatherhead (LHD) and Lewes (LWS)

None of these led to any routes being added with either change, so the overall effect is much the same as simply combining the descriptions.

 

[infobleep]

The map changes did seem tightly focussed on routes between Effingham/Leatherhead and Eastbourne-Brighton-Croydon, so I expected it to have a single source. It's interesting to know what it was, though.

I have looked a bit further into the map changes, and ended up with the following:

New dataset RJRG0426 published 07 September 2016

A review of the use of Map LB and its replacement with alternative maps has led to the following changes (part 1)

Map sequence added

BRIGHTON GROUP (G04) and Leatherhead (LHD) - added sequence 'VB+HR'
BRIGHTON GROUP (G04) and Leatherhead (LHD) - added sequence 'VB+TN+DK'

Map sequence removed

BRIGHTON GROUP (G04) and Leatherhead (LHD) - removed sequence 'LB+DK'
BRIGHTON GROUP (G04) and Leatherhead (LHD) - removed sequence 'LB+HR'​

This removes mapped routes:
via Worthing;
via Peckham Rye and New Cross Gate; and
via Crystal Palace while avoiding Tulse Hill and London.
The last included routes such as Brighton-Croydon-Crystal Palace-Streatham Hill-Clapham Junction-Wimbledon-Epsom-Leatherhead.

None of these led to any routes being added with either change, so the overall effect is much the same as simply combining the descriptions.[/QUOTE]
With regards to route you mentioned, quoted just above, how would one produce an itinerary on National Rail Enquiries for that or in fact from any of the journey planners?

I'm aware it wasn't an intentional route but it was valid one for a time none the less.

I find all these fascinating.

Sent from my SM-G925F using Tapatalk

 

[RJ]

You have to use what tools are available to you. NRE and Trainsplit allow you to use one via point in union with one avoid point. Or you could pop into a ticket office which has Journey Planner - the one where I work also has the option to filter by TOC, train type and can vary layovers. I can usually find some way of reproducing routes such as the above using it and it confirms whether or not the route is valid - and if not, it says why.

 

[MKB]

I'm a bit shocked to discover that Nuneaton to Wolverhampton via Stafford is not a valid route. After 8pm on a weekday evening, the fastest journey time is via Stafford so it seems bizarre that it wouldn't be allowed.

Anyone know if this is a recent change or has it been ever thus?

 

[martinsh]

I'm a bit shocked to discover that Nuneaton to Wolverhampton via Stafford is not a valid route. After 8pm on a weekday evening, the fastest journey time is via Stafford so it seems bizarre that it wouldn't be allowed.

Not only is it quicker via Stafford, it's also cheaper ! Providing you split at Stafford ..

Wolves - Nuneayon = £15.80
Wolves - Stafford = £7.70
Stafford - Nuneaton = £7.00

 

[kieron]

With regards to route you mentioned, quoted just above, how would one produce an itinerary on National Rail Enquiries for that or in fact from any of the journey planners?

In that specific case, you can simply ask NRE for journey via Streatham Hill. NRE offers this route with an "any permitted" ticket, at least for the first result listed in each direction.

This isn't what I expected, but I don't know why. There is definitely no Crystal Palace-Streatham Group link on any of the maps which remain available (DK, HR, TN, VB, XB and XE). These are not through trains, and the shortest route doesn't cross the M25. There may be easements which affect things, but I don't know what they are.

- -

I've realised that there was a mistake in how I'd checked things with some changes made a couple of weeks ago.

There are a few corrections to the post I made about them as a result, as follows:

Dataset RJRG0426 published 07 September 2016:

BRIGHTON GROUP (G04) and Leatherhead (LHD) has also lost routes via New Cross Gate, Elephant and Castle and Clapham Junction.

Effingham Junction (EFF) and BRIGHTON GROUP (G04) has also lost routes which do not pass through London or Tulse Hill, but do go via:
Mitcham Junction and Crystal Palace; or
Motspur Park and Crystal Palace.

Effingham Junction (EFF) and CROYDON GROUP (G08) has also lost routes via Tulse Hill.

Effingham Junction (EFF) and Lewes (LWS) has not lost all of the routes I said before.
It hasn't lost all of the routes via Norwood Junction which avoid London and Tulse Hill, but only those which also went via Epsom. The ones via Motspur Park (and on to Wimbledon, etc.) are still there.

Effingham Junction (EFF) and Wivelsfield (WVF):
I incorrectly said that routes via Mitcham Junction but not London had been removed. I don't think this is the case.
I do think that routes via Motspur Park and Crystal Palace which do not pass through London or Tulse Hill have been removed, however.

I forgot to provide any details for Leatherhead-Lewes. These should have been:

Leatherhead (LHD) and Lewes (LWS) - added sequence 'DK+TN+VB'
Leatherhead (LHD) and Lewes (LWS) - added sequence 'HR+VB'
Leatherhead (LHD) and Lewes (LWS) - removed sequence 'DK+LB'
Leatherhead (LHD) and Lewes (LWS) - removed sequence 'HR+LB'​

This removes mapped routes:
via Worthing;
via Peckham Rye and New Cross Gate;
via Wimbledon, Streatham and New Cross Gate; and
ones via Crystal Palace which avoid London and Tulse Hill.

- -

In addition to this, another update was published on Tuesday:

New dataset RJRG0428 published 20 September 2016

To ensure routes via Herne Hill are in place the following changes have been made.

Map sequence added

Bedford (BDM) and Kingston (KNG) - added sequence 'TK+WW'​

This adds maped routes via Herne Hill (and, with it, Thameslink).

Bedford (BDM) and LONDON GROUP (G01) - added sequence 'TK'​

No effect. You still can't go from Bedford to London via Herne Hill.

Bedford (BDM) and Motspur Park (MOT) - added sequence 'TK+WW'
Bedford (BDM) and New Malden (NEM) - added sequence 'TK+WW'
Bedford (BDM) and Raynes Park (RAY) - added sequence 'TK+WW'
Bedford (BDM) and Surbiton (SUR) - added sequence 'TK+WW'​

No effect. These already had mapped routes via Herne Hill.

To align fares and map permissions, the following changes have been made.

Map sequence added

SCARBOROUGH GROUP (G48) and Gilberdyke (GBD) - added sequence 'HL'

Map sequence removed

SCARBOROUGH GROUP (G48) and Gilberdyke (GBD) - removed sequence 'DS'
SCARBOROUGH GROUP (G48) and Gilberdyke (GBD) - removed sequence 'MN+HM'​

This removes mapped routes via Selby and adds ones via Hull.
The shortest Scarborough-Gilberdyke route is via Hull. Scarborough-Howden is shorter via Selby, though.

SCARBOROUGH GROUP (G48) and Hull (HUL) - removed sequence 'MN+HM'​

This removes mapped routes via Selby.

SCARBOROUGH GROUP (G48) and Selby (SBY) - removed sequence 'MN+HM'​

This removes mapped routes via Leeds.

For Trans Pennine Express Club 55 promotion

Easement added

700666: Between 19 September and 20 November 2016 customers using Club 55 promotional fares routed (00085) TPE ONLY travelling from Newcastle and stations south of Newcastle on TPE services may travel via Manchester for onward connecting TPE services to destinations whose permited routes do not include via Manchester. This fare route easement applies in both directions.

700667: Between 19 September and 20 November 2016 customers using club 55 promotional fares routed (00085) TPE ONLY travelling from Newcastle and stations south of Newcastle may travel via Leeds for onward connecting TPE services to destinations whose permitted routes do not include via Leeds. This fare route easement applies in both directions.

700668: Between 19 September and 20 November 2016 customers using Club 55 promotional fares routed (00085) TPE ONLY travelling from Newcastle and stations south of Newcastle may travel via Preston for onward connecting TPE services to destinations to the north of Preston whose permitted routes do not include via Preston. This fare route easement applies in both directions​

Newcastle and stations south of Newcastle covers everywhere TPE serve in England. That said, you don't have much choice in the route you take if you're only using TPE trains.

For South West Trains promotion

Easement added

700669: Between 14 October and 11 December 2016 customers with promotional fares, (ticket type EGH), routed (00127) SWTRAINS ONLY may travel on South West Trains services via Clapham Junction to destinations where the permitted routes do not include via Clapham Junction. This fare route easement applies in both directions​

As with TPE, except without identifying the promotion. SWT's network doesn't have quite the same problem, of course.

Someone at ATOC have also changed an easement from 2013. Easement 700448 now reads:

700448: Customers travelling from or via Leamington Spa to Claverdon, Bearley, Wilmcote, Stratford Parkway or Stratford Upon Avon may double back between Hatton, Lapworth, Dorridge, Widney Manor and Solihull. This easement applies in both directions.​

It used to say "Bicester North" rather than "Leamington Spa", so this means there are more circumstances in which a passenger can benefit from this.

 

[infobleep]

You have to use what tools are available to you. NRE and Trainsplit allow you to use one via point in union with one avoid point. Or you could pop into a ticket office which has Journey Planner - the one where I work also has the option to filter by TOC, train type and can vary layovers. I can usually find some way of reproducing routes such as the above using it and it confirms whether or not the route is valid - and if not, it says why.

Thanks for that explanation. Hopefully some programmer is writing a booking engine as good as journey planner. I like playing around for my own curiosity but couldn't do that with a queue of people behind me.

Sent from my SM-G925F using Tapatalk

 

[embers25]

For South West Trains promotion

Easement added

700669: Between 14 October and 11 December 2016 customers with promotional fares, (ticket type EGH), routed (00127) SWTRAINS ONLY may travel on South West Trains services via Clapham Junction to destinations where the permitted routes do not include via Clapham Junction. This fare route easement applies in both directions​

As with TPE, except without identifying the promotion. SWT's network doesn't have quite the same problem, of course.

Does anyone have any details of this promotion?

 

[bb21]

Does anyone have any details of this promotion?

£14.95 single, excluding stations west of Yeovil Junc.

Singles only. No returns.

 

[embers25]

£14.95 single, excluding stations west of Yeovil Junc.

Singles only. No returns.

Thanks...so much worse than previous ones then (particularly for those of us west of Yeovil). I see its available for sale now on their website and is more restricted than the last one.

 

[kieron]

There was another update on Monday.

New dataset RJRG0429 published 03 October 2016

Due to planned diversions on Sundays between Orpington and London the following amendments ahve been published.

Map sequence added

BRISTOL GROUP (G05) and Tonbridge (TON) - added sequence 'WP+TU'
BRISTOL GROUP (G05) and Tonbridge (TON) - added sequence 'WR+TU'
LONDON GROUP (G01) and Tonbridge (TON) - added sequence 'AF+TU'​

These add mapped routes:
via the Shortlands-Orpington link described below; and
via West Dulwich (specifically, via the routes Orpington-London Victoria trains normally use).

For what it's worth, the Bristol map changes above don't do anything. WR+TU was already allowed as 'LONDON' is one of the listed map combinations. Everything WP+TU did was previously allowed by LA+TU. The extra London-Tonbridge routes do still add options for travellers from Bristol, though.

Map changed

Map TU - LONDON BRIDGE TO TUNBRIDGE WELLS VIA NEW BECKENHAM AND ORPINGTON changed (1 link added G85 rto SRT)​

This has created a mapped route which goes between Shortlands and Orpington or Petts Wood without passing through Bromley South or Grove Park.
I think this must be a bus-related thing, as I don't know of any plausible routes for this by train.

The TU map is also used for the following routes (as well as some longer distance routes which go through central London). It doesn't affect anything on the normal timetable by itself, though, unless there's an easement I haven't spotted for this.

Beckenham Junction (BKJ) to London Group
Beckenham Junction (BKJ) to New Cross (NWX)
Bromley South Group (BKL, BMS) to London Group
Bromley South Group (BKL, BMS) to New Cross (NWX)
London Group to Orpington Group (ORP, PET)
London Group to Sevenoaks (SEV)
London Group to Shortlands (SRT)
New Cross (NWX) to Orpington Group (ORP, PET)
New Cross (NWX) to Sevenoaks (SEV)
New Cross (NWX) to Shortlands (SRT)
New Cross (NWX) to Tonbridge (TON)​

I should mention that New Cross-Tonbridge does now have mapped routes via West Dulwich owing to the London-Tonbridge change above.

To prevent routeings via Edinburgh between Glasgow and Inverness

Easement added

700670: Customers travelling from or via Aviemore to Glasgow and destinations via Glasgow may not travel via Haymarket and Edinburgh. This negative circuitous route easement applies in both directions.​

All trains between Edinburgh and Aviemore or Inverness call at Haymarket, but Crosscountry run a couple of trains between Glasgow and Edinburgh a day which don't. A Glasgow-Inverness ticket (for example) didn't allow travel via Edinburgh before this change, anyway.

 

[Bletchleyite]

Is there a fares reason for wanting that in there? I can't see why that should be an issue otherwise - it's mostly one TOC.

 

[Merseysider]

None at all.

 

[John @ home]

To prevent routeings via Edinburgh between Glasgow and Inverness

Easement added

700670: Customers travelling from or via Aviemore to Glasgow and destinations via Glasgow may not travel via Haymarket and Edinburgh. This negative circuitous route easement applies in both directions.​

All trains between Edinburgh and Aviemore or Inverness call at Haymarket, but Crosscountry run a couple of trains between Glasgow and Edinburgh a day which don't. A Glasgow-Inverness ticket (for example) didn't allow travel via Edinburgh before this change, anyway.

Is there a fares reason for wanting that in there? I can't see why that should be an issue otherwise - it's mostly one TOC.

None at all.

It seems to me that this negative Easement is in breach of the Group Stations rule:

How to Use the National Routeing Guide
GROUP STATIONS

Some stations are grouped together to improve interchange between trains by offering customers access to a wider choice of train services and station facilities. A customer may travel via any station in such a group, including doubling back, provided that the group is on one of the permitted routes between their origin and destination stations. This extended availability is for interchange purposes only and does not apply where the origin or destination stations are part of a group.

The new negative Easement is particularly perverse because travel remains permitted via four of the five Routeing Guide Group Stations (Dalmeny, Edinburgh Park, Haymarket and South Gyle) but not via the station offering the widest "choice of train services and station facilities", Edinburgh (Waverley).

 

[Bletchleyite]

I read it as "Haymarket or Edinburgh". Anyone know the implementation?


Sent from my iPhone using Tapatalk

 

[BurtonM]

I'm a bit shocked to discover that Nuneaton to Wolverhampton via Stafford is not a valid route. After 8pm on a weekday evening, the fastest journey time is via Stafford so it seems bizarre that it wouldn't be allowed.

Anyone know if this is a recent change or has it been ever thus?

Wouldn't this route involve doubling back at Stafford?

 

[Bletchleyite]

Wouldn't this route involve doubling back at Stafford?

Does it require you to pass through a station twice? That is the specified definition of a double-back, not simply heading back in the same direction. I don't think it does?

 

[Merseysider]

Wouldn't this route involve doubling back at Stafford?

No it wouldn't. You'd change trains at Stafford. Doubling back refers to going past a station in one direction and then going past it in the other.

 

[BurtonM]

Seems I was misreading then. That does sound like a logical route in that case, then.