@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.

@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 😎 🚀