OwlMan
Established Member
New rules have come into place restricting fare checks to the fares in NFM64.
It doesn't work on a Mac. I've tried Safari, Chrome and Firefox.
The reCAPTACHA keeps resetting each time I try to enter an Origin or Destination and the Show Routeing Points button remains greyed out.
New rules have come into place restricting fare checks to the fares in NFM64.
New rules have come into place restricting fare checks to the fares in NFM64.
What benefits for the passenger are we looking at here?About bloody time.
It's not working for me either (iPhone 5, Safari, v7.0.3). I got asked to confirm I was a human no less than nine times whilst I was in the middle of typing station names. I then had to 'Select all images of drinks' followed by 'Select all images of borritos' and then 'Type the text'. It still didn't work.It doesn't work on a Mac. I've tried Safari, Chrome and Firefox.
The reCAPTACHA keeps resetting each time I try to enter an Origin or Destination and the Show Routeing Points button remains greyed out.
What benefits for the passenger are we looking at here?
Quite a few, I think. A quick example: Oxford to Tilehurst via Reading. Current fares are:What benefits for the passenger are we looking at here?
I follow now. A lot of route removals have been due to price anomalies, despite the route being reasonable. So if you go back to comparing when the fares were equal, there's no reason for a route to be invalid.Valid routes not suddenly becoming invalid due to fares rising by different proportions at a fares round.
Example: I think Blackwater to Wembley Stadium is valid via Reading. The tool confirms this, but NRE says no.
6.20 File :- NFM64 files Description :- This is a single file of fares data that makes up the National Fares Manual Issue 64. These Fares are used as a Baseline by the Routeing Guide process for various functions. It is not the main source of Fares information. This is not a complete fare set; only records with TICKET_CODE SOS, SDS, SVS and CDS are included, as these are the only relevant fares to be checked by an ENRG application. This file will only be available on CDROM. The file name is nfm64, and it is uncompressed. Its file size is 221mb. Note that the header and footer records contained in the data feed files described in Section 4 are not included in this file. As this is a large and static file it will form part of the normal datafeed but only be provided as a one-off load to new customers or by special request to existing customers. Each record in the NFM files has been simplified to contain only the data necessary for ENRG use. The fares contained in this file are used by the routeing guide to determine the appropriate routeing point(s).
NFM64 Fare Records:
Key.................................... Field Name................................ Length.............. Description..............................
Y......................................... FROM_NLC_CODE...................... 4...................... The NLC code of the fare origin
Y......................................... TO_NLC_CODE......................... 4....................... The NLC code of the fare destination
Y......................................... ROUTE_CODE........................... 5....................... The route code pertaining to the flow.
Y......................................... TICKET_CODE.......................... 3........................ The ticket code of the fare.
.......................................... FARE_PRICE............................. 6 .......................Fare price in pence.
This tool does not list all Permitted Routes. It simply determines which routeing points can be used for working them out. Other rules such as not doubling back as well as the easements still need to be applied.
For those of you that have been complaining about the lack of NFM 64 data this is now available from the ATOC NRG site.
Valid routes not suddenly becoming invalid due to fares rising by different proportions at a fares round.
Correct. I stand by what I've said.
The tool reports that from Wokingham routeing point the permitted mapped routes are LONDON. One of the LONDON routes is Wokingham - Reading - Paddington, therefore an Any Permitted ticket from Blackwater to Wembley Stadium (which is valid via Wokingham as Wokingham passes the fares check) can be used to go Blackwater - Wokingham - Reading - Paddington / Marylebone - Wembley Stadium.
But NRE does not agree, hence my comment about different logic or base data being used.
Yes that's why there are routeing point easements to override the fares check when a route would not be permitted. There is quite a list of them in Section EBut presumably there must also be examples of routes that are valid with current fares data, that were invalid under NFM 64 data.
I think this is a technical difficulty caused by there being no intermediate stations between London Marylebone and South Ruislip at the time of NFM 64. Wembley Stadium station opened later.The tool says Marylebone is not a valid destination routeing point and the only valid one is South Ruislip. E
The tool says Marylebone is not a valid destination routeing point and the only valid one is South Ruislip.
But presumably there must also be examples of routes that are valid with current fares data, that were invalid under NFM 64 data.
So a big part of determining the routes that I can now take by train depend on what the fares were 19 years ago, with current fares being irrelevant? Madness.
But that is exactly what many members of this forum have been arguing for some time, especially when using the current fares would deny a route, where the historical fares would allow it. Only one set of data should be used, for consistency. Personally I think it should be current fares, as those are easier for everyone to check and are more transparent, but if people insist on using the historical fares, then so be it. You can't just use whichever fare you fancy, it is either one or the other. You can't have your cake and eat it.
But that is exactly what many members of this forum have been arguing for some time, especially when using the current fares would deny a route, where the historical fares would allow it. Only one set of data should be used, for consistency. Personally I think it should be current fares, as those are easier for everyone to check and are more transparent, but if people insist on using the historical fares, then so be it. You can't just use whichever fare you fancy, it is either one or the other. You can't have your cake and eat it.