Harald Kliems wrote: > Until then you could consider a user setting to avoid/not avoid > unpaved roads.
Unfortunately contraction hierarchies - the routing algorithm used by OSRM - don't really allow user settings. For each distinct routing profile, you need to regenerate the routing graph, which takes (many) hours and requires (many) GB of RAM both to route and to host. cycle.travel penalises surface types variably: surface=mud gets a big penalty, surface=gravel not so much. cheers Richard -- View this message in context: http://gis.19327.n5.nabble.com/cycle-travel-US-bike-routing-and-unreviewed-rural-TIGER-tp5848084p5848600.html Sent from the USA mailing list archive at Nabble.com. _______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us