Our attempt to build a calendar feed with personalised disruption services has mostly failed due to lack of structured data.

What it does

It is a demonstration of what disruption data feeds can look like with no complicated steps on the side of the data providers. Also a visualisation that can be built with ease using our purposed structure.

How I built it

Challenges I ran into

Making good use of disruption data feeds, as the important bits of the data is not structured.

Accomplishments that I'm proud of

We are building a demonstration of what can be done and attempting to convince the relevant people to adopt this new data structure, which will save months for many companies attempting to use this data.

What I learned

Open data is the first step towards useful things. The next step is to make this data structured and easily accessible. Our vision goes beyond disruption in rail services, we want to fix rail open data, one feed at the time.

What's next for Disruption Feeds

Moving to other open data feeds which are too hard to use, and make them actually useful, not just available.

Share this project: