3 ms·
My day job is OpenTripPlanner work, so I absolutely love to see this. I've long thought about what a RAPTOR engine would look like written in Rust. So cool that
by danielhep 2y ago
My day job is OpenTripPlanner work, so I absolutely love to see this. I've long thought about what a RAPTOR engine would look like written in Rust. So cool that you've done it. You should share this in the OTP Gitter chat if you haven't already, the people there would love to see it. I wonder if this would be small enough to run on a phone? I have thought about offline trip planning on a phone, but running OTP is out of the question as a graph can be gigabytes and take minutes to load.
- ellenhp 2y agoIt's after midnight here so take this with a grain of salt but the generated timetable for the puget sound is taking up about 40 MiB on-disk and the server process is using 100k of RAM I think. Most of the timetable is zero-copy so it can be memory mapped on a platform that supports it. So yes, I think it would run on a phone. See also mobroute, which powers Transito https://git.sr.ht/~mil/mobroute https://git.sr.ht/~mil/mobroute https://git.sr.ht/~mil/transito https://git.sr.ht/~mil/transito
- MaBu 2y agoI'm not sure how they do it, but Rail planner app for interrail has fully offline train planner. https://www.eurail.com/en/plan-your-trip/rail-planner-app https://www.eurail.com/en/plan-your-trip/rail-planner-app