Osr vs Brouter

[laem]

Hi, after reading the readme, I'm wondering how this project compares to brouter. Brouter is specialised on bike profiles, but the principles look similar. Sorry if it's not, I'm just a re-user of routers, I haven't delved into their internals :)

[felixguendling]

I think the main difference is the scope. Brouter doesn't seem to target walking, wheelchair, multi-level indoor routing, and car routing. Besides that, OSR uses only a fraction of the RAM other routers use. Our focus is on 1:N and N:1 routing performance to enable calculating shortest paths from the start coordinate to all public transport stops or for the last mile from all public transport stops to the destination coordinate. OSR also can combine profiles like driving to a parking place and walking to the train platform in one go while optimizing not just the path but also the parking place choice (what the parking module did previously in MOTIS). Or what we're currently working on: walking to a e-scooter/shared bike, driving with it (respecting no-go zones), parking it (again respecting no-go zones) and then walking to the bus stop or train platform (while optimizing also which scooter to take and where to park). We're planning to add support for an elevation profile, live traffic, speed it up with A* or bidirectional A*, etc. etc. - it has a lot of potential! 😄 🚀