osrm-backend

There is an issue on their GitHub relating to customisable contraction hierarchies, but it doesn't seem to have gotten much interest. https://github.com/Project-OSRM/osrm-backend/issues/6574

Merged https://github.com/Project-OSRM/osrm-backend/pull/6923 :)

Two C++ projects I’m involved in that you might enjoy: https://github.com/systemed/tilemaker https://github.com/Project-OSRM/osrm-backend

> As a cyclist I’m almost always disappointed by google, apple, and Valhalla Have you tried the OSRM bike config? (The one you find in https://github.com/Project-OSRM/osrm-backend/blob/master/pro...)

OSRM can be augmented with your traffic data. https://github.com/Project-OSRM/osrm-backend/wiki/Traffic It works quite well.

If you track the vehicles every day and collect the location data, you can easily augment the Open Source Routing Machine to give you traffic accounted estimates.[0] Combined with some Kalman filters you'd get almost perfect estimates when live. Of course, this is for a use case where you have similar routes every day, this allows you to really tune the Kalman filters. 0: https://github.com/Project-OSRM/osrm-backend/wiki/Traffic

PSA: Open Source Routing Machine (OSRM) was largely abandoned by its maintainers. Several of us are working to reboot it, so if you enjoy map data and/or graph theory and have C++ skills, this would be a great project to work on. https://github.com/Project-OSRM/osrm-backend/ (Reboot discussion at https://github.com/Project-OSRM/osrm-backend/issues/5209)

> There's no way to optimize for minimizing left turns Any decent road routing engine does take into consideration a "turn penalty" and makes left turns more costly then right, among other things. E.g. see the Valhalla docs (Mapbox's routing engine): > Turn type - whether the turn is a left turn, right turn, or is crossing another road. The cost applied to the turn type also needs to know if driving is done on the left side or right side of the road. While left turns are generally more costly in the US than right turns, the opposite holds in UK. https://github.com/valhalla/valhalla/blob/716fd6e99ab6f271b6... OSRM also does this, but slightly differently: https://github.com/Project-OSRM/osrm-backend/wiki/Traffic#tu... --- With routing applications there are many configurable parameters, rather than providing too many options and risking ov

Daimler Autonomous Services | ONSITE, Full-Time | Berlin, Germany | VISA Sponsorship We are building AV-enabled routing and mapping capabilities to help ride-hailers and car manufacturers around the world shape the future of autonomous mobility. Together with Daimler's autonomous and vehicle teams our goal is not simply to get our customers from A to B but to get them there with the quality and safety they have come to expect from our brand. We are hiring for: * Backend - Node.js, Swagger/OpenAPI, k8s; to work on our services and the underlying infrastructure * Routing & Maps - Python, C++, Rust; to work on graphs, shortest path algorithms, machine maps / lane-level maps * Machine Learning - PyTorch, TensorFlow; to work on feature extraction, graph embeddings, traffic models, and demand prediction Some example projects our engineers have

Hi, We are trying to replace [Google Maps]( https://developers.google.com/maps/premium/) to use other alternatives like Mapbox, HERE in the future. However, we found that there are some Open Source Project like OSRM [1], Valhalla [2]. I would like to know what is your experiences with OpenStreetMaps as a backend for routing systems. If it is the case, would you please share your opinion and experience. [1]: https://github.com/Project-OSRM/osrm-backend [2]: https://github.com/valhalla

> For example, while Mapbox use open source (OSM) tiles, other services - e.g. their search API - aren't open, as Mapzen's is(/was). The geocoding engine[1] powering the Mapbox Search API is open source, and has been since its inception in 2012. The same is true of the routing engine[2] powering the Mapbox Directions API (OSRM), and the engine used to create Vector Tiles[3] for the Mapbox Maps API, along with the engines powering most Mapbox APIs. Non-open code at Mapbox is usually tightly coupled to our infrastructure or data processing pipelines, which would not be generally useful to the community at large. The useful bits of even this infrastructure code is also typically abstracted into generally useful libraries for community use, such as earcut[4], rasterio[5], tile-cover[6], and hundreds of other modules of all varieties. - [1]

This was a fun weekend project that I made because I will soon be moving and wanted to find some cool places to stop. Here's an example of the output (SF to LV): https://makemydrive.fun/directions/HipHummingbird. In case anyone is curious about how it works the source is available [1]. It is written in Go and it relies heavily on the amazing Open Source Routing Machine backend [2]. Would love any feedback on improvements on the design or code. [1]: https://github.com/schollz/makemydrivefun [2]: https://github.com/Project-OSRM/osrm-backend

OSRM is looking at improving this exact situation right now: https://github.com/Project-OSRM/osrm-backend/pull/2912

I'm paid to work on OSRM. Obviously the data is imperfect, and there are lots of edge cases (https://github.com/Project-OSRM/osrm-backend/issues/2145). But overall, it works pretty well. There are regional disagreements about the highway hierarchy (primary/secondary/tertiary/etc), but as long as the structure is locally consistent, you generally get the routing results you expect (routes tend to major arteries, etc). ETA calculation is a bit hit-and-miss, but the only way to correct this is to use real-world measurements. The great thing is that if you find something weird, you can just fix it. This happens overwhelmingly more often that people deliberately introducing errors.