News for hackers. Stuff that matters.

A comment on Nuts and bolts: our routing algorithm. Parent comment

Re:Nuts and bolts: our routing algorithm by boultonmark on Wednesday October 28, 2015 @03:17PM (#10466620)
Yeah it's the Hacon API like http://www.thetrainline-europe.com/ use. That is not the raw data but a journey-planning API. You need to spend 15k to become a licensed Deutsche Bahn partner and then pay Hacon per query. But the Captain Train post seems to be talking about them doing their own journey planning from raw schedule data. I just want to know how they got it when no-one else including Loco2 can get it.
[ Parent | on HN ]
Re:Nuts and bolts: our routing algorithm by boultonmark on Thursday October 29, 2015 @06:47AM (#10470115)
Update from CaptainTrain in the comments in my reply to where do you get the data:

"It’s magic. :) To be honest, this is a strategic topic we can’t comment on. I’m sorry."

i.e they have it via a backdoor - someone is giving them it who shouldn't or they're scraping it.

[ Parent | on HN ]
Re:Nuts and bolts: our routing algorithm by joelhaasnoot on Saturday October 31, 2015 @06:27AM (#10482304)
The backdoors aren't hard to guess BTW - one noteable source is reverse engineering the HaCon offline products.
[ Parent | on HN ]