Open Rail Data - An Overview

My talk at JSOxford covering the many aspects of open rail data available from Network Rail and National Rail.

Transcript

1. Hello!
3. https://www.flickr.com/photos/ed_webster/7510063496/ Open Rail Data
4. Master Plan • Data Overview • “Rail Data Engine” • Lessons Learned
5. https://www.flickr.com/photos/mattbuck007/9273579839/ Data Overview
6. Detail VS Usability
8. Darwin
10. Entirely based on predictions
11. Some people question it… http://thomas-cairns.co.uk/2013/02/orr-real-time-train-information-consultation/
12. http://nrodwiki.rockshore.net/index.php/About_the_NRE_Feeds
13. Demo
14. Darwin Summary • Easiest to access. • Questionable accuracy.
17. Internal Systems Train Planning System Train Running System Train Describers Schedule Data Train Movements Berth Data Signalling Data
18. Schedule Data
19. Header (Schedule metadata)
20. TIPLOCS (Timing Point Locations)
21. Schedule Records
22. Schedule Locations
23. Schedule Data Process Integrated Train Planning System (ITPS) Train Company A Train Company C Train Company B “Full file” “Update file” Nightly
24. VSTP Feed (Very Short Term Plan)
25. What Is Very Short Term?
26. <48 Hours
27. Which Record Is Correct?
28. STP Indicator Permanent - Long Term Overlay - Long Term Alteration Cancellation - Long Term Short Term Plan - Alteration or Cancellation
29. An Example Schedule Permanent Overlay Cancellation STP Monday Tuesday Wednesday Thursday Friday Saturday Sunday
30. Accessing The Data • Initial bulk import (FGW ~70k records). • Nightly delta updates.
31. Demo
32. Schedule Summary • Timing Point Locations (TIPLOCs) • Schedule Records • Schedule Locations
33. Train Movements Feed
34. Activations
35. Cancellations
36. Movements
37. Movement Data Process Train Planning System Schedule Record Activation Train Running System Active journey
38. Train Running System Active journey Movement Data Process Movement Cancellation
39. Train Describer Feed
40. Berth Messages
41. What is a berth?
42. Usually represents a signal
43. Signal Messages
44. 1B47 1 2 3 4 5 1A35 1Y57 Paddington - Ladbroke Grove 1 2 3
45. 1A35 1Y57 1 2 3 4 5 1B47 Paddington - Ladbroke Grove 1 2 3
46. 1A37 1 2 3 4 5 Paddington - Ladbroke Grove 1 2 3
47. 1 2 3 4 5 1A37 Paddington - Ladbroke Grove 1 2 3
48. Detail VS Usability
49. https://www.flickr.com/photos/mikepaws/8679582600/ Rail Data Engine
50. Story Time
51. C# .NET
52. Sometime last week…
53. “Screw it. I’ll write it in Node.” Me
54. “Thats great.” Mum
55. “At least it will be more functional.” @spikeheap
56. “It’s all about IO.JS now.” The Community
57. Two days ago…
58. “He's going to rewrite it in Go tonight ;)” @marcus_noble_
59. Serious Point
60. Rail Data Engine - Mining STOMP client Message parsers Save to database node stomp client moment / change- case couchDB wrapper
61. https://www.flickr.com/photos/capuchinoking/5877189025/ Lessons Learned
62. Experiment
63. Mine Early
64. Break Stuff
65. Thanks! /tomlane @neverontarget
66. Stickers!!1