What’s new – 21st January 2018

This week has been crazily busy – we have a brand new map, and also an updated map for you:

Some of the minor issues fixed this week include platforms at Grangetown near Cardiff Central, signal 2041 at Bristol Parkway mislabelled, routes on the Banbury and Oxford maps, and the link between the Victoria and Chatham maps.

Please keep on reporting problems to support@opentraintimes.com – we keep track of every message you send so we can get back to you.

Until next time, enjoy the new maps!

What’s new – 14th January 2018

Another Sunday creeps up on us, and it’s time to release the new maps and updates to the site. Work is continuing in the background on brand new features for the next major version of the site – constrained, as always, by having to go out and earn money to pay for all of this.

This week, there are two new maps:

  • London Victoria to Nunhead and Herne Hill covers the entirety of London Victoria station, including the Down Carriage Sidings and Stewarts Lane Depot, down to Clapham High Street. The curve toward Loughborough Junction extends the map to fringe with the Thameslink Core map, and we also have toward Herne Hill and the routes to and from Loughborough Junction and Brixton. Peckham Rye and Queens Road Peckham fringe the map nicely with the London Bridge and East London Line maps, and past Nunhead, we also fringe with the North Kent Lines map via Lewisham
  • The West Dulwich to Teynham and Sheppey map extends from the other new map, taking us down through Beckenham Junction (fringing with the Norwood Junction map for trains to and from Crystal Palace), through to Sittingbourne and Teynham. We’ve also included the branch to Sheerness-on-Sea

A vast amount of work has gone in to these maps, and we’re rightly quite proud of what we’ve achieved in such a small time. On top of that, we’ve also been busy fixing problems with the existing maps – so many this time that we can’t actually show them on our development system on a single page!

  • Signal L249 was missing from the Liverpool Street to Romford map, and we’ve revised the layout around the Carpenters Road Curve and lines off to the North London Line
  • Platform 1 at Filton Abbey Wood had mysteriously disappeared, but we’ve been assured it exists in real-life, so have added it
  • One of the ETCS marker boards at London Paddington was facing the wrong way, and now points toward the track to which it applies
  • Again, another ETCS marker board was the wrong way around at London Blackfriars, and we’ve also removed the berths for the cab-signalling markers on the line toward London Bridge
  • We’d drawn the fringe between the Stour Valley and Wolverhampton workstations incorrectly on the Smethwick Galton Bridge to Stafford (exc.) map, so we’ve fixed it – trains no longer disappear at BW4248 and BW4249 signals
  • Signal T646 at Plumpton is a distant signal, so we’ve removed the berth
  • We think the signal at Ashchurch for Tewkesbury sidings is G234, not G324, so we’ve corrected it on the map
  • At Loughborough, the Limit of Shunt (LOS) board by signal 524 was showing as an ETCS marker board, and this now shows as a LOS marker
  • Some additional routes are shown around Three Bridges, as well as the misnumbering of T510 signal being fixed. Reigate’s RG23 berth now clears out when a train passes the signal
  • Some trackwork missing at Lancaster has now been added
  • A set of points was misdrawn around platform 4 and 6 at Cardiff Central, making it look like it was impossible to move from platform 4 to the main lines – this is fixed
  • Kenilworth station is shown between Coventry and Leamington Spa, although no trains are booked to call there yet
  • At Ashford International, the berth for signal 664 in platform 1 has been fixed, the map extended to Chartham and the signals past Sevington now display descriptions

Please keep reporting bugs, problems and issues to support@opentraintimes.com – you’ll get an email back which will let you see progress of your report, and also when it’s fixed. We like to keep in touch.

Until next time, enjoy the new maps!

What’s new – 3rd January 2018

Happy New Year to you all – we’ve been hard at work over the Christmas break updating several maps, which are now live:

As well as those major pieces of work, there are a handful of minor things that have been fixed:

  • Between Winsford and Crewe, some signals were placed out-of-order
  • At Lydney, some berths were missing from the loops
  • On the Exeter map at Norton Fitzwarren, signal E627 was mis-drawn as a ground position light signal, rather than a main aspect
  • Signal 7125 at Metheringham failed to show a train description
  • Route from signal S136 at Sheffield were drawn incorrectly

There is still competition back at OpenTrainTimes HQ between updating the public site and working on projects which bring in the money we need to keep the public site running. We have a rather large backlog of support tickets waiting to be answered – if you’ve logged something and not had a reply, we’re sorry – and we’ll get around to responding as soon as we can.

Until next time (which will be sooner than three months since last time!), enjoy the maps!

What’s new – 1st October 2017

After a lot of work, the Bristol Parkway map has been redrawn slightly and extended to cover the Avonmouth loop and the Severn Beach branch.

Drawing and making the Filton Diamond look sensible was a challenge. For those of you not familiar with the area, Google Maps shows it well. West from Bristol Parkway are two tracks to the north and two to the south, plus a single track across. From the north and south, the track splits in to a single line toward the west. It all sounds pretty straightforward, but representing it on a map and making it look and feel usable was one of the biggest challenges we’ve ever undertaken.

Due to spending all our time working on this map, the only other update is on the Wilmslow map, where routes from MS4132 now show.

It’s time for a much needed chill-out now. We’re working nearly seven days a week on OpenTrainTimes and other projects, but planning on tackling a couple of smaller, simpler routes for the next update in a couple of weeks.

What’s new – 10th September 2017

I’m happy to say that we’re back up to full speed! Summer is behind us, and the wet weather has given us the perfect excuse to start attacking the support tickets and emails which continue to flood in.

Fifteen or so support tickets have been reviewed and sorted out this weekend, fixing the following bugs:

We’re going to start working on some new maps in the coming weeks, as well as preparing for further engineering works happening later in the year – as well as other projects to bring you even more detail on maps.

Until next time, keep watching the trains!

What’s new – 4th September 2017

It’s taken much longer than we ever thought, but the new London Bridge and North Kent Lines maps are now live.

So, what took us so long? It’s just down to a case of bad planning – although the signalling plans arrived some months before the work was to be carried out, we didn’t carry out our normal assessment of how much we need to change on our maps. That, coupled with plenty of other work and holidays meant we’re running slightly behind.

The good news is that the final layout of London Bridge and the surrounding area will now be much, much easier to draw, and we’re fully anticipating the next updates will be ready much closer to the event.

We’re also updating the London Waterloo map in the next few days – we won’t make an announcement as it’s trivial, but you can expect the new points and signalling around the low numbered platforms to be shown on the map soon.

What’s new – 20th August 2017

As explained blog post earlier this week, we’ve had a bit of a hiatus. But we’ve just released the new Bristol Parkway to Newport map, with extensions to the Swindon map to cover a few signals past the fringe between two signalling areas of control, and some extras on the Gloucester map to add Chepstow.

Please get in touch at support@opentraintimes.com if you notice any errors on the map – it’s a complex one behind the scenes!

August 2017 Update

Things have been quiet over the last couple of months, so it’s time to give you an update and tell you what’s happening.

Keeping the public version of OpenTrainTimes entirely free is not easy. Working long hours to bring in the money to cover rent, bills and the occasional holiday takes a lot of time and energy. The sort of work I carry out isn’t a normal 9-to-5 job either – it’s impossible to leave at 5pm and not think about creative solutions for the problems you’ve discussed that day. Some days, I’m still working at 10pm to do the best possible job I can.

Occasionally, other projects come along that take up all my free time. That is precisely what’s happened over the last couple of months – I’ve been working with some very talented people on a new product which involves lots of fresh thinking and creative ideas. That project is starting to wind down again, so I’m back in the hot-seat and ready to work more on OpenTrainTimes.

Thanks to everyone who’s been in touch to ask if everything’s OK – I’m coming to the end of almost 20 days of back-to-back work after a few frantic weeks being airlifted in, metaphorically speaking, to rescue somebody else’s project.

The good news is that we have a brand new map of Bristol Parkway launching on Sunday. This gives us full coverage of the Great Western Main Line all the way from London to Bridgend. Alongside the new map, there are some fixes to the Gloucester map which we released back in June.

After Sunday’s release, it’ll be a busy week to prepare for several changes to maps as a result of engineering works over the August Bank Holiday, and we’re hoping to release the maps on Monday afternoon, ready for Tuesday morning.

And after that? You can expect more maps, more real-time information and even better insight in to how the railway’s running. There’s also lots of work going on to scale the site up so it copes with the continually increasing demand. Most of that will be invisible, but in the next few months, we’ll have some minor changes to how the website looks to allow us to roll out new features.

In summary, don’t worry – OpenTrainTimes is still open for business!

What’s new – 25th June 2017

Monday’s problems on the website has caused us to scale our release plans back a bit to make sure the site’s stable. Some of the work we’ve done since Monday has involved adding in extra monitoring to check that our fixes have been successful and, so far, they have been.

So, what have we added?

The biggest thing is the new Gloucester map, which links up with the Bromsgrove and Swindon maps, covering Gloucester to near Chepstow, Stroud and Stonehouse to Standish Junction, Gloucester Yard and all the way up to just outside Bristol Parkway. We’re planning to extend our coverage westwards too.

We’ve also fixed numerous little things, from platform numbers and junction links on the Warrington map, to missing signals between Crewe and Winsford, some TVM430 marker boards which should have been limit-of-shunt markers at Staines, and missing signals at Worting Junction. We’ve also taken off the schedule count on the Schedule Search page, which was causing inefficient database lookups and contributing to Monday’s issue.

Thanks to everyone who’s been in touch over the past fortnight – it’s time to sit in the remains of the sunshine with a glass of wine and chill out for a bit.

Post-Incident Review

We had some problems with OpenTrainTimes earlier today. Although the public site is not operated for profit, we take uptime seriously and we’ve produced this review of what happened.

If you use OpenTrainTimes as part of your job and you’re interested in a commercially supported version of the site, including freight data and integrations with your stock and crew systems, please drop us a mail at hello@opentraintimes.com.

What happened?

Earlier this evening, we had multiple users reporting that maps on OpenTrainTimes were lagging.

Upon investigation, we found an unusually large number of users on the site for the time of day combined with a 45 minute backlog on our train describer feed.

We temporarily disabled the train movement feed and turned off logging for the real-time maps in order to process this backlog. Once the backlog had cleared, we turned the train movement feed back on and monitored the service whilst the backlog of TRUST messages cleared.

The site returned to normal operation by about 2045.

More detail

OpenTrainTimes is a very popular site, and several hundred users are usually viewing multiple maps at the same time. This figure grows steadily and gradually over time, and we review our capacity every few months to make sure we’re not caught out. Each time we release a new map, the base load on our servers increases as we have anything up to 500 new pieces of signalling data to process – and then there are the extra users that the maps attract.

But that wasn’t the issue – but not by the number of users, but by the type of users!

Briefly, when a user’s web browser connects to our map server, it either uses a long-lived connection over which map data is sent, or it requests map data every few seconds. Several things influence which is chosen, but it’s usually down to whether the device is behind a proxy server – not all proxy servers allow, or support, long-lived connections over websockets.

This evening, we noticed a larger than normal number of polling users. Since a large percentage of OpenTrainTimes users are coming from a mobile device, we think this may be because a change was made at one of the mobile network providers which meant our websocket implementation couldn’t be used by clients.

Normally, this is OK – but the gradual and continual increase in users each week, coupled with a gradual surge in the number of connections that our server was logging, meant there was insufficient CPU time available to process all of the data coming in to us from Network Rail.

The first thing we did was to turn off logging – we don’t really need it day-to-day, and it bought us some time. We then switched off processing TRUST messages, allowing them to queue whilst we allocated the rest of the server’s capacity to processing the backlog of train describer (TD) messages. It took about 20 minutes to process the TD messages, after which we turned TRUST messages back on. Processing the backlog of those messages, plus the remaining TD messages took about another hour.

What we’re going to do about it

First of all, we’re sorry that we missed a trick and took too long to respond to the initial reports of a problem.

We’re going to add some new health checks to our monitoring system, one of which will enable us to monitor the size of any message backlog.

We’re also going to look at scaling out our servers to cope with the extra demand and leave more breathing room – but this means our costs will double, so we’ll need to make sure this is sustainable.

And finally, we’re going to press forward with the new version of OpenTrainTimes which builds on the six years experience we’ve had working with railway data, and will be quicker and better than the current version.

So, sorry for the problems this evening.

Peter Hicks
Director, OpenTrainTimes Ltd.