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!
Correct - it was in reply to people pointing out passenger trains which are listed on RTT
but don't show allocations because the operators do not use the GEMINI system, such as
Tyne and Wear Metro, Sheffield supertram, etc.
There was a time when they did show, although at a different Wimbledon station. I seem to remember that they were either 1Ixx or 2Ixx depending on whether they were Edgware Road or 'City' services.
That's a known issue with the data on the branch; it doesn't even show the trains correctly on the platform indicators at the stations between West Brompton and Wimbledon.
I'm hoping to get something out for Traksy soon, although I expect it to initially be an extension of the way we currently do C2C tracking - barebones unit numbers, and on the new site only. Will take a couple of weeks to think through whether I want to do a more comprehensive version and how to make it available to free users.
The release comes entirely without documentation in the form of gigantic XML files fed through a new connection method, so it's not going to be trivial, and it's unlikely to be released for a day or two. You may see me hacking away on Monday and Tuesday as I take very stupid way round from London to Edinburgh.
The good thing about c2c is the trains don't divide on route. I've only just started properly looking at this, but now I'm having trouble finding a service that divides so I can handle the deallocation properly on a schedule route...
I've found today's Horsham / bognor splits but I've only just started logging so I've missed the input...
Agree documentation would be good but I guess that takes the fun out of it. Eg not knowing the difference between TrainDest and AllocationDest lol
The good thing about c2c is the trains don't divide on route. I've only just started properly looking at this, but now I'm having trouble finding a service that divides so I can handle the deallocation properly on a schedule route...
I've found today's Horsham / bognor splits but I've only just started logging so I've missed the input...
Agree documentation would be good but I guess that takes the fun out of it. Eg not knowing the difference between TrainDest and AllocationDest lol
To be honest I think it's reasonably clear, or not incredibly difficult to figure out, and waiting for somebody to clear the documentation as well would only have delayed the process even further. It's mostly just quite a lot to parse through and get set up, with having to use an external Kafka connection. The Kafka client library I'm using is already a bit dicey for internal connections, so I'll probably need to look at something which just copies the queue over to my local Kafka server.
To be honest I think it's reasonably clear, or not incredibly difficult to figure out, and waiting for somebody to clear the documentation as well would only have delayed the process even further. It's mostly just quite a lot to parse through and get set up, with having to use an external Kafka connection. The Kafka client library I'm using is already a bit dicey for internal connections, so I'll probably need to look at something which just copies the queue over to my local Kafka server.
There is an ICD (Interface Control Document) on its way, and some XSDs (FOI request pending) for the XML data will be available soon too. I will also write a less formal explanation of how to use the data for the Open Rail Data wiki in due course.
There is an ICD (Interface Control Document) on its way, and some XSDs (FOI request pending) for the XML data will be available soon too. I will also write a less formal explanation of how to use the data for the Open Rail Data wiki in due course.
I think looking at the messages that I've got a fairly good grip of what most of the fields mean. It would be good to know what some of the possible values are for operators and liveries (I guess the operators might be the same values from Trust, but just as a 4 digit number?). Would also be handy to know whether the train id (which is embedded in a longer code for the examples I've looked at) can be depended on, or whether I should be figuring it out from operator/station/headcode.
Hopefully it will happen at some point given most TOPS data is already available "on demand". Eg through groups.io where various groups publish loco pool lists daily...
Yes, but TOPS access is tracked, and a few similar “holdouts” on the freight side of thing view it as infringing on “commercial sensitivity” - it took a lot of work to get freight headcodes unscrambled - I remember the days of FRGT and random headcodes being displayed in data!
I was looking this morning for the operator codes I wasn't sure if it had something to do with the 2 digits at the end of the train ID eg (not a real example) 2K21W1234523 as I can't see anything else it could be.
The last two digits at the end of the Train ID in LINX messaging from memory is the hour of train departure from origin. RTT uses the Core identifier and plucks the UID out of it. From memory in some cases a TRUST ID can also appear in that field (but that might have been changed in the past few years!)
From experience the metadata that goes along with the messages, e.g. livery/operator/seats, can be taken with somewhat of a pinch of salt.
The last two digits at the end of the Train ID in LINX messaging from memory is the hour of train departure from origin. RTT uses the Core identifier and plucks the UID out of it. From memory in some cases a TRUST ID can also appear in that field (but that might have been changed in the past few years!)
From experience the metadata that goes along with the messages, e.g. livery/operator/seats, can be taken with somewhat of a pinch of salt.
Yes, but TOPS access is tracked, and a few similar “holdouts” on the freight side of thing view it as infringing on “commercial sensitivity” - it took a lot of work to get freight headcodes unscrambled - I remember the days of FRGT and random headcodes being displayed in data!
I'd love to be able to access TOPS if only to find out about wagon locations and train-lists, but I can see that they might be deemed commercially-sensitive, so I don't hold out any hope.
You can get the sector code from the ResponsibleRU field. I'm not sure I would trust the Operator/Livery fields personally on the actual allocations based on past experience - RTT uses a custom mapping.
You can get the sector code from the ResponsibleRU field. I'm not sure I would trust the Operator/Livery fields personally on the actual allocations based on past experience - RTT uses a custom mapping.
Real-time train running information for 1A01 0630 departure from Edinburgh to Aberdeen on 22/09/2025. From Realtime Trains, an independent source of train running info for Great Britain.
I'd love to be able to access TOPS if only to find out about wagon locations and train-lists, but I can see that they might be deemed commercially-sensitive, so I don't hold out any hope.
If you have some money, you can get access to the rail mainframe for yourself - we're taking a few thousand pounds per year for two CICS sessions. No guarantees you'll be able to make the TOPS enquiries you want, but it is possible.
== Doublepost prevention - post automatically merged: ==
I think looking at the messages that I've got a fairly good grip of what most of the fields mean. It would be good to know what some of the possible values are for operators and liveries (I guess the operators might be the same values from Trust, but just as a 4 digit number?). Would also be handy to know whether the train id (which is embedded in a longer code for the examples I've looked at) can be depended on, or whether I should be figuring it out from operator/station/headcode.
Operator codes are 99xx, with the 'xx' being the numeric code as used in TRUST messages. Liveries... that's another story, I'm now trying to assemble all the associated reference data to help people make best use of it.
You shouldn't need to work anything out - allocations have start/end times and TIPLOCs which you can match up to a schedule. Likely you won't even need to reference any of the train identification data, but if I were you, I'd work with the UID embedded in the TransportOperationalIdentifiers tag.
You shouldn't need to work anything out - allocations have start/end times and TIPLOCs which you can match up to a schedule. Likely you won't even need to reference any of the train identification data, but if I were you, I'd work with the UID embedded in the TransportOperationalIdentifiers tag.
I'm hoping to keep building this as a separate model which doesn't need access to the CIF schedules, but l'll see where we get - it all ends up running in the same process anyway, so it's not the end of the world if it has to do a schedule lookup
It's possible, but obviously it's not going to ever be 100% accurate, I've seen 377 diagrams get updated late evening for services they worked in the morning.
Yes, there is enough detail to do that - but only where resource allocations are made. You don't know if a resource diagram is an LTP or STP diagram, therefore you can only guess (but quite reasonably most of the time) until you've had what you think are all allocations in for a particular day.
You can enter a unit number into the search on Realtime Trains and if it's currently doing something it will bring that journey up.
One thing that would be REALLY handy would be if this data included which way round a given unit is, particularly on TOCs where units can end up either way like TPE and XC. That would require input by guards, I guess, though, so I doubt it's coming soon.
One thing that would be REALLY handy would be if this data included which way round a given unit is, particularly on TOCs where units can end up either way like TPE and XC. That would require input by guards, I guess, though, so I doubt it's coming soon.
That's quite interesting as the formation diagrams on CIS displays usually do show the orientation correctly for most TOCs so the data must be there somewhere. Those diagrams for something like WMT obviously don't show first class (even though it'd be useful for those of us who like the declassified bit to know where it is so we can get there first, same for the bike spaces which if accurate would result in fewer bikes shoved blocking the way in vestibules) but for the likes of XC it often is correct. However there do seem to be multiple sources of this data - one I noted recently was SWR platform screens saying in the text "this train is formed of 6 coaches" but the little icons showing three (the 6 was correct).
Yes, there is enough detail to do that - but only where resource allocations are made. You don't know if a resource diagram is an LTP or STP diagram, therefore you can only guess (but quite reasonably most of the time) until you've had what you think are all allocations in for a particular day.
Don’t the “associations” records in the Schedule feed essentially describe diagrams? I played with them a bit recently but not to the extent of trying to build up a UI for them. Looked fairly comprehensive though from just playing with SQL.
== Doublepost prevention - post automatically merged: ==
Greater Anglia upload formations and capacity for long term and short term each week on the marketplace. I’m guessing that it would be possible to match the data using the ID. C2C also publish their formation data each day and a number of other operatots have uploaded long term plan formation data. I’m told that the open Gemini data includes diagram numbers, NT 301 as an example, that should simplify creating diagrams.
That's a known issue with the data on the branch; it doesn't even show the trains correctly on the platform indicators at the stations between West Brompton and Wimbledon.
I think that is a major London Underground wide issue. Nothing really to do with this section in particular. Lots of stations between Earls Court and Ealing Broadway also fail to show trains properly on the station boards. Even some stations in Central London can be very out of sync with the reality of when trains are due to arrive. London Underground are just very poor at providing correct next train data at stations.
We are aware of an issue with emails from the Forum to Microsoft-based email accounts (hotmail/outlook/live.com email addresses). This is being looked into currently, thanks for your patience meanwhile.