The reason for MY being shown as a mishap is that it
was a mishap previously. I don't presently have the ability to alter attribution codes across the entire fleet of servers because of build issues on the website. This problem will be solved quite soon.
Cancellations coming down from TRUST only show the originally allocated cause. It can and does change later, but TRUST does not pass this down the TD.net channels. This applies for systems both internally and via the open data platform. Darwin (NRE) may show different reasons, and these ones
can change. However, RTT cannot use these reasons for licensing reasons which NRE allow various entities to ignore, but have yet to tell me I can.
I'm nevertheless quite content to take feedback via the normal channels -
[email protected] email address being the prime one - as ultimately if something is wrong then it helps to fix it. I don't often see issues appearing on forums appear in my mailbox, and I rarely read forums, so if I don't know I can't do anything about it.
What you've got to remember is that RTT interprets the cancellation codes how the developer likes - for example, in the autumn, when theres excessive wheelslip caused by leaf fall, RTT shows the cancellation reason as 'because it's Autumn'.
The only delay codes that result in 'it being Autumn' are FT and TT (from memory) which are "Autumn-attribution Neutral Zone delays". The best summary of those reasons are literally is that it's Autumn as there are so many things that can come under that banner. If anyone has better suggestions for it, then send them via the normal channels, but no-one has yet to do so that I've seen.
Agree with that, but then also some see RTT and Open Train as gospel and the information being put forward is 'official'
We are prohibited under our licensing conditions from saying official about anything one does, so you shouldn't see any open data site saying that.