Morning,
As I understand it, it is primarily non-passenger, including freight that get obfuscated for the reasons you stated, nuclear trains, safety, competition/commercial, etc. It makes perfect sense to hide those on the public feed (which is why is said 'or internally').
Internally was a bad word for me to chose as non-public would have been better. Although if you look at the service code or schedules that use FOC specific tiplocs, you can actually work out who it is - making obfuscation a bit redundant, but that's a different
story.
I said with at least ZZs as possible as I'd expect even those non-obfuscated feeds would at least hide nuclear trains and a few other trains for national security reasons (royal train maybe).
Network rail must have a feed available for companies that need non-obfuscated data for non-public/internal research projects and have a name for it. I thought it was the ATOC which did show the TOC code for some schedules instead of ZZ, but it also missed
out some data. I suspect companies bypass the ATOC, OpenDataFeeds, etc and hook straight into the source.
Schedule feeds and every related subsystems within Network Rail isn't my area of expertise, so I apologise for the confusion and coming across as a bit of an idiot. I should also proof read more.
I work primarily on the infrastructure data of things, so if you anyone needs help with digitised infrastructure capability or just all the tiploc locations - then those I can help with.
Thanks again.
Regards,
Liam Crozier
Sent from mobile