Routing engine gets stuck on one way dead ends

[dnathe4th]

In generating some random points to route between in San Francisco on my local OSRM instance I happened upon a coordinate pair which I could not route from: { lat: 37.77733389282893, lng: -122.41769518579345 }

By chance this point lands next to a parking garage with two disconnected oneway roads, an entrance and an exit -

Unfortunately I was next to the one way entrance; the routing engine will not route from this point because the node it snaps to (the oneway entrance) has no paths that connect it to the rest of the graph of the city.

Nudging the point over slightly puts me on the oneway exit, which can be routed from as expected -

While this is a nuanced example, I would imaging it might not be a terribly uncommon one. An immediate possible solution seem to be to recognize the node snapped to from a point is a dead end and to expand the search for nodes to snap to until a sufficiently-connected one is found, although I am not versed in the codebase and would leave that up for discussion.

[emiltin]

i believe this is covered by #930?

[DennisOSRM]

Thanks @dnathe4th for reporting this.

@emiltin
Right, closing here in favor of #930.

[dnathe4th]

Ah thanks guys, didn't scroll back far enough on the issues list. Will track #930 instead