There’s been a few changes and updates to Realtime Trains today.
Most of the changes are small incremental changes and fixes but the major one fixes an issue with trains incorrectly reporting and overwriting in the London Bridge area.
Changes will all be in effect immediately with the exception of the distance engine which affect services from Tuesday onwards.
- Terminology change on detail train pages - “passes another service here” to “passed another here”
- GB Railfreight operated services are no longer obfuscated at all
- Fix to inhibit blank speeds showing when the timing load changes
- Slight performance improvements
- Fixes a problem where, in certain cases, an ‘all day’ search does not work
- Fix issues with overwriting trains in situations where two trains with similar headcodes serve the same geographical TIPLOCs but the Train Describer areas differ
- Improve an issue around MongoDB write concerns and some trains not saving properly
- Improvements to the distance engine preventing potentially illogical timings displaying on WTT infill
- Fix an issue with VSTPs not always showing speeds