Some of you are harvesting our iRail API. That’s okay, you can do whatever you want with the API, but right now, we have reached a limit (300.000 requests per day) where we might want to give you another option that is cheaper for us: datadumps of all departures with their platform, delay, expected arrival time and so on, harvested each 5 to 7 minutes. We hope that this will give you more flexibility and will leave you with new ideas for new applications.

You can find the data dumps at “The iRail Archive”

Please start using this data and tell us what should change. We are still experimenting with giving you direct querying possibilities on top of this data (to be announced later), building on top of this data (by our intern Nico, can be followed on github) and with more compact data structures which may allow us to archive this data cheaper.

The data model for the archives

You can find iRail RDF files which follow the iRail schema (see below) using the RPLOD and Transit ontologies. The 00-nmbs-latest.ttl is the last version which can be used for showing delay information to end-users. They will become queryable through this server soon. The other archives will need to be downloaded before using.

We would love to know how you use our data and how we can improve them. Send us a mail on our mailinglist or tweet us @iRail.


About Pieter Colpaert

Pieter is a researcher in linked transport data publishing at MMLab - UGent - iMinds. He also co-founded Open Knowledge Belgium, in which he represents the iRail/Open Transport Working Group.

15. May 2014 by Pieter Colpaert
Categories: Uncategorized | Leave a comment

Leave a Reply