Happy Birthday, OpenTrainTimes

On Monday 10th January 2012, I launched OpenTrainTimes.  I believe it marked a turning point in opening up Great Britain’s railway data – leading the way and showing that it can be done, and that the outcome would be positive.

We’ve come a long way in those three years.  Network Rail opened up detailed real-time data through their Data Feeds platform and have opened up their timetable, fares and associated data through their Rail Industry Data portal.

Most recently, National Rail Enquiries opened up their Live Departure Boards web service and loosened their terms and conditions so that nearly anyone can work with the data.

In the coming months, the pièce de résistance will be unveiled – open and scaleable access to Darwin – one of the most important systems that produces a ‘single source of truth’, whose information is distributed to websites, mobile phones, station departure boards and numerous other technology platforms.

If you’re familiar with OpenTrainTimes, you’ll realise that it only uses two or three of the available data sources.  There are two very good reasons for that.  First, it’s a more compelling argument when you can appraise somebody else’s work as a talking point and reason to open up data than when you’re presenting your own.  Secondly, OpenTrainTimes started off as an experiment and I never expected it to be as popular as it is.  The architecture has run in to a number of scalability issues which can only be fixed with a lot of behind-the-scenes work.

I’ve been putting in many hours of work each week, outside the time I spent working for Rockshore to improve the railway’s real-time systems, to re-build the entire site and make it even more successful than it is.

I am not quite at the end yet – the majority of the heavy lifting’s already been done and the scaffolding’s starting to be taken down.  There are a few more weeks of testing I need to do to iron out bugs and make sure the new site performs much better than the other did.  Please get in touch if you’re interested in helping test the new site.

When I launch the new site, probably in a month or so’s time, it’ll include real-time data from more feeds at Network Rail and, once the Darwin feed from National Rail Enquiries launches, it’ll include forward-looking predictions that mirror what you see on other systems powered by Darwin.  No “Your site says X, but the National Rail site says Y, how do I don’t know who’s right?” – consistency trumps accuracy in predicting when a train will turn up.

Thank you to everyone who’s helped me out – especially to the numerous industry people who have kept my enthusiasm up and made helpful suggestions on where to go next.

Watch this space – a new OpenTrainTimes is around the corner!

August 2014 Update

It’s been a few weeks since I’ve written about the site – the day-job has to take priority and the number of days when I want to come home and spend more time wrangling over railway data has dropped somewhat.

Rest assured, the site is still under development and I’m working on fixing bugs and compatibility issues before I start work on the next set of enhancements.

Scheduled downtime – Saturday 21st June 2014

OpenTrainTimes is a popular site – so much so that it’s necessary to upgrade one of the servers that runs the site.

To do this, there will be an outage from approximately 0900 to 1300 on the morning of Saturday 21st June, and the site will be offline during this time.

After this upgrade is complete, there will be plenty of spare capacity on the site to allow the next set of exciting features to be developed… watch this space!

What's new – 3rd June 2014

I missed the Sunday planned release date due to a family bereavement – I’ve had too many of those over the past year. However, it has been somewhat comforting to sit and concentrate on drawing maps.

So, a little later than planned, the Liverpool Street to Romford map and Rugby to Birmingham map are both now live.

Coming up next, the Paddington map will be returning, as well as Rugby and the Trent Valley.

Enjoy!

What's new – 26th May 2014

It’s another Bank Holiday weekend, which means an extra lie-in – unless you’re up at 8am in preparation for walking the tunnel between Rotherhithe and Wapping.

This week’s updates have been released on to the site:

A few other minor changes have gone in, such as mislabelled berths – and there are a handful more to go in during this week.

Once again, thank you to everyone who has given feedback. In the pipeline for the next few weeks are things like the return of the Liverpool Street and Marylebone maps, and more real-time data.

What's new – 18th May 2014

Sunday rolls around again, as does summer. As a result, I’ve been spending time soaking up Vitamin D rather than working too hard. Nevertheless, this week brings you two new maps:

  • The new Bournemouth – Weymouth map includes the Poole – Wool resignalling, which is taking place at the moment. This will become fully operational in the next few days
  • On the Midland Mainline, the new Ambergate Junction – Meadowhall map covers Chesterfield and Sheffield – an often-requested area which I’m delighted to have nearly finished

There are a few invisible back-end changes which have also taken place to make the site more robust, but nothing too major.

So, if you’re not out in the sunshine, enjoy the maps 🙂

What's New – 11th May 2014

Sunday rolls around again, and a chance to let you know about the bugs fixed and improvements I’ve made in OpenTrainTimes over the past week.

This week’s new feature is clickable headcodes. When a headcode appears in white, you can click it and see details of the train. This isn’t completely foolproof – I’ve noticed a Hounslow Loop service be mistakenly linked to a train out of London Victoria, and linking doesn’t always carry over between train describers – but it’s a start.

And now, on to the minor things:

  • Signalling on the Hertford Loop map is now fixed, and route indications show up correctly. There is now also an normal/ERTMS indication to show when ERTMS testing is taking place. Thanks to @avgeek777 for spotting this problem
  • Some berths on the London Victoria map have been fixed, particularly in sidings. Thanks to one of the signallers at Victoria ASC for their help and input
  • Platform numbers on the London Euston map have been fixed (thanks, Adrian), as well as a berth which was drawn upside-down (thanks, Ben)

Enjoy 🙂

May Day Bank Holiday update

Thanks largely to having a week off work in a seaside town in North Yorkshire, I’ve had plenty of free time to work on OpenTrainTimes.

Here are the important points about the release I’ve just made live:

  • The maps now show correctly on Internet Explorer 9 and above – this bug took me three or four days to work out 🙁
  • The site will look much better on many screens
  • The London Euston – Kenton and Kenton – Tring maps are now back, and the pointwork removed at Watford Junction this weekend is reflected on the map
  • The Thameslink Core map is back, with some signal aspect data (although this appears to be unreliable)
  • Schedule types (WTT, VAR, STP and CAN) are now highlighted on location pages
  • The “Earlier” and “Later” buttons on location pages now change the time by 1 hour, not 2
  • Trains which originate and terminate at locations, where the trains pass through the location multiple times (e.g. Railhead Treatment Trains) are only shown as ‘Starts here’ or ‘Terminates here’ when they make their first or last, and not on each visit

Finally, I’m aware there have been a few problems with the data feeds that the site uses – not all of them I have control over, but I have found a number of weak areas I’ll be re-engineering over the coming weeks.

So, until next time… enjoy the maps and keep emailing!

Peter

Happy Easter

A very Happy Easter to you all!

A brief update on some changes on the site, based on feedback I’ve had over the past few days:

There are also some bugs which have been reported, which I’m still working on:

  • Maps do not display fully on Internet Explorer – and it’s only a problem on Internet Explorer. I’m currently investigating.
  • Maps are very slow on some browsers – which appears to be a problem with the Javascript code I’m using. Again, I’m currently investigating.

Finally, thanks to everyone for your feedback – it’s great to be back and developing OpenTrainTimes!