Hi,
Regarding the situation below, I've upgraded to v5.19.0 to try to get a
more descriptive response from osrm-routed.
Classes has been added to ways and differ at the point where steps are
expected to split.
Nevertheless I still get a single step merging 3 different ways with
different
Hi all,
I recently find a situation where OSRM/route service doesn't make
distinction between two different geometries of my routing graph.
I get a single step as a combination of both geometries despite they
haven't the same speed nor the same name attribute. Then I'm not able to
make a good
