lvb.transport.rest

[transgirllucy]

i would like to see the lvb in this api

[derhuerst]

Contributions welcome!

If you have an API with LVB data, or a "wrapper API" around their API, I can set up lvb.transport.rest for it.

[StofLE]

LVB is using on their website the INSA/NASA endpoint with mgate.exe.

I'm using v6.db as data source for a Home Assistant dashboard but some cancelled journeys in Leipzig aren't marked "cancelled" at DB endpoint but in INSA it is correct.

@derhuerst:
Do you think, you can set up such a service?

[derhuerst]

[…] some cancelled journeys in Leipzig aren't marked "cancelled" at DB endpoint but in INSA it is correct.

For the sake of documenting this in a google-able way: Do you know which journeys/trips this applies to?

[derhuerst]

LVB is using on their website the INSA/NASA endpoint with mgate.exe.

Let's name it insa.transport.rest then, that fits better IMO.

Note that you linked to insa-hafas, which currently depends on an outdated version (5.x) of hafas-client. When setting up insa.transport.rest, we should either a) first update insa-hafas, or b) use hafas-client@6's INSA profile directly.

Do you think, you can set up such a service?

While hosting another hafas-rest-api + hafas-client "instance" on the server is not an issue, the long-term maintenance of keeping the insa-rest repo up-to-date would mean yet another tiny amount of open source burden.

Do you think you can commit to "mirror" the changes in the bvg-rest repo for the time being? (db-rest and vbb-rest are more confusing because they both have more custom logic.)

I'd be very willing to answer questions and make the process of getting another instance running more transparent, so that others can follow them in the future!