SlimJim1694
Member
Thanks Tom. That's an extremely informative response and opens my eyes to how it all works. I'll be honest that up until reading that I wasn't really sure.Let me start with the simple things: the cancellation reason that shows on RTT is the first that goes into TRUST. If it is subsequently corrected then that does not carry through. This is an artefact of how the feeds 'take' data from TRUST.
The way the NR train describer works between Mantles Wood and Harrow-on-the-Hill South Jn, where Marylebone IECC fringes with the Metropolitan Line, is a series of several queue berths. These queue berths work on the basis that when the train steps into the Met Line at, say, Mantles Wood then it enters the queue and steps forward as far as possible. If it is the one and only train moving on the southbound Met, then it steps up to the berth just prior to the first step back in. It works likewise for the northbound. This makes the train describer 'blind' to what happens on the Metropolitan Line.
For Harrow-on-the-Hill northbound departures and Amersham southbound departures, there is a berth offset that is a positive number (it's normally negative) against the fringing NR signal into the Metropolitan Line. This means that you will always have a constant dwell time at those stations in those directions. It works similiarly with a negative arrival for Harrow-on-the-Hill southbound and Amersham northbound.
Once you are on the Metropolitan Line proper, Network Rail systems are effectively blind to what is happening. Up until about October last year when it broke properly for the final time, RTT had a mechanism to use track circuit data pulled from Trackernet to track trains through the area. In a similar mechanism to how it works on Network Rail metal, it used the time it stepped into the circuits to infer a departure and arrival time at each location based on fixed offsets.
Chiltern introduced the GPS reporting facility onto their fleet more recently which meant I was less inclined to fix the issues around Trackernet as it, really, didn't seem worth it. GPS reporting works mildly different for each operator due to the whims of the systems that drive it but, in a simplified/generalised view, the data goes into Network Rail's GPS Gateway as well as some other data warehouses. There are a series of geofences at most reporting locations which translates from time/position to reporting. I don't have a view of how big those geofences are for the Metropolitan Line but for some locations they are insanely large and they also don't always require the train to stop in the station limits to report for a station call.
My personal opinion is that the geofence, based on what I know historically, is that the geofence for Chalfont & Latimer is ... large.
Just an aside... is there AWS on that LU section for the Chilterns?