Volker Krause

A new combined journey details view, ride sharing and support for new Apple Wallet pass formats - the past two months around #KDE Itinerary: https://volkerkrause.eu/2026/08/01/kde-itinerary-june-july-2026.html

Here's a few more details on what we discussed at last week's workshop on mapping indoor spaces in #OpenStreetMap, and why that level of detail matters: https://volkerkrause.eu/2026/07/18/osm-indoor-workshop-july-2026.html

At HTW Berlin in Schöneweide for working on tagging and modelling issues of indoor spaces in #OSM.

Some of this has proven challenging over the past years as it requires to carefully balance easy mapability and maintainability, the needs of 2D, 3D and tactile rendering, graph- and area-based routing, BIM compatibility, and being able to model all accessibility-relevant properties. Let's see if locking people from all those areas in a room for two days helps :)

Filling a few gaps in the location/positioning stack for #KDE and #Qt applications on #LinuxMobile: https://volkerkrause.eu/2026/06/27/kde-xdg-portal-location-api.html

An update on a whole bunch of recent work on Android platform support for #KDE applications, and what's about to change there: https://volkerkrause.eu/2026/06/13/kde-android-news-june-2026.html

#KeepAndroidOpen

Booking URLs, updated foundations for the Android packages, more detailed GBFS vehicle information - the past two months around #KDE Itinerary: https://volkerkrause.eu/2026/05/30/kde-itinerary-april-may-2026.html

A few more details on the organizational work around #OpenTransport2026 and #Transitous from last week's #FOSSGIS community meeting: https://volkerkrause.eu/2026/05/09/fossgis-community-meeting-may-2026.html

On the way back home from joining the @FOSSGISeV@mastodon.online Community Meeting at Linuxhotel in Essen for two days, for working on various organizational details for the @opentransport@en.osm.town conference.

We should be able to open the registration soon, later than originally anticipated but at least we wont have to run a 100+ attendee conference as a few individuals without a legal entity behind this anymore.

#OpenTransport2026

@zverik@en.osm.town I'd say this isn't even limited to flights but common to all (long distance) travel. Both multi-criteria routing algorithms and UIs for more manual control (e.g. @trans_europe_planner@fosstodon.org) are being looked into to help with that. Cost/availability is currently tricky to consider given the lack of open data. But e.g. optimizing uninterrupted sleep time on night trains could be possible. Either way, the first step is getting the basic schedule data in, all the above builds on top of that.

Experimenting with adding international flights to @transitous@en.osm.town. Performance seems to hold up and we indeed get working multi-modal door-to-door routing from e.g. Brussels to Tokyo.

There's a few issues with the router cheating around minimum transfer times that need to be sorted out before this could be deployed though.

AppStream-based in-app release notes, Android crash reporting, better popup notification configuration for Flatpak apps and many other things were discussed at last week's pre-#GLT26 #KDE sprint in Graz: https://volkerkrause.eu/2026/04/18/kde-sprint-linuxtage-graz-2026.html

Following 5 days of #KDE sprint at #TUGraz, #GLT26 is starting today. I'll be speaking about @transitous@en.osm.town tomorrow 15:15 in HS i7.

https://pretalx.linuxtage.at/glt26/talk/AJZHEG/

#OSM indoor mapping & routing, #Transitous, #KDE Itinerary, #OpenTransport2026 logistics, and dynamic traffic data - some notes from #FOSSGIS2026 - https://volkerkrause.eu/2026/04/04/osm-fossgis-conferenz-2026.html

@iinavpov@mastodon.online @transitous@en.osm.town I think the current default threshold is 15min, below that it should already at least include a direct walk in the results. Increasing that to 20min also works, a relative amount gets problematic on long distance trips though, 15% is enough to get a walk suggested for transferring between major railway stations in Paris for example, which is most likely not what you'd want on such a trip.

@iinavpov@mastodon.online At least with @transitous@en.osm.town we do have detailed control over such routing parameters/preferences, we still have to expose that in the user interface somehow though.

New welcome page, warnings about potentially unpleasant mistakes, and support for opentransportdata.swiss OJP 2.0 and train formation APIs - the past two months around #KDE Itinerary - https://volkerkrause.eu/2026/03/28/kde-itinerary-february-march-2026.html

On my way to #FOSSGIS2026. Tomorrow at 14:15 I'll host the Indoor OSM BoF together with Tobias Knerr in room BoF2, on Friday at 13:45 I'll talk about the work on OSM indoor routing for #KDE's Itinerary and Kongress apps in room HS3 (in German) - https://pretalx.com/fossgis2026/talk/CYW3VL/

Another small preparation for traveling to Switzerland for #OpenTransport2026: #KDE Itinerary now warns when leaving the EU roaming regulation area if you happen to live inside that.

In preparation for the #OpenTransport2026 conference #KDE's travel apps Itinerary and KTrip will support the Swiss OpenJourneyPlanner 2.0 and train formations APIs in the upcoming 26.04 release.

@frankgerhardt@mstdn.social Transitous hat auch einen Mastodon-Account: @transitous@en.osm.town

Ride sharing, meta stations and SIRI-FM realtime elevator data for #Transitous, and a few improvements for #KDE Itinerary - some of the things we worked on during the #OSM Hack Weekend at @geofabrik@en.osm.town in Karlsruhe last week: https://volkerkrause.eu/2026/02/28/osm-hack-weekend-karlsruhe-february-2026.html

Some impressions from the #KDE and #Transitous presence at #FOSDEM this year: https://volkerkrause.eu/2026/02/07/fosdem-2026.html

The #OSM Hack Weekend at @geofabrik@en.osm.town in Karlsruhe hasn't even started yet and my first agenda item is done already thanks to running into the right people on the way: A WFS/OGC layer for @foss_public_alert_server@floss.social.

At the #CAP Implementation Workshop two weeks ago this was presented as something so far only offered by a commercial entity, but it looks like we could provide this easily enough as well, a prototype was done in time for dinner.

@deathbydenim@mstdn.social Having this as part of the official protocol eventually would of course be much preferable. First step is figuring out what is possible and what makes sense though.

Live location support and room maps coming to #KDE's #Matrix client @neochat@kde.social: https://volkerkrause.eu/2023/06/24/matrix-neochat-location-sharing.html - powered by #OSM of course.