> Signalbox's technology identifies the train a device is on by matching a snapshot of smartphone data to a train’s trajectory data. The technology uses advanced algorithms works even with severely degraded data. We are able to pinpoint a smartphone to any type of train without background location tracking or hardware.
"Acquired by Trainline in 2023, Signalbox works with organisations across the rail ecosystem to improve customer information and operational awareness."
So, we don't know if this is the case, but one way to do this is not to ask the phones but the cells. The mobile network has to know where the phones are by cell; the cells are often small relative to the speed of the train; there are also cells installed specifically to improve service on trains, or provide a base station to the train wifi, or for communications to railway staff.
If you get a bunch of phones switching cell near simultaneously, you can tell that a train movement across the cell boundary has probably happened. Then correlate that with the other data feed about train blocks, and bob's your uncle.
You're missing the fact that the system is also divided into explicit signal blocks and those blocks do report train presence to a centralized system[1]. I am not certain if they want to share that information, but if someone got serious about building a system like signalbox I'd expect that NetworkRail would either offer their data, a degraded version of their data on a lag for security reasons, or consider those security reasons so serious that they'd attempt to prohibit deriving that data from cell signals.
1. Mostly, some signal blocks are still entirely manually managed but, IIRC, at this point those manually managed segments are low traffic areas where only one train is allowed into the block group at a time even if the old signal management systems would allow multiple trains.
Before he was hired by a San Diego-based defense contractor, my maternal grandfather worked on the railroads as a pipe-fitter, and he designed and built for me a high-quality Lionel model railroad in his home, before he passed away. It even had those little smoke-generating tablets that you could drop into the smokestack. I was only six years old.
This year, I was curious about whether I could track freight trains in my region or nearby, in real-time, and perhaps more details like what sort of cars were linked in the train, how many locomotives, what sort of freight they were carrying, etc.
After a few fruitless searches for this tracking info, I realized that the same info that would be "recreational" for me would be "operationally valuable" to any domestic terrorist cell or motivated insurrectionist, as well.
Trains derail all the time, we are told, and trains are robbed blind increasingly often, so I am sure there is some sort of illicit/underground tracking that takes place already, but for now, I must content myself with noticing trains using my own eyes and ears. The freight line next door is inhibited from sounding their horns except in emergencies. And thankfully, I find freight-train and light-rail noise to be calming and soothing, even at 3:30am...
Few questions, wonder if anyone knows the answers:
1. So it's Trainline on a persons phone that is tracking this info and using it to enrich this service? I use Trainline and didn't know it was doing that, but I do have location permissions on because I was told that powered the search picker when I started using the app.
2. What did they use _before_ Trainline? Or was Trainline selling user location data to them?
I think you're misunderstanding what they are saying. They don't use background location data, but they do use your current location data. Try the "Find My Train" demo on their site - it asks for location permission.
Or their API - it also expects device location data:
> At a minimum, requests to the detect endpoint _must_ contain a device's location measurement. Additional fields can be included where available to improve the accuracy of the returned results as outlined below.
You are giving it to them. That's why the demo asks for your location permission, and that's why the API expects location info.
"You" here means another app that integrates their API (or you as an individual using the demo on their website). How the other app gets it is up to the other app - ideally it also just queries it directly and requires location permission.
Not sure how you came to that conclusion. An empty train would still exist in the live train data. It does not depend on mobile phones, but on rail signals and other such tracking built into the rail infrastructure.
The location of the train comes from trackside sensors and is available as a free API. It doesn't give actual lat/lon – it only shows when it went past a particular checkpoint. The part that needs location permission is the one that works out which train you are on. It doesn't use that to produce the main map, it's just to work out which train you are likely to be on.
It works fairly well empirically: my 7yo likes to watch trains and we regularly use this map to know when to expect one to pass. Not perfect, but pretty good
Hmm, that's...interesting?