-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backend OEBB (Austria) not working anymore #3
Comments
As far as I can remember this backend worked untill the whole original SW stopped working under Sailfish 4.x |
I can confirm that it's not working in my last release. I'm working on the netherlands so I'll get back to this. |
Thank you. For many here in Austria, Fahrpaln was (and still would be) one of the most important everyday applications under Sailfish. |
Might take bit of time ;) Hopefully they haven't changed the entire api :) |
The 9292 api's had been radically overhauled. The changes from smurfy/fahrplan#287 that I modified to work are mostly new code. It's not finished yet, but won't take long. The 9292 branch is already usable with the dutch backend but 'flake'. The Providers in de/shildbach/pte can be useful reference, but there is not way to use them directly. |
But, of course you're right that all backends that use: HafasClientInterfaceProvider will be fixed with an update to the ParserHafasXml.h and binary headers. I hope :) |
So, those changes work. The sbb backend needs work, but oebb basically works. It's odd in filtering names (Graz vs. Görlitz!) ... but Wien -> Innsbruck in 7 hours on the Zürich route seems reasonable :) |
Thanks a lot. Looking forward for the update. But there should be a connection Wien-Innsbruck in less than 4.5 hours every hour. |
There's the RJX 564 which seems to get from Hbf to Hbf om 4:14. So it's looking like good data. |
https://github.com/poetaster/fahrplan/releases/tag/2.0.36 |
fixed with: 706e78e |
Great + THX. OEBB seems to work pretty fine so far. |
No description provided.
The text was updated successfully, but these errors were encountered: