juliuste / api.direkt.bahn.guru Goto Github PK

Not sure if this is in the scope of this project, but in countries with a timezone west of Germany (Portugal, UK), the timezone offset seems to be added to the travel durations, e.g., 65 min instead of 5 min. (Example: https://direkt.bahn.guru/?origin=9400674). However, this seems to be a mismatch between the timezones of departures and arrivals coming from db-hafas. So, might be a bit hacky to fix this here.
(The timezone of my browser is GMT, but I don't think this matters.)

Hi,
I'd like to get all the departure from Paris Eurostar Nord, especially the ones to the UK but the API doesn't know this station. But it seems that this station is missing from the dataset. Only Paris Gare du Nord exists, and it doesn't have the Eurostar connection associated.

The DB does know it:

Thanks again for your amazing dataset !

When I try to search the Munich Central Station (https://direkt.bahn.guru/?origin=8000261), I get the following error: "Oops?!
Unknown error. Please try again in a few moments or contact us, if the issue persists.".

Any possible fix for this issue? Thanks!

Some examplery cities that do not work are Goch and Kleve.

• https://direkt.bahn.guru/?origin=8002296
• https://direkt.bahn.guru/?origin=8000205

Error: "Leider konnten für die Stadt, die du gesucht hast, keine Verbindungen gefunden werden."

Occasionally, the pop-ups on https://direkt.bahn.guru/ show travel durations that are by 360 h = 15 d too high. These numbers are reproducible.

Examples:

• London St. Pancras - Paris Nord
• Lille Europe - Dunkerque
• Lille Europe - London St. Pancras

The wrong travel durations seem to come from the API. Without having tracked down the specific cause for this issue, a simple fix might be to filter out these travel times in the reachableForDay function. Currently, there seems to be no train on the world that runs for more than 206 h.