No routes to/from some buildings in local area

[recallfx]

No routes to/from some buildings in local area:

54.696679, 25.282320
54.696381, 25.276880
54.696605, 25.282459
54.696747, 25.282652

Any point outside of these buildings will find a route.

One example:
http://map.project-osrm.org/?hl=en&loc=54.698357,25.276936&loc=54.696369,25.276902&z=16&center=54.697739,25.275722&alt=0&df=0&re=0&ly=763558683

What could be the cause of this behavior?

[emiltin]

The reason is that the service road inside the building is inaccessible due to oneway settings and barriers (gates).
A solution for this is planned, see #930.

[DennisOSRM]

The purple line on the map marks the spot, which is way https://www.openstreetmap.org/way/25488986:

It carries the access=yes tag which is wrong as this doesn't imply that the way is accessible to the general public but that it can be accessed with all modes of travel (car, bike, foot, ..). Generally speaking, the issue will fix itself with the next update cycle once the faulty access tag is removed.

[emiltin]

ï think it might be this way: https://www.openstreetmap.org/way/191672944

[DennisOSRM]

Actually, both. 👍

[recallfx]

I found actual issue - gates. If point is closer to the access road that has a gate, it will not calculate any other route.

[emiltin]

yes, as i wrote initially :-) due to barriers (gates) the service way is inaccessible.

[emiltin]

the question is - should gates be whitelisted?

[recallfx]

If we are traveling by car, then gates should not be white listed, but at least it should point to nearest viable point. So this is duplicate of #930 .

[DennisOSRM]

No, barrier=gate should not be white listed. If it is always accessible, it should be tagged as such by adding the previously mentioned access=yes tag to the node.

[emiltin]

makes sense