#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 😎
Hi @felixguendling, that's awesome ! Using Pfaedl I guess ?
What about performance though ? Do you have benchmark showing the compilation cost in hours of this new feature, with and without ?
@maeool 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 😎 🚀
@felixguendling thanks a lot ! That was my fear : I couldn't make Pfaedle work on France neither.
So I should try your implementation some day. Thanks for the great work
@maeool 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 will do this during the week and recompute shapes only 1x/week on Sunday. This way, the import should be fast and smooth.
@felixguendling @transitous no, no, we're not using shapes yet. These are given by the local authority.
We have lots of things to fix first before going on this subject.
Felix Gündling
maeool
