query BVG/VBB APIs directly

[derhuerst]

While I intend to keep *.transport.rest up, it would be better if this integration would query the upstream BVG/VBB APIs behind *.transport.rest directly.

I elaborated at https://github.com/kennell/schiene/issues/1#issuecomment-445468008, how you could use hafas-client from Python.

Let me know if this is an option.

[derhuerst]

Advantages:

• Your integration will behave almost exactly like a BVG/VBB app on a phone.
• You depend on one less service on the internet run by random people. 😁 Even though I want to keep *.transport.rest running as a low-barrier way to access public transport data, it makes sense to access the information as directly as reasonably possible.

Disadvantages:

• When the upstream BVG/VBB APIs change, hafas-client needs to be adapted. With *.transport.rest, this happens "behind the scenes". By using hafas-client directly, your users would probably have to upgrade every now and then.
• While a Python <-- JSON-RPC --> Node with hafas-client should work reliably, it isn't the most elegant setup.

[derhuerst]

The situation has changed a bit, I recommend to keep using my wrapper APIs for now.

But: 1.bvg.transport.rest is shut off, the latest version of the API is v5.bvg.transport.rest.

[tobias-richter]

@derhuerst I think the bvg_sensor is not actively maintained at the moment. I had opened a PR with a fix for 2.bvg.transport.rest in April 2020 and it got no attention (https://github.com/fluffykraken/bvg-sensor/pull/6). I have just created a PR with a "hotfix" for v5.bvg.transport.rest (https://github.com/fluffykraken/bvg-sensor/pull/7). Sadly I have not the time to implement the usage of your wrapper at the moment.