It’s Sunday evening again, which means it’s time to announce the work I’ve done over the last seven days – and it’s all map-related.

Maps take an incredibly long time to get right – there’s no quick way of drawing them other than by hand. Despite this, I finished drawing Kensal Green to Hatch End on the London Euston – Hatch End map earlier today. There’s more work needed – the relief lines at Willesden aren’t correct as the documentation I have misses out signals.

As a surprise extra, I drew out the East London Line from Highbury & Islington down to Surrey Quays. Again, it requires more work, and there are a couple of bugs at Highbury & Islington, and also one at Dalston Junction.

If you know either of the routes well and would like to help out, please get in touch.

I also spent a chunk of time working on showing Temporary Speed Restrictions (TSRs). The code will be ready for next week.

This week, I’m planning on making the site quicker. I’ve tested some significant speed improvements when looking up train schedules in a test environment, and I’m looking to put these in to production very soon. The production database has more than 600,000 train schedules and 9,000,000 calling points – sorting through these can take a couple of seconds.

Once again, thank you to everyone who’s been in touch over the past week. Keep sending in your feedback and comments! If you’re on Twitter, follow @opentraintimes, and of course, at the OpenTrainTimes Facebook page.

The first of the new real-time signalling maps is now live – London Euston to Kensal Green Tunnel has just gone live. I had planned to complete the whole line up to Hatch End, where control moves over to Watford Junction PSB, but I have to sleep sometimes.

As well as this map, there are several little bugs that have been fixed, mostly cosmetic, but there are still more to fix, and new features.

I’m hoping to complete the map and add the track up to Hatch End this week, then work on Watford Junction the week after. I am also working on speeding up the site – it’s still really slow at times thanks to the popularity of the site – but I have some ideas I’m testing out.

As usual, please keep sending in your feedback either to feedback@opentraintimes.com, or through Twitter.

There’s a new version of the site up today – a few minor bug-fixes, a couple of new features, and hopefully a speed improvement when searching for trains at a location.

The iPhone bug – where it was impossible to switch to Detailed mode on an iOS device – should now be fixed. If you’re still having problems switching to detailed mode and you’re on an iPhone, please drop me a mail.

I’d planned to have ECS movements (at least) back on the site this weekend. For some reason, Network Rail’s system didn’t send over the usual load of timetable data on Friday night, and so we’re running on out-of-date data. “D’oh!” as Homer Simpson would say.

So, let me revise my estimation of ECS movements back, and push it to Wednesday morning – assuming, of course, I can get the timetable data sorted out in the meantime!