mod_mbtiles VS Open Source Routing Machine (OSRM)

Here's a little bit of code I wrote that lets you host from a normal webserver, where that "normal webserver" is Apache: https://github.com/systemed/mod_mbtiles

This is great. Servers have been the weak link in the open mbtiles stack for a good while and an out-of-the-box recipe like this will make a real difference.

(For those running on bare metal, I knocked this up a few months ago - https://github.com/systemed/mod_mbtiles - which is an Apache module that does pretty much the same thing.)

then called the Open Streetmap api described here using Power query: https://github.com/Project-OSRM/osrm-backend/blob/master/docs/http.md

OSRM: A super fast and easy to use routing engine that runs on OSM data. You only need to run 5 lines of code to (1) download a .pbf from Geofabrik, (2-5) download the OSRM docker image and pre-process the OSM data. There are also 3 profiles predefined that you can use: car, bike, foot (e.g. foot.lua). It basically hosts a local server. I find the easiest way is to combine it with the osrm R package. I have seen you also need to adjust for the elevation. I think I have seen some custom LUA profiles that also account for DTM derived elevation changes as an additional weight.

I am trying (and failing) to setup an OSRM instance with docker compose. The issue I've encountered is with setting up osrm-backend. According to the Github and Docker Hub pages, the process is as follows:

I am creating Rust bindings to https://github.com/Project-OSRM/osrm-backend using autocxx. This allows for fast routing on openstreetmap data. They have a nodejs server, but I'm going to write a Rust one with these new bindings. I am finding that many of the config classes in C++ are't Plain-Old-Data structures, so are opaque structs, so I have to write getters and setters in C++.

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

This is a 30 second exercise on OSRM, or any other service that provides directions.

As for the rules for routing algorithms, OSMR's foot profile looks like good place to start. You could copy the file into something like for_women.lua and extend it with rules for e.g. street lighting and any other features of interest. Of course, it would be best to reach out to the other devs first.

I'm trying to calculate walking distances using OSM and OSRM but this results in distance matrices that violate triangle inequality. This is a pretty bad issue for the spatial models I'm building. I was wondering whether there are alternatives to OSRM that guarantee that triangle inequality is respected. Mostly, I really don't care about the routing algorithm looking at red lights, whether streets are one or two way streets, private roads, etc. I just need the distance along pathways between points.