Machine readable tour sharing for other apps

[gerion0]

Acknowledgments
Please check the following boxes with an x if they apply:

• The feature I want to propose would be useful for the majority of users, not only for me personally.
• I am aware that Transportr is mostly developed by one person in their unpaid spare time.
• I can help myself to get this feature implemented or know someone who wants to do it.
• If I want to add support for a new region or country, I checked that this is already available in public-transport-enabler and know the process described on the Transportr homepage.

Is your feature request related to a problem? Please describe.
Transportr (or Öffi) are really useful for train tour planing. KDE Itinerary is useful for full tour/vacation planning.
It would be nice to combine both apps, so that the tours from Transportr could be imported into KDE Itinerary.

However, the data generated for sharing a trip by Transportr (and Öffi) are human readable and not machine readable.

Describe the solution you'd like
The problem would be solved, if the data are machine readable.

Describe alternatives you've considered

• do not connect the apps and reimplement everything in KDE Itinerary.
• parse the human readable data and refetch the missing bits.

Additional context
The whole feature request is a follow up of this bug in KDE Itinerary.

I can think of a few more use cases for machine readable data with other apps:

• share and display a tour in a map program, with an extended detailed route (to walk or cycle) that is planned by the map program. Maybe the map program can even invoke Transportr to calculate the train bits of the route and take care of the rest.
• share the tour within a group chat and open/importing it in Transportr/Öffi on another smartphone again.

Maybe you like the idea. It would be meaningful, if the data are somehow standardized.

[gerion0]

Ping @vkrause (author of KDE Itinerary).

[ialokim]

If this is going to be approached someday, it might make sense to standardize something compatible to https://github.com/public-transport/friendly-public-transport-format