I can’t say which is the best option or the best backend for the app. I’m just a user and would be happy to be able to use this app again. I find importing the trips into the calendar really useful and the app was always very quick and easy to use. I already enjoyed using it on my Nokia N9.
2 Likes
you can use the austrian öbb backend for the ice routes at least
I noted that you were using the v5 backend for routing. Those (and v6) are also down.
On the up side, I did a bunch of testing with the new v2 version of transitous and it DOES include proper delay information.
I’m going to suggest:
- Implement routing in Multimodal using transitous
- A QML only (maybe python, maybe just js) transitous only app. Including calendar support
At the moment, fixing hafas based and or custom JS backends for Fahrplan seems to be a deadend.
On the other hand, transitous covers a LOT of territory. The newer apis are simple to use, even if they are not 100 % stable. yet. And the bonus is we get multiple territories in one app with one backend.
4 Likes
Cool…
On Fdroid for android i saw the app öffi
It is working well on my xperia xa2.
But it is an android app.
A native one is much better.
It’s my favourite app in sailfish os
As workaround for Germany just select oebb.at as backend. All railway stations work, but not bus, tram…
1 Like
Sadly, this doesn’t seem to be the case in the UK. Whether it’s trains, buses, or trams, I always get a realTime: false flag.
Ergh. If you try routing in the webgui, do you not get any info messages? The UK data seems to include MORE metadata, at least (line color and the like).
I don’t see any indication the web UI would have access to any real time data either.
Ok, I do get realtime (delay) information at least in the rendered views for Metro Journeys. I’m about half finished with a basic app, so I’ll just get it finished and compare data with the bahn data.
6 Likes
I tested a route between two stations within Berlin using their web UI, and it does indeed appear to show real-time data (indicated by a green departure time). However, this does not seem to be the case in, for example, Manchester.
The positive aspect is that both Transitous and National Rail use somewhat compatible stop point IDs, which means I might be able to use Transitous for routing while still enhancing the data with real-time information.
Ah, that sounds promising! I haven’t found a proper way to do routing with the dbahn apis without having a paid account. It’s a bit crazy since the timetable apis which are free don’t even yield convincing results. Try finding Rosa-Luxemburg-Platz ! In any case, on I go …
Seems not to work for Rosa-Luxemburg-Platz, likely because it’s not a DB station.
I think if it’s a genuine Deutsche Bahn station, the ID numbers are somewhat compatible:
e.g.
Transitous:
{
"name": "Genthin, Bahnhof",
"stopId": "de-VBB_710008010123",
"lat": 52.403233,
"lon": 12.156539000000002,
"level": 0,
"vertexType": "TRANSIT"
},
Stripping de-VBB_71000 from the ID seems to result in a valid stop-point-ID which then can be used with the DB api:
https://apis.deutschebahn.com/db-api-marketplace/apis/timetables/v1/plan/**8010123**/250129/09
1 Like
Ah, thanks for the tip. I do believe there are two many kings in the kingdom!
Are there any news on this side? I miss Fahrplan badly. What are others using. I know there is Öffi in Fdroid. But it is an Android app.
4 Likes
You can use the oebb backend, which seems to cover germany. I’ve used it successfully. Or, pick a regional provider.
The version of Ktrip in chum also works for some providers (VBB, berlin/brandenburg, münich, etc.).
I haven’t had time beyond what I’ve put in, and the DB apis are ‘no fun’ ™ and very limited without a commercial plan (routing is basically pay to play). It’s a travesty. But then, that’s just the tip of the ice berg 
3 Likes
Thanx for the tipp with oebb! This works indeed…
For me vrr.de works (Deutschland, Rhein Ruhr)
1 Like
Great it works with vrr.de also for lower saxony Hannover gvh 
1 Like
Did you try the vendo/movas APIs used by railway as suggested in the bahn .de API failure issue on Github?
For me those APIs seem to work quite well and I wrote a parser for fahrplan using them. I don’t use Github anymore so for now I’ve uploaded the patches to fahrplan here:
Patch adding the movas parser: https://paste.debian.net/plain/1366179
Patch updating english and german translations: https://paste.debian.net/plain/1366181
The journey support should be pretty much on par with the old hafas xml/binary API parser. There are some problems with the timetables though. The movas API only returns 1 hour of timetable information per request. Could be worked around by doing multiple requests for different times but I haven’t implemented that. Also the API does not seem to support querying timetables by destination so I’ve implemented that by filtering the results.
4 Likes
Thanks a lot! I’ll stash the patches and try making something of it on Monday.
In the main, I had such a shitty experience with the ‘new’ DB xml apis that I started (about 1/2 finished) building a transitous client instead But, I’ll give your approach a shot!
Thanks!
3 Likes