3 ms·
I don't think routing is that resource intensive, especially in transit setting where there are set number of stops (nodes) and the graph is fairly static - we
by alsodumb 2y ago
I don't think routing is that resource intensive, especially in transit setting where there are set number of stops (nodes) and the graph is fairly static - we can do tons of preprocessing and then routing queries would have minimal computational overhead.
- maelito 2y agoIt is. Especially to do multimodal routing offline. https://github.com/motis-project/motis/issues/423 https://github.com/motis-project/motis/issues/423
- alsodumb 2y agoThanks for sharing the link! Multimodal routing definitely changes the game, Imma go through the issue.
- denysvitali 2y agoI did implement an A* routing "offline" routing algorithm based on GTFS data + walking paths (OptiTravel) and built a GTFS server (to easily serve the data, do geospatial queries, ...) a few years ago. Granted that this was a university project, for some cities the calculation was rather intensive (e.g: London). I might be wrong though. [1]: https://github.com/denysvitali/optitravel https://github.com/denysvitali/optitravel [2]: https://github.com/denysvitali/gtfs-server https://github.com/denysvitali/gtfs-server
- dikkechill 2y agoCool projects! I actually had a look at you gtfs-server, to use Rust for processing GTFS files. Processing GTFS (basically large zipped text files) is quite resource intensive indeed, especially if you want to do it for the whole planet. What would you do differently now?