I wonder how/where the author gets connection time information. Each country, and sometimes each public transport company, seems to have their own system, sometimes hard to access digitally.
I've been building a mobile app for quick and convenient public transport departure lookup in Switzerland[0], which is doable because there's a free, well-documented public API[1]. Since it's fairly popular, I thought about extending it to other countries, but as mentioned above, the API landscape looks super heterogenous and spotty.
I'm sure he also benefits a lot from feedback. Someone goes to book a route he suggests, and the connection now doesn't work, they are going to tell him, and he can update his page on it.
Given that he actually travels the routes in question, I imagine he gets the information in the same way he books his tickets - online if its there, in the station if its not.
The people of the European Rail Timetable[0] compile and publish a lot of this information every month (worldwide actually, not just Europe). And he has an entire network of contacts himself now.
The European schedules are published centrally, and you can search them on many websites; the one of the German railways is generally seen as the best. Live data is more of a mess, but you don't need that for a site like this.
I've been building a mobile app for quick and convenient public transport departure lookup in Switzerland[0], which is doable because there's a free, well-documented public API[1]. Since it's fairly popular, I thought about extending it to other countries, but as mentioned above, the API landscape looks super heterogenous and spotty.
[0]: http://billhillapps.com/billhill/quickov.html [1]: http://transport.opendata.ch/