search

Project-OSRM / osrm-backend

Open Source Routing Machine - C++ backend
http://map.project-osrm.org
BSD 2-Clause "Simplified" License
6.42k stars 3.4k forks source link

Avoiding barrerier, foot, yes #7010

Closed hup333 closed 2 months ago

hup333 commented 3 months ago

OSRM avoiding the barrerier It set to foot, yes

image image image

https://www.openstreetmap.org/directions?engine=graphhopper_foot&route=46.5308%2C22.7005%3B46.5303%2C22.7023#map=19/46.53062/22.70148

Start 46.53083, 22.70050 End 46.53031, 22.70232

jcoupey commented 3 months ago

TL;DR the expected route should be provided using the default foot profile.

Long version: the demo server runs a modified version of the foot profile. The blacklist logic from the default profile is replaced by a white list logic, and lift_gate (the value for barrier tag here) is not in the white list.

Now since you just added foot=yes to that node, the next data update on the demo server should hit this check and route across the barrier all right due to the new tag.

Maybe worth adding lift_gate to barrier_whitelist in the demo profile though, what do you think @datendelphin?

hup333 commented 3 months ago

If the road or path, are set to acces, all, or foot yes And the barrerier missing the tag Should are it being avoided?

jcoupey commented 2 months ago

This is now fixed in the demo server due to the data change. A similar situation elsewhere would actually not be a problem with this repo, but rather with the specific setup from the demo server profile. Worth opening a ticket over there if you think lift_gate should be added to barrier_whitelist in the demo profile.