What's New – 9th December

Another week has slipped by so quickly, and I can’t believe it’s Sunday again. Here’s what I’ve been working on this week:

  • PPM Data data is now sorted correctly by PPM, and service groups are shown
  • The Thameslink map now extends down to Kentish Town
  • The Kings Langley – Wolverton map now covers Bletchley, Milton Keynes Central and Wolverton
  • Those of you using the Opera web browser will now be able to load the signalling maps, as I’ve fixed the code that loads maps
  • The Map of Great Britain’s Railways now has panning and zooming controls

Other things that are less significant:

  • Sheffield now appears in the list of Train Describers
  • Platform 4 at Willesden Junction is now correctly shown, and was previosuly mis-labelled as Platform 6
  • Boxmoor Sidings are now shown on the Kings Langley – Wolverton map, and the Linslade and Northchurch tunnel bores are now accurate

I’m at a conference on transparency hosted by the Office of Rail Regulation on Monday 10th December. If you’re there, come find me and say hello – but regardless, please read ORR’s calls for improved access to real-time train information and consider responding to their consultation on access to National Rail Enquiries’ Darwin system.

Remember – we’re on Twitter as @opentraintimes and also on Facebook.

Until next week, enjoy the updates!

New features in 2nd December 2012 release

Wow, what a busy few weeks I’ve had! Two hours a day of my free time has been taken up by commuting across London to a temporary contract. Updates have therefore been a little slow, although I’ve made the best use I can of my mega-commute.

This week’s highlights:

Signalling diagrams

Statistics and Information

As well as all of those, the site is ready for Network Rail’s release of S-Class data, where available, from train describers. When this becomes live, some of the maps will show signal aspects (red or green), routes set from signals and track circuit occupation.

Thanks to everyone who’s emailed in asking for maps of specific areas. I’m working on geographical maps, and I’m looking for volunteers to use a GPS device to record the routes of trains. The more data the better – wait for the next blog post, which will have all the juicy details.

Hatch End to Kings Langley

This week has been all about maps. There are only two major updates this week:

First off is the Hatch End to Kings Langley map. Why such a small area? Simple – it’s the only part of the West Coast Main Line that’s directly under Watford Junction PSB’s control.

Next, and finally, the London Euston to Hatch End map has had substantial work and now includes the relief lines used by Southern services, and a handful of other locations in the Willesden and Wembley area. It’s a map which doesn’t fit neatly on to one page, but I’m working on ways to compress it without losing detail.

Behind the scenes, I’m been working on processing Temporary Speed Restriction (TSR) data, published weekly on Friday mornings – and beavering away at producing a richer and more colourful map of Action Wells to Stratford, with signal aspects and routes.

That’s it for another week – I’m hoping to get the TSR pages ready for next Sunday’s release, and I’m still working on ways to make the site faster as it continues to be popular. Do keep your feedback coming in, as well as suggestions for new features.

Remembrance Day release

I missed the deadline for last week’s release – there were some problems that cropped up which took a few days to fix. This means there are two weeks of fixes and new features to announce!

There are two exciting things to announce this week:

  • The East London Line map is now complete up to New Cross, New Cross Gate and Silwood Junction. There is little information about this in the Sectional Appendix, so I spent a few hours yesterday surveying the line by hand
  • I’ve done a lot of work to restructure the timetable database, which respond more consistently. I have another set of performance improvements to put in, which I’m testing at the moment

There is more work to do on the London Euston – Hatch End map, particularly with the Relief lines, and I’ve also started on a Hatch End – Kings Langley map.

As always, most of the bugs that have been reported are now fixed:

  • Switching between tabs on the schedule page is now fixed – you can click on the Facilities and Technical links again
  • Pointwork at Euston and a missing crossover at Mitre Bridge Junction have been corrected – there were some missing crossovers. Thanks to Roger for noticing
  • Some TD areas were shown as dead on the TD Status page. It turns out that not all train describers send heartbeats, so I’ve worked around this. There are still some areas which show a cross – these are train describers which haven’t yet been commissioned

Once again, thanks to everyone for your feedback. Having a full-time job and a busy social life means I can’t always fix all bugs every week, but I do record them all in a bug tracking database so they’re not forgotten.

Wembley Mainline and East London Line maps

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 Big Map

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.

New site release

It’s a week since I relaunched the site, and there’s been a steady stream of messages coming in reporting bugs, offering thanks or suggesting new features. Please, keep them coming!

I have just deployed new code to the server which should fix these bugs:

  • The signalling map sometimes didn’t load berth data, resulting in seeing a screen with four numbers in boxes
  • Bedford South Junction was missing from the Bedford – Luton map
  • The ‘favourite’ icon wasn’t appearing in browsers
  • The feedback button sometimes overlapped, invisibly, some schedules making it impossible to click the ‘i’ button
  • Allowances were shown in hours and minutes, and are now shown in minutes

There’s a bunch more work to do this week. Amongst other things, I’m working on speeding the site up – there are times when it’s impossibly slow for seemingly no reason. I’m also half way there with a map of London Euston – Hatch End (Wembley Mainline) and I hope this will be in next week’s release.

Thank you to everyone for the continued support and lovely emails!

On Freight

Here are possibly my final words on opening up freight schedules.

Freight schedules are commercially sensitive. Real-time data on freight trains is commercially sensitive. Freight operating companies (FOCs) don’t want the whole world to know about their operations because they’re in competition with other modes of transport – primarily road haulage. This makes the data quite different from passenger TOCs because there’s no outside competition.

I’ve tried to come up with a compelling justification for opening up freight schedules and real-time data, but I’m afraid I simply cannot find one. A few people have been in touch with me with legitimate reasons to analyse freight data – for example, in transport planning to construct bus timetables such that they don’t use level crossings around the time freight is due. However, the vast majority of people are enthusiasts, some of whom think everything should be free and don’t understand that commercial organisations are there to make money, not to service the enthusiast community.

You can get ‘gen’ about freight trains if you look in the right place. Yahoo! Groups has several groups just for freight workings, including consists (the loco and wagon numbers). Most of it appears to be supplied by insiders with access to the right IT systems and then filtered out gradually through a network of others. It’s is a process that’s been going on for years. I won’t comment on whether I agree with it or not – it’s not relevant – but I know this process will continue.

And now, the final words on whether freight will ever appear back in OpenTrainTimes – it’s very unlikely unless the Department for Transport, Network Rail and freight operators change the situation from above. I’m not going to pursue the issue any more – it was never on my agenda in the first place, and isn’t something I have time to fight for any more. However, if a freight company is willing for their schedules to appear on OpenTrainTimes, please contact me via email and I can make it happen.

Intermittent outage

Sorry if you’ve been unable to access the site over the last 48 hours – there was a problem with one of the DNS servers that handles opentraintimes.com which was directing people at an old server for the site. It’s fixed now.

In case you want the details – the primary nameserver for opentraintimes.com has been upgraded and reinstalled, but the BIND configuration I put back was a copy from several months ago before I migrated from Amazon to Rackspace. The serial number on the zone was lower than that on the secondary servers for the domain, so none of the secondaries picked it up. It’s a case of luck as to which server you get sent to, so there was roughly a 1-in-5 chance of picking up the server with rogue information.

Backups are good, but restoring the right one is even better!

Open Data

What a lot has happened in the last three months since the last post.

Network Rail, working with Rockshore, have opened up some of their information systems. This is the same data that I started working with a year ago – except it’s now open to everyone. I met with Network Rail shortly before the platform was released (along with a group of other developers) and made suggestions for several, more detailed sets of information to be opened up, and I have more on my list for the next meeting in September.

To help the developer community, I’ve started the Open Rail Data Wiki, and it’s a busy little thing already. OpenTrainTimes is getting a design overhaul and these real-time feeds integrated, which is a massive job to do properly – but ‘properly’ is what I want to do.

Finally, two other items of great interest are that Network Rail have also released the Working Timetable and Sectional Appendices, both available on their transparency page. I’m still hiding freight trains from OpenTrainTimes, and still pestering Network Rail to make a decision on whether or not these are shown.