Martin

> You can't merge .osrm files. Yes, aware of that - would be a completely invalid binary as you suggest! To clarify, I'm dealing with a single .osrm file (that...

> A fingerprint errors means the data was prepared (osrm-extract, osrm-contract) with a different version and is likely not compatible. In general: osrm-extract, osrm-contract and your libosrm / osrm module...

> Maybe we should make this a bit more clear in the Readme. Thanks - that would be useful. I see it's currently at 5.4.1 so looks like I'm not...

According to https://github.com/Project-OSRM/osrm-backend/issues/4940#issuecomment-371180588: "We do not yet support NodeJS 9.x, please downgrade to 8.x LTS." So switch to Node.js 8: `nvm install 8 && nvm use 8` then retry.

> as for property '24' error, make sure your location variable in your index.js is inside your osrm network. Perhaps you've mixed up long/lat or just forgot to change it...

> I can't seem to find a description explaining what resolution should be or what units it's expressed as. The value is passed to the `turf-isolines` module here: https://github.com/Turfjs/turf/blob/v3.5.2/packages/turf-isolines/index.js#L20 where...

Benchmarking of routing performance will depend entirely what/which you're optimising for: - Network size (city vs continent) - Dynamic data (e.g. live traffic) - Number of routing output types, involving...

Duplicate of #257 - suggest this ticket be closed (and renamed...).

There is Galton: https://github.com/urbica/galton However, as noted in https://github.com/urbica/galton/issues/231 this works to 5.17.2 but will need some kind of adjustment for >5.17.2. Perhaps someone can add a patch to that?

@mjjbell > The main problem with implementation is the output is too accurate, it returns a traversal of all the boundary faces of the reachable area. The resultant output has...