Preventing snapping to very small components

[jcoupey]

I have a question related to the snapping behavior encountered in the following situation: a one-way street leads to a highway that is flagged for construction so is (rightly) ignored for routing. The default behavior as shown below when using two locations that are snapped to the one-way "Rue Carnot" is to route withing that small component (see current debug view). This result in a route found or NoRoute depending on the start/end ordering:

Right order, route found

Wrong order, NoRoute

Now I definitely understand that if only one location snaps to that small component, then OSRM will reach to another (non-small) component for connectivity:

Of course one could argue that a one-way dead-end is a data problem. However in that situation, we probably should not expect a contributor marking one road as construction to also bother removing one-ways to adjacent streets just for routing purposes. In order to have a more robust behavior with regard to this kind of situation, I'd like to avoid the NoRoute scenario by avoiding snapping to this very small component.

Is there a way to make sure very small components are discarded altogether for snapping?

[DennisOSRM]

thanks for reporting. I have to re-acquaint myself with the snapping logic. At one point we had it that it wouldn't snap to the small components segment if that wouldn't yield a route.