Real-time transport data in KDE Itinerary
Last year KDE Itinerary was presented at Akademy for the first time, striving to build a privacy-protecting alternative to digital travel assistance features. Teaming up with the Open Transport community since then has paved the way for real-time transportation data access. What data is available, how is it used in KDE Itinerary, and what else can we use it for?
While KDE Itinerary had access to personal booking information (via its own extraction engine) and static information (via Wikidata), access to real-time or transient information such as delays, gate or platform changes, or service disruptions was still missing a year ago. Today, such information are available via the KPublicTransport framework.
In this talk we will look at the system KPublicTransport is based up-on, the Free Software and Open Data service Navitia which aggregates public transport data provided by hundreds of operators around the world, as well as how KPublicTransport makes this information available to application developers.
Besides the already listed kinds of information, KPublicTransport also provides journey query capabilities. That is, determining how to get from A to B using public transport services. And while we of course will see how this is used by KDE Itinerary for more assistance features, this is equally interesting for applications targeting a commuter use-case for example (such as a possible resurrection or successor of the KDE4-era public transport Plasmoid).
While several brave test subjects managed to do quite a few tests^Wtrips with KDE Itinerary already, there is a remaining risk of the author failing to show up due to highly experimental support for Milan's local transport system.