• Our new ticketing site is now live! Using either this or the original site (both powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!

What happened to the through trains to common routeing points rule?

Status
Not open for further replies.
Joined
30 Oct 2019
Messages
206
Location
GEML
Since the inception of the Routeing Guide in 1996, it has been allowed to take direct trains to and from a common routeing point.

This is a sensible rule for multiple reasons. Namely, routeing points are normally larger stations, specifically designed with interchanges in mind and therefore tend to have waiting rooms, food/drink facilities and better staff presence. These larger stations also have the passenger numbers to justify investment in accessible access e.g. lifts. Additionally, the nature of the rule as it stood meant that customers would only have to make one change at a maximum - highly convenient for the passenger and not open to abuse on wild circuitous routes around the country (especially compared to almost every other aspect of the routeing guide).

However, with the withdrawal of Routeing Guide routes being "permitted" in the National Rail Conditions of Travel, only routes that can be shown on a journey planner are valid, and journey planners do not seem to have this rule implemented.

The crux of the issue seems to be that the existence of the "shortest route rule" permits these journeys in most cases, and masks the lack of this rule's implementation in journey planners. Therefore, you fail to see these journeys validate wherever two lines merge and there is an intermediate station between the merge point and the routeing point station. (i.e. >3 miles)

Examples include:
  • Any station on the Hertford East branch to Roydon to Bishops Stortford via Cheshunt, by which if you go further north you begin to use the more reasonable mapping rules
  • Okehampton to the remainder of the Barnstaple branch via Exeter.
  • Burton-on-Trent, Willington to Longton, Blythe Bridge, Uttoxeter, Tutbury & Hatton via Derby
  • Stations from the Norwich-Lowestoft line to and from the Great Yarmouth branch via Ipswich also wouldn't validate, were it not for the existence of the first ever routeing easement.
  • Stations on the Ipswich-Lowestoft line changing to the Ipswich-Felixstowe line wouldn't validate, were it not for an easement existing.
  • (generally) Any pair of stations, with a common routeing point, where the junction station is not a routeing point

It is especially interesting because the very example in the Routeing Guide used to demonstrate this rule, Stratford-Upon-Avon to Leamington Spa is no longer valid (via Birmingham). Additionally, the protection of this right to not always follow the "blind" shortest journey rule was the original reason easements were introduced in the first place!

What happened to this rule - how come this rule didn't get added to journey planner logic?
Ought this be changed? it is admittedly covered in many cases by appropriate VIA points allowing a split route check, easements, and some just making it under the 3-mile rule, however the only way to guarantee these routes always show is by implementing this rule.
Despite the fact you are highly unlikely to be challenged when travelling on these very reasonable routes, what recourse do you have if stopped and challenged?
 
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

MrJeeves

Established Member
Associate Staff
Senior Fares Advisor
Joined
28 Aug 2015
Messages
4,721
Location
Burgess Hill
It is especially interesting because the very example in the Routeing Guide used to demonstrate this rule, Stratford-Upon-Avon to Leamington Spa is no longer valid (via Birmingham).
Without yet delving into the rest of your post, it is very important to note that the examples in the routeing guide use example data which does not account for later changes to the data since its creation. They simply serve as examples of how to interpret the data stated alongside the example, and not as examples which match the current state of the routeing guide.

In fact, this journey (at least if travelling via Birmingham New Street, but I'm not sure if some journey planners will interpret Birmingham N St as referring to all of Birmingham Group) was prohibited since 2004 (at least according to the dates in the electronic data!) via a negative easement. The human-readable wording does not expressly forbid this kind of journey, as it is intended to prevent a journey from Birmingham to Leamington or Stratford-u-Avon from being used via the other station, but the electronic data does forbid it.

Elec. easement 000312 — Circuitous Route
From 2004-05-07 on all days

If all of the below apply to the journey:
ends at { Stratford-Upon-Avon [SAV] }
passes through all of { Birmingham New Street [BHM], Leamington Spa [LMS] }

then the journey may not pass through any of { Birmingham New Street [BHM] }


Elec. easement 000313 — Circuitous Route
From 2004-05-07 on all days

If all of the below apply to the journey:
starts at { Stratford-Upon-Avon [SAV] }
passes through all of { Birmingham New Street [BHM], Leamington Spa [LMS] }

then the journey may not pass through any of { Birmingham New Street [BHM] }




The actual rules implemented by journey planners differ to the routeing guide in detail. It's also worth noting that the actual specification has a significant number of ambiguities and outright misleading statements, and it is likely every journey planner will implement the routeing guide slightly differently.

7.2.9 Through trains to and from routeing point

7.2.9.1 The following rules apply to journeys which start and end at stations which are not routeing points, and pass through a routeing point station which is common to both the journey origin and journey destination. The routeing point station is either a routeing point or a member of a station-group which is a routeing point. The Local Journey is permitted if all of the following conditions are satisfied:
  • The Local Journey does not include a change of trains
  • the first change station is either a routeing point or a member of a station-group which is a routeing point.
  • this routeing point is a related routeing point for the journey origin/journey destination.
  • the Local Journey does not include any station twice, except for other stations in the same station-group as the change station.

7.2.9.2 The Local Journey is also permitted if all of the following conditions are satisfied:
  • there are several changes of train on the Local Journey.
  • all of the change stations are members of the same station-group which is a routeing point.
  • this routeing point is a related routeing point for the journey origin/journey destination.
  • the Local Journey does not include any station twice, except for other stations in the same station-group as the change stations.

7.2.9.3 When the journey origin and journey destination have two, three or four common routeing points then the journey is only permitted if the journey via the change station is shorter than the journey via any other common routeing point

In this excerpt, I understand "Local Journey" to refer to the overall journey between the origin and destination, and not each journey to and from the common routeing point, due to 7.2.1 further up:
7.2.1 These are the rules which apply to a journey between origin and destination with common routeing points, or to a part-journey to or from a routeing point related to a station. Within this section the term Local Journey is used to refer to that journey or part-journey.

Since you are stating a change of trains at the common routeing point or one of its station-group members, I would say this falls under 7.2.9.2 which regards changes of trains within the local journey with a common routeing point. The fourth bullet point within 7.2.9.2 denies many of your examples.

For the Okehampton to Barnstaple via Exeter example, this would require double-backing through Crediton and Newton St Cyres. This isn't permitted as these are only associated with the Exeter Group routeing point, and not members of the group. If they were members, this would be permitted as they would be stations in the same station-group as the change station.

For the Burton-on-Trent to Tutbury & Hatton via Derby example, both legs to and from Derby would pass through Peartree which, again, is not a member of Derby Group, but instead just associated with Derby Group (and Stoke-on-Trent), so this wouldn't be permitted for the same reason.

The act of "includ[ing]" a station isn't defined in the spec. Some journey planners will only include timetabled locations in this logic, while others might infill missing stations from an itinerary using the series of stations along the shortest route between each location in the itinerary from the station distances data.

An example of where this is permitted is a journey in journey planners would be Polegate to Pevensey & Westham via Eastbourne. The doubleback between Hampden Park and Eastbourne is 3.98 miles, so over the threshold, and journey planners will permit the journey on a direct train to Eastbourne and from Eastbourne despite the doubleback because Hampden Park is a member of Eastbourne Group. There is also an easement to appease journey planners which don't follow these rules, but I have personally verified that the forum's site does not use this easement to determine that the journey is valid.

The above example may also be permitted due to 7.2.6 of the linked spec:
7.2.6 Journey within allowed margin of shortest route

7.2.6.1 The Local Journey is permitted if the distance of the actual journey is within a specified margin of the distance of the shortest route, if an allowed margin has been specified.

7.2.6.2 Any deviations or double-backs within that station-group should not be included in the distance calculation. However, journeys involving a short doubleback will continue to be invalid, even if the doubleback distance is within the permitted margin.
In this example, the Hampden Park - Eastbourne - Hampden Park doubleback would be permitted as the 3.98mi used in the doubleback would be disregarded, and the shortest journey rule can then be used to permit the Local Journey.

To find a concrete example of a journey planner not permitting a journey via the through trains to/from a common routeing point rule, you'd have to find one which has a doubleback through RP group members, but is also not the shortest journey when you ignore that doubleback. I think an example of this might be Sandwich to Sturry via Ramsgate. If the journey planner does not infill locations from shortest routes, you'd need an itinerary which calls at Thanet Parkway both to and from Ramsgate to check this.

I haven't checked your other examples, and will leave that as an exercise to the reader so I don't stay up too late :p
 
Last edited:

Kite159

Veteran Member
Joined
27 Jan 2014
Messages
22,855
Location
West of Andover
For the Burton-on-Trent to Tutbury & Hatton via Derby example, both legs to and from Derby would pass through Peartree which, again, is not a member of Derby Group, but instead just associated with Derby Group (and Stoke-on-Trent), so this wouldn't be permitted for the same reason.
However most guards won't bat an eyelid if someone has a Burton to Tutbury/Uttoxeter ticket travelling via Derby owing to the complete lack of trains which call at Peartree from the Burton direction and limited number of trains which call there heading towards Stoke.

Similar in a way to stations on the Matlock branch having to travel via Derby if they want Chesterfield & beyond owing to the very limited number of calls at Belper on Intercity services.
 
Joined
30 Oct 2019
Messages
206
Location
GEML
Thanks for such a detailed look at it! I have now gone and chucked a bunch of these examples in a variety of different journey planners and it seems like most take the same approach that Trainsplit's engine does too, with a random selection of other engines accepting a random selection of routes above without rhyme or reason.

I wasn't actually aware that journey planners were told to ignore any route that "includes" a station twice, which seems counterintuitive as the purpose of the rule is to get you to the better interchange station, in spite of any (small) doubleback that occurs - for the reasons I mentioned in an opening post it is often far more sensible to go to a larger interchange station.

All these examples I chose included some sort of doubleback so I could be sure that the shortest route rule was not validating these examples, however they are instead being denied because of this doubleback/accepted because the doubleback isn't detected, then that's a pretty silly situation to be in where you have to book with the right journey planner to get the best fare.

However most guards won't bat an eyelid if someone has a Burton to Tutbury/Uttoxeter ticket travelling via Derby owing to the complete lack of trains which call at Peartree from the Burton direction and limited number of trains which call there heading towards Stoke.

Similar in a way to stations on the Matlock branch having to travel via Derby if they want Chesterfield & beyond owing to the very limited number of calls at Belper on Intercity services.
This limited calls issue isn't something I had thought about. It makes me think of other examples like Newark Northgate to Retford which would also be denied for the same reason, however in this case it's not two junction stations merging, but the lack of trains calling at both stations which force you to go via a common routeing point. It shouldn't be necessary to have a hodgepodge of easements (which can be encoded very badly/not apply to all tickets/not apply to all relevant journeys that they ought to).

This "don't include any station twice" rule is far too broad to be useful. Take Longport to Macclesfield as well where only 2 trains per day call, thereby making the best journey via Stoke. Only a random selection of retailers will permit this journey.

To find a concrete example of a journey planner not permitting a journey via the through trains to/from a common routeing point rule, you'd have to find one which has a doubleback through RP group members, but is also not the shortest journey when you ignore that doubleback. I think an example of this might be Sandwich to Sturry via Ramsgate. If the journey planner does not infill locations from shortest routes, you'd need an itinerary which calls at Thanet Parkway both to and from Ramsgate to check this.
I haven't checked your other examples, and will leave that as an exercise to the reader so I don't stay up too late :p
Unfortunately easement 700475 (may travel via Ramsgate) means that this can't be tested. It was an example I noted but didn't use as Thanet Parkway wasn't a mandatory timing point as you've alluded to
 
Status
Not open for further replies.

Top