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 classes, speed and weight. It's important for me to distinguish different geometries with really different data attached to them. The step lengths 300m and merge 3 segments of 200m, 80cm and 99m. The merge is occurring in the result only and the graph actually have the 3 independent geometries. Is there a threshold to set to prevent such a merge to occur at anytime please? All the best François Le lun. 27 août 2018 à 12:26, François Lacombe <fl.infosrese...@gmail.com> a écrit : > 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 process of the answer. > Can you explain why osrm doesn't give two steps for this particular case > please? > > The route : > https://imgur.com/a/LE3xIg3 > > The geometry : > https://imgur.com/a/O109GG4 > > Debug view : > https://imgur.com/a/IdXokbt > > The route service response, the first step should stop at point 6 : > First step actually stops at the end of D999 road. > https://imgur.com/a/IdXokb > > I can give any more detail if needed, all the best > > François Lacombe >
_______________________________________________ OSRM-talk mailing list OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk
