Internal workings of the API

[Mark531]

Hello,

I'm using your API through https://v5.db.transport.rest and I have some questions about its internal workings if you don't mind.

I'm looking for all reachable destinations from Paris Gare du Nord:
https://v5.db.transport.rest/stops/reachable-from?latitude=48.880697&longitude=2.354598&address=%27%27&maxDuration=300
I get London St Pancras associated with a duration of 79 min.

Now, if looking for all reachable destinations from London St Pancras:
https://v5.db.transport.rest/stops/reachable-from?latitude=51.531922&longitude=-0.126361&address=%27%27&maxDuration=300
I get Paris Nord Eurostar associated with a duration of... 199 min!

Why is that? The 1 hour time difference between Paris and London doesn't explain the 2 hour difference. My questions are the following: when computing the trip durations, are time differences taken into account? Moreover, does the API take into account the difference between the current time and the time departure of the train (so if the train will leave in 4 hours, will these 4 hours be added to the total duration)? And is the current search based on the current time (in other words if I run a search at 3:00 am for instance, won't the API return anything)?

Thanks in advance,
Mark

[derhuerst]

Note that reachableFrom()/stops/reachable-from is time-dependent, so it is affected by the trains available at that particular date+time.

This (weird durations with travels across time zone borders) might be a bug in HAFAS (or in hafas-client!), please try to investigate further. Could it be that it found a 79+60 min connection from Paris to London, and a 199-60 connection back? Please tripe-check this assumption by a) querying journeys (using journeys()//journeys) that use such a connection, and b) by checking actual PDF/website timetables.

[Mark531]

Sure, I can investigate by running the query with different times. But today, I'm unable to make any run. All queries trigger a 503 error without any message. Are you currently working on the API?

[traines-source]

See #331, I think there exist no bugs in the DB HAFAS API anymore, since it has probably been discontinued.