Sehr geehrter Herr [########],
Ihre E-Mail vom 06.04.2016 haben wir erhalten. Bitte entschuldigen Sie die verspätete Antwort.
BVG-eigene Fahrausweisprüfer und die im Auftrag der BVG tätigen Mitarbeiter der Firma WISAG führen flächendeckend im gesamten Stadtgebiet Fahrausweisprüfungen durch.
Die BVG beförderte im Jahr 2014 rund 978 Millionen Fahrgäste. Für das Jahr 2015 liegen die endgültigen Zahlen noch nicht vor, erwartet werden rund eine Milliarde Fahrgäste.
| 0: Ohne BahnCard, | |
| 1: BahnCard 25, 1. Klasse, | |
| 2: BahnCard 25, 2. Klasse, | |
| 3: BahnCard 50, 1. Klasse, | |
| 4: BahnCard 50, 2. Klasse, | |
| 9: A - VORTEILScard (incl. RAILPLUS), | |
| 10: CH - HalbtaxAbo (incl. RAILPLUS), | |
| 11: CH - HalbtaxAbo (ohne RAILPLUS), | |
| 12: NL - Voordeelurenabo (incl. RAILPLUS), | |
| 13: NL - Voordeelurenabo (ohne RAILPLUS), |
direkt.bahn.guru internally uses a (legacy) API by Deutsche Bahn to find all direct trains running via a given station within the next 1-2 weeks. This API includes most trains in central Europe, but data availability gets significantly lower the further away stations are from routes (co-)operated by DB. Furthermore, trains operated by smaller companies seem to be missing more often than those run by state-owned operators, probably due to a lack of data sharing agreements.
Why do we use this DB-specific API in the first place? Unfortunately, there still isn't any public dataset available which covers all public transport routes in Europe (or even the EU, at least). Some countries don‘t provide data at all, others only publish data per region and operator (e.g. France), which is very hard to combine into a single dataset. See also: https://eu.data.public-transport.earth
That being said, we‘ll try to use a more complete data source as soo
| { | |
| "stadaToEvas": { | |
| "1": [ | |
| "8000001" | |
| ], | |
| "2": [ | |
| "8000406" | |
| ], | |
| "3": [ | |
| "8000404" |
