Felix Gündling

We're getting closer to the next #MOTIS release 😎

The next version will display stops on the map. The "highest" mode (high speed, long distance, local trains, metro, subway, trams, buses) will be used for the stop icon. Clicking on the stop will show its departure times.

I hope this feature will help with orientation when searching for the next bus stop :-)

The next #MOTIS version will have leg alternatives! 😎

So in case the transfer is a bit tight or if you prefer another mode of transport, you can click on the alternative and the MOTIS UI will update the journey. This includes potentially a different walk/bike/car/etc. ride from/to another stop at the start/destination. So it's also a way to explore more options to start/finish your journey.

Alternatives respect query settings like bike carriage, allowed modes, wheelchair compatibility, etc.

@VolkerKrause@floss.social did a great presentation giving a good overview about @transitous@en.osm.town on Grazer Linuxtage 🤩
https://media.ccc.de/v/glt26-679-transitous-free-and-open-public-transport-routing

Maybe we also find a way to generate public transport predictions based on opentrafficmap.org which also was presented in Graz 🎉
https://media.ccc.de/v/glt26-688-c-its-mit-einem-esp32-ampeln-straenbahnen-und-autos-tracken

@Jbb@social.tchncs.de @mapterhorn@mastodon.social @transitous@en.osm.town the proxied option would have advantages in case Cloudflare would stop hosting Mapterhorn. Pointing our own URL to something new (self-hosted maybe) would be easy. But since MOTIS works without hillshading, maybe we don’t need this emergency plan for now :)

@Jbb@social.tchncs.de @mapterhorn@mastodon.social @transitous@en.osm.town that could be one option. But since it’s off by default (also for bandwidth reasons) I wouldn’t be too concerned to release it without the reverse proxy. But also setting up a proxy shouldn’t be hard. The PR is merged now in MOTIS but we can update the URL to the proxied one once its set up.

@Jbb@social.tchncs.de @mapterhorn@mastodon.social @transitous@en.osm.town

• for https://test.motis-project.org pmtiles hosted by Cloudflare
• any objections regarding privacy? Cloudflare doesn't get/set cookies for those requests but will see user IPs/Referer/User-Agent/etc if the layer is enabled (off by default).
• we could potentially self-host the planet pmtiles file which goes up to zoom level 12 (656.90 GiB)
• the complete dump is 9.8 TiB which is more disk than we have available on Transitous servers atm
• PR https://github.com/motis-project/motis/pull/1359

Shoutout to @mapterhorn@mastodon.social for those nice terrain tiles. Hill shading looks really nice in the #MOTIS UI!

I hope, we'll have this soon on @transitous@en.osm.town 😎

@maeool@mastodon.social Nice! 🎉 🚀 Those are newly computed shapes? Was it fast? :)

If you experience memory problems, you can try to lower the memory usage by running it with less threads: set timetable.route_shapes.n_threads to a lower value

You can also configure to keep the shape cache even if the OSM data changes. @transitous@en.osm.town will do this during the week and recompute shapes only 1x/week on Sunday. This way, the import should be fast and smooth.

@maeool@mastodon.social On our server, it takes ~2.5h to recompute every single shape in the dataset (all setting). For production, we keep existing shapes (missing setting) which makes it even faster because datasets like FlixBus already come with shapes.

Routing speedups for osr (like Contraction Hierarchies) will likely translate to even faster shape computation 😎 🚀

@maeool@mastodon.social We couldn't build on Pfaedle because in @Transitous experiments we couldn't make it work for planet-scale processing on the hardware we have. One option would've been to cut out extracts using OverpassTurbo, but since it puts heavy load on the Overpass server, we would've needed to host our own instance which comes with its own complexities and hardware requirements. Since we needed extra features like caching and had the efficient osr routing model anyway, it was easier to start there.

#MOTIS v2.9 is out! 🎉 🤩

Highlights include:

We now have the option to compute shapes (exact line geometry) on import. Before, buses would sometimes pass through buildings on the map if the #GTFS dataset doesn't provide shapes. Now, everything (buses, trains, etc.) is routed based on OSM data. The development was supported by MOBIDROM 🙏

#MOTIS also gained initial support for OJP now, Europe's standardized API for journey planners.

SIRI-FM for elevator status updates is also available now 😎

#MOTIS just got support for SIRI-FM (FM = Facility Monitoring)! 😎

This means #Transitous will gain real-time updates for elevators for indoor and public transport transfer routing with the next MOTIS release! 🎉 🎉

On the screenshots you see how the routing finds a way around the blocked elevator (yellow dots = working elevator, pink dots = blocked elevator) in Berlin main station with the wheelchair routing profile 👩‍🦽‍➡️

Thanks to @mfdz@chaos.social for providing the DIID vs OSM matching table 🙏