- how do we handle vendor api keys?
- privacy concerns?
- are the vendor terms and conditions compatible with FOSS/KDE and/or our use-case?
- are there sources we don't know yet that already have this aggregated for a larger number of vendors?
- how does the publictransport plasmoid do this?
- is there any other existing work in this area we could get inspiration from?
Description
Description
Comment Actions
I looked into this some time ago. I think https://transportr.app/ handles it in some cases, trough their own server, that uses https://www.navitia.io/ (a data aggregator, from what I can see).
I think they use their own open source server, which has the API keys.
If going this route as well, it would be nice to provide others with an access to the API, and perform some caching server-side. Maybe the transportr server could be used as well?
Comment Actions
Yep, for trains this looks like a very promising approach, already talking to the people behind navitia.io :)
Something similar for flights would be nice too though.